ci(release): revert to force pushing release tag #3380
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
Since we're only pushing a tag, this shouldn't delete commits Even if someone adds commits in the meantime, we still want to move the release tag to the commit we have just pushed. Without this change, we'll see a "rejected stale info" error in CI
ev-codes
changed the title
|
Git push to origin failed for release/8.3 with exitcode 1 |
|
Git push to origin failed for release/8.4 with exitcode 1 |
|
Git push to origin failed for release/8.5 with exitcode 1 |
sbuettner
pushed a commit
that referenced
this pull request
Sep 30, 2024
Since we're only pushing a tag, this shouldn't delete commits Even if someone adds commits in the meantime, we still want to move the release tag to the commit we have just pushed. Without this change, we'll see a "rejected stale info" error in CI (cherry picked from commit da79706)
|
Successfully created backport PR for |
ev-codes
added a commit
that referenced
this pull request
Sep 30, 2024
Since we're only pushing a tag, this shouldn't delete commits Even if someone adds commits in the meantime, we still want to move the release tag to the commit we have just pushed. Without this change, we'll see a "rejected stale info" error in CI (cherry picked from commit da79706)
ev-codes
added a commit
that referenced
this pull request
Sep 30, 2024
Since we're only pushing a tag, this shouldn't delete commits Even if someone adds commits in the meantime, we still want to move the release tag to the commit we have just pushed. Without this change, we'll see a "rejected stale info" error in CI (cherry picked from commit da79706) Co-authored-by: Ev <ev.bilske@camunda.com>
ev-codes
added a commit
that referenced
this pull request
Sep 30, 2024
Since we're only pushing a tag, this shouldn't delete commits Even if someone adds commits in the meantime, we still want to move the release tag to the commit we have just pushed. Without this change, we'll see a "rejected stale info" error in CI (cherry picked from commit da79706)
ev-codes
added a commit
that referenced
this pull request
Sep 30, 2024
Since we're only pushing a tag, this shouldn't delete commits Even if someone adds commits in the meantime, we still want to move the release tag to the commit we have just pushed. Without this change, we'll see a "rejected stale info" error in CI (cherry picked from commit da79706)
ev-codes
added a commit
that referenced
this pull request
Sep 30, 2024
Since we're only pushing a tag, this shouldn't delete commits Even if someone adds commits in the meantime, we still want to move the release tag to the commit we have just pushed. Without this change, we'll see a "rejected stale info" error in CI (cherry picked from commit da79706)
ev-codes
added a commit
that referenced
this pull request
Sep 30, 2024
Since we're only pushing a tag, this shouldn't delete commits Even if someone adds commits in the meantime, we still want to move the release tag to the commit we have just pushed. Without this change, we'll see a "rejected stale info" error in CI (cherry picked from commit da79706)
ev-codes
added a commit
that referenced
this pull request
Sep 30, 2024
Since we're only pushing a tag, this shouldn't delete commits Even if someone adds commits in the meantime, we still want to move the release tag to the commit we have just pushed. Without this change, we'll see a "rejected stale info" error in CI (cherry picked from commit da79706)
ev-codes
added a commit
that referenced
this pull request
Sep 30, 2024
Since we're only pushing a tag, this shouldn't delete commits Even if someone adds commits in the meantime, we still want to move the release tag to the commit we have just pushed. Without this change, we'll see a "rejected stale info" error in CI (cherry picked from commit da79706)
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.
Description
Since we're only pushing a tag, this shouldn't delete commits
Even if someone adds commits in the meantime, we still want to move the release tag to the commit we have just pushed.
Without this change, we'll see a "rejected stale info" error in CI
Related issues
related https://github.com/camunda/team-connectors/issues/763
Checklist
no milestonelabel.