NASA-AMMOS / NASA-AMMOS/3DTilesRendererJS
Automate release
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 2.5k
- Forks
- 416
- Avg merge
- 17h 52m
- Merged PRs (30d)
- 37
Description
Would there be any interest in automating the release process?
That way whenever something is merged to master, we know it is getting released right away.
Thanks!
Contributor guide
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
The issue names no files, tests, or release entry point. Start by mapping the current release process and the workflow for changes merged to master, then clarify the expected release trigger and verification steps. Done should mean that an approved merge reliably produces the intended release.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100