Investigate a good testing story for testing github workflow change
Open
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
Currently, we do not have a good way to test github workflow change. We always have to merge it in order to test it. We need to investigate a good test story for this.
Some related work that we may want to look into:
https://dev.to/byteslash/how-to-test-your-github-actions-locally-3830
https://github.com/nektos/act
Contributor guide
Research direction
No files or tests are named. Start by reviewing the linked article and nektos/act to compare ways of testing GitHub workflow changes locally; done would be a documented, validated testing approach for this repository.
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