Displaying 2 results from an estimated 2 matches for "check_suite_id".
2019 Nov 12
8
RFC: Using GitHub Actions for CI testing on the release/* branches
...unless there are any
strong objections, I would like to get this enabled by Mon Nov 18, to maximize its
usefulness. Let me know what you think.
Thanks,
Tom
[1] https://github.com/features/actions
[2] https://github.com/tstellar/llvm-project/commit/952d80e8509ecc95797b2ddbf1af40abad2dcf4e/checks?check_suite_id=305765621
[3] https://github.com/tstellar/llvm-project/commit/6d74f1b81632ef081dffa1e0c0434f47d4954423/checks?check_suite_id=303074176
[4] https://github.com/tstellar/actions
2020 Jan 15
0
Github action build for CMake and AutoMake
...le build software. More than 40 million people use GitHub to discover, fork, and contribute to over 100 million projects.
github.com
I attached the patch to get it building and I am already building it on my fork:
https://github.com/xnorpx/opus/commit/a6a7bf81e155b267159d86a76fc84ffc2c14c100/checks?check_suite_id=402591586
It will build desktop flavors of CMake and also build the same configurations as TRAVIS-CI builds with AutoMake.
So my proposal is to remove the Travis-CI build and replace with github actions instead.
Work is based on this example: https://cristianadam.eu/20191222/using-github-actions...