-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
Implement Continuous Integration Using GitHub Actions #1709
base: master
Are you sure you want to change the base?
Conversation
04a0f68
to
bb3e1f8
Compare
89333e9
to
8300294
Compare
This is ready for review, it seems to work well. Please take a look and let me know what you think. |
Oh, great! Thank you 👍 Is it possible to enable/test it without pushing it on master? |
It have been doing some testing on my fork here https://github.com/dylanmtaylor/scrcpy/actions |
b2858ce
to
28f9877
Compare
28f9877
to
0e773a1
Compare
I squashed those commits to make it a cleaner merge. |
OK, thank you. 👍 Sorry, I currently don't have much time to work on scrcpy. I'd like to investigate the checkstyle issue too. But don't worry, I didn't forget, and I have it in mind 😉 |
Just asking. Is it necessary to use docker container to build the project? As far as I have seen, installing packages in GHA does not take too much time. |
Docker makes the build more reproducible, and you can run in the same container locally as on the CI system, where you cannot easily reproduce the GitHub actions virtual machine. |
This pull request leverages GitHub Actions to automatically build scrcpy on every commit or pull request.