platisd / platisd/bad-commit-message-blocker
Retrieve proper commitish for comparison from forked repos in PRs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 31m
- Merged PRs (30d)
- 1
Description
The current action implementation assumes that commits are always coming from the upstream repository but in reality, they don't, in the case of forks.
Context: https://github.com/cherrypy/cheroot/pull/401#issuecomment-1003351474.
This needs to be fixed here: https://github.com/platisd/bad-commit-message-blocker/blob/master/entrypoint.sh#L14.
Action items:
- Check the GitHub Actions docs to figure out the variable that exposes this information
- Use that to send a PR
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
Start with entrypoint.sh at line 14 and consult the GitHub Actions documentation for the value that identifies the proper commitish for pull requests from forks. Confirm that the action uses that value when comparing commits, then prepare the requested pull request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions, shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100