Fix fatal checkout error in linter workflow by removing ready_for_review trigger - #9
Merged
Merged
Conversation
|
|
VimukthiPerera
marked this pull request as ready for review
March 3, 2026 07:29
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: VimukthiPerera <15902071+VimukthiPerera@users.noreply.github.com>
Copilot
AI
changed the title
Update linter workflow to fix fatal checkout error
Fix fatal checkout error in linter workflow by removing ready_for_review trigger
Mar 3, 2026
VimukthiPerera
approved these changes
Mar 3, 2026
HiranAdikari
approved these changes
Mar 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
The linter workflow was failing with
fatal: bad objectduring the super-linter step when triggered by theready_for_reviewpull_request event. Draft-to-ready conversions can fire before commit refs are consistently available on the runner, causing the SHA-based checkout/diff to fail.Goals
pull_requesttrigger to[opened, synchronize, reopened], eliminating the unreliableready_for_reviewtrigger path.ref: github.event.pull_request.head.sha,fetch-depth: 0) and base-branch fetch logic.Approach
Single-line change in
.github/workflows/linter.yml:The
pull_request_reviewtrigger (approved reviews only) and all downstream steps are unchanged.User stories
N/A — internal CI reliability fix.
Release note
N/A — workflow-only change with no product impact.
Documentation
N/A — no user-facing documentation affected.
Training
N/A
Certification
N/A — no feature or behavioral change.
Marketing
N/A
Automation tests
Security checks
Samples
N/A
Related PRs
N/A
Migrations (if applicable)
N/A
Test environment
GitHub Actions / ubuntu-latest
Learning
N/A
Original prompt
This pull request was created from Copilot chat.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.