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 repository-level Fullsend support for issue and pull request events.
  • Introduced a command to stop automated fix actions on a pull request when needed.
  • Enabled issue creation for selected repositories only, with controlled access settings.

[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: dfedfa1c-17de-474f-a6db-0b10177b9cce

📥 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 issue, issue_comment, pull_request, and pull_request_review events to the reusable Fullsend dispatch workflow. The workflow also handles /fs-fix-stop pull request comments by applying a fullsend-no-fix label and posting a reply.

Changes

Fullsend integration

Layer / File(s)	Summary
Per-repo config .fullsend/config.yaml	Defines the Fullsend config version, role assignments, and an allowlist of repositories for issue creation.
Event dispatch .github/workflows/fullsend.yaml	Sets workflow permissions and event triggers, then forwards matching events to the pinned reusable Fullsend dispatch workflow with event data, config values, URLs, and secrets.
/fs-fix-stop handling .github/workflows/fullsend.yaml	Adds the PR comment gate for /fs-fix-stop, creates or applies the fullsend-no-fix label, and posts the comment that explains how to re-enable fixes.

Sequence Diagram(s)

Event dispatch

sequenceDiagram
  participant GitHub
  participant fullsend as fullsend workflow
  participant reusable as reusable-dispatch.yml
  GitHub->>fullsend: issue, issue_comment, pull_request, or pull_request_review event
  fullsend->>reusable: call pinned workflow with event action, config URL, and secrets

Loading

Stop-fix command

sequenceDiagram
  participant Contributor
  participant GitHub
  participant fullsend as fullsend workflow
  participant gh as GitHub CLI
  Contributor->>GitHub: `/fs-fix-stop` pull request comment
  GitHub->>fullsend: issue_comment event
  fullsend->>gh: create or apply fullsend-no-fix label
  gh->>GitHub: apply label and post re-enable comment

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[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