rajbos / rajbos/github-actions-requests
Check for action repository redirects
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Some repositories have been renamed and GitHub handles both the new name and the old name: the old one just gets redirected. See for example the Snyk actions:
Old name: https://github.com/snyk/snyk-actions
New name: https://github.com/snyk/actions
We don't see that and fork over the new name (probably because of the API gives us that). But loading the action from the issue still gives us the old name. This ends in errors since the fork was made with the new name, but we try to inject the CodeQL workflow with the old repository name :-(.
- Check if the name is different in the
find-action-name(check the GetRepo result) and if so, use the new name
Contributor 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.
Research direction
Start in the find-action-name entry point and inspect the GetRepo result for the action repository. Confirm that the redirected repository name is retained when the fork is created and when the CodeQL workflow is injected; done means the workflow uses the new repository name for renamed actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100