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
Currently, when "Release PR" runs, it checks if a PR exists and otherwise skips the creation step. We should create a new PR if a release PR has been created but then closed.
The text was updated successfully, but these errors were encountered:
pwtyler
changed the title
Create a new PR if a previous release PR has been previously closed
Create a new PR if a previous release PR has been closed
Jun 6, 2023
The case here is if a pre-release PR was created and then closed. It is my current thought that a new PR should be created, but it could be argued that the existing PR should be re-opened.
pwtyler
changed the title
Create a new PR if a previous release PR has been closed
Create a new PR if a previous release PR exists but has been closed
Dec 22, 2023
pwtyler
transferred this issue from pantheon-systems/plugin-pipeline-example
Dec 22, 2023
Currently, when "Release PR" runs, it checks if a PR exists and otherwise skips the creation step. We should create a new PR if a release PR has been created but then closed.
The text was updated successfully, but these errors were encountered: