Skip to content

[scanner] fix: add CODEOWNERS to enforce code review on PRs#5898

Merged
kubestellar-hive[bot] merged 1 commit into
mainfrom
scanner/fix-5881
Jun 11, 2026
Merged

[scanner] fix: add CODEOWNERS to enforce code review on PRs#5898
kubestellar-hive[bot] merged 1 commit into
mainfrom
scanner/fix-5881

Conversation

@kubestellar-hive

Copy link
Copy Markdown
Contributor

Fixes #5881

Adds explicit CODEOWNERS rules for sensitive directories (cluster-objects/, Dockerfile*, .github/workflows/) to ensure supply-chain-critical paths always require an approving review before merge.

Add explicit CODEOWNERS rules for sensitive directories (cluster-objects/,
Dockerfile*, .github/workflows/) to ensure supply-chain-critical paths
always require an approving review before merge.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: sec-check <sec-check@hive.local>
Copilot AI review requested due to automatic review settings June 11, 2026 15:56

Copilot AI 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.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Jun 11, 2026
@kubestellar-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@netlify

netlify Bot commented Jun 11, 2026

Copy link
Copy Markdown

Deploy Preview for kubestellar-docs failed. Why did it fail? →

Name Link
🔨 Latest commit ed805e1
🔍 Latest deploy log https://app.netlify.com/projects/kubestellar-docs/deploys/6a2adaa2ac87040008488e03

@kubestellar-prow kubestellar-prow Bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jun 11, 2026
@kubestellar-prow

Copy link
Copy Markdown

Hi @kubestellar-hive[bot]. Thanks for your PR.

I'm waiting for a kubestellar member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@kubestellar-hive
kubestellar-hive Bot merged commit 9ea2c80 into main Jun 11, 2026
10 of 16 checks passed
@kubestellar-prow
kubestellar-prow Bot deleted the scanner/fix-5881 branch June 11, 2026 16:17
@github-actions

Copy link
Copy Markdown
Contributor

Thank you for your contribution! Your PR has been merged.

Check out what's new:

Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey

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

Labels

copilot dco-signoff: yes Indicates the PR's author has signed the DCO. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[sec-check] HIGH: Code-Review score 5/10 — only 13 of 25 recent changesets reviewed (Scorecard #69)

1 participant