Skip to content

chore: update fullsend shim workflow - #960

Open
fullsend-ai-fullsend[bot] wants to merge 2 commits into
mainfrom
fullsend/onboard
Open

chore: update fullsend shim workflow#960
fullsend-ai-fullsend[bot] wants to merge 2 commits into
mainfrom
fullsend/onboard

Conversation

@fullsend-ai-fullsend

Copy link
Copy Markdown
Contributor

This PR updates the fullsend shim workflow to match the current template in the .fullsend config repo.

The shim content has drifted from the template — this brings it back in sync.

@fullsend-ai-review

fullsend-ai-review Bot commented Jul 6, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 8:55 PM UTC · Completed 9:00 PM UTC
Commit: 14477fe · View workflow run →

@fullsend-ai-review

fullsend-ai-review Bot commented Jul 6, 2026

Copy link
Copy Markdown

Review

Findings

High

  • [security/supply-chain] .github/workflows/fullsend.yaml:44 — Replacing the SHA-pinned reusable workflow reference (@ec21706cccc58d01588ecd842464a5afcc375ba1) with a floating branch reference (@main) removes supply-chain integrity for this external workflow call. The dispatch.yml workflow from konflux-ci/.fullsend will now resolve to whatever commit happens to be at main at invocation time. Because this workflow runs on pull_request_target with id-token: write and actions: write permissions, any future push to main in the .fullsend repo instantly changes what privileged code executes in this repository without any review gate in this repo. Every other uses: directive across all workflows in this repository is SHA-pinned, making this an inconsistency with the established security convention.
    Remediation: Keep the SHA-pinned reference. If the intent is to update to a newer commit of dispatch.yml, pin to the new SHA with the branch name as a trailing comment (e.g., uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@<new-sha> # main), consistent with every other workflow reference in this repository.

  • [protected-path] .github/workflows/fullsend.yaml — This PR modifies a file under the .github/ protected path. The PR has no linked issue providing authorization for changes to governance/infrastructure files. Human approval is required for all protected-path changes.


Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR
Previous run

Review

Findings

High

  • [supply-chain integrity regression] .github/workflows/fullsend.yaml:44 — Replaces a SHA-pinned reusable workflow reference (@ec21706cccc58d01588ecd842464a5afcc375ba1) with a mutable branch reference (@main). Every other uses: directive across all workflows in this repository is SHA-pinned for supply-chain integrity, and the most recent commit (b71d1e0, PR Pin kindest/node image by digest #1010) explicitly established this policy. A mutable @main reference means any future commit to konflux-ci/.fullsend will execute automatically in this repository's context without review.
    Remediation: Pin to the new commit SHA with a trailing comment (e.g., @<new-sha> # main), matching the convention used throughout the repository.

  • [permission-expansion] .github/workflows/fullsend.yaml:44 — The unpinned workflow reference inherits actions: write and id-token: write permissions via pull_request_target. A compromised or malicious upstream commit to konflux-ci/.fullsend would gain OIDC token access across all enrolled repositories without any review gate in this repo.
    Remediation: Keep the reference SHA-pinned. Update the SHA when the upstream workflow changes.

  • [contradicts-project-direction] .github/workflows/fullsend.yaml:44 — The most recent commit to this file (b71d1e0, PR Pin kindest/node image by digest #1010) was titled "Pin kindest/node image by digest for supply-chain integrity." This PR reverses that security posture for the fullsend workflow reference without explaining why the trade-off is different for this dependency.
    Remediation: Document why this dependency should be unpinned, or pin it to match the project's supply-chain integrity policy.

  • [protected-path] .github/workflows/fullsend.yaml — This file is under .github/, a protected path requiring human approval. The PR has no linked issue and does not provide sufficient justification for modifying governance files.
    Remediation: Link to an issue or provide explicit justification for the governance file change.

Medium

  • [scope-classification-mismatch] .github/workflows/fullsend.yaml:44 — PR titled "chore: update fullsend shim workflow" but the change removes supply-chain integrity protections (SHA pinning) — this is a security-relevant change, not a maintenance chore.

  • [template-sync-claim-unverified] — PR body claims template drift without linking to the canonical template or showing a diff. The claim that this syncs with an upstream template is unverified.

  • [author-conflict-of-interest] — The PR author (fullsend-ai-fullsend[bot]) is part of the fullsend system, and the change removes supply-chain protections on the fullsend workflow reference. This structural conflict of interest warrants extra human scrutiny.

  • [consistency] .github/workflows/fullsend.yaml:44 — Uses @main while all other workflow references in the repository use SHA-pinned format with trailing version/branch comments.

Low

  • [missing-authorization] .github/workflows/fullsend.yaml — No linked issue or Jira ID. Per AGENTS.md conventions, commits should include a Jira ID (KFLUXINFRA-XXX format).

Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR
Previous run (2)

Review

Findings

High

  • [supply-chain] .github/workflows/fullsend.yaml:44 — The reusable workflow reference is changed from a pinned commit SHA (ec21706cccc58d01588ecd842464a5afcc375ba1) to the mutable branch reference @main. This workflow runs on privileged event triggers including pull_request_target and issue_comment, and has top-level permissions for actions: write and id-token: write. A mutable branch reference means anyone with write access to the .fullsend repository can change what code executes in this repository's CI context without any review or visibility in this repository. The OIDC id-token: write permission is particularly sensitive — the called workflow can mint OIDC tokens scoped to this repository. Additionally, the workflow behavior is no longer deterministic — it can change without any commit to this repository.
    Remediation: Keep the SHA-pinned reference. If updating to a newer version of dispatch.yml, pin to the new SHA and retain the # main comment for traceability: uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@<new-SHA> # main.

  • [protected-path] .github/workflows/fullsend.yaml — This PR modifies files under the protected path .github/. No linked issue justifies the change to governance/infrastructure files. Human approval is always required for protected-path changes.

Medium

  • [dependency-pinning-convention] .github/workflows/fullsend.yaml:44 — All 30+ workflow references across 9 workflow files in this repository use pinned SHA commits with a trailing comment indicating the branch/version (e.g., @<SHA> # main). This change is the only reference that would use a bare branch name, violating the established repository convention.
    Remediation: Revert to the pinned SHA pattern: uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@<current-SHA> # main.

Low

  • [missing-authorization] .github/workflows/fullsend.yaml — Security-posture change (SHA pinning to floating branch reference) submitted without a linked issue explaining the rationale for the policy change.
    Remediation: Link an issue or add PR body rationale explaining why floating branch references are acceptable for this workflow.

Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR
Previous run (3)

Review

Findings

High

  • [supply chain / reproducibility] .github/workflows/fullsend.yaml:44 — The change replaces a pinned commit SHA (ec21706cccc58d01588ecd842464a5afcc375ba1) with a mutable branch reference (@main) for the reusable workflow konflux-ci/.fullsend/.github/workflows/dispatch.yml. All 18 external action/workflow references across 7 workflow files in this repository are SHA-pinned. This breaks that universal convention and introduces supply-chain risk: any push to .fullsend main will immediately change the code executed in this repo's CI. See also: [permission-expansion] finding at this location.
    Remediation: Pin to the current commit SHA: uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@701e62a9c6f104ed68f8d4085d9c3b8bad3a82e4 # main

  • [permission-expansion] .github/workflows/fullsend.yaml:44 — SHA-pinned reusable workflow reference replaced with mutable branch reference (@main). This workflow runs on pull_request_target with top-level permissions including actions:write and id-token:write (OIDC). A compromise or malicious push to the .fullsend repo's main branch would immediately gain these elevated permissions in this repository without any review gate. See also: [supply chain / reproducibility] finding at this location.
    Remediation: Keep the reference SHA-pinned (e.g., @701e62a9c6f104ed68f8d4085d9c3b8bad3a82e4 # main).

  • [protected-path] .github/workflows/fullsend.yaml — This PR modifies a file under .github/ (protected path). The PR has no linked issue justifying the change. Human approval is always required for protected-path changes.
    Remediation: Link an issue that documents the rationale for modifying this governance/infrastructure file.

Low

  • [missing-authorization] .github/workflows/fullsend.yaml:44 — Non-trivial workflow change with no linked issue. The change unpins the fullsend dispatch workflow from a fixed SHA to track main branch, which alters the security and deployment model.
    Remediation: Create a linked issue documenting why unpinning is authorized.

Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR
Previous run (4)

Review — PR #960

Verdict: request-changes

Summary

This PR changes the fullsend shim workflow (.github/workflows/fullsend.yaml) to reference the reusable workflow dispatch.yml from konflux-ci/.fullsend by branch name (@main) instead of a pinned commit SHA (@ec21706cccc58d01588ecd842464a5afcc375ba1). While the PR description says this syncs the shim with the current template, the change removes a concrete supply chain security control from a workflow that runs with elevated permissions.

Findings

🔴 HIGH — Supply chain: reusable workflow unpinned from SHA to mutable branch reference

File: .github/workflows/fullsend.yaml, line 44

The uses directive for the reusable workflow is changed from a SHA-pinned reference to a mutable branch reference:

-    uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@ec21706cccc58d01588ecd842464a5afcc375ba1 # main
+    uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@main

Why this matters:

This workflow declares elevated permissions — id-token: write (OIDC token minting), actions: write (workflow dispatch) — and is triggered by pull_request_target, which runs with write access to the base repository and access to repository secrets. SHA pinning ensures that the exact, reviewed version of the external workflow executes. Using a branch reference (@main) means any future commit to the main branch of konflux-ci/.fullsend — including unauthorized or compromised changes — will automatically execute with these elevated permissions in the context of this repository.

GitHub's security hardening guide explicitly recommends pinning to full-length commit SHAs for supply chain integrity.

Mitigating factors:

  • The referenced repo (konflux-ci/.fullsend) is in the same GitHub organization
  • This is a managed shim workflow (the fullsend bot syncs it with a centralized template)
  • The shim does not check out PR code, limiting direct pwn-request exposure

These mitigating factors reduce practical risk but do not eliminate it. A compromise of the .fullsend repo's main branch would cascade to every enrolled repo. SHA pinning provides a concrete defense-in-depth layer against that scenario.

Remediation: If the intent is to update to a newer version of dispatch.yml, pin to the current commit SHA on main and annotate with a branch comment for traceability:

uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@<current-sha> # main

1 finding | 1 high


Labels: PR modifies GitHub Actions workflow with security implications

Previous run (5)

Review — PR #960

Verdict: request-changes

Summary

This PR replaces a SHA-pinned reusable workflow reference with a branch reference (@main) in .github/workflows/fullsend.yaml. While the intent is to sync the shim with the current fullsend template, this change weakens supply chain security and breaks an established project convention.

Findings

🔴 [high] Supply chain: SHA pin removed from reusable workflow reference

File: .github/workflows/fullsend.yaml, line 44

The change replaces a commit-SHA-pinned reference:

uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@ec21706cccc58d01588ecd842464a5afcc375ba1 # main

with an unpinned branch reference:

uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@main

Why this matters:

  1. Breaks project convention. Every other action and workflow reference across all six workflow files in this repository is SHA-pinned (22 references total). This would be the only unpinned reference, creating an inconsistency in the project's supply chain security posture.

  2. Elevated permissions at risk. This workflow declares id-token: write (OIDC token generation) and actions: write. An unpinned reference means any future commit to main of konflux-ci/.fullsend is automatically trusted — if that repository is compromised, the attacker gains access to these permissions without any review gate in the consuming repo.

  3. No review gate for dispatch changes. With a SHA pin, updating the referenced workflow version requires a PR to this repo, which goes through code review. With @main, changes propagate silently.

Mitigating factors acknowledged:

  • The referenced repo (konflux-ci/.fullsend) is within the same GitHub organization
  • The shim uses pull_request_target, so PR authors cannot modify the workflow itself
  • The shim does not check out PR code, preventing "pwn request" attacks

Remediation: Keep the SHA-pinned reference. If dispatch.yml has been updated on main, pin to its current HEAD commit SHA:

uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@<current-sha> # main

This maintains the project's consistent SHA-pinning convention while still tracking the latest version.

Dimensions Reviewed

Dimension Status Notes
Correctness Syntactically valid; no logic errors
Security SHA pin removal weakens supply chain security
Intent & coherence Intent to sync with template is clear, but the template's approach conflicts with this repo's established convention
Style/conventions Breaks the project-wide SHA-pinning convention
Documentation No documentation impact
Cross-repo contracts No contract changes

fullsend-ai-review[bot]

This comment was marked as outdated.

@codecov-commenter

codecov-commenter commented Jul 6, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.92%. Comparing base (8c12c4b) to head (b3cfa76).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #960   +/-   ##
=======================================
  Coverage   76.92%   76.92%           
=======================================
  Files          26       26           
  Lines        2817     2817           
=======================================
  Hits         2167     2167           
  Misses        452      452           
  Partials      198      198           
Flag Coverage Δ
e2e-tests 30.35% <ø> (+0.07%) ⬆️
unit-tests 73.98% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8c12c4b...b3cfa76. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@fullsend-ai-review

fullsend-ai-review Bot commented Jul 17, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 8:53 AM UTC · Completed 8:57 AM UTC
Commit: 37b10e4 · View workflow run →

fullsend-ai-review[bot]

This comment was marked as outdated.

@qodo-app-for-konflux-ci

qodo-app-for-konflux-ci Bot commented Jul 31, 2026

Copy link
Copy Markdown

PR Summary by Qodo

Update fullsend shim workflow to track upstream template

⚙️ Configuration changes 🕐 Less than 5 minutes

Grey Divider

AI Description

• Switch fullsend shim to use the upstream reusable workflow from the main branch.
• Remove the pinned commit SHA to re-align with the current .fullsend template.
Diagram

graph TD
  A["Repo workflow: fullsend.yaml"] --> B["Reusable workflow: konflux-ci/.fullsend dispatch.yml"]
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Pin to a commit SHA
  • ➕ Max reproducibility; workflow behavior won't change unexpectedly
  • ➕ Easier incident triage (exact version is known)
  • ➖ Requires manual/automated updates to stay in sync with the upstream template
  • ➖ Can drift again if updates are not maintained
2. Pin to a release tag (e.g., vX.Y) maintained in .fullsend
  • ➕ More stability than @main while still allowing controlled upgrades
  • ➕ Clear upgrade cadence and changelog-friendly
  • ➖ Requires the upstream repo to publish and maintain tags/releases
  • ➖ Still needs periodic bump PRs

Recommendation: Using @main best matches the stated goal of staying synced with the .fullsend template and avoiding drift. If workflow stability/reproducibility is a higher priority than auto-sync, prefer pinning to a commit SHA (or an upstream version tag) and use an update mechanism (e.g., scheduled bump PRs) to manage upgrades intentionally.

Files changed (1) +1 / -1

Other (1) +1 / -1
fullsend.yamlTrack upstream reusable workflow on @main +1/-1

Track upstream reusable workflow on @main

• Updates the reusable workflow reference from a pinned commit SHA to the upstream 'main' branch for 'konflux-ci/.fullsend/.github/workflows/dispatch.yml'. This brings the shim back in sync with the current upstream template.

.github/workflows/fullsend.yaml

@fullsend-ai-review

fullsend-ai-review Bot commented Jul 31, 2026

Copy link
Copy Markdown

🤖 Review · ❌ Terminated · Started 12:47 PM UTC · Ended 12:59 PM UTC
Commit: 701e62a · View workflow run →

@qodo-app-for-konflux-ci

qodo-app-for-konflux-ci Bot commented Jul 31, 2026

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Grey Divider


Action required

1. Unpinned workflow reference 🐞 Bug ⛨ Security
Description
The fullsend shim now calls konflux-ci/.fullsend using the mutable ref @main, so upstream
changes can alter what runs in this repo without a PR here. This reduces
auditability/reproducibility and increases supply-chain blast radius (this workflow requests
actions: write and id-token: write).
Code

.github/workflows/fullsend.yaml[44]

+    uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@main
Relevance

●●● Strong

Repo recently replaced @main with pinned SHA for this exact fullsend workflow in PR #949.

PR-#949
PR-#940
PR-#879

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The PR changes the reusable workflow reference from a pinned commit to @main, making the executed
workflow depend on a moving branch tip. The same file declares elevated permissions, and other
workflows in this repo consistently pin action refs to SHAs, supporting that this repo expects
immutable refs for CI dependencies.

.github/workflows/fullsend.yaml[20-24]
.github/workflows/fullsend.yaml[41-46]
.github/workflows/go-ci.yaml[14-20]
.github/workflows/test-e2e.yml[43-57]
.github/workflows/auto-merge.yaml[16-24]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`.github/workflows/fullsend.yaml` references a reusable workflow via `@main`, which is mutable and can change behavior without review in this repo.

### Issue Context
This workflow runs with elevated permissions (including `id-token: write`), so keeping the called workflow immutable improves auditability and limits supply-chain risk.

### Fix Focus Areas
- .github/workflows/fullsend.yaml[44-44]

### Suggested fix
- Replace `@main` with an immutable ref (commit SHA, or a protected/immutable tag if your org uses those).
- If you need to stay aligned with the template, update the pinned SHA as part of a reviewed/automated bump process (e.g., periodic PRs).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Context sources
✅ Compliance rules (platform): 2 rules

Grey Divider

Tip of the day
💡 Did you know, you can switch off images and animations for a plain-text comment

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Previous reviews

Review updated until commit b3cfa76 ⚖️ Balanced

Results up to commit 7d543a9 ⚖️ Balanced


🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)


Action required
1. Unpinned workflow reference 🐞 Bug ⛨ Security
Description
The fullsend shim now calls konflux-ci/.fullsend using the mutable ref @main, so upstream
changes can alter what runs in this repo without a PR here. This reduces
auditability/reproducibility and increases supply-chain blast radius (this workflow requests
actions: write and id-token: write).
Code

.github/workflows/fullsend.yaml[44]

+    uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@main
Relevance

●●● Strong

Repo recently replaced @main with pinned SHA for this exact fullsend workflow in PR #949.

PR-#949
PR-#940
PR-#879

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The PR changes the reusable workflow reference from a pinned commit to @main, making the executed
workflow depend on a moving branch tip. The same file declares elevated permissions, and other
workflows in this repo consistently pin action refs to SHAs, supporting that this repo expects
immutable refs for CI dependencies.

.github/workflows/fullsend.yaml[20-24]
.github/workflows/fullsend.yaml[41-46]
.github/workflows/go-ci.yaml[14-20]
.github/workflows/test-e2e.yml[43-57]
.github/workflows/auto-merge.yaml[16-24]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`.github/workflows/fullsend.yaml` references a reusable workflow via `@main`, which is mutable and can change behavior without review in this repo.

### Issue Context
This workflow runs with elevated permissions (including `id-token: write`), so keeping the called workflow immutable improves auditability and limits supply-chain risk.

### Fix Focus Areas
- .github/workflows/fullsend.yaml[44-44]

### Suggested fix
- Replace `@main` with an immutable ref (commit SHA, or a protected/immutable tag if your org uses those).
- If you need to stay aligned with the template, update the pinned SHA as part of a reviewed/automated bump process (e.g., periodic PRs).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Qodo Logo

github.event_name != 'issue_comment'
|| github.event.comment.user.type != 'Bot'
uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@ec21706cccc58d01588ecd842464a5afcc375ba1 # main
uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@main

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Unpinned workflow reference 🐞 Bug ⛨ Security

The fullsend shim now calls konflux-ci/.fullsend using the mutable ref @main, so upstream
changes can alter what runs in this repo without a PR here. This reduces
auditability/reproducibility and increases supply-chain blast radius (this workflow requests
actions: write and id-token: write).
Agent Prompt
### Issue description
`.github/workflows/fullsend.yaml` references a reusable workflow via `@main`, which is mutable and can change behavior without review in this repo.

### Issue Context
This workflow runs with elevated permissions (including `id-token: write`), so keeping the called workflow immutable improves auditability and limits supply-chain risk.

### Fix Focus Areas
- .github/workflows/fullsend.yaml[44-44]

### Suggested fix
- Replace `@main` with an immutable ref (commit SHA, or a protected/immutable tag if your org uses those).
- If you need to stay aligned with the template, update the pinned SHA as part of a reviewed/automated bump process (e.g., periodic PRs).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 12:47 PM UTC · Completed 12:59 PM UTC
Commit: 701e62a · View workflow run →

@fullsend-ai-review

fullsend-ai-review Bot commented Aug 11, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 9:28 PM UTC · Completed 9:39 PM UTC

Commit: 9103755 · View workflow run →

fullsend-ai-review[bot]

This comment was marked as outdated.

Update the shim workflow to match the current template
in the .fullsend config repo.
@fullsend-ai-review

fullsend-ai-review Bot commented Aug 14, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 7:49 PM UTC · Completed 8:03 PM UTC

Commit: 9ee3c25 · View workflow run →

fullsend-ai-review[bot]

This comment was marked as outdated.

@qodo-app-for-konflux-ci

Copy link
Copy Markdown

Code review by qodo was updated up to the latest commit b3cfa76

@fullsend-ai-review

fullsend-ai-review Bot commented Aug 24, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 6:40 AM UTC · Completed 6:51 AM UTC

Commit: 9ee3c25 · View workflow run →

@fullsend-ai-review fullsend-ai-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the review comment for full details.

github.event_name != 'issue_comment'
|| github.event.comment.user.type != 'Bot'
uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@ec21706cccc58d01588ecd842464a5afcc375ba1 # main
uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@main

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[high] security/supply-chain

Replacing the SHA-pinned reusable workflow reference (@ec21706cccc58d01588ecd842464a5afcc375ba1) with a floating branch reference (@main) removes supply-chain integrity for this external workflow call. The dispatch.yml workflow from konflux-ci/.fullsend will now resolve to whatever commit happens to be at main at invocation time. Because this workflow runs on pull_request_target with id-token: write and actions: write permissions, any future push to main in the .fullsend repo instantly changes what privileged code executes in this repository without any review gate in this repo. Every other uses: directive across all workflows in this repository is SHA-pinned, making this an inconsistency with the established security convention.

Suggested fix: Keep the SHA-pinned reference. If the intent is to update to a newer commit of dispatch.yml, pin to the new SHA with the branch name as a trailing comment (e.g., uses: konflux-ci/.fullsend/.github/workflows/dispatch.yml@ # main), consistent with every other workflow reference in this repository.

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

Labels

github_actions Pull requests that update GitHub Actions code Possible security concern Review effort 1/5

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants