Make CI testing more robust
Open
enhancement
- Dominant language
- JavaScript
- Stars
- 226
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
The current GitHub actions do not test whether the PR would break `develop` after being merged. If this repo is anticipated to see more activity, we should add testing for that condition.
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the repository's GitHub Actions configuration and how pull requests target develop. Determine how CI can test the post-merge state described in the issue, then validate the workflow with a representative pull request. Done means CI detects changes that would break develop after merging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100