Add TESTS_REPOSITORY_BRANCHING.md

[kkaarreell]

Summary by Sourcery

Documentation:

• Add a comprehensive TESTS_REPOSITORY_BRANCHING.md guide covering branching strategies, dynamic ref mapping, CI setup, and rebase workflows for RHEL and Fedora.

[sourcery-ai]

Reviewer's Guide

Documents branching strategy, dynamic tmt ref mapping, and CI configuration workflows for the keylime-tests repository, focusing on how to create and maintain RHEL and Fedora test branches and how to handle rebases safely.

File-Level Changes

Change	Details	Files
Add comprehensive branching and CI operations guide for keylime-tests, covering RHEL/Fedora branching, dynamic ref mapping, and rebase workflows.	Introduce TESTS_REPOSITORY_BRANCHING.md describing how tmt dynamic_ref mapping selects test branches per distro and how rule ordering works. Document procedures for creating new RHEL minor version branches, including updating .tmt/dynamic_ref.fmf, per-branch .packit.yaml, and plan filters. Describe the RHEL/CentOS Stream rebase process with temporary dynamic_ref redirects, backup and force-push rewrite of rhel-X-main branches, and subsequent CI fixes and cleanup. Provide workflow for creating and wiring up new Fedora version branches, including packit jobs, plan filters, and dynamic_ref entries. Add checklists, best practices, and standardized commit messages to guide and automate branch / CI maintenance tasks.	TESTS_REPOSITORY_BRANCHING.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.

[sourcery-ai]

Hey - I've left some high level feedback:

• In the YAML snippets, consider quoting string-valued conditions like distro == 'rhel-10.1'/'fedora-42' to avoid ambiguity with dotted numeric-like values in some YAML parsers and to make copy-paste usage safer.
• The guide is quite long; you might improve navigability by adding a short table of contents at the top with links to the three main scenarios and the checklists, so that people can quickly jump to the workflow they need.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In the YAML snippets, consider quoting string-valued conditions like `distro == 'rhel-10.1'`/`'fedora-42'` to avoid ambiguity with dotted numeric-like values in some YAML parsers and to make copy-paste usage safer.
- The guide is quite long; you might improve navigability by adding a short table of contents at the top with links to the three main scenarios and the checklists, so that people can quickly jump to the workflow they need.

---

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.}