Scheduled actions raise duplicate PRs about create-pull-request HOT 9 CLOSED

Awesome! Again, thank you for your work here!

from create-pull-request.

So it's best to delete the branch after you merge or close the PR.

I hadn't thought about that. I'll be sure to do that. I may even set branches to be automatically cleaned up.

from create-pull-request.

I'm facing a similar use case.
Maybe try branch-suffix: none for the start. That should prevent the duplicate PRs.

from create-pull-request.

@jacobtomlinson I think your use case fits Strategy B - Create and update a pull request branch.

As @matfax suggested, if branch-suffix is set to none it will create the pull request branch if it doesn't exist and then any subsequent changes will be updated to the same branch name.

from create-pull-request.

Ah ok! I saw this line

Any subsequent changes will be committed to the same branch and reflected in the existing pull request.

and assumed it would only raise a single pull request. If I merge the pull request and then new commits are added is another pull request raised?

from create-pull-request.

Yes, if you merge or close the pull request another one will be created.

I will revise the wording of that sentence and make it clearer.

from create-pull-request.

Another quick question. If the repo uses "squash and merge" for it's merging strategy will this cause problems with using a single branch?

from create-pull-request.

I don't think so. The only possible problem right now is that there is no rebase feature. So it's best to delete the branch after you merge or close the PR. I'm thinking about adding a rebase feature so this won't be a problem.

from create-pull-request.

Looks like this has been resolved in 6342438.

from create-pull-request.