-
Notifications
You must be signed in to change notification settings - Fork 30
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
TODO: Figure out how to automerge JLL packages #6
Comments
@staticfloat So, I think I have an idea for how to automerge JLL packages. It will not require you to make any changes to your PR titles or your workflows in general. I'll put a prototype together, will keep you posted. |
I'm just about to get to this; (I've been chewing through other things over the past two weeks) What do you think about this, it would be something much more similar to what Registrator creates:
Because we don't have JLL package restrictions on version numbers, it seems like we don't need to worry about new vs. updated packages, so we don't need to worry about different titles or anything like that. |
I think that the second line of the body should look like this, right? I.e. there is a
|
Why not just use registrator instead of reinventing the wheel? |
Internally, much of this is using |
@staticfloat pinged me on Slack that everything is set on their end, so we need to implement JLL automerging on our end. Unfortunately I am swamped right now and won’t have the time to work on this anytime soon. @fredrikekre @staticfloat would either of you have time to add JLL automerging to RegistryCI? Basically need to check if it’s a JLL package, and if so exempt it from the version number and compat bounds requirements. If not, I’ll try to work on it when I have the time.... realistically speaking, that might not be until next year 😬 |
…_registryci-1.5.3 Update RegistryCI.jl by updating the .ci/Manifest.toml file (1.5.3)
No description provided.
The text was updated successfully, but these errors were encountered: