Lock Your GitHub Actions
0 comments
- Points255
- Comments51
0 comments
Story details from Hacker News ↗ · linked article on hugovk.dev.
Lock Your GitHub Actions was first seen on Hacker News · Front page on Nov 11, 2026. Since then it has appeared in 69 checks on 2 different days. Its best position was #11 of 30, reached on Nov 12, 07:54 UTC. It dropped off the list after Nov 12, 15:28 UTC. The same link also trended on Lobsters, which raises its cross-platform score.
Position on Hacker News · Front page at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Hacker News.
| List | Best | Days | Checks | Last seen |
|---|---|---|---|---|
| Hacker News · Front page | #11 | 2 | 69 | |
| LLobsters · Hottest Lock your GitHub Actions | same link | |||
A few top-level comments from Hacker News, shortened. Read the full thread on Hacker News.
The advice here is really great (as I'd expect from Hugo), but as the maintainer of zizmor I want to note some caveats with the current iteration of workflow lockfiles: - They only lock normal action calls. If your workflows invoke other reusable workflows, you need to keep those hash-pinned manually for now. -…
Quoting someone else's blog I've forgotten but you're trading the trust in the repo owner not moving a tag for trusting whoever merges the commit hash to have checked that's a release in the repo you want and not _some_ forks commit. All forks on github are the same repo you can pin any commit, merged upstream or…
No, I'm still keep using 'pinact run -u', and some dependabot actions to remind me on updates.
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 12, 15:28 UTC, after 2 days of trending.
#11 on Hacker News · Front page, on Nov 12, 07:54 UTC. Trendoday checks this list every 15 minutes.
It was first seen on Nov 11, 2026 and has been on the list on 2 days (69 checks) since.
255 points and 51 comments; submitted by gslin on Nov 11, 2026.