-
Notifications
You must be signed in to change notification settings - Fork 13
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
Improve workflow for updating slice subtree #3584
Comments
If we want to keep the icerpc-slice history we just need to preserve the merge commit created by git subtree pull. As long as we preserve the merge commits it should be fine, Here the workflow action is too restrictive, to avoid accidentally squashing the changes (which is the default for our PRs) and screwing the slice history. |
@pepone Some of our previous subtree commits have nice commit messages:
Our later ones seem to just look like regular run-of-the-mill merge commits.
Any idea what the difference is here that causes different messages? The first one is much more informative. |
The first one is for |
Can we use |
No, you use add only to add the initial subtree, and then you just use pull to upgrade it. |
slice/
in a commit. A PR can have multiple commits that change other files. Not sure how doable this is.Originally posted by @externl in #3583 (comment)
The text was updated successfully, but these errors were encountered: