Add build flow doc (from upstream Go commit to MCR image)
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
We should have a doc that goes through all the builds/PRs that happen during a sync from upstream, all the way to images ending up on MCR.
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 mapping the builds and pull requests involved in a sync from an upstream Go commit through to images published on MCR. The work is done when a document covers that full flow clearly, including the intermediate build and PR steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100