GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Remember PR remote name for `cherry_picker --continue` · Issue #8 · python/cherry-picker

Remember PR remote name for cherry_picker --continue #8

New issue
Copy link
New issue
Copy link
Open
Open
Remember PR remote name for cherry_picker --continue#8
Copy link

Description

@ncoghlan
ncoghlan
opened on Jun 2, 2017
Issue body actions

The option to set the PR remote does work with cherry_picker --continue, but currently needs to be specified explicitly, rather than being remembered from the original CLI invocation.

Reacted by 🇺🇦 Sviatoslav Sydorenko (Святослав Сидоренко)

Activity

  1. Mariatta commented on Jun 4, 2017

    @Mariatta
    Mariatta
    on Jun 4, 2017
    Member
    More actions

    What --continue does right now is do git commit in the current branch (as long as it's not a master branch) then push to origin.
    If we want to remember the previously specified pr-remote then it has to be stored in a temp file or something? 🤔

  2. ncoghlan commented on Jun 4, 2017

    @ncoghlan
    ncoghlan
    on Jun 4, 2017
    ContributorAuthor
    More actions

    Aye, something along those lines. Such a file could potentially also be used to keep track of whether or not the commit step had already been completed, as before I finally realised that --pr-remote needed to be passed together with --continue, I accidentally created 3 copies of the cherry-pick commit.

    One possible option: we could add .tmp-backport/ to CPython's .gitignore file, and then use that as a working directory for temporary state in cherry_picker.py.

  3. webknjaz commented on Feb 26, 2019

    @webknjaz
    webknjaz
    on Feb 26, 2019
    Member
    More actions

    FTR: Now with the work done in #295/#277 it should possible to implements storing more state-related data in git config --local (i.e. .git/config) throughout the whole backport cycle.

    Reacted by Mariatta
  4. Mariatta
    transferred this issue frompython/core-workflowon May 30, 2019
  5. CAM-Gerlach commented on Jan 15, 2023

    @CAM-Gerlach
    CAM-Gerlach
    on Jan 15, 2023
    Member
    More actions

    To note, the fact that this wasn't stored along with the other state was also incredibly confusing for me when attempting to reproduce #78

  6. cmaloney commented on Oct 29, 2026

    @cmaloney
    cmaloney
    on Oct 29, 2026
    Contributor
    More actions

    Proposing that we reuse git's remote.pushDefault for this: #198

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402520 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.