-
Notifications
You must be signed in to change notification settings - Fork 20
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: github action workflow #76
Conversation
@ChaelCodes okay this will fix the problem with CI, I added some double-quotes and add the pry gem if you don't want them, I can remove it, should I? BTW, it would be nice if you add the hacktoberfest label to this PR, hahaha LOL. |
Double quotes and pry are fine. I think this is setup to only run CI on new pull requests and pushes to main. |
Also, the Hacktoberfest label is on the repo, so all PRs approved or merged should apply! I'm happy to add a Hacktoberfest label and tag all your PRs with it though, for an extra level of security. |
And I think it's what we want, didn't it? Run the CI when somebody opens a PR and when it’s merged to the main branch it will run again. |
I think it would be better if it ran whenever they pushed to their branch, so they could get to a green build. |
this will work as you expect, let me push again with a failing test just to confirm. |
the one which is failing it's because it takes the |
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'd really like for the line limiting checks to pushes to main to be removed.
Especially since we can't test the CI on this PR, and we're hoping that it does what we want to forked repo PRs.
.github/workflows/check.yml
Outdated
push: | ||
branches: [main] |
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 happy to add the pull_request key, but I don't want to limit CI to pushes to main.
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.
updated 🤖
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.
Let's try this out, and see if it works.
it seems like it works well, 👍 |
No description provided.