CI Improvements
#2136
Replies: 3 comments 1 reply
-
+1 for everything |
Beta Was this translation helpful? Give feedback.
0 replies
-
Ideally, I'd like to be able to specify what I want to test, perhaps, just checker or code style |
Beta Was this translation helpful? Give feedback.
1 reply
-
I'm going to merge #2134 so we can build atop that. Will be fun to see the CI only partially run as commits are added (ex: tweaking GitHub Actions to only run checkstyle once shouldn't fire the AppVeyor). |
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
-
Couple things I've been thinking about are:
@v1
tags. This one can go either way as using tags allow you to stay on top of security fixes, but you risk the tags changing if the repository itself gets compromised. There's also a stability issue though that's less of a concern if the action repo follows semver.Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions