-
Notifications
You must be signed in to change notification settings - Fork 55
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
Always run eamxx workflows on PRs #3100
Conversation
0420238
to
d2e869b
Compare
d2e869b
to
096ef56
Compare
97f5d30
to
a4f4a42
Compare
c06fed2
to
add709c
Compare
add709c
to
e415048
Compare
3193196
to
9b551ab
Compare
b376a57
to
22692a5
Compare
fda2ea8
to
5da234f
Compare
* Remove check-skip-labels action * For each eamxx workflow * Run a "pre-process" jobs on ubuntu-latest to - retrieve labels - check touched files Then, add skip logic to other jobs to avoid running unnecessarily if certain labels are found or touched files are irrelevant
5da234f
to
9b3ae78
Compare
@mahf708 I think the current version is the best I could do. It does the job, and we may even use it down the road to avoid starting the jobs if the triggering user does not have the necessary permissions. The down side (super minor) is that we add an extra check to the PR for each workflow. |
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.
🎉
Jobs can be skipped if paths touched are non-eamxx, but at least they will appear on PR checks. This makes branch protection rules easier to implement, since we can set eamxx checks as REQUIRED (since they will always be there)