Skip to content

CNTRLPLANE-3722: updating context docs for agentic SDLC contextification#8828

Open
georgelipceanu wants to merge 1 commit into
openshift:mainfrom
georgelipceanu:new-contributingmd
Open

CNTRLPLANE-3722: updating context docs for agentic SDLC contextification#8828
georgelipceanu wants to merge 1 commit into
openshift:mainfrom
georgelipceanu:new-contributingmd

Conversation

@georgelipceanu

@georgelipceanu georgelipceanu commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:

This PR aims to update the HyperShift repo's contextification files in accordance with the Agentic SDLC context efforts for this Control Plane Shift Week.

  • Add code conventions to CONTRIBUTING.md based on the new template found here.

Which issue(s) this PR fixes:

Fixes CNTRLPLANE-3722

Special notes for your reviewer:

These changes are simple additions using some provided templates from the Control Plane team and may not be entirely necessary. I figured I would provide this PR anyway for feedback and thoughts from the team.

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

Summary by CodeRabbit

  • Documentation
    • Expanded contribution guidelines with a new code conventions section covering Bash and Go.
    • Updated section organization and formatting for easier reading.
    • Added clearer guidance on merge labels, including a note to use NO-JIRA sparingly.
    • Included an additional review note advising contributors not to use AI when responding to review comments.

This addtion is in accordance with the Agentic SDLC contextification efforts for this Control Plane Shift Week

Signed-off-by: George Lipceanu <glipcean@redhat.com>
@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

@openshift-ci openshift-ci Bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. do-not-merge/needs-area labels Jun 24, 2026
@openshift-ci

openshift-ci Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: georgelipceanu
Once this PR has been reviewed and has the lgtm label, please assign devguyio for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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 requested review from Nirshal and jparrill June 24, 2026 21:45
@coderabbitai

coderabbitai Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

CONTRIBUTING.md is updated with a new Code Conventions section, revised guidance for required merge labels, and an added note in the review process about not using AI to respond to review comments.


Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 error)

Check name Status Explanation Resolution
Container-Privileges ❌ Error The PR adds privileged settings in two manifests: hostPID/hostNetwork/privileged in one DaemonSet and privileged plus allowPrivilegeEscalation in another. Remove or justify these settings, or document an explicit exception; prefer non-privileged containers and allowPrivilegeEscalation: false unless required.
✅ Passed checks (10 passed)
Check name Status Explanation
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 Only CONTRIBUTING.md changed; no Ginkgo test titles were added or modified, so the stability rule is unaffected.
Test Structure And Quality ✅ Passed PR only updates CONTRIBUTING.md; no Ginkgo test code or cluster-interaction tests were changed, so this check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed Matches were only API schema/CRD docs for nodeSelector/tolerations/maxUnavailable; no controller/operator scheduling logic was added.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR only updates CONTRIBUTING.md; no Ginkgo e2e tests or networking code were added, so the IPv6/disconnected-network check is not applicable.
No-Weak-Crypto ✅ Passed CONTRIBUTING.md only adds docs guidance; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret-comparison code appears.
No-Sensitive-Data-In-Logs ✅ Passed The diff only updates CONTRIBUTING.md guidance; it contains no log statements or sensitive data like passwords, tokens, or PII.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the documentation-focused agentic SDLC contextification changes in CONTRIBUTING.md.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CONTRIBUTING.md`:
- Around line 47-50: The nested list under the commit format section has
inconsistent indentation and is triggering markdownlint MD005. Update the
Markdown in the commit guidance so the sublist under the “Use proper commit
format” item is consistently nested, using the same indentation style as the
surrounding list in CONTRIBUTING.md.
- Around line 83-85: The markdown for the area label is split incorrectly,
making the label pattern hard to read. Update the label entry in CONTRIBUTING.md
so the token is written as area/* consistently, and keep the examples aligned
with that same pattern in the labels list.
- Around line 16-18: The markdown guidance in CONTRIBUTING.md has a
spelling/style inconsistency: change the platform name in the
scripts-compatibility bullet to use macOS consistently. Update the relevant line
in the document so it matches the repo’s docs spelling rules and passes the
markdown spell check.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: ac2e8372-ef90-47b6-b020-e895d592fecb

📥 Commits

Reviewing files that changed from the base of the PR and between 64c8878 and 15578ea.

📒 Files selected for processing (1)
  • CONTRIBUTING.md

Comment thread CONTRIBUTING.md
Comment on lines +16 to +18
- Follow the [shell styleguide](https://google.github.io/styleguide/shellguide.html).
- Use `[shellcheck](https://github.com/koalaman/shellcheck)` to identify common mistakes or caveats.
- Ensure that all scripts run consistently across Linux and MacOS.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Use macOS here.

MacOS is a spelling/style inconsistency in a markdown file and will trip the repo's docs spell check. As per coding guidelines, **/*.md: use make verify-codespell to catch spelling errors.

Fix
-Ensure that all scripts run consistently across Linux and MacOS.
+Ensure that all scripts run consistently across Linux and macOS.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- Follow the [shell styleguide](https://google.github.io/styleguide/shellguide.html).
- Use `[shellcheck](https://github.com/koalaman/shellcheck)` to identify common mistakes or caveats.
- Ensure that all scripts run consistently across Linux and MacOS.
- Follow the [shell styleguide](https://google.github.io/styleguide/shellguide.html).
- Use `[shellcheck](https://github.com/koalaman/shellcheck)` to identify common mistakes or caveats.
- Ensure that all scripts run consistently across Linux and macOS.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~18-~18: The operating system from Apple is written “macOS”.
Context: ...ripts run consistently across Linux and MacOS. ### Golang (Go) - Review [Effective ...

(MAC_OS)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CONTRIBUTING.md` around lines 16 - 18, The markdown guidance in
CONTRIBUTING.md has a spelling/style inconsistency: change the platform name in
the scripts-compatibility bullet to use macOS consistently. Update the relevant
line in the document so it matches the repo’s docs spelling rules and passes the
markdown spell check.

Sources: Coding guidelines, Linters/SAST tools

Comment thread CONTRIBUTING.md
Comment on lines +47 to 50
4. **Use proper commit format**:
1. Write commit subjects in [imperative mood](https://en.wikipedia.org/wiki/Imperative_mood) (e.g., "Fix bug" not "Fixed bug")
2. Follow [conventional commit format](https://www.conventionalcommits.org/) and include "Why" and "How" in commit messages

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Normalize the nested list indentation.

The commit-format sublist is inconsistently indented, and markdownlint already flagged this as MD005. Please align the nesting before merging.

🧰 Tools
🪛 markdownlint-cli2 (0.22.1)

[warning] 48-48: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2

(MD005, list-indent)


[warning] 49-49: Inconsistent indentation for list items at the same level
Expected: 0; Actual: 2

(MD005, list-indent)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CONTRIBUTING.md` around lines 47 - 50, The nested list under the commit
format section has inconsistent indentation and is triggering markdownlint
MD005. Update the Markdown in the commit guidance so the sublist under the “Use
proper commit format” item is consistently nested, using the same indentation
style as the surrounding list in CONTRIBUTING.md.

Source: Linters/SAST tools

Comment thread CONTRIBUTING.md
Comment on lines +83 to 85
**Note:** NO-JIRA should be used sparingly. Please have a Jira issue associated with your PR whenever possible.
- `area/`* - Area label (e.g., `area/documentation`, `area/control-plane`)
- `verified` - QA verification passed (for more information refer to the [documentation](https://docs.ci.openshift.org/docs/architecture/jira/#the-verified-label))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Fix the area/* label formatting.

The current markdown splits the token as area/, which makes the required label hard to read. Use area/` so the label name stays unambiguous.

Fix
-- `area/`* - Area label (e.g., `area/documentation`, `area/control-plane`)
+- `area/*` - Area label (e.g., `area/documentation`, `area/control-plane`)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
**Note:** NO-JIRA should be used sparingly. Please have a Jira issue associated with your PR whenever possible.
- `area/`* - Area label (e.g., `area/documentation`, `area/control-plane`)
- `verified` - QA verification passed (for more information refer to the [documentation](https://docs.ci.openshift.org/docs/architecture/jira/#the-verified-label))
**Note:** NO-JIRA should be used sparingly. Please have a Jira issue associated with your PR whenever possible.
- `area/*` - Area label (e.g., `area/documentation`, `area/control-plane`)
- `verified` - QA verification passed (for more information refer to the [documentation](https://docs.ci.openshift.org/docs/architecture/jira/#the-verified-label))
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CONTRIBUTING.md` around lines 83 - 85, The markdown for the area label is
split incorrectly, making the label pattern hard to read. Update the label entry
in CONTRIBUTING.md so the token is written as area/* consistently, and keep the
examples aligned with that same pattern in the labels list.

@openshift-ci

openshift-ci Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

@georgelipceanu: The label(s) area/docs cannot be applied, because the repository doesn't have them.

Details

In response to this:

/area docs

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.

@codecov

codecov Bot commented Jun 24, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 42.89%. Comparing base (64c8878) to head (15578ea).
⚠️ Report is 13 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #8828   +/-   ##
=======================================
  Coverage   42.89%   42.89%           
=======================================
  Files         766      766           
  Lines       94684    94684           
=======================================
  Hits        40617    40617           
  Misses      51259    51259           
  Partials     2808     2808           
Flag Coverage Δ
cmd-support 36.25% <ø> (ø)
cpo-hostedcontrolplane 44.84% <ø> (ø)
cpo-other 44.94% <ø> (ø)
hypershift-operator 53.05% <ø> (ø)
other 31.69% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@georgelipceanu

Copy link
Copy Markdown
Contributor Author

/area documentation

@openshift-ci openshift-ci Bot added area/documentation Indicates the PR includes changes for documentation and removed do-not-merge/needs-area labels Jun 24, 2026
@openshift-ci

openshift-ci Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

@georgelipceanu: 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.

@georgelipceanu georgelipceanu changed the title [WIP] updating context docs for agentic SDLC contextification [WIP] CNTRLPLANE-3722: updating context docs for agentic SDLC contextification Jun 25, 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 Jun 25, 2026
@openshift-ci-robot

openshift-ci-robot commented Jun 25, 2026

Copy link
Copy Markdown

@georgelipceanu: This pull request references CNTRLPLANE-3722 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 story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

What this PR does / why we need it:

This PR aims to update the HyperShift repo's contextification files in accordance with the Agentic SDLC context efforts for this Control Plane Shift Week.

  • Add code conventions to CONTRIBUTING.md based on the new template found here.

Which issue(s) this PR fixes:

Fixes

Special notes for your reviewer:

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

Summary by CodeRabbit

  • Documentation
  • Expanded contribution guidelines with a new code conventions section covering Bash and Go.
  • Updated section organization and formatting for easier reading.
  • Added clearer guidance on merge labels, including a note to use NO-JIRA sparingly.
  • Included an additional review note advising contributors not to use AI when responding to review comments.

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.

@georgelipceanu georgelipceanu changed the title [WIP] CNTRLPLANE-3722: updating context docs for agentic SDLC contextification CNTRLPLANE-3722: updating context docs for agentic SDLC contextification Jun 29, 2026
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/documentation Indicates the PR includes changes for documentation jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants