Add lucky-commit support to embed version in commit hash on release
Open
Nobody has claimed this yet.
mergebot
- Dominant language
- Python
- Stars
- 159
- Forks
- 156
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 16
Description
Since b0b609ebe7faf7b105b86b5551d81e71b6f902d0 moved stagings & freezes to being performed locally it's possible to run a vectorised SHA search against the repo
Issues:
- only works with hex prefix, so not entirely general-purpose (but works with odoo versions e.g.
0d00181) - lucky-commit always runs against HEAD which makes it a bit annoying to use in bare repos (although HEAD can absolutely be manipulated via
git symbolic-ref)
Also needs to be installed on the machine, but not available in debian.
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 local staging and freeze flow introduced by commit b0b609ebe7faf7b105b86b5551d81e71b6f902d0, then examine how release versions are currently handled. Determine the scope for supporting lucky-commit, including hex-prefix searches and operation in bare repositories; done should embed the version in the release commit hash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100