node-unicode / node-unicode/node-unicode-data
Please tag releases -- like you already do for the resulting packages!
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 154
- Forks
- 18
- Avg merge
- 9h 48m
- Merged PRs (30d)
- 3
Description
I asked for tagged releases four years ago, and was told it would be a bother -- but since then I see the bootstrap.sh script does tagged releases for the resulting packages, it woud in fact be a one-liner to also tag this source repository.
Notice that the current bootstrap.sh mentions the v1.2.0 in two places -- it should probably be slightly modified so the number is set in one place and used in both (and, for this issue: thrice!)
Thanks!
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 with bootstrap.sh and inspect the two places where v1.2.0 is currently written, along with the existing package-tagging flow. Consolidate the version value so it can also drive a source-repository tag; done means the release process creates all intended tags without repeating the version number.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100