gravitational / gravitational/shared-workflows
Run tests for ./libs on when there are changes
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 4
- Avg merge
- 19h 53m
- Merged PRs (30d)
- 5
Description
We currently don't run tests when there are changes in ./libs, also tagging seems manual which can be incorporated into GHA
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 by inspecting the repository's GitHub Actions workflows and how changes under ./libs are currently handled. Determine the existing test and tagging steps; done means library changes trigger the appropriate tests and tagging is incorporated into GHA rather than handled manually.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100