-
Notifications
You must be signed in to change notification settings - Fork 12
CI: Add a CI workflow that tests downstream packages #109
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
Conversation
|
Nice. We want RegistryCI too here, right? |
Good call. I've added it. |
195bbf4 to
a714ccf
Compare
9380a26 to
a3cdd94
Compare
a3cdd94 to
9011e60
Compare
|
Alright, I think this is all set now. We currently test against Registrator.jl, RegistryCI.jl, and LocalRegistry.jl. Any other downstream packages we want to add? |
|
It looks like it does what it should but I have no competence to review GitHub actions. |
|
Maybe I can recruit someone to review the GitHub Actions details. @giordano maybe? |
It should be fine to `Pkg.activate()` with a trailing slash. Co-authored-by: Mosè Giordano <[email protected]>
Co-authored-by: Mosè Giordano <[email protected]>
|
Thank you @giordano!! |
|
@GunnarFarneback Shall we give this a go? |
|
Bump? |
Currently, we test the following downstream packages:
And we can easily add more.
The motivation here is to catch breakages (example GunnarFarneback/LocalRegistry.jl#99) sooner.