Skip to content
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

Fix the duplicate GitHub Actions #820

Merged
merged 1 commit into from
Apr 20, 2022

Conversation

directionless
Copy link
Contributor

I noticed that we were running twice the number of GitHub actions as expected. I believe this is because both the push and the pull_request triggers were active. This shifts them so the push is only on the main branches

I noticed that we were running twice the number of GitHub actions as expected. I believe this is because both the `push` and the `pull_request` triggers were active. This shifts them so the `push` is only on the main branches
@directionless directionless merged commit 64e8019 into kolide:master Apr 20, 2022
@directionless directionless deleted the seph/workflows branch April 20, 2022 13:46
@@ -2,7 +2,7 @@ name: ci

on:
push:
branches: '**'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@directionless , this means now CI will only run in my forked repo when I push to a main or master branch ... do we loose anything by having it the way it was?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was causing two sets of tests to run on the PRs. One triggered for the push, and one triggered for the PR.

For my branches, I usually push to a draft PR. But maybe there's a way we can get the best of both worlds. I wonder if we can specify fork names or something

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants