Automatically create release tags on git
- Dominant language
- PHP
- Stars
- 156
- Forks
- 72
- Avg merge
- 12h 43m
- Merged PRs (30d)
- 203
Description
For every prod deployment, it would be cool to have a matching git tag on the deployed commit, in the same style as manual configured tags:
[PROD-2025-06-10](https://github.com/ecamp/ecamp3/releases/tag/PROD-2025-06-10)
[PROD-2025-04-13-II](https://github.com/ecamp/ecamp3/releases/tag/PROD-2025-04-13-II)
[PROD-2025-04-13](https://github.com/ecamp/ecamp3/releases/tag/PROD-2025-04-13)
[PROD-2025-04-12](https://github.com/ecamp/ecamp3/releases/tag/PROD-2025-04-12)
[PROD-2025-03-18](https://github.com/ecamp/ecamp3/releases/tag/PROD-2025-03-18)
...
It is highly unusual to have multiple releases a day, and if so, we can append roman numerals.
As we only have at max around 12 deployments a year, it won't clutter as much.
Contributor guide
Research direction
Start by locating the production deployment configuration and the existing process for manual release tags. Confirm how deployed commits are identified and how release names are generated; done means each production deployment receives a matching tag, with a defined suffix for multiple deployments on one day.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100