You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
I push a commit to a branch. This invokes atlantis plan. I realize I made a mistake and push a second commit to the same branch. This invokes atlantis plan again, but the second invcation fails with
the default workspace at path . is currently locked by another command that is running for this pull request.\nWait until the previous command is complete and try again
Describe the solution you'd like
Atlantis should detect when the lock is held by the same PR that got the new commit. If that's the case, Atlantis should cancel the prior plan and start a new plan on the latest commit.
Describe the drawbacks of your solution
More complexity in the codebase.
Describe alternatives you've considered
Wait and invoke plan again once the old plan has finished.
The text was updated successfully, but these errors were encountered:
Community Note
Describe the user story
I push a commit to a branch. This invokes atlantis plan. I realize I made a mistake and push a second commit to the same branch. This invokes atlantis plan again, but the second invcation fails with
Describe the solution you'd like
Atlantis should detect when the lock is held by the same PR that got the new commit. If that's the case, Atlantis should cancel the prior plan and start a new plan on the latest commit.
Describe the drawbacks of your solution
More complexity in the codebase.
Describe alternatives you've considered
Wait and invoke plan again once the old plan has finished.
The text was updated successfully, but these errors were encountered: