Can't find commit when triggering on release publish
See original GitHub issueWhen working on a pipeline that is triggered by a release publish:
on:
release:
types: [ published ]
I get the following error:
Unable to get commit from workflow event: trying with the GitHub API...
Error: Request failed with status code 404
at createError (/home/runner/work/_actions/EndBug/add-and-commit/v4.4.0/lib/index.js:1:428)
at settle (/home/runner/work/_actions/EndBug/add-and-commit/v4.4.0/lib/index.js:1:31578)
It seems like the latest changes have broken this functionality. I pinned the library to v4.3.0 and was able to run successfully.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Github Action trigger on release not working on tag
Just creating a git tag is not enough. In short git tag is not the event that triggers a GitHub Release event.
Read more >Frequently Asked Questions - semantic-release
Yes, every commits that contains [skip release] or [release skip] in their message will be excluded from the commit analysis and won't participate...
Read more >Release triggers - Azure Pipelines - Microsoft Learn
A release will be triggered only if the Git push contains a commit on the specified branch. For example, selecting main will trigger...
Read more >Git Hooks | Atlassian Git Tutorial
It's possible to use post-commit to trigger a local continuous integration system, but most of the time you'll want to be doing this...
Read more >How to Publish a Python Package from GitHub Actions
Manually-created releases still trigger the GitHub Actions workflow ... don't need to create and push a git commit in order to do a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry, I haven’t had a chance to test it, and since it’s on production for something that’s rarely changed, I probably won’t have the opportunity for a while. Thanks for looking into it!
This issue is being marked as “stale” because it has been open 20 days with no activity. Remove the “stale” label or comment, otherwise this will be closed in 5 days.