[DO NOT MERGE] Test

[lsm5]

Summary by Sourcery

Documentation:

• Clean up markdown formatting for the SELinux blog links in the README.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR makes minor formatting adjustments in README.md by removing trailing double-space markdown line breaks from a list of SELinux-related blog links, standardizing the paragraph formatting, and appending a temporary "DO NOT MERGE" note at the end of the section.

File-Level Changes

Change	Details	Files
Normalize markdown formatting for SELinux blog link entries in the README.	Remove trailing double spaces after bolded link titles to avoid forced line breaks Keep accompanying explanatory text on the following line for each link Ensure consistent formatting across all SELinux-related blog entries	README.md
Add a temporary non-technical note indicating the PR should not be merged.	Append a standalone "DO NOT MERGE" line at the end of the modified section to flag the PR as experimental or for testing	README.md

---

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.

[gemini-code-assist]

Summary of Changes

Hello @lsm5, 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 is a test PR, as indicated by its title and the addition of a 'DO NOT MERGE' marker in the README.md file. The primary purpose is to serve as a temporary placeholder or an environment for testing PR workflows without introducing functional changes.

Highlights

• Testing Placeholder: A 'DO NOT MERGE' tag has been added to the README.md file, indicating this pull request is for testing purposes only.

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 cleans up trailing whitespace in the README.md file, which improves markdown formatting consistency. However, it also adds a 'DO NOT MERGE' instruction directly into the file content. While the PR is marked as a test, this line should be removed before any potential merge to keep the documentation clean.

[gemini-code-assist]

This blank line and the 'DO NOT MERGE' instruction appear to be temporary artifacts related to this test pull request. They should be removed before merging to avoid including them in the final documentation.

[packit-as-a-service]

Tests failed. @containers/packit-build please check.

[LecrisUT]

I don't see it failing on our runs https://artifacts.dev.testing-farm.io/38c42501-18ff-4998-a16e-4ccf1d9f15bc/#work-the-rest7iyh8mhi_plans-provision-container-the-rest_17_default-0 but let me check the freshest build, maybe something changed in rawhide?

Edit: still passing in recent test