Unverified50% confidenceDecision RuleExact time
GitHub's official explanation: the corresponding latest commit that needs to be checked must be checked; if a merge commit status exists, check that, otherwise check the latest head commit, and one must not mechanically use only the earliest run as the basis.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/13/2026
First Seen
Valid until: 1/11/2027
Sources
Related Entities
Related Claims
UnverifiedThe /review command can automatically compare current changes with content on GitHub or review uncommitted changes, identify errors, and provide comments.72% similarUnverifiedIt is recommended to make a Git commit after each small feature is completed and passes testing, with a brief note describing the changes.71% similarUnverifiedThe GitHub team emphasizes that the evaluation process must set metric thresholds in conjunction with specific business objectives, as there is no universal answer for the balance point in secret scanning and it must be calibrated repeatedly based on real data71% similarUnverifiedOn GitHub, a neutral status means the check completed but the result is neither pass nor fail; skipped means the check was not executed because conditions were not met, and these two statuses may by default be treated as passing in branch protection rules.69% similarUnverifiedGitHub branch protection rules require CI status checks to pass before merging, and will block PR merges when CI runs fail or are in a pending state.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1016647API
curl https://kongchang.com/api/v1/knowledge/claims/1016647MCP
get_claim(id=1016647)