Adapt production branch names to 1ES standards
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
Production pipelines can only be triggered from production branches, as per this doc: https://eng.ms/docs/cloud-ai-platform/devdiv/one-engineering-system-1es/1es-docs/1es-pipeline-templates/features/releasepipelines/release-features/release-gating#branch-validation-1es-pt.
Production branches are autodetected by inspecting the name, which should follow an standard pattern. We currently name our production branches following the microsoft/release-branch.go* pattern, which is not in the official list.
https://github.com/microsoft/go/pull/1522 added a configuration file to the repo so that 1ES detects our release branches as production branches.
We should consider adopting the official naming convention instead of using our own.
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
Review the linked 1ES branch-validation documentation and the configuration file added by PR #1522. Compare the current microsoft/release-branch.go* pattern with the official convention, then determine the branch and configuration changes needed and verify that production pipelines recognize the resulting branches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100