theupdateframework / theupdateframework/specification
chore: draft branch notoriously lagging behind
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 405
- Forks
- 59
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 1
Description
We've done a good job at automating most of the release management rules. One chore that remains to be done manually, and, as a consequence, is usually forgotten, is:
Merges with 'master' must be followed by a rebase of 'draft' onto 'master'.
Let's find a better (automatied) way to keep draft in-sync with master.
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 linked release management rules and the repository's existing automation around merges to master. Determine how draft is currently updated and define a verifiable workflow in which draft is automatically rebased or otherwise kept in sync after each relevant merge; the issue names no files or tests.
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
- Mostly clear
- Newbie friendliness
- 35/100