[6.19.z]: Changes for 6.19.z new branch

[Satellite-QE]

Problem Statement

New 6.19.z branch

Solution

• Dependabot labels are updated for new branch
• Removed dispatch release GHA from 6.19.z as we are releasing only master changes
• Airgun and Nailgun Requirements uses 6.19.z branch
• Constants are using new version now
• Stream tests removed
• pyproject.toml uses new version

Summary by Sourcery

Align the project configuration and dependencies with the new 6.19.z release branch and remove obsolete GitHub workflow files.

Enhancements:

• Point airgun, nailgun, and Azure-related constants to the 6.19.z branch instead of master.
• Update the project version in pyproject.toml to 6.19.z.

CI:

• Add 6.19.z label to Dependabot configuration for both pip and GitHub Actions updates.
• Remove legacy GitHub workflow and CODEOWNERS files that are no longer needed for the 6.19.z branch.

[Satellite-QE]

trigger: test-robottelo

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Prepares the repository for the new 6.19.z branch by pointing dependencies and constants to the 6.19.z branch/version, updating automation labels, and removing now-irrelevant GitHub workflows and configuration.

Flow diagram for updated dependencies and constants pointing to 6.19.z

flowchart LR
  subgraph Repo_Config
    PyProject[pyproject.toml version 6.19.z]
    Requirements[requirements.txt]
    Constants[robottelo.constants AZURERM_FILE_URI]
  end

  Dev[Developer on branch 6.19.z] -->|runs tests or installs project| Pip

  Pip[pip install -r requirements.txt] --> Requirements

  Requirements -->|airgun git URL @ 6.19.z| AirgunRepo[airgun GitHub repo branch 6.19.z]
  Requirements -->|nailgun git URL @ 6.19.z| NailgunRepo[nailgun GitHub repo branch 6.19.z]

  Dev -->|executes tests that use Azure script| Constants
  Constants -->|downloads uri.sh from 6.19.z| Robottelo_6_19_z[robottelo GitHub repo branch 6.19.z]

  PyProject -->|defines project version 6.19.z| Packaging[build and publish artifacts]

Loading

File-Level Changes

Change	Details	Files
Point internal testing dependencies to the 6.19.z branch instead of master.	Update airgun dependency to track the 6.19.z branch Update nailgun dependency to track the 6.19.z branch	requirements.txt
Configure Dependabot to recognize and label updates for the new 6.19.z branch.	Add 6.19.z to the list of labels applied to pip dependency updates Add 6.19.z to the list of labels applied to GitHub Actions dependency updates	.github/dependabot.yml
Align project metadata and constants with the 6.19.z line.	Bump the project version to 6.19.z in pyproject configuration Update the Azure script URI to point at the 6.19.z branch of robottelo	pyproject.toml robottelo/constants/__init__.py
Remove obsolete GitHub configuration and workflows that are not used for the 6.19.z branch.	Delete global CODEOWNERS configuration Remove auto-branching workflow Remove dependency merge automation workflow Remove dispatch release workflow	.github/CODEOWNERS .github/workflows/auto_branching.yml .github/workflows/dependency_merge.yml .github/workflows/dispatch_release.yml

---

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 found 1 issue, and left some high level feedback:

• The AZURERM_FILE_URI constant now hardcodes the 6.19.z branch in the URL; consider deriving this from a single version/branch variable so future branch/version updates don’t require touching this constant again.
• Removing .github/CODEOWNERS and the GitHub workflow files for this branch is a significant process change; if the intent is to only disable specific behaviors, consider narrowing the deletions or scoping them by branch instead of dropping the files entirely.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The `AZURERM_FILE_URI` constant now hardcodes the `6.19.z` branch in the URL; consider deriving this from a single version/branch variable so future branch/version updates don’t require touching this constant again.
- Removing `.github/CODEOWNERS` and the GitHub workflow files for this branch is a significant process change; if the intent is to only disable specific behaviors, consider narrowing the deletions or scoping them by branch instead of dropping the files entirely.

## Individual Comments

### Comment 1
<location> `pyproject.toml:3` </location>
<code_context>
 [project]
 name = "robottelo"
-version = "0.1.0"
+version = "6.19.z"
 description = "Robottelo is a test suite which exercises The Foreman."
 readme = "README.rst"
</code_context>

<issue_to_address>
**issue (bug_risk):** The version string `6.19.z` is not PEP 440–compliant and may cause packaging/tooling issues.

Python packaging tools (pip, build, twine, etc.) require PEP 440–compliant versions; a suffix like `z` is invalid and can break build/publish flows. If you need to track the Satellite/Foreman stream (`6.19.z`), please map it to a compliant `version` (e.g. `6.19.0` or `6.19.0+6.19.z`) and store the stream identifier separately (e.g. constant, tag, or metadata).
</issue_to_address>

---

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