[Sync] Update project files from source repository (5417792)

[mrz1836]

What Changed

• Updated GO_PRE_COMMIT_VERSION from v1.6.2 to v1.7.0 in .github/env/10-pre-commit.env
• Added error output logging to persist cleaned pre-commit check output to pre-commit-output.log file when checks fail, using multiple sed commands to strip ANSI escape sequences and control characters
• Enhanced GitHub Actions workflow summary generation to display error details from the log file in an expandable section (showing first 200 lines) when pre-commit checks fail
• Added handling for early workflow failures where log file doesn't exist, displaying a warning message in the summary instead
• Modified success message logic to check for log file presence and failure conditions before showing passed checks summary

Why It Was Necessary

• The pre-commit tool version bump ensures the workflow uses the latest features and bug fixes from the upstream tool
• Capturing and displaying pre-commit failure output in the GitHub Actions summary improves debugging visibility without requiring users to dig through raw workflow logs
• Stripping ANSI escape codes from the output ensures the log file and summary display are clean and readable in GitHub's markdown renderer

Testing Performed

• Verify the workflow successfully downloads and executes pre-commit tool version v1.7.0
• Test failure scenarios to confirm the log file is created with cleaned output and appears correctly in the GitHub Actions summary
• Validate that early failure cases (before log creation) properly display the fallback warning message
• Confirm successful pre-commit runs still display the appropriate success summary without error sections

Impact / Risk

• Low Risk: Version bump is a minor update; log file creation only occurs on failure path and doesn't affect success scenarios
• Improved Developer Experience: Failed pre-commit checks now show actionable error details directly in the workflow summary
• No Breaking Changes: Existing workflow behavior is preserved; enhancements are additive only

[Copilot]

Pull request overview

Updates the GoFortress pre-commit workflow to improve failure diagnostics by persisting cleaned check output to a log file, surfacing it in the GitHub Actions job summary, and uploading it as an artifact; also bumps the go-pre-commit tool version.

Changes:

• Bump GO_PRE_COMMIT_VERSION to v1.7.0.
• On pre-commit failure, write cleaned output to pre-commit-output.log and show truncated details in the workflow summary.
• Upload the failure log as a retained artifact for later inspection.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
.github/workflows/fortress-pre-commit.yml	Adds failure log persistence, summary rendering of error output, and artifact upload of the log.
.github/env/10-pre-commit.env	Updates go-pre-commit tool version to v1.7.0.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

The ANSI/control-character stripping pipeline is duplicated here and earlier in the step when printing output. Duplicating it increases the chance the console output and persisted log diverge over time; consider factoring this into a single reusable variable/function (e.g., compute cleaned output once, then both print and write the file).

[Copilot]

The comment says printf is used to avoid echo misinterpreting leading -n/-e, but the step still uses echo "$CHECKS_OUTPUT" | ... earlier to render the cleaned output to logs. Either update the earlier output path to use printf as well, or adjust this comment so it doesn't imply the problem is fully addressed.

[Copilot]

The summary text says "Click to expand full output", but the workflow only appends head -200 of the log. This is misleading; either include the full log content (if safe) or adjust the wording to indicate it is truncated (e.g., "first 200 lines").

[Copilot]

The section header says "Upload pre-commit results (only present on failure)", but this step runs unconditionally with if: always() (it just ignores missing files). Either make the step conditional on the log file existing, or update the header/comment to match the actual behavior.

[mrz1836]

LGTM!