New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tag a previous Upstream Sync PR as duplicate of a new Sync PR #509

Open

jenstroeger opened this issue Apr 2, 2023 · 0 comments

Assignees

Owner

jenstroeger commented Apr 2, 2023 •

edited

Loading

would it make sense to check if a branch for that previous version exists, and close the PR and delete that now older branch? Or, if not, mark the older PR as a duplicate of the new PR?

The new branch that’s being opened should include all changes from that older branch🤔

Yes, the new PR should technically supersede the previous one and close it.

Originally posted by @behnazh in #482 (comment)

jenstroeger mentioned this issue

fix(ci): improve automatic template synchronization #537

Merged

jenstroeger assigned behnazh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment