chore: initialize fullsend-0.21.0 per-repo installation

[samanthajayasinghe]

What type of PR is this?

• fix (Bug Fix)
• feat (New Feature)
• docs (Documentation)
• test (Test Coverage)
• chore (Clean Up / Maintenance Tasks)
• other (Anything that doesn't fit the above)

What this PR does / Why we need it?

Which Jira/Github issue(s) does this PR fix?

• Related Issue #
• Closes #

Special notes for your reviewer

Unit Test Coverage

Guidelines

• If it's a new sub-command or new function to an existing sub-command, please cover at least 50% of the code
• If it's a bug fix for an existing sub-command, please cover 70% of the code

Test coverage checks

• Added unit tests
• Created jira card to add unit test
• This PR may not need unit tests

Pre-checks (if applicable)

• Ran unit tests locally
• Validated the changes in a cluster
• Included documentation changes with PR
• Backward compatible

/label tide/merge-method-squash

Summary by CodeRabbit

• New Features

  • Added per-repository setup for Fullsend, enabling issue creation and role-based workflows for selected repositories.
  • Introduced automated handling for repository events and pull request activity to keep Fullsend in sync.

• Bug Fixes

  • Added a command-based way to pause fix-related automation on a pull request and re-enable it later.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 825c534a-6bc1-4658-82c4-6b118555f070

📥 Commits

Reviewing files that changed from the base of the PR and between 0f4969f and a309c60.

📒 Files selected for processing (10)

• .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/schemas/.gitkeep
• .fullsend/customized/scripts/.gitkeep
• .fullsend/customized/skills/.gitkeep
• .github/workflows/fullsend.yaml

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

---

Walkthrough

Adds a per-repo Fullsend config and a GitHub Actions workflow that forwards supported issue, comment, PR, and review events to a reusable Fullsend dispatch workflow. It also adds a /fs-fix-stop command path that labels pull requests and posts a disabling comment.

Changes

Fullsend per-repo setup

Layer / File(s)	Summary
Per-repo config .fullsend/config.yaml	Defines Fullsend version 1, enabled roles, and issue creation targets restricted to the two listed repositories.
Workflow triggers and dispatch .github/workflows/fullsend.yaml	Sets the fullsend workflow name, workflow permissions, event triggers, and the reusable dispatch call with install mode and GCP inputs.
Stop-fix command handling .github/workflows/fullsend.yaml	Checks /fs-fix-stop PR comments, adds the fullsend-no-fix label, and posts a PR comment disabling fix-agent runs.

Sequence Diagram(s)

sequenceDiagram
  participant GitHub
  participant fullsend_workflow as fullsend workflow
  participant reusable_dispatch as reusable-dispatch.yml
  participant PR as Pull Request

  GitHub->>fullsend_workflow: issue, PR, and review events
  fullsend_workflow->>reusable_dispatch: reusable workflow dispatch
  GitHub->>fullsend_workflow: /fs-fix-stop issue_comment on a PR
  fullsend_workflow->>PR: add fullsend-no-fix label
  fullsend_workflow->>PR: post disabling comment

Loading

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

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

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 53.99%. Comparing base (0f4969f) to head (a309c60).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #961   +/-   ##
=======================================
  Coverage   53.99%   53.99%           
=======================================
  Files          82       82           
  Lines        6323     6323           
=======================================
  Hits         3414     3414           
  Misses       2463     2463           
  Partials      446      446           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: samanthajayasinghe

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [samanthajayasinghe]

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