-
Notifications
You must be signed in to change notification settings - Fork 25
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #7 from terrateamio/pro-578-fix-apply-after-merge-…
…workflow PRO-578 FIX Apply-after-merge workflow when the PR is not the last to…
- Loading branch information
Showing
4 changed files
with
112 additions
and
54 deletions.
There are no files selected for viewing
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,16 +1,7 @@ | ||
# Could not run operation | ||
# Operation Canceled | ||
|
||
## Why? | ||
## Why did this happen? | ||
This pull request was already merged, and another pull request was merged between the initiation of this operation and when the action was executed. To ensure accuracy, Terrateam cancels the operation if changes occur during this window. | ||
|
||
This pull request is merged and another pull request has been merged after this pull request. In order to avoid drift, Terrateam runs all operations against the most recent contents of a branch. Because a pull request has been merged after this pull request, this pull request is not the most recent contents of the destination branch and Terrateam cannot run any operations against this pull request. | ||
|
||
## What to do next? | ||
|
||
The recommended action is to revert this change, then create a new pull request and plan and apply it. | ||
|
||
## What to do in the future? | ||
|
||
In order to avoid this, it is recommended to do one of the following: | ||
|
||
1. If you wish to have an apply-after-merge workflow, enable `autoapply`. Terrateam will apply any changes immediately after merge. See the [documentation](https://terrateam.io/docs/advanced-workflows/apply-after-merge/) for how to enable `autoapply`. | ||
2. Use an apply-before-merge workflow. This is the most robust because an apply may fail for a variety of reasons. An apply-before-merge workflow gives the most flexibility. | ||
## What should you do? | ||
Initiate the operation again via a GitHub comment. Terrateam will perform the operation against the most recent commit of the destination branch (HEAD). |