popcodeorg / popcodeorg/popcode
Push tag to GitHub after deployment
Open
Nobody has claimed this yet.
deployment
- Dominant language
- JavaScript
- Stars
- 191
- Forks
- 143
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 5
Description
It’s a good practice to tag each deployment, and keep those tags synced to GitHub. This should happen automatically as part of the deployment process.
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
The issue names only the deployment process and GitHub, with no files, tests, or entry points. Start by locating how deployments are performed and where deployment completion is handled; done means each deployment automatically creates and pushes its tag to GitHub.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100