News for hackers. Stuff that matters.
Re:Pricing Changes for GitHub Actions by Nextgrid on Tuesday December 16, 2025 @07:10PM (#46296555)
There's value in enforcing checks on the server side to avoid people accidentally/maliciously merging code that doesn't pass said checks. Checks can be linters, security scanners, etc.
Re:Pricing Changes for GitHub Actions by Cyph0n on Tuesday December 16, 2025 @07:18PM (#46296614)
> Checks can be linters, security scanners, etc.

The first checks I setup are build and test. The rest is “extra”.

Re:Pricing Changes for GitHub Actions by bdangubic on Tuesday December 16, 2025 @08:46PM (#46297239)
why on the server?!
Re:Pricing Changes for GitHub Actions by Nextgrid on Tuesday December 16, 2025 @09:08PM (#46297378)
Because then you protect against a compromised/misbehaving developer workstation. No matter what the individual developer does, the server will prevent a PR being merged if it doesn’t pass the server-enforced checks.

Running builds on a designated server would also protect against malware on a developer’s machine silently embedding itself into the resulting artifact and then deployed to production.

Re:Pricing Changes for GitHub Actions by franklyworks on Tuesday December 16, 2025 @10:17PM (#46297855)
This was probably the question to ask before declaring it all as junk.