Allow pinning GitHub provider of compose to a specific tag
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Current "on tag" behavior makes it hard to find out what tag current container is using and unable to pin to a specific tag.
Describe the solution you'd like
Allow pinning GitHub provider of compose to a specific tag
Describe alternatives you've considered
Use release branches like release/v1.0.0 and release/v1.0.1 and pin to a specific branch. But this is not best practice, because a release shouldn't be modifiable, but a branch can be re-pushed again. Releases should use tags.
Additional context
No response
Will you send a PR to implement it?
No
Contributor guide
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 locating the TypeScript compose deployment code that handles the GitHub provider and current “on tag” behavior. Trace how the provider selects its ref, then define done as allowing a specific tag to be selected and used consistently; the issue names no files or tests, so those will need to be identified first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, github, typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100