chore: initialize fullsend-0.21.0 per-repo installation by samanthajayasinghe · Pull Request #961 · openshift/backplane-cli · GitHub
Skip to content

chore: initialize fullsend-0.21.0 per-repo installation#961

Closed
samanthajayasinghe wants to merge 1 commit into
openshift:mainfrom
samanthajayasinghe:fullsend/scaffold-install
Closed

chore: initialize fullsend-0.21.0 per-repo installation#961
samanthajayasinghe wants to merge 1 commit into
openshift:mainfrom
samanthajayasinghe:fullsend/scaffold-install

Conversation

@samanthajayasinghe

@samanthajayasinghe samanthajayasinghe commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

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

coderabbitai Bot commented Jun 26, 2026

Copy link
Copy Markdown

@openshift-ci openshift-ci Bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jun 26, 2026
@openshift-ci

openshift-ci Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

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

@openshift-ci openshift-ci Bot requested review from feichashao and typeid June 26, 2026 04:18
@codecov-commenter

Copy link
Copy Markdown

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

Impacted file tree graph

@@           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

openshift-ci Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants