Skip to content

Clarify description of go-bin-path output and its fallback behavior - #803

Merged
v-HarithaVattikuti merged 4 commits into
actions:mainfrom
v-mahabaleshwars:docs/go-bin-fallback
Nov 2, 2026
Merged

v-HarithaVattikuti merged 4 commits into
actions:mainfrom
v-mahabaleshwars:docs/go-bin-fallback

Conversation

@v-mahabaleshwars

Copy link
Copy Markdown
Contributor

Description:
Clarifies the documentation for the go-bin-path output. The updated description specifies that it uses GOBIN when set and otherwise falls back to the bin directory under the first GOPATH entry.

Related issue:
#54

Check list:

  • Mark if documentation changes are required.
  • Mark if tests were added or updated to cover the changes.

Copilot AI balanced review requested due to automatic review settings October 21, 2026 16:19
@v-mahabaleshwars
v-mahabaleshwars requested a review from a team as a code owner October 21, 2026 16:19

Copilot AI 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.

🟢 Approval recommended

The documentation-only changes match the existing behavior, with no unresolved findings.

No open issues 🎉

What changed in this PR

Clarifies the existing go-bin-path output behavior without changing runtime logic.

Changes:

  • Specifies that an empty GOBIN triggers fallback to bin under the first GOPATH entry.
  • Clarifies version-dependent defaults and cross-compilation behavior.
File Description
docs/​advanced-usage.md Clarifies fallback behavior and cross-compilation paths.
action.yml Makes the output’s fallback condition explicit.

Review effort: Balanced

@v-mahabaleshwars v-mahabaleshwars self-assigned this Oct 27, 2026
@v-HarithaVattikuti
v-HarithaVattikuti merged commit b2a9ab2 into actions:main Nov 2, 2026
127 of 130 checks passed
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.

5 participants