A lot of that pain can be reduced by writing and running your code locally before pushing it to a CI environment. Generally with our automation we write a CLI, And GitHub actions is just an execution environment that calls the CLI.
And if what you’re trying to do must execute inside an action. You can run workflows locally with docker!
GitHub Actions mostly.
The rest is usually plumbing and code to support it. The actions are just the automated execution environment.
Ah yes, the classic:
They must be maliciously lying instead of me using something wrong argument.
Very solid, much sound.
Unfortunate Newsflash:
It’s smaller reddit.
The lowest common denominator consumes all. And that denominator includes not being able to read articles or apply critical thought.
I’m currently running Vivaldi and it’s been fine. YouTube is even smoother.
So you switched to a Google controlled ecosystem. To no one’s surprise their own products, which intentionally run worse on competitive browsers, will work more smoothly once you use their backing software…
Google has a long history of abusing their position of power to “punish” users of other browsers and ecosystems by violating web standards, don’t use Google’s browsers or their derivatives.
Probably a fork of Firefox that can only survive as a side effect of the Mozilla engineering team’s constant efforts.
Or a Chromium based browser.
Edit: I forgot this was self-hosted community, disregard.
How does organization work out?
We have dozens of workflows for our monorepo CI/CD stuff. GitHub organization with the flat structure is incredibly annoying.
GitLab is a single file?? (Or am I misinformed? )How does that work out?