sameersbn / sameersbn/docker-gitlab
Improving the Release Cycle
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi there,
first of all thanks for this great repository. it has a big benifit for me with all that preconfigured fancy features , it is easy maintainable and the big benifit - it saves work for me and others.
but i have an important question...
how can we acclerate the release cycle?
many updates are tagged from the gitlab organisation as security-issue and asap.
unfortunately, it always takes a few days until these updates are entered here in this repository.
i want to help and not fork the repo into an own managed repo.
e.g.
these important pull-requests hangs for 4days ...
https://github.com/sameersbn/docker-gitlab/pull/1675
best regards
matthias
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 reviewing pull request #1675 and the repository's existing release workflow. The issue does not name files, tests, or a specific implementation; work would be complete only after maintainers agree on and document a faster process for incorporating urgent GitLab security updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git, gitlab, shell
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100