#24661 New Branch "epel8-playground" for "rpms/python-testscenarios"
Closed: Invalid 3 years ago by limb. Opened 3 years ago by salimma.

{
 "action": "new_branch",
 "branch": "epel8-playground",
 "namespace": "rpms",
 "repo": "python-testscenarios",
 "create_git_branch": true
}

Existing epel8 package, but for some reason epel8-playground never got created

Turns out to be similar to https://pagure.io/releng/issue/8717 that @smooge filed. PDC has it, but the branch never got created; pushing the first commit in the epel8 branch fixes the issue.

Interestingly, this package's EPEL8 branch seems to be identical to the F32 and master branches -- trying to figure out how it got branched.

I requested the epel8 branch with --no-git-branch, which created the requests for both epel8 and epel8-playground. The branches are approved and can be pushed to at any time. I'd recommend you take these steps.

git checkout epel8
git pull
git checkout -b epel8-playground
git push -u origin epel8-playground

This issue should be closed as a duplicate of #24560.

epel8-playground branch can be empty because epel8 branch mirrors the builds with package.cfg.

The branch in PDC already exists, you can now create it yourself as follows:
Check in the project's settings if you have activated the git hook preventingnew git branches from being created and if you did, de-activate it.
Then simply run in cloned repository: git checkout -b <branch_name> && git push -u origin <branch_name>.
<branch_name> is the name of the branch you requested.
You only need to do this once and you can then use fedpkg as you normally do.

Metadata Update from @limb:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata