Skip to content
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.

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

add ability to check what PRs should be backported in backport_pr #4172

Merged
merged 2 commits into from Sep 4, 2013

Conversation

minrk
Copy link
Member

@minrk minrk commented Sep 4, 2013

just run:

python tools/backport_pr.py 1.x

to see what PRs are marked for backport, but not yet applied.

just run:

    python tools/backport_pr.py 1.x

to see what PRs are marked for backport, but not yet applied.
if len(sys.argv) < 3:
branch = sys.argv[1]
already = already_backported(branch)
should = should_backport("backport-1.1")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we name future backport tags backport-<branch>, e.g. backport-1.x, so we can pick this programmatically?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, because I want their mark to be distinct for each backported release. If we want to get this programmatically, we would have to parse things out.

@takluyver
Copy link
Member

👍

minrk added a commit that referenced this pull request Sep 4, 2013
add ability to check what PRs should be backported in backport_pr
@minrk minrk merged commit 04176e0 into ipython:master Sep 4, 2013
@minrk minrk deleted the backport-pr branch September 4, 2013 22:52
mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this pull request Nov 3, 2014
add ability to check what PRs should be backported in backport_pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants