Working with reusables hurts
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11
- Forks
- 25
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 3
Description
To test a change to a GHA in our actions repo one usually makes a fork but to use that fork one must:
- change all paths to use the fork instead of our actions repo
- add the changes to the fork
- make a pr to test said changes
- if it fails one must start from 2 again because rerunning an action does not pick up the latest changes so a new change to the pr needs to be made as well
this is very time consuming and horrible.
We should see if there is another way. Might be good to talk with someone from github about this too
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
No files, tests, or entry points are named. Start by documenting the current fork, path-rewriting, pull-request, and rerun workflow described in the issue, then review GitHub Actions reusable-workflow behavior and possible alternatives. Done requires a concrete, agreed approach that avoids repeating the fork and pull-request cycle, with implementation scope identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100