release: a dispatch from a non-main ref pushes that ref to main and tags it
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start by reading release.yml, especially its workflow_dispatch configuration and the git push origin HEAD:main command at line 84. Check how the dispatched ref reaches the job and how the suggested ref guard would prevent the release steps from running. Done means a dispatch from any ref other than main exits before pushing or tagging.
Written by the indexing model from the issue text.
Description
Why it matters
release.yml is workflow_dispatch with no ref guard. It checks out the dispatched ref, commits CITATION.cff, runs git push origin HEAD:main (line 84) and tags HEAD. Dispatching it from any other branch would fast-forward main to that branch and tag it. The obvious candidate is the bot's own thumbs/<month> branch, which is main plus an unreviewed commit. A mis-click in the Actions UI would ship that content.
Suggested approach
Add if: github.ref == 'refs/heads/main' to the job, or build the CITATION commit on a fresh checkout of origin/main regardless of the dispatched ref. (Related: #137 tracks running the first release.)
Done when
A dispatch from any ref other than main exits before pushing or tagging.
- Dominant language
- JavaScript
- Stars
- 58
- Forks
- 15
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 TMHSDigital/Free-Game-Dev-Assets
-
documentation priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
TMHSDigital/Free-Game-Dev-Assets#178 ·
Maintainers usually reply within 1 day
-
enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
TMHSDigital/Free-Game-Dev-Assets#176 ·
Maintainers usually reply within 1 day
-
copy: headline and README badge count 418 including 2 deprecated entries; the catalog shows 416Openbug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
TMHSDigital/Free-Game-Dev-Assets#175 ·
Maintainers usually reply within 1 day
-
enhancement priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
TMHSDigital/Free-Game-Dev-Assets#174 ·
Maintainers usually reply within 1 day
-
hardening priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
TMHSDigital/Free-Game-Dev-Assets#169 ·
Maintainers usually reply within 1 day
All issues in TMHSDigital/Free-Game-Dev-Assets
Similar issues
-
bug confirmed js v6
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
BUG
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
linuxmint/cinnamon-spices-applets#9223 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
fastify/fastify-swagger-ui#299 ·