GitHub pull_request_target blocked by default December 2
Comments on “GitHub pull_request_target blocked by default December 2”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
GitHub will block pull_request_target events by default in public repositories on Free, Team and Enterprise Cloud starting December 2, 2026, a delay from the earlier November 2 date. Private, internal and Enterprise Server repositories are unaffected. The trigger runs with base-repo secrets, so executing fork code can leak them. Two brownouts, November 9 and 16 (16:00–18:00 UTC), will fail blocked runs. Teams can check Insights, then allow specific workflows through an Actions event policy. The claim check found no cited sources for these details.
Why it ranked
No. 9 of 137 with a score of 0.71. The panel rated it highest on new information (0.89) and practical relevance (0.89), lowest on audience breadth (0.63). The judges disagreed most on substantiated (spread 0.53), so the story is marked contested. Placed No. 9, No. 11 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Concrete platform policy change affecting CI/CD security for many public repo maintainers; practical, actionable, and well-documented, though it is an official notice with limited technical depth.
- AI judgeJudge 3gpt-5.6-luna
- A well-substantiated platform security-policy change with concrete dates, affected repositories, brownouts, and remediation steps. It directly affects public-repository CI/CD and secret-handling workflows, though it is specific to one platform.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.71total under rubric v2.3Contestedjudges differ by 0.53 on substantiated
- Significance0.64
- Reader interest0.74
- Audience breadth0.63
- Practical relevance0.89
- Substantiated0.69
- Technical depth0.63
- New information0.89
- Counts against: Promotional0.05
- Counts against: Overclaim0.10
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.66 | 0.55 | 0.72 | 0.64 | 0.17 | +0.24 | +0.154 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.62 | 0.70 | 0.90 | 0.74 | 0.28 | +0.26 | +0.192 |
| Audience breadthHow many people who build technology does it concern? | 0.50 | 0.67 | 0.72 | 0.63 | 0.22 | +0.13 | +0.082 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.92 | 0.85 | 0.90 | 0.89 | 0.07 | +0.22 | +0.196 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.42 | 0.70 | 0.95 | 0.69 | 0.53 , above the contested threshold | +0.05 | +0.035 |
| Technical depthHow technically substantive is it? | 0.73 | 0.55 | 0.62 | 0.63 | 0.18 | +0.05 | +0.032 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.90 | 0.80 | 0.98 | 0.89 | 0.18 | +0.05 | +0.045 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.09 | 0.05 | 0.02 | 0.05 | 0.07 | −0.19 | −0.010 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.17 | 0.10 | 0.02 | 0.10 | 0.15 | −0.11 | −0.011 |
| Sum of contributions | +0.715 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.715 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-04/9/"><img src="https://rubric.hrih.si/badge/2026-11-04/9.svg" alt="Ranked #9 on Rubric, 4 Nov 2026" width="231" height="28"></a>Claim check
Claim check: 8 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenDate
Starting December 2, 2026, GitHub Actions will block pull_request_target events by default in all public repositories unless an applicable Actions event policy explicitly allows them.
The article gives no link or citation for it.
The article says “Starting December 2, 2026, GitHub Actions will block pull_request_target events by default in all public repositories, unless an applicable Actions event policy explicitly allows them”
The source says No source to compare with.
No source givenDate
Enforcement of the default pull_request_target block was previously scheduled for November 2, 2026.
The article gives no link or citation for it.
The article says “Enforcement was previously scheduled for November 2, 2026”
The source says No source to compare with.
No source givenVersion
The default rule initially runs in evaluate mode, so users can see which workflow runs it would block before enforcement begins.
The article gives no link or citation for it.
The article says “The rule initially runs in evaluate mode, so you can see which workflow runs it would block before enforcement begins”
The source says No source to compare with.
No source givenGeneralization
Private and internal repositories are not affected by the change.
The article gives no link or citation for it.
The article says “Private and internal repositories aren’t affected”
The source says No source to compare with.
No source givenCausal conclusion
pull_request_target runs in the context of the base repository and can access its secrets, so executing untrusted fork code could compromise a pipeline or steal secrets.
The article gives no link or citation for it.
The article says “pull_request_target runs in the context of the base repository and can access its secrets. If a workflow executes untrusted code from a fork, that code could compromise your pipeline or…”
The source says No source to compare with.
No source givenDate
GitHub will run two brownouts, on November 9 and November 16, 2026, from 16:00 to 18:00 UTC, during which the default protection is temporarily enforced.
The article gives no link or citation for it.
The article says “November 9, 2026 16:00–18:00”
The source says No source to compare with.
No source givenNumber
During each brownout, blocked pull_request_target workflow attempts in affected public repositories create failed runs with an error annotation and do not execute; afterward the rule returns to evaluate mode.
The article gives no link or citation for it.
The article says “pull_request_target workflow attempts blocked by the default rule in affected public repositories will create failed runs with an error annotation; the workflows won’t execute”
The source says No source to compare with.
No source givenVersion
The change applies to public repositories on GitHub Free, GitHub Team, and GitHub Enterprise Cloud, not GitHub Enterprise Server.
The article gives no link or citation for it.
The article says “This change applies to public repositories on GitHub Free, GitHub Team, and GitHub Enterprise Cloud, not GitHub Enterprise Server”
The source says No source to compare with.
Also covered by
Elsewhere
Elsewhere: HN 5 pts, not on front page
Recorded for context only, checked 4 Nov 2026, 05:47 UTC. It played no part in the ranking.