un-ts / un-ts/changesets-gitlab
Publishing a Docker image
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 129
- Forks
- 44
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 12
Description
How would one go about publishing a Docker image after a changeset MR has been completed?
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 repository's GitLab CI and changeset workflow to determine how a Docker image should be published after a changeset merge request completes. Document the relevant workflow entry point and the steps that confirm the image was published successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab
- Domain
- devops, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100