3 ms·
Having to push a commit to test the Github equivalent (Actions) was a huge pain. I think I ended up with 80+ commits. I wish the existing solutions on the Git
by jnwatson 6y ago
Having to push a commit to test the Github equivalent (Actions) was a huge pain. I think I ended up with 80+ commits.
I wish the existing solutions on the Github side worked.
Mildly ironic that you're hosting this on Github.
- mdaniel 6y ago> I wish the existing solutions on the Github side worked. I did experience a bad outcome using act[0] for a super weird matrix-y workflow, but I'd say for the most part it behaved sanely; did you report your complaints to their issue tracker? 0 = https://github.com/nektos/act https://github.com/nektos/act
- jnwatson 6y agoI briefly tried it. It couldn’t even parse the yaml.
- benibela 6y ago> I think I ended up with 80+ commits. Happens all the time to me. (although I have not used Actions) . Especially when I also had to set up a cross compiler on the CI. And each change needs 15 minutes to run the VM again CI is an enormous productivity killer
- c7DJTLrn 6y agoYep, CI like this is a catastrophe. Sourcehut's ad-hoc builds are really nice because you can test without pushing any changes. But sadly, Sourcehut CI is lacking in other areas.