Ripping out GitLab CI
- Dominant language
- Haskell
- Stars
- 1.7k
- Forks
- 750
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 28
Description
Now that GitHub has been used to do one major release (3.16), the countdown has started for dropping GitLab.
My assumption is that GitLab has to stick around until 3.14 stops being updated. It was the last major version released from GitLab.
Can someone tell me when that might be?
*This question brought to you by yet more failures on GitLab pipelines due to garbage-collected runner images*
Contributor guide
Research direction
The issue names GitLab pipelines and the GitHub-based 3.16 release, but no files, tests, or entry points. First confirm when 3.14 stops receiving updates, then compare the GitLab CI configuration with the current GitHub release process. Done means a maintainer-approved plan for removing GitLab without disrupting supported releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, haskell
- Domain
- ci-cd, devops, release
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100