Unverified50% confidenceFactExact time
GitHub push protection covers command-line pushes, commits created in the GitHub UI, file uploads, REST API requests, and GitHub MCP server interactions limited to public repositories.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/14/2026
First Seen
Valid until: 1/12/2027
Sources
Related Entities
Related Claims
VerifiedPlatforms such as GitHub Actions and GitLab CI grant runners write access to repositories by default through built-in credentials such as GITHUB_TOKEN.80% similarUnverifiedBy default, anyone with write access to a repository can bypass GitHub push protection by specifying a bypass reason.76% similarUnverifiedGitHub对公开仓库免费、对私有仓库和企业功能收费；GitLab采用开源核心+企业版的混合模式75% similarUnverifiedGitHub的Raw文件服务默认设置了宽松的CORS策略，允许任何域名下的前端页面直接请求GitHub仓库中的文件75% similarVerifiedGitHub dynamically generates a temporary merge commit (refs/pull/*/merge) on the server side for each PR, which must be explicitly fetched via git fetch and does not exist in a normal git clone result.75% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1023114API
curl https://kongchang.com/api/v1/knowledge/claims/1023114MCP
get_claim(id=1023114)