chore: initialize fullsend per-repo installation

[samanthajayasinghe]

This PR adds the fullsend scaffold files for per-repo installation.

Merge this PR to activate fullsend workflows.

Summary by CodeRabbit

• New Features
  • Added automated issue, comment, pull request, and review event processing through Fullsend.
  • Added support for stopping automated fixes on a pull request with a command, including a status label and guidance for re-enabling fixes.
  • Added repository-level configuration for Fullsend roles, approved sources, and issue creation permissions.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

• OWNERS

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

[coderabbitai]

Walkthrough

Adds per-repository Fullsend configuration and a managed GitHub Actions workflow. The workflow dispatches selected repository events to Fullsend and supports stopping fix agents through an authorized pull request comment.

Changes

Fullsend automation

Layer / File(s)	Summary
Fullsend configuration and event dispatch .fullsend/config.yaml, .github/workflows/fullsend.yaml	Defines enabled Fullsend roles, allowed sources, and issue-creation repositories. Routes selected GitHub events to the pinned reusable workflow with required permissions and secrets.
Pull request fix-agent control .github/workflows/fullsend.yaml	Recognizes authorized /fs-fix-stop comments, applies the fullsend-no-fix label, and posts instructions for re-enabling fix agents.

Estimated code review effort: 2 (Simple) | ~10 minutes

Sequence Diagram(s)

sequenceDiagram
  participant GitHub
  participant fullsend.yaml
  participant FullsendDispatch
  participant PullRequest

  GitHub->>fullsend.yaml: Issue, comment, pull request, or review event
  fullsend.yaml->>FullsendDispatch: Dispatch event with configuration and secrets
  FullsendDispatch-->>fullsend.yaml: Process Fullsend event

  GitHub->>fullsend.yaml: Authorized /fs-fix-stop pull request comment
  fullsend.yaml->>PullRequest: Apply fullsend-no-fix label
  fullsend.yaml->>PullRequest: Post re-engagement instructions

Loading

Suggested reviewers: joshbranham, sam-nguyen7

🚥 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 summarizes the addition of Fullsend per-repository configuration and workflow files.
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	The pull request changes only Fullsend YAML and placeholder files; it adds or modifies no Ginkgo test declarations or test titles.
Test Structure And Quality	✅ Passed	The PR adds only YAML workflow/configuration and .gitkeep files. It changes no *_test.go files and contains no Ginkgo test constructs, so this check is not applicable.
Microshift Test Compatibility	✅ Passed	The PR adds only Fullsend YAML configuration and workflow files; it adds no Ginkgo e2e tests or OpenShift API references requiring MicroShift compatibility review.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The PR adds only Fullsend configuration, workflow, and placeholder files; it adds no Ginkgo e2e tests or multi-node test assumptions.
Topology-Aware Scheduling Compatibility	✅ Passed	The patch adds only Fullsend configuration, a GitHub Actions workflow, and empty marker files; it adds no deployment manifests, operator/controller code, or Kubernetes scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The pull request changes only Fullsend YAML and .gitkeep files. It adds no OTE binary, suite setup, or process-level stdout writes.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The PR adds only Fullsend YAML/configuration files and placeholder directories. It adds no Ginkgo e2e tests, so this compatibility check is not applicable.
No-Weak-Crypto	✅ Passed	Added files contain only YAML and .gitkeep files. Searches found no weak crypto primitives, crypto APIs, custom crypto, or secret/token comparisons; the 40-hex value only pins a reusable workflow.
Container-Privileges	✅ Passed	The changed YAML has no container/Kubernetes privilege declarations, no prohibited capabilities, and no container block; the only runner is GitHub-hosted ubuntu-24.04.
No-Sensitive-Data-In-Logs	✅ Passed	The workflow passes secrets as reusable-workflow inputs but does not print them; its only PR comment is static, and no sensitive literals or logging commands are present.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[coderabbitai]

Actionable comments posted: 2

🤖 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 @.github/workflows/fullsend.yaml:
- Around line 45-51: Add the fullsend_version input with value v0.32.0 to the
with block of the reusable-dispatch.yml call, keeping the CLI version aligned
with the pinned workflow reference.
- Around line 22-28: Move the write permissions for actions, contents, issues,
and pull-requests from the workflow-level permissions block to
jobs.dispatch.permissions. Set the top-level permissions to an empty mapping,
and preserve the existing packages: read and id-token: write scopes only where
required by their jobs so stop-fix remains narrowly scoped.

🪄 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: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 4c610da3-ef56-4a5a-a7d8-3d1add2c8fc3

📥 Commits

Reviewing files that changed from the base of the PR and between 9fb7f0c and ad2f5fb.

📒 Files selected for processing (12)

• .fullsend/config.yaml
• .fullsend/customized/agents/.gitkeep
• .fullsend/customized/env/.gitkeep
• .fullsend/customized/harness/.gitkeep
• .fullsend/customized/plugins/.gitkeep
• .fullsend/customized/policies/.gitkeep
• .fullsend/customized/profiles/.gitkeep
• .fullsend/customized/providers/.gitkeep
• .fullsend/customized/schemas/.gitkeep
• .fullsend/customized/scripts/.gitkeep
• .fullsend/customized/skills/.gitkeep
• .github/workflows/fullsend.yaml

[RaphaelBut]

Otherwise looks good to me! <3

[coderabbitai]

Actionable comments posted: 1

🤖 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 @.github/workflows/fullsend.yaml:
- Around line 40-44: Update the dispatch job condition in the workflow so the
non-Bot branch also requires github.event.comment.body to differ from
'/fs-fix-stop', preventing that command from entering dispatch while preserving
the existing event and Bot checks.

🪄 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: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: ac5b7b6d-7a59-463e-841b-e10a3e6320a8

📥 Commits

Reviewing files that changed from the base of the PR and between 565a2c1 and e1062ac.

📒 Files selected for processing (12)

• .fullsend/config.yaml
• .fullsend/customized/agents/.gitkeep
• .fullsend/customized/env/.gitkeep
• .fullsend/customized/harness/.gitkeep
• .fullsend/customized/plugins/.gitkeep
• .fullsend/customized/policies/.gitkeep
• .fullsend/customized/profiles/.gitkeep
• .fullsend/customized/providers/.gitkeep
• .fullsend/customized/schemas/.gitkeep
• .fullsend/customized/scripts/.gitkeep
• .fullsend/customized/skills/.gitkeep
• .github/workflows/fullsend.yaml

🚧 Files skipped from review as they are similar to previous changes (1)

• .fullsend/config.yaml

[openshift-ci]

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