Reference podman-next project for main packit builds

[saschagrunert]

What type of PR is this?

/kind ci

What this PR does / why we need it:

Refering to #1108 (comment) and #1108 (comment), we now reference the project podman-next when building packages for main.

Which issue(s) this PR fixes:

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

None

[saschagrunert]

PTAL @haircommander @lsm5 @rphillips

[codecov-commenter]

Codecov Report

Merging #1109 (6328a33) into main (7b2a32a) will decrease coverage by 0.09%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1109      +/-   ##
==========================================
- Coverage   33.51%   33.42%   -0.09%     
==========================================
  Files          13       13              
  Lines        1119     1119              
  Branches      387      391       +4     
==========================================
- Hits          375      374       -1     
  Misses        487      487              
- Partials      257      258       +1     

[lsm5]

/lgtm
/hold

🤞

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lsm5, saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [saschagrunert]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[saschagrunert]

/unhold

[lsm5]

ugh, i forgot to add some settings to the podman-next copr. let me do that now.

[lsm5]

/packit copr-build

[saschagrunert]

Thank you @lsm5 !

[lsm5]

Thank you @lsm5 !

don't thank me yet 😄 . Looks like it's still sending the trigger:commit build to the packit-builds copr and not the podman-next corp ☹️ . Let me look further..

[lsm5]

i'm gonna try deleting the conmon-rs package from podman-next and try a packit copr-build to see if it gets picked up.

[lsm5]

/packit copr-build

[lsm5]

@saschagrunert so slash-packit copr-build will trigger for pull_request not once merged. To see the main branch get built on podman-next, we gotta do another PR. I now the packit forge setting enabled, so I think we should be good to go.