Skip to content

CLID-634: Update CONTRIBUTING.md#1450

Open
dorzel wants to merge 1 commit into
openshift:mainfrom
dorzel:CLID-634
Open

CLID-634: Update CONTRIBUTING.md#1450
dorzel wants to merge 1 commit into
openshift:mainfrom
dorzel:CLID-634

Conversation

@dorzel

@dorzel dorzel commented Jun 23, 2026

Copy link
Copy Markdown
Member

Description

Update CONTRIBUTING.md. Removed some references to docs that only existed in v1. Open item as to whether we want to include those or not again. I think pointing to an ARCHITECTURE.md will cover some of that ground.

Github / Jira issue: https://redhat.atlassian.net/browse/CLID-634

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Code Improvements (Refactoring, Performance, CI upgrades, etc)
  • Internal repo assets (diagrams / docs on github repo)
  • This change requires a documentation update on openshift docs

How Has This Been Tested?

Expected Outcome

Summary by CodeRabbit

  • Documentation
    • Rewrote contribution guidelines to simplify and reorganize instructions.
    • Added a clearer make-based workflow for building and running checks, including a recommendation to run make sanity before committing; streamlined bug/enhancement request checklists.
    • Updated pull request expectations, including signed commits and “if applicable” test/docs updates, and refreshed documentation contribution guidance.

@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 23, 2026
@openshift-ci-robot

openshift-ci-robot commented Jun 23, 2026

Copy link
Copy Markdown

@dorzel: This pull request references CLID-634 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:

Description

Update CONTRIBUTING.md. Removed some references to docs that only existed in v1. Open item as to whether we want to include those or not again.

Github / Jira issue: https://redhat.atlassian.net/browse/CLID-634

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Code Improvements (Refactoring, Performance, CI upgrades, etc)
  • Internal repo assets (diagrams / docs on github repo)
  • This change requires a documentation update on openshift docs

How Has This Been Tested?

Expected Outcome

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.

@coderabbitai

coderabbitai Bot commented Jun 23, 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: Enterprise

Run ID: a32beb8b-4e60-49ff-a943-b41a7ccf2c56

📥 Commits

Reviewing files that changed from the base of the PR and between 5649560 and 58165cb.

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

Walkthrough

CONTRIBUTING.md is reorganized around direct contribution paths, adds a make-based development workflow with make sanity, and rewrites the bug, enhancement, pull request, testing, and docs sections into shorter checklists or pointers.

Changes

Contribution guide rewrite

Layer / File(s) Summary
Navigation and development workflow
CONTRIBUTING.md
The table of contents is simplified, and the introduction adds a Development section with a root-directory note, a make-based workflow, and a make sanity pre-commit step.
Issue reporting checklists
CONTRIBUTING.md
The Reporting Bugs and Requesting Enhancements sections are rewritten as GitHub Issues checklists with required fields and conditions.
Pull requests, testing, and docs
CONTRIBUTING.md
The Pull Requests section updates signing, testing, docs, and template requirements; the Testing section points to the strategy document; the Docs Contributions section narrows accepted contribution types.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 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 accurately reflects the main change: a documentation update to CONTRIBUTING.md.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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 Docs-only PR changes CONTRIBUTING.md; no test files or Ginkgo titles were modified, so the check is not applicable.
Test Structure And Quality ✅ Passed PR only changes CONTRIBUTING.md; no Ginkgo/spec test code was touched, so this check is not applicable.
Microshift Test Compatibility ✅ Passed Only CONTRIBUTING.md changed; no Go/e2e tests or Ginkgo declarations were added, so MicroShift compatibility is not implicated.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PASS: The PR only rewrites CONTRIBUTING.md; no Ginkgo/e2e test files or test additions were introduced, so SNO compatibility review isn’t applicable.
Topology-Aware Scheduling Compatibility ✅ Passed Only CONTRIBUTING.md changed; no manifests, controllers, or scheduling code were modified, so topology-aware scheduling is not implicated.
Ote Binary Stdout Contract ✅ Passed PR only rewrites CONTRIBUTING.md (docs); no main/init/TestMain/suite setup code was changed, so stdout-contract risk is not applicable.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PASS: Diff vs main only changes CONTRIBUTING.md; no Ginkgo/e2e test files or networking logic were added.
No-Weak-Crypto ✅ Passed PR only rewrites CONTRIBUTING.md; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret-comparison code was introduced.
Container-Privileges ✅ Passed PR only changes CONTRIBUTING.md; no container/K8s manifests were modified, so the privilege check is not applicable.
No-Sensitive-Data-In-Logs ✅ Passed Docs-only CONTRIBUTING.md changes; no logging statements or secret-bearing output were added.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci openshift-ci Bot requested review from adolfo-ab and aguidirh June 23, 2026 17:27
@openshift-ci

openshift-ci Bot commented Jun 23, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dorzel
Once this PR has been reviewed and has the lgtm label, please assign aguidirh 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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
CONTRIBUTING.md (1)

14-14: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Markdown heading style inconsistency.

The guide uses ATX-style headers (# syntax) but the project's markdownlint configuration expects setext-style headers (underline with === or ---). For consistency, convert these headings to setext style to match the linter's expectations.

💫 Proposed fix for heading style conversion
-## Development
+Development
+===========

 Active development happens in the root directory (v2). Code under `v1/` is deprecated. Please do not submit changes there.

 Development workflow:

-## Reporting Bugs
+Reporting Bugs
+==============

 Please submit bug reports as GitHub Issues using our [template](.github/ISSUE_TEMPLATE.md). Include:

-## Requesting Enhancements
+Requesting Enhancements
+======================

 1. A concise title and description of the modification

-## Pull Requests
+Pull Requests
+=============

 When submitting pull requests, please ensure the following:

-## Testing
+Testing
+=======

 See our [testing strategy](docs/testing/README.md) for guidelines on testing levels and principles.

-## Docs Contributions
+Docs Contributions
+==================

Also applies to: 31-31, 39-39, 47-47, 55-55, 59-59

🤖 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` at line 14, The markdown headings in CONTRIBUTING.md use
ATX-style headers (# and ## syntax) but the project's markdownlint configuration
requires setext-style headers with underlines. Convert all ATX-style headers to
setext-style by replacing the hash symbols with underlines using equals signs
(===) for level-one headings and hyphens (---) for level-two headings. This
applies to the "Development" heading at line 14 and the additional headings at
lines 31, 39, 47, 55, and 59 mentioned in the comment.

Source: Linters/SAST tools

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

Nitpick comments:
In `@CONTRIBUTING.md`:
- Line 14: The markdown headings in CONTRIBUTING.md use ATX-style headers (# and
## syntax) but the project's markdownlint configuration requires setext-style
headers with underlines. Convert all ATX-style headers to setext-style by
replacing the hash symbols with underlines using equals signs (===) for
level-one headings and hyphens (---) for level-two headings. This applies to the
"Development" heading at line 14 and the additional headings at lines 31, 39,
47, 55, and 59 mentioned in the comment.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 1f60b27a-7137-452a-a168-a1c05ef6b86a

📥 Commits

Reviewing files that changed from the base of the PR and between 507b46a and 592f5d5.

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

@aguidirh aguidirh 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.

Hi @dorzel,

I added few comments, but overall LGTM.

Comment thread CONTRIBUTING.md Outdated
Comment thread CONTRIBUTING.md
@openshift-ci

openshift-ci Bot commented Jun 30, 2026

Copy link
Copy Markdown

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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.

3 participants