semantic-release / semantic-release/gitlab
Add the option to specify the target project via project id
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 344
- Forks
- 89
- Avg merge
- 16h 11m
- Merged PRs (30d)
- 4
Description
My main repo is in bitbucket, and the CI/CD runs there in a bitbucket pipelines, but my client has it's own git repo which mirrors mine, and when I "release" a new version, I just push into their GitLab.
When semantic-release runs in my bitbucket pipeline, I am pushing to my client's GitLab using this custom plugin I wrote: https://github.com/tomerh2001/semantic-release-gitlab-merge-request, but then I also want to create a GitLab release right after
Their gitlab is hosted at a specific URL, and the target project has a different ID then the one the CI runs in, so it would be great if we could specify a target project ID (and possibly the branch from the target) for the release
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 names no files or tests; start by tracing the GitLab release configuration and the current-project lookup. Confirm the supported target-project setting and whether branch selection is included, then add coverage showing that a release is created for the requested target project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100