-
-
Notifications
You must be signed in to change notification settings - Fork 145
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
Add options for [skip-ci], [skip-editor-ci], and [skip-package-ci] on PR #109
Conversation
Allow skipping tests when not required, for example, when only making changes to MD files.
Allow skipping tests when not required, for example, when only making changes to MD files.
Allow for one set of tests to be skipped, while still testing the other
Allow for one set of tests to be skipped, while still testing the other
- Updated job names to better align the actions being performed during them
- Format step names
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.
This looks great to me. And also love that this can cut down on the many tests that are created for every single PR. And lets us be a little nicer to GitHub's servers.
The only thing I'd recommend is, either adding it to this PR, or additionally opening a PR on our website, or really somewhere to add the documentation about this.
Maybe we even just add it to the PR template?
@confused-Techie Added PR pulsar-edit/.github#54 to coincide |
@pulsar-edit/core Can we have someone else review this 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.
It always amazes me how many commits do we need to fix CI things, because CI's syntaxes are always quite crazy :D
Anyway, LGTM
Allow skipping tests when not required, for example, when only making changes to MD files.
The conditions are only set up to skip during the
pull_request
event. What that means in practice, is that the workflows will still execute when you merge a PR, regardless of whether the title starts with one of the 3 options above