-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
Change GitHub Actions Workflow Triggers #127
Conversation
@@ -2,7 +2,6 @@ | |||
|
|||
on: | |||
- pull_request | |||
- push |
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.
@drupol do you want these to run in master
as well, after a merge?
Currently we have them set up like that but I don't know if it was intentional or not: https://github.com/loophp/collection/actions?query=branch%3Amaster
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 don't think it's necessary. All the changes happening in this project should be committed through PRs and not directly in the master branch, so... it will be tested in PRs. WDYT ?
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.
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.
Fair enough, let's not modify these.
.github/workflows/tests.yml
Outdated
push: | ||
branches: | ||
- master | ||
pull_request: |
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 decided to keep it on the safe side so this means it runs:
- on pull requests
- on pushes but only to the
master
branch (effectively after merging a PR as well)
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.
The indentation has been changed... and it was not supposed to.
Based on the .editorconfig
, the indentation is 4 spaces.
If you're using VSCode or VSCodium with the .editorconfig
plugin, do: SHIFT+CTRL+i
to reformat the file correctly.
Nice, thanks for that I wasn't using the |
Merci :) |
This PR looks to solve workflows triggering multiple times on PRs.