Skip to content

Allow publication of empty repositories #1424

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

Merged
quba42 merged 1 commit into from
Apr 2, 2026

Allow publication of empty repositories

ce0c6a6
Select commit
Loading
Failed to load commit list.
Merged

Allow publication of empty repositories #1424

Allow publication of empty repositories
ce0c6a6
Select commit
Loading
Failed to load commit list.
Patchback / Backport to 3.8 completed May 8, 2026 in 4s

Backport to 3.8: 💔 cherry-picking failed — could not push

❌ Current GitHub App installation does not grant sufficient privileges for pushing to https://github.com/pulp/pulp_deb.git. Lacking Contents: write or Workflows: write permissions are known to cause this.

the underlying command output was:

$ git --git-dir /tmp/pulp--pulp_deb---3.8---4nycmxoh---PR-1424.git/.git --work-tree /tmp/pulp--pulp_deb---3.8---4nycmxoh---PR-1424.git -c user.email=45432694+patchback[bot]@users.noreply.github.com -c user.name=patchback[bot] -c diff.algorithm=histogram push --force-with-lease origin HEAD

[RETURN CODE]: 1

[OUTPUT]:


[STDERR]:

Details

Backporting merged PR #1424 into main

  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_deb.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/3.8/482bd0d45442ffe5f7f4335e8714d4c3e7fd7ea6/pr-1424 upstream/3.8
  4. Now, cherry-pick PR #1424 contents into that branch: 
    $ git cherry-pick -x 482bd0d45442ffe5f7f4335e8714d4c3e7fd7ea6
    If it'll yell at you with something like fatal: Commit 482bd0d45442ffe5f7f4335e8714d4c3e7fd7ea6 is a merge but no -m option was given., add -m 1 as follows instead: 
    $ git cherry-pick -m1 -x 482bd0d45442ffe5f7f4335e8714d4c3e7fd7ea6
  5. At this point, you'll probably encounter some merge conflicts. You must
    resolve them in to preserve the patch from PR #1424 as close to the
    original as possible.
  6. Push this branch to your fork on GitHub: 
    $ git push origin patchback/backports/3.8/482bd0d45442ffe5f7f4335e8714d4c3e7fd7ea6/pr-1424
  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!
View more details on Patchback