Allow pushing to another branch / manually pushing
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- git, javascript
- Domain
- release
Research direction
Start by tracing the plugin's existing commit and push behavior and its configuration entry points. Determine how to support selecting a target branch or suppressing the push while still creating the release commit. Done means either workflow can create the commit and then allow the user to open and merge a PR manually.
Written by the indexing model from the issue text.
Description
Due to the way GitHub Actions work, it's currently impossible to use this plugin on a branch that has required status checks. Hopefully this will change, but in the meantime it would be useful if we could control the pushing more granularly.
Specifically what I would like to do to work around the GHA limitations is to:
- cut the new release
- push the resulting commit to a new branch
- open a PR
- use mergify to auto-merge it back in.
The problem is that I can't easily do step 2, because this package has no configuration (at least none that I could find) to control the pushing of the commit. It would be useful if there was a setting to either control which branch gets pushed to, or, even better, just a setting to say "don't push". That way the commit could be made automatically, but then we have to deal with it manually afterwards, which allows for much finer control.
- Dominant language
- JavaScript
- Stars
- 339
- Forks
- 75
- Avg merge
- 5h 15m
- Merged PRs (30d)
- 6
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.
More from semantic-release/git
-
semantic-release
Difficulty 3/5 1-2 days Newbie friendliness 35/100
semantic-release/git#584 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
semantic-release/git#536 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
semantic-release/git#532 · 3 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 28/100
semantic-release/git#531 · 1 comment ·
-
Dependencies upgrade Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
semantic-release/git#529 · 2 comments ·
All issues in semantic-release/git
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·