-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: run tests on push to dev
, main
and all PRs
#77
base: dev
Are you sure you want to change the base?
Conversation
@@ -1,6 +1,12 @@ | |||
name: tests | |||
|
|||
on: push | |||
on: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think is better to run tests on every branch. We may have checks that prevent merges to master when tests fail but I think is better to know if they are failing in any other PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m not sure I follow. This PR setup runs tests/checks on PRs targeting main
and direct pushes to it. Are you suggesting we should also run tests on:
- PRs targeting any branch?
- Any commit pushed to any branch?
If that’s the case, there could be some downsides to consider:
- Duplicate test runs
- Increased resource usage
More notifications (added noise)not applicable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, the problem is when developing an epic (the PRs would target a branch different from dev
or master
). I would let the rule to:
- Target any push in
dev
ormain
- Target any PR no matter the branch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
dev
, main
and all PRs
✨🧪✨