Sync releases to the eln branch

[nforro]

Related to packit/packit-service#2822.

[gemini-code-assist]

Summary of Changes

Hello @nforro, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request modifies the Packit configuration to extend the synchronization of rawhide changes to the eln branch. By adding eln to the fast_forward_merge_into list for rawhide in two job configurations, the PR ensures that the eln branch consistently receives the latest updates from rawhide through automated fast-forward merges, streamlining the development workflow for future Fedora releases.

Highlights

• Configuration Update: The .packit.yaml configuration file has been updated to include the eln branch as a target for fast-forward merges from rawhide.
• Branch Synchronization: This change ensures that changes from the rawhide branch are automatically synchronized into the eln branch for specific job definitions within the Packit service.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the Packit configuration to also sync releases from the rawhide branch to the eln branch. The change is applied to two separate jobs, which introduces some duplication into the configuration file. I've left a suggestion to refactor this using YAML anchors to improve maintainability, which could be handled in a follow-up.

[gemini-code-assist]

This change introduces duplication. The fast_forward_merge_into configuration for rawhide is now identical here and in the pull_from_upstream job definition (line 228). To improve maintainability and avoid potential inconsistencies in the future, consider using a YAML anchor to define this configuration once and reuse it in both places.

For example, you could define an anchor:

x-rawhide-ff-config: &rawhide-ff-config
  fast_forward_merge_into:
    - fedora-branched
    - eln

And then reference it in both jobs:

# ... in propose_downstream job
rawhide:
  <<: *rawhide-ff-config
# ...
# ... in pull_from_upstream job
rawhide:
  <<: *rawhide-ff-config

This would make the configuration easier to manage if more branches need to be added in the future. Since this would require changes outside of the current diff, it could be addressed in a follow-up.

[centosinfra-prod-github-app]

Build succeeded.
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/packit-service/buildset/c79d45f85a6d4b0097a73404c9c90515

✔️ pre-commit SUCCESS in 2m 13s
✔️ specfile-tests-rpm-deps SUCCESS in 1m 45s
✔️ specfile-tests-pip-deps SUCCESS in 1m 38s

[centosinfra-prod-github-app]

Build succeeded (gate pipeline).
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/packit-service/buildset/63a2b6aa1787445c8c379efb2c14dbcb

✔️ pre-commit SUCCESS in 2m 01s

[gotmax23]

Why does python-specfile need an eln branch? See https://docs.fedoraproject.org/en-US/eln/eln-branch/.

[nforro]

Why does python-specfile need an eln branch? See https://docs.fedoraproject.org/en-US/eln/eln-branch/.

It doesn't. But we want to dogfood Packit as Fedora CI for ELN as well, to catch potential issues early.