Skip to content

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

Description

@jenstroeger

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)

Activity

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions