Skip to content
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

Auto-update ViperServer submodule #539

Merged
merged 2 commits into from
Oct 4, 2022
Merged

Auto-update ViperServer submodule #539

merged 2 commits into from
Oct 4, 2022

Conversation

ArquintL
Copy link
Member

@ArquintL ArquintL commented Oct 4, 2022

No description provided.

@ArquintL ArquintL requested a review from jcp19 October 4, 2022 14:08
@jcp19
Copy link
Contributor

jcp19 commented Oct 4, 2022

I'm a bit on the fence about having this by default. On one hand, its it nice to not have to do it by hand 90% of the time. On the other, we often decide to postpone updating to the latest Viper release because it may break some important assumption that Gobra (and SCION) rely on.

@jcp19
Copy link
Contributor

jcp19 commented Oct 4, 2022

Maybe the best option is for the bot to open the PR automatically but wait for one of us to merge it

@ArquintL ArquintL merged commit ebe1d8f into master Oct 4, 2022
@ArquintL ArquintL deleted the update-submodules branch October 4, 2022 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants