Replies: 4 comments 1 reply
-
I think the CI actions can be configured to run on push to main. Something like:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
I'm fine with doing that as long as we don't run out of free minutes. |
Beta Was this translation helpful? Give feedback.
1 reply
-
More detailed example on this page: https://docs.github.com/en/actions/examples/using-scripts-to-test-your-code-on-a-runner. |
Beta Was this translation helpful? Give feedback.
0 replies
-
As this is now implemented, closing. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Most github repositories show a check when the current contents of main pass the ci tests. Currently ours does not. Perhaps it is because the CI actions do not run on on push, only on pull requests. I like not having redundant runs on each push to a branch and then on the PR from that branch, but I would not mind having the (admittedly slightly redundant) check on main. Is there a way to configure Github actions so that the tests will run after each merge to main and then be shown on the github home page for the repo? If so, would we want to do that?
Beta Was this translation helpful? Give feedback.
All reactions