Centralise GitHub actions code
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
Using the new composite GitHub actions (https://github.blog/changelog/2020-08-07-github-actions-composite-run-steps/) we can presumably combine and centralise many of the current GitHub action scripts that we currently use. If we don't version them, then this gives an easy way to update them.
Maybe not suitable for all workflows, but could be good for the more generic stuff like checking the PR target branch.
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 by inventorying the current GitHub Actions workflows and identifying the generic steps, especially checks for the pull request target branch. Compare which workflows could use composite actions and which should remain separate. Done means the agreed reusable actions are centralized and the affected workflows still perform their existing checks, but the issue does not define the exact scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100