build commits into @theforeman/develop copr

[evgeni]

What are the changes introduced in this pull request?

instead of building to packit/theforeman-foreman_rh_cloud-develop this builds into @theforeman/develop so that all plugins can have a central "nightly" place

Considerations taken when implementing this change?

What are the testing steps for this pull request?

Can't be tested before merging.

https://packit.dev/docs/configuration/upstream/copr_build#using-a-custom-copr-project was followed

Summary by Sourcery

Build:

• Configure Copr owner as '@theforeman' and project as 'develop' in .packit.yaml

[sourcery-ai]

Reviewer's Guide

Update .packit.yaml to redirect Copr builds for the develop branch into a centralized @theforeman/develop project by adding the appropriate owner and project settings.

File-Level Changes

Change	Details	Files
Configure packit to build into a shared @theforeman/develop Copr project	Add owner field set to '@theforeman' Add project field set to 'develop'	.packit.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @evgeni - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[evgeni]

@ehelms @ares this should lay the groundwork for the centralized "plugins nightly copr" we talked about

[evgeni]

Until fedora-copr/copr#3804 is implemented, each git repo needs to be added to copr manually :/