translate-tools / translate-tools/core
Publish builds to a repository or on releases page
Open
Nobody has claimed this yet.
documentation
enhancement
- Dominant language
- TypeScript
- Stars
- 90
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
We should to proof NPM package contains original files with no changes. So let's start publish builds for each new release
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the package's build and release configuration to determine how builds are produced and where release artifacts can be published. Confirm how a new release is created and how package contents can be compared with the original files. Done means each new release publishes its builds and the package contents are verified as unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100