easystats / easystats/workflows
Reduce workflows on main
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 9
- Forks
- 3
- Avg merge
- 5h 51m
- Merged PRs (30d)
- 4
Description
Given that we usually create PRs before changes enter the main branch, wouldn't it be enough to just run a few checks on push/main, and run all checks only on pull-request/main?
I'd suggest for push/main:
- pkgdown
- win-devel (or release?)
- ubuntu-devel (or release?)
- maybe some more, probably one check-hard-ubuntu-devel?
And for PR/main, all the above checks plus the remaining ones (lintr, HTML, all examples, ...).
This would save some resources.
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
Review the existing workflow definitions for push/main and pull-request/main, then compare the checks listed in the issue, including pkgdown, win-devel, ubuntu-devel, lintr, HTML, and examples. Confirm the intended split and validate that push/main runs only the selected checks while pull-request/main retains the complete set without reducing required coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, r
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100