GitLab CI external status for Gitpod
Open
Nobody has claimed this yet.
meta: never-stale
type: feature request
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
It would be great if Gitpod could comment or create an external status for GitLab MRs
Here is how Vercel does it 😄
/cc @gtsiolis 🏀 @dnsmichi 🦊
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
The issue names GitLab merge requests and GitLab CI, and shows Vercel as a reference. Start by reviewing GitLab's external status and MR comment capabilities, then determine whether the intended result is a comment, an external status, or both. Done should include an agreed behavior and working Gitpod integration, but no implementation files or tests are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab
- Domain
- ci-cd, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100