Skip to content

ci: harden Trunk tool discovery and YAML format - #327

Draft
KooshaPari wants to merge 1 commit into
codex/byteport-trunk-plugin-resolutionfrom
codex/byteport-trunk-format-followup
Draft

ci: harden Trunk tool discovery and YAML format#327
KooshaPari wants to merge 1 commit into
codex/byteport-trunk-plugin-resolutionfrom
codex/byteport-trunk-format-followup

Conversation

@KooshaPari

Copy link
Copy Markdown
Owner

Summary

  • discover the Trunk Prettier tool directory from the action's INPUT_CACHE_PATH rather than assuming HOME or a .bin executable
  • preserve plugin installation into Trunk's isolated tool directory
  • satisfy yamllint comment spacing and line-length gates without disabling any linter

Evidence

  • actionlint v1.7.8 targeted workflow
  • frontend-rooted Prettier checks for changed YAML and frontend/web
  • git diff --check

Stacked on PR #325; no merge performed.

@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown

Legacy Tooling Scan Report

Severity Count
Critical 0
High 0
Medium 0
Low 0

No violations detected.

This is a WARN-mode scan. Fix before strict enforcement begins.

@sonarqubecloud

sonarqubecloud Bot commented Aug 2, 2026

Copy link
Copy Markdown

@github-actions

github-actions Bot commented Aug 2, 2026

Copy link
Copy Markdown

📊 Tier-2 Coverage Gate Results

Tier Threshold Status
Rust lib (byteport-transport) ≥71% ✅ Pass
Go framework (backend) ≥70% ✅ Pass
Frontend unit (frontend/web) ≥60% ✅ Pass

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