semantic-release should not commit to master
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
Research direction
Locate the semantic-release configuration and release workflow; start by tracing how the publish step currently updates master and how CI is triggered. Done means releases use a release branch, open a PR containing the changelog changes, and CI ignores that PR.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
At the moment, when semantic release is doing the publish step, it includes the changelog.
However, it also commits the changelog, and pushes this commit to master. Since master should be a protected branch, this presents some challenges that force us to loosen the rules, and to put powerful tokens in sketchy places.
Describe the solution you'd like
semantic-release should do everything on a release branch, opening a PR with the results instead of pushing them directly to master. This PR should be ignored by CI.
Describe alternatives you've considered
I've tried nothing and I'm all out of ideas.
Additional context
Perfection is the goal here ladies & non ladies.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 etclabscore/pristine-typescript
-
Add 'pristine' topicOpentriage
Difficulty 1/5 Under an hour Newbie friendliness 35/100
All issues in etclabscore/pristine-typescript
Similar issues
-
cdx-audit output written to a pipe is cut off at 64 KiBMay be free again A pull request for this issue was closed without being merged. Openbug mode:cli
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Build produces empty forge.min.js: package.json lists "forge" instead of "node-forge"Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fei2411/DeepSeek-Bot#963 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Miaotofu01/Study-Mate#244 ·
Maintainers usually reply within 1 day
-
test-reliability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Azure/azure-sdk-for-js#40672 · 1 reaction ·
Maintainers usually reply within 1 day