Skip to content

chore(SREP-4482, SREP-4486, SREP-4800: Boilerplate Update for Agentic SDLC Rollout)#430

Open
devppratik wants to merge 1 commit into
openshift:masterfrom
devppratik:rosa-730-boilerplate-update
Open

chore(SREP-4482, SREP-4486, SREP-4800: Boilerplate Update for Agentic SDLC Rollout)#430
devppratik wants to merge 1 commit into
openshift:masterfrom
devppratik:rosa-730-boilerplate-update

Conversation

@devppratik
Copy link
Copy Markdown

What type of PR is this?

boilerplate

What this PR does / why we need it?

This PR moves the changes introduced in boilerplate for Agentic SDLC Rollout into MVP for ocm-agent-operator.
Related BP MRs

Which Jira/Github issue(s) this PR fixes?

Part of Rollout for Agentic SDLC -

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 15, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 15, 2026

@devppratik: This pull request references SREP-4482 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.

This pull request references SREP-4486 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.

This pull request references SREP-4800 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 type of PR is this?

boilerplate

What this PR does / why we need it?

This PR moves the changes introduced in boilerplate for Agentic SDLC Rollout into MVP for ocm-agent-operator.
Related BP MRs

Which Jira/Github issue(s) this PR fixes?

Part of Rollout for Agentic SDLC -

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
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 15, 2026

Warning

Rate limit exceeded

@devppratik has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 27 minutes and 14 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 712e4e30-0196-4681-9449-37f5159563d4

📥 Commits

Reviewing files that changed from the base of the PR and between 3f3b57f and 4383f86.

⛔ Files ignored due to path filters (8)
  • boilerplate/_data/backing-image-tag is excluded by !boilerplate/**
  • boilerplate/_data/last-boilerplate-commit is excluded by !boilerplate/**
  • boilerplate/openshift/golang-osd-operator/.codecov.yml is excluded by !boilerplate/**
  • boilerplate/openshift/golang-osd-operator/OWNERS_ALIASES is excluded by !boilerplate/**
  • boilerplate/openshift/golang-osd-operator/golangci.yml is excluded by !boilerplate/**
  • boilerplate/openshift/golang-osd-operator/pre-commit-config.yaml is excluded by !boilerplate/**
  • boilerplate/openshift/golang-osd-operator/standard.mk is excluded by !boilerplate/**
  • boilerplate/openshift/golang-osd-operator/update is excluded by !boilerplate/**
📒 Files selected for processing (6)
  • .ci-operator.yaml
  • .codecov.yml
  • .pre-commit-config.yaml
  • OWNERS_ALIASES
  • build/Dockerfile
  • build/Dockerfile.olm-registry
✨ 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 and usage tips.

@openshift-ci openshift-ci Bot requested review from aliceh and wshearn May 15, 2026 11:18
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 15, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: devppratik
Once this PR has been reviewed and has the lgtm label, please assign bergmannf 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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 15, 2026

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

@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.44%. Comparing base (3f3b57f) to head (4383f86).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #430   +/-   ##
=======================================
  Coverage   72.44%   72.44%           
=======================================
  Files          11       11           
  Lines         704      704           
=======================================
  Hits          510      510           
  Misses        173      173           
  Partials       21       21           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment thread .codecov.yml
Comment on lines +11 to +18
project:
default:
target: 35%
threshold: 1%
patch:
default:
target: 50%
threshold: 1%
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.

What effect will this have on other PRs for this repo? Will it prevent them from passing until there is sufficient coverage or is it only for new code?

Comment thread .pre-commit-config.yaml
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.

Are these rules also enforced server-side during CI or just as part of local pre-commit hooks?

Comment thread .pre-commit-config.yaml
# Auto-fix hooks (trailing-whitespace, end-of-file-fixer) will correct
# pre-existing violations on the first run. Stage and commit those fixes
# separately before day-to-day use.
#
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.

Suggested change
#
# Fix commits can be excluded from git blame
# https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-filefile
#

It would be a good idea to add these instructions to the Boilerplate file as well.

Comment thread .pre-commit-config.yaml
# =============================================================================
#
# INSTALL
# pip install pre-commit
Copy link
Copy Markdown
Contributor

@dem4gus dem4gus May 18, 2026

Choose a reason for hiding this comment

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

Suggested change
# pip install pre-commit
# pip install 'pre-commit==4.6.0'

Golden Rule 15 requires version pinning of dependencies and this needs to apply here as well. The change should be made in Boilerplate and pulled into the projects that consume it.

Also see this comment for more general suggestions regarding Python dependencies.

@dem4gus
Copy link
Copy Markdown
Contributor

dem4gus commented May 18, 2026

Why was a new PR opened for this? #426 should have been updated with the requested changes to preserve the discussion log.

@dem4gus
Copy link
Copy Markdown
Contributor

dem4gus commented May 18, 2026

Python dependency management is typically done through virtual environments to ensure consistency. Although pip has been the de facto tool to manage Python dependencies in the past, I would strongly urge the use of uv due to its improvements over pip. Unlike pip, uv includes both virtual environment and dependency management. It also generates a dependency lock file that includes a package hash, which will provide further protection against supply-chain attacks. Setup instructions for uv can be added to a more detailed docs/pre-commit.md file that is sourced from Boilerplate and referenced here.

# Create pyproject.toml
$ uv init --bare

# add dependency and generate uv.lock file
$ uv add --dev pre-commit==4.6.0

If pyproject.toml already exists the setup becomes a single command.

$ uv sync

From here pre-commit can be called by activating the virtual environment and using the same command.

$ source .venv/bin/activate
$ pre-commit install

npecka added a commit to npecka/splunk-forwarder-operator that referenced this pull request May 20, 2026
Regenerated boilerplate-managed files from image-v8.3.6:
- Updated golang-osd-operator and golang-osd-e2e conventions
- Added pre-commit hooks configuration
- Updated build Dockerfiles with latest UBI base images
- Updated OWNERS_ALIASES and codecov configuration
- Updated linting and testing configurations

This follows the same pattern as PR openshift#430 to bring in
the latest boilerplate updates for CVE-2026-25679.
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.

4 participants