GitLab Runner
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24
- Forks
- 15
- Avg merge
- 10d 3h
- Merged PRs (30d)
- 1
Description
What would you like to see added?
In docs document the existence of a "publicly-available" GitLab runner (be cautious about what that means and the exact phrasing). Document how to find and use the runner in the GitLab web interface. Consider both individual projects, and groups.
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
The issue does not name a file or test. Start by locating the repository's relevant documentation page and navigation, then verify how a runner is found and used in the GitLab web interface for both individual projects and groups. Done means the documentation explains the runner's availability with careful wording and covers both scopes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab
- Domain
- ci-cd, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100