semantic-release / semantic-release/git
Pushing to another repository than the current?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 339
- Forks
- 75
- Avg merge
- 5h 15m
- Merged PRs (30d)
- 6
Description
With a gitops approach, it is common to have a an application repo and a separate gitops repo.
It would be very helpful if I could use this plugin in the common way (update and commit release related files in the current repo), but also push some files (e.g. an updated helm values.yaml file) to another repo.
would that be possible today?
If not, would the maintainers see this in scope for the current plugin, or would it better be part of a separate, new plugin?
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 by reviewing how the plugin currently updates and commits release-related files in the current repository, then compare that with the requested gitops repository and helm values.yaml flow. Done would require an agreed scope and an implementation path for pushing selected files to another repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, helm, javascript
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100