self-managed GitLab CI pipeline
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.2k
- Forks
- 1.8k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 6
Description
Hello guys Emanuele here from Arkage team tech.
After seeing the "GitLab with Vercel" guide I created the gitlab-ci.yml, created the vercel cli project and added to gitlab the required variables BUT,
when I try to push something to some branch or merge a pull request to the main branch nothing happens. Do we have some logs in order to fix these problems? Anyone has facing the same issue?
Thanks,
Emanuele
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
Start with the referenced gitlab-ci.yml and the GitLab project variables, then inspect pipeline and job logs for a branch push and a merge into main. Done means the intended events trigger the pipeline and the cause of the current failure is identified and resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab
- Domain
- ci-cd, cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100