Skip to content

Pin click to z-streams#1192

Merged
ggainey merged 1 commit into
pulp:0.31from
mdellweg:patchback/backports/0.31/1eafe5c38450280fe0f13a8387b9ed69699583b4/pr-1191
May 12, 2025
Merged

Pin click to z-streams#1192
ggainey merged 1 commit into
pulp:0.31from
mdellweg:patchback/backports/0.31/1eafe5c38450280fe0f13a8387b9ed69699583b4/pr-1191

Conversation

@mdellweg
Copy link
Copy Markdown
Member

It turns out the click library introduces breaking changes with y-releases.

(cherry picked from commit 6d643dd) (cherry picked from commit 1eafe5c)

It turns out the click library introduces breaking changes with
y-releases.

(cherry picked from commit 6d643dd)
(cherry picked from commit 1eafe5c)
@mdellweg mdellweg marked this pull request as ready for review May 12, 2025 12:57
@ggainey ggainey enabled auto-merge (rebase) May 12, 2025 12:59
@ggainey ggainey merged commit 3c1cba5 into pulp:0.31 May 12, 2025
18 checks passed
@patchback
Copy link
Copy Markdown

patchback Bot commented May 12, 2025

Backport to 0.30: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 3c1cba5 on top of patchback/backports/0.30/3c1cba52d3fba8fd617148a2e052ec73bfa2bf5e/pr-1192

Backporting merged PR #1192 into 0.31

  1. Ensure you have a local repo clone of your fork. Unless you cloned it
    from the upstream, this would be your origin remote.
  2. Make sure you have an upstream repo added as a remote too. In these
    instructions you'll refer to it by the name upstream. If you don't
    have it, here's how you can add it:
    $ git remote add upstream https://github.com/pulp/pulp-cli.git
  3. Ensure you have the latest copy of upstream and prepare a branch
    that will hold the backported code:
    $ git fetch upstream
    $ git checkout -b patchback/backports/0.30/3c1cba52d3fba8fd617148a2e052ec73bfa2bf5e/pr-1192 upstream/0.30
  4. Now, cherry-pick PR Pin click to z-streams #1192 contents into that branch:
    $ git cherry-pick -x 3c1cba52d3fba8fd617148a2e052ec73bfa2bf5e
    If it'll yell at you with something like fatal: Commit 3c1cba52d3fba8fd617148a2e052ec73bfa2bf5e is a merge but no -m option was given., add -m 1 as follows instead:
    $ git cherry-pick -m1 -x 3c1cba52d3fba8fd617148a2e052ec73bfa2bf5e
  5. At this point, you'll probably encounter some merge conflicts. You must
    resolve them in to preserve the patch from PR Pin click to z-streams #1192 as close to the
    original as possible.
  6. Push this branch to your fork on GitHub:
    $ git push origin patchback/backports/0.30/3c1cba52d3fba8fd617148a2e052ec73bfa2bf5e/pr-1192
  7. Create a PR, ensure that the CI is green. If it's not — update it so that
    the tests and any other checks pass. This is it!
    Now relax and wait for the maintainers to process your pull request
    when they have some cycles to do reviews. Don't worry — they'll tell you if
    any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

@mdellweg mdellweg deleted the patchback/backports/0.31/1eafe5c38450280fe0f13a8387b9ed69699583b4/pr-1191 branch September 8, 2025 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants