Replies: 4 comments 3 replies
-
Hi, thanks for the suggestion! Currently, running
I believe that this is enough to give you a hint that a PR already exists and that, in most cases, you can just do a I'm not sure if |
Beta Was this translation helpful? Give feedback.
-
How about a flag? I have an action that creates a PR automatically from an issue, and the branch is named after the issue. I imagine this is a very common use case, so not having to write the code to check that the PR exists and conditionally creating it would be good to have. |
Beta Was this translation helpful? Give feedback.
-
Hey guys.
And It's works. |
Beta Was this translation helpful? Give feedback.
-
I have to create multible prs. But these Workarounds just working with one pr. I have feature1 -> main, feature1 -> staging and feature1 -> develop. I think a flag might be the cleaner solution. A flag that overwrites the existing pr instead sending an error. |
Beta Was this translation helpful? Give feedback.
-
At this moment if you run
gh pr create
twice, it will attempt to create a new pull request, even if one already existing.It would be much better if
gh pr create
will instead update a pull request if already existing and outdated, aka by runninggit push
.gh
is already able to detect existing pr as we can see by running a command likegh pr ready
.Having a default
create-or-update
would enable us to use gh more ways (including scripting!) and increase productivity.This would make the command a little bit more idempotent, as it will ensure that a PR is active and updated at the end.
Beta Was this translation helpful? Give feedback.
All reactions