Re:Launch a Debugging Terminal into GitHub Actions
by embedding-shape on Monday January 12, 2026 @03:52PM
(#46594150)
Can't do much about that when there is something you're troubleshooting about the CI platform itself. Say you're troubleshooting why the deployment doesn't work, somehow got the environment variable wrong for whatever reason. So you edit and add a "env | sort" before that, commit it, push it, so on. With "rebuilt with ssh", you literally are inside the "job" as it runs.
[ Parent
| on HN ]
Re:Launch a Debugging Terminal into GitHub Actions
by Storment33 on Monday January 12, 2026 @04:00PM
(#46594245)
Yes you can't really debug CI specific stuff locally, like if your setting up build caching or something. But it seems like 90%+ of the time people are complaining about builds/tests that should have local feedback loops.
Re:Launch a Debugging Terminal into GitHub Actions
by embedding-shape on Monday January 12, 2026 @04:13PM
(#46594384)
Yeah, fair point, I see that a lot in the wild too. I guess I kind of assumed we all here had internalized the practice of isolating everything into one command that runs remotely, like "make test" or whatever, rather than what some people do and put entire shellscripts-but-yaml in their pipeline configs.
Re:Launch a Debugging Terminal into GitHub Actions
by Storment33 on Monday January 12, 2026 @05:43PM
(#46595247)
Yeah everytime I see logic in YAML I cringe. Trying at work to get people to use a task runner or even call out to scripts was a fight...