Add go-infra tool to manage our branches
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
It's complicated to add release branches (and other types of branches). I wrote a doc about how to manage a release branch fork, and it splits into three ways to handle it based on the situation, and in some cases, shows bash scripts to copy-paste and modify to get through some situations: https://github.com/microsoft/go/tree/microsoft/main/eng/doc/branches.
We should have a tool that helps determine which state we're in and runs through the steps.
Related, we could really use a better way than manual work to get infra fixes onto our existing release branches, so we can reliably maintain each one properly once they're set up:
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 reading eng/doc/branches, including its three release-branch cases and the bash scripts described there; also review related issue #145 for the infra-fix maintenance concern. Done means a go-infra tool can determine the applicable branch state and run the documented steps instead of requiring the manual process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, go
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100