Skip to content

NE-2880: Update GitHub issue template URLs - #487

Merged
openshift-ci[bot] merged 1 commit into
openshift:masterfrom
redhat-chai-bot:NE-2880/update-issue-template-urls
Sep 12, 2026
Merged

NE-2880: Update GitHub issue template URLs#487
openshift-ci[bot] merged 1 commit into
openshift:masterfrom
redhat-chai-bot:NE-2880/update-issue-template-urls

Conversation

@redhat-chai-bot

@redhat-chai-bot redhat-chai-bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Updates .github/ISSUE_TEMPLATE/config.yml to use the current Red Hat Jira and documentation URLs. The OKD link and the remaining contact-link structure are unchanged.

Validation completed:

  • YAML parsing
  • git diff --check
  • Confirmed legacy domains are absent
  • Confirmed all three contact links remain

AI-generated. Review for accuracy.

@candita requested in Slack thread

Summary by CodeRabbit

  • Documentation
    • Updated the bug report contact link to the new Red Hat issue tracker.
    • Updated the DNS Operator documentation link for OpenShift Container Platform.
    • Updated the DNS Operator documentation link for OKD to its revised documentation path.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@coderabbitai

coderabbitai Bot commented Sep 3, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 2fbeecb0-3770-4fa6-bb99-4f3dae36fd70

📥 Commits

Reviewing files that changed from the base of the PR and between 444c2cf and 280d4bd.

📒 Files selected for processing (1)
  • .github/ISSUE_TEMPLATE/config.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


Walkthrough

The issue template updates the bug report tracker URL and both DNS Operator documentation URLs.

Changes

Issue template contact links

Layer / File(s) Summary
Update contact links
.github/ISSUE_TEMPLATE/config.yml
The bug report link uses the updated Jira URL and parameters. The OpenShift and OKD DNS Operator links use their current documentation paths.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to ceba2

The issue-template bug-report and DNS Operator documentation links are updated as intended, with no current merge-readiness risk identified.

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: updating issue template links to current Red Hat Jira and documentation URLs.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml, replacing three contact-link URLs. The full origin/master...HEAD diff contains no Ginkgo tests or test-title expressions, so …
Test Structure And Quality ✅ Passed PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml, with three URL substitutions. It adds or modifies no Ginkgo test code, test setup, cleanup, waits, or assertions. Therefore non…
Microshift Test Compatibility ✅ Passed PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml. The full diff from origin/master contains three URL updates and no new or modified Ginkgo e2e tests. Therefore, the MicroShif…
Single Node Openshift (Sno) Test Compatibility ✅ Passed PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml. The verified commit diff contains no new Ginkgo tests or other test code, so the Single Node OpenShift compatibility check does…
Topology-Aware Scheduling Compatibility ✅ Passed PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml. The diff updates two contact-link URLs and adds no deployment manifests, operator code, controllers, replicas, affinity, topolo…
Ote Binary Stdout Contract ✅ Passed PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml. The merge-base diff contains three URL replacements, with no source-file changes and no stdout-contract tokens such as `fmt.Pri…
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml. The diff adds no Ginkgo e2e tests and no test networking behavior. The updated documentation and Jira URLs are issue-template c…
No-Weak-Crypto ✅ Passed The pull request changes only .github/ISSUE_TEMPLATE/config.yml. The diff updates two URLs and removes old Jira query parameters. It adds no cryptographic algorithm, custom crypto implementation, or…
Container-Privileges ✅ Passed PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml, which contains contact-link URLs and descriptions. The complete diff introduces no container or Kubernetes manifest fields for …
No-Sensitive-Data-In-Logs ✅ Passed PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml contact-link URLs. The diff adds no logging statements and no passwords, tokens, API keys, PII, session IDs, or customer data to…
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Full details: Stable And Deterministic Test Names

Explanation

PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml, replacing three contact-link URLs. The full origin/master...HEAD diff contains no Ginkgo tests or test-title expressions, so it introduces no unstable or overly-specific test names.

Full details: Test Structure And Quality

Explanation

PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml, with three URL substitutions. It adds or modifies no Ginkgo test code, test setup, cleanup, waits, or assertions. Therefore none of the stated Test Structure and Quality failure conditions apply.

Full details: Microshift Test Compatibility

Explanation

PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml. The full diff from origin/master contains three URL updates and no new or modified Ginkgo e2e tests. Therefore, the MicroShift test compatibility check is not applicable.

Full details: Single Node Openshift (Sno) Test Compatibility

Explanation

PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml. The verified commit diff contains no new Ginkgo tests or other test code, so the Single Node OpenShift compatibility check does not apply.

Full details: Topology-Aware Scheduling Compatibility

Explanation

PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml. The diff updates two contact-link URLs and adds no deployment manifests, operator code, controllers, replicas, affinity, topology spread, node selection, tolerations, or PDB settings. The topology-aware scheduling check is therefore not applicable.

Full details: Ote Binary Stdout Contract

Explanation

PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml. The merge-base diff contains three URL replacements, with no source-file changes and no stdout-contract tokens such as fmt.Print, klog, RunSpecs, or BeforeSuite. The YAML parses with three contact links. The custom check is therefore not applicable.

Full details: Ipv6 And Disconnected Network Test Compatibility

Explanation

PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml. The diff adds no Ginkgo e2e tests and no test networking behavior. The updated documentation and Jira URLs are issue-template contact links, not test dependencies under this check.

Full details: No-Weak-Crypto

Explanation

The pull request changes only .github/ISSUE_TEMPLATE/config.yml. The diff updates two URLs and removes old Jira query parameters. It adds no cryptographic algorithm, custom crypto implementation, or secret/token comparison. No MD5, SHA1, DES, RC4, 3DES, Blowfish, or ECB usage appears in the changed lines.

Full details: Container-Privileges

Explanation

PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml, which contains contact-link URLs and descriptions. The complete diff introduces no container or Kubernetes manifest fields for privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation.

Full details: No-Sensitive-Data-In-Logs

Explanation

PASS: The pull request changes only .github/ISSUE_TEMPLATE/config.yml contact-link URLs. The diff adds no logging statements and no passwords, tokens, API keys, PII, session IDs, or customer data to logs. The Atlassian URL parameters are configuration data, not log output.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

Update the issue template contact links to use the current Red Hat
Jira and OpenShift and OKD documentation URLs.

This commit resolves NE-2880.

https://redhat.atlassian.net/browse/NE-2880

* .github/ISSUE_TEMPLATE/config.yml:
  Update Jira and DNS/OKD documentation links.
@redhat-chai-bot
redhat-chai-bot force-pushed the NE-2880/update-issue-template-urls branch from 280d4bd to ceba2b0 Compare September 3, 2026 14:59
@Miciah

Miciah commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

/retitle NE-2880: Update GitHub issue template URLs

@openshift-ci openshift-ci Bot changed the title Update issue template URLs to current Red Hat domains NE-2880: Update GitHub issue template URLs Sep 3, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 3, 2026
@openshift-ci-robot

openshift-ci-robot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

@redhat-chai-bot: This pull request references NE-2880 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Updates .github/ISSUE_TEMPLATE/config.yml to use the current Red Hat Jira and documentation URLs. The OKD link and the remaining contact-link structure are unchanged.

Validation completed:

  • YAML parsing
  • git diff --check
  • Confirmed legacy domains are absent
  • Confirmed all three contact links remain

AI-generated. Review for accuracy.

@candita requested in Slack thread

Summary by CodeRabbit

  • Documentation
  • Updated the bug report contact link to the new Red Hat issue tracker.
  • Updated the DNS Operator documentation link for OpenShift Container Platform.
  • Updated the DNS Operator documentation link for OKD to its revised documentation path.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@gcs278

gcs278 commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

/assign @davidesalerno

@davidesalerno

davidesalerno commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 10, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-operator
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-aws-ovn-upgrade
/test e2e-hypershift

@davidesalerno

Copy link
Copy Markdown
Contributor

/approve

@openshift-ci

openshift-ci Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: davidesalerno

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 10, 2026
@melvinjoseph86

Copy link
Copy Markdown

/retest-required

@melvinjoseph86

Copy link
Copy Markdown

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 12, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@melvinjoseph86: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci

openshift-ci Bot commented Sep 12, 2026

Copy link
Copy Markdown
Contributor

@redhat-chai-bot: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci
openshift-ci Bot merged commit 3d991ed into openshift:master Sep 12, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants