Seth Larsonsethmlarson@mastodon.social
Oct 1, 2026, 3:39 PM
Replies
Glyphglyph@mastodon.socialOct 1, 2026, 6:49 PM@sethmlarson are they ever going to let us run CI on private forks though
- Seth Larsonsethmlarson@mastodon.socialOct 1, 2026, 8:03 PM
@glyph That would be a great thing, but not yet :( I heavily suspect that "private forks" are completely their own thing compared to a normal repository. For example: they can't be deleted using the "delete repository" API even with admin credentials, only manually. Not sure if that's still true, but it was when I tested this a ~year ago.
- Glyphglyph@mastodon.socialOct 1, 2026, 8:10 PM
@sethmlarson I seriously don't know how to manage security workflows, especially at this higher volume and with lower-quality reports, if I can't _run the damn tests_. it's very annoying.
- Seth Larsonsethmlarson@mastodon.socialOct 1, 2026, 8:16 PM
@glyph yep, I'm sure tons of projects get bitten by things that would've been caught in CI if it had run, but local testing didn't surface. Python has run into this in the past, and then you have to make decisions under pressure.
I've been asking for specific features (this among them) from GitHub across multiple channels and I know I'm not alone, I'm hopeful that this new feature means that there'll be more behind it?
Oct 1, 2026, 9:17 PM@sethmlarson Also:
Rate limits for private vulnerability reports
https://github.blog/changelog/2026-10-01-rate-limits-for-private-vulnerability-reports/
Structured forms for private vulnerability reports
https://github.blog/changelog/2026-10-01-structured-forms-for-private-vulnerability-reports/