[#1310] Airy CLI sha changes after the release #1443
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pascal-holy
force-pushed
the
feature/1310-airy-cli-sha-changes-after-the-release
branch
from
864928f
to
77d60a4
Compare
pascal-holy
force-pushed
the
feature/1310-airy-cli-sha-changes-after-the-release
branch
from
fbb680a
to
080f0b4
Compare
pascal-holy
force-pushed
the
feature/1310-airy-cli-sha-changes-after-the-release
branch
from
f11d88a
to
c19af61
Compare
lucapette
approved these changes
Apr 7, 2021
pascal-holy
deleted the
feature/1310-airy-cli-sha-changes-after-the-release
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think that should solve it. I at least remember one instance where I accidentally pushed to the release branch after the release and that caused the last commit sha to change and therefore the sha of the cli binary