Run template generation during go-images sync from upstream
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
Right now, we sync changes from upstream to e.g. the template file, but the template doesn't get applied until the next Go build update. The sync PR should also re-evaluate the templates for our Microsoft-side Dockerfiles, so CI catches issues ASAP.
We also must do this in order to add this test to go-images CI (or else the sync PRs would get blocked very often):
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 tracing the upstream sync workflow, then inspect the template file and the Microsoft-side Dockerfiles it generates. Review the test requested in microsoft/go#290 and verify that sync PRs re-evaluate the templates so Go-images CI catches template issues immediately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100