semantic-release / semantic-release/git
Feature request: make push optional
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 339
- Forks
- 75
- Avg merge
- 5h 15m
- Merged PRs (30d)
- 6
Description
Problem
I'm trying to use semantic-release with semantic-release-monorepo to automate release process of Terraform modules in monorepo hosted on Azure DevOps. I've got the solution working in most cases, except when I merge a PR that changes multiple modules at the same time. The first module to run thought semantic-release to the end pushes changes to remote repository and next module is failing with: "The local branch main is behind the remote one, therefore a new version won't be published."
Solution
Configure automation for every individual module to only commit changes locally but not push them to remote repository until all modules are processed and all changes accumulated in the local repository. After that do one push for all changes at once.
Issue
It seems like git plugin for semantic-release cannot be configured to skip the push after commit. This all happens in the same processing step.
I understand that my use case is pretty unique, but I think making push optional defaulting to true is also not a huge change.
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
No files or tests are named. Start by locating the git plugin's commit and push processing and its configuration handling, then inspect existing tests for that flow. Done means a configuration option can skip the push while retaining the current default behavior, with coverage for both enabled and skipped pushes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript, terraform
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100