Skip to content

HYPERFLEET-1307 - fix: correct plugin installation command in hyperfl…#67

Open
Ruclo wants to merge 1 commit into
openshift-hyperfleet:mainfrom
Ruclo:hyperfleet-jira-instructions
Open

HYPERFLEET-1307 - fix: correct plugin installation command in hyperfl…#67
Ruclo wants to merge 1 commit into
openshift-hyperfleet:mainfrom
Ruclo:hyperfleet-jira-instructions

Conversation

@Ruclo

@Ruclo Ruclo commented Jul 1, 2026

Copy link
Copy Markdown

Summary

The install command referenced the full GitHub org/repo path instead of the marketplace name, causing a "Marketplace not found" error.

Change marketplace reference from openshift-hyperfleet/hyperfleet-claude-plugins to hyperfleet-claude-plugins

  • HYPERFLEET-1307

Test Plan

  • Unit tests added/updated
  • make test-all passes
  • make lint passes
  • Helm chart changes validated with make test-helm (if applicable)
  • Deployed to a development cluster and verified (if Helm/config changes)
  • E2E tests passed (if cross-component or major changes)

…eet-jira README

The install command referenced the full GitHub org/repo path instead of
the marketplace name, causing a "Marketplace not found" error.

- Change marketplace reference from `openshift-hyperfleet/hyperfleet-claude-plugins` to `hyperfleet-claude-plugins`
@openshift-ci

openshift-ci Bot commented Jul 1, 2026

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

@openshift-ci openshift-ci Bot requested review from ldornele and tirthct July 1, 2026 09:11
@coderabbitai

coderabbitai Bot commented Jul 1, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 98c7fed9-11cf-4ca3-9d43-ed0d7817bcce

📥 Commits

Reviewing files that changed from the base of the PR and between 15df83b and 3ec3ba1.

📒 Files selected for processing (1)
  • hyperfleet-jira/README.md
🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

  • openshift-hyperfleet/architecture (manual)
  • openshift-hyperfleet/hyperfleet-api (manual)
  • openshift-hyperfleet/hyperfleet-sentinel (manual)
  • openshift-hyperfleet/hyperfleet-adapter (manual)
  • openshift-hyperfleet/hyperfleet-broker (manual)

📝 Walkthrough

Summary by CodeRabbit

  • Documentation
    • Updated the JIRA plugin installation command in the README to use the new package reference.

Walkthrough

Single-line documentation edit in hyperfleet-jira/README.md changing the plugin install command's source identifier from hyperfleet-jira@openshift-hyperfleet/hyperfleet-claude-plugins to hyperfleet-jira@hyperfleet-claude-plugins. No code, config, or dependency manifest changes. No exported/public entity declarations altered.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Security note: No CWE/CVE applicable — this is a documentation string change, not a supply-chain artifact (no lockfile, CI/CD config, .gitattributes, or IDE config touched). Verify the new plugin source identifier hyperfleet-jira@hyperfleet-claude-plugins resolves to the intended trusted registry/org before merge — an unqualified or ambiguous package identifier can be a namespace-confusion / dependency-substitution vector (CWE-829: Inclusion of Functionally Unrelated Code) if the plugin resolution mechanism permits lookups outside the expected org.

Suggested labels: documentation

Suggested reviewers: None specified — assign per hyperfleet-jira README ownership.

🚥 Pre-merge checks | ✅ 11
✅ Passed checks (11 passed)
Check name Status Explanation
Title check ✅ Passed The title matches the README plugin install command fix and the HYPERFLEET-1307 context.
Description check ✅ Passed The description directly explains the marketplace path fix and references the changed install command.
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.
Sec-02: Secrets In Log Output ✅ Passed No non-test/example Go sources and no log statements with token/password/credential/secret fields; README-only change. CWE-532 not triggered.
No Hardcoded Secrets ✅ Passed README-only docs change; no CWE-798/CWE-259 secrets, credentialed URLs, or long base64 literals found. Token text is a placeholder example.
No Weak Cryptography ✅ Passed Changed files are docs/workflows/scripts only; no crypto/md5/des/rc4, SHA1-for-security, ECB, custom crypto, or secret comparisons found (CWE-327/CWE-208).
No Injection Vectors ✅ Passed PASS: PR only updates README command text; no SQL/exec/template/yaml sinks or untrusted-data paths changed (CWE-89/78/79/502).
No Privileged Containers ✅ Passed No Kubernetes/OpenShift manifests, Helm templates, or Dockerfiles in the PR contain privileged/root/host* settings; no CWE-250/266 issue found.
No Pii Or Sensitive Data In Logs ✅ Passed README-only change; no logging statements or sensitive data exposure introduced. No CWE-532/CWE-200 finding.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
✨ Simplify code
  • Create PR with simplified code

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant