chore: add 'propose-downstrem' job for CentOS

[mmartinv]

Signed-off-by: Miguel Martín [email protected]

[gemini-code-assist]

Summary of Changes

Hello @mmartinv, 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 enhances the continuous delivery pipeline by introducing an automated propose_downstream job for CentOS Stream. This ensures that the go-fdo-server-centos package is automatically synced to the downstream distribution upon release, with specific branch merging strategies implemented to maintain consistency and avoid divergence.

Highlights

• New CentOS Downstream Job: A new propose_downstream job has been added to the .packit.yaml configuration, specifically targeting CentOS Stream.
• Package Configuration: This new job is configured to handle the go-fdo-server-centos package upon release.
• Branch Management: The dist_git_branches setting for CentOS Stream has been configured to ensure c10s fast-forwards merge into c9s, preventing divergent branches as per Packit's recommendations.
• Documentation Reference: A documentation link for Packit's propose_downstream configuration has been added above the existing Fedora job for clarity.

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 adds a propose_downstream job for CentOS to the Packit configuration. The change for Fedora adds a helpful documentation link. The new job for CentOS includes configuration to synchronize branches between CentOS Stream 9 and 10. My review identifies a potential issue with the branch synchronization logic, where changes from a newer stream (c10s) are proposed to be fast-forwarded to an older stream (c9s). I've suggested reversing this to follow the more common and safer practice of merging from older to newer streams.

[gemini-code-assist]

The current dist_git_branches configuration attempts to fast-forward merge changes from CentOS Stream 10 (c10s) into CentOS Stream 9 (c9s). This is an unusual workflow, as it pushes changes from a newer release stream to an older one. This could unintentionally introduce breaking changes or features that are not compatible with the older environment of c9s.

The conventional approach is to manage changes in the oldest supported branch and fast-forward them to newer branches. This ensures that a change is compatible with the older environment first. I'd recommend reversing the logic to apply changes to c9s and fast-forward them into c10s.

      c9s:
        fast_forward_merge_into: ["c10s"]