-
Notifications
You must be signed in to change notification settings - Fork 146
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 github CI, fix cmake test definition #152
base: master
Are you sure you want to change the base?
Conversation
This is borrowed/stolen from @ClausKlein's commit
Let me know if you want the history on this cleaned up. I'm expecting this to be squash-merged into your repo. |
@jaredgrubb any chance of getting this merged? |
I haven't used GitHub CI before .. how will this appear once merged? |
@jaredgrubb You get a checkmark next to a verified commit, You can inspect the build and logs for set amount of time theyre available, in the build it's pretty standard, You get step rundown with logs and success/failures. Every Pull Request will have CI rundown for each new update. Here's a short introduction video. |
So once we merge this, it'll just kick in? or is there further setup that I'll need to do? Thanks for the idea on this! |
Yes, on pushes and pull-requests to master branch, this will automatically
trigger and run a regression, reporting results.
Eric
…On Thu, May 19, 2022, 3:04 PM Jared Grubb ***@***.***> wrote:
So once we merge this, it'll just kick in? or is there further setup that
I'll need to do?
Thanks for the idea on this!
—
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAPDCCAO3JALODU5VEQI3VK23GPANCNFSM5RXVJRNA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This looks like a great idea and a good implementation to me. |
This pull request adds github CI support so master and branches can be regressed automatically against existing tests.