3 ms·
Internal repositories, for example, make it easier to have one set of Git Actions that is available to any Git Actions runner in your Org. What this means in pr
by hatware 4y ago
Internal repositories, for example, make it easier to have one set of Git Actions that is available to any Git Actions runner in your Org. What this means in practical terms, is cleaner code that is less repetitive. It's a total cop-out for GH to act like this is a feature worth paying for enterprise. It's not just useful to enterprise users, it's useful to everyone, including free users.
TL;DR: GH encourages bad coding practices unless you pay them enough. It's not consumer friendly and they can barely keep Actions running consistently enough to justify a paywall for such a staple feature.
- dboreham 4y agoI suspect parent is asking you to explain how this is different than a "private" repository.
- hatware 4y agoPrivate repositories can only be used by the Git Actions runner for that repository. For a monorepo, this works fine. If you have any semblance of microservices in their own repos, orchestrating CI/CD and other build/artifact processes is a nightmare. Internal repositories allow the Git Actions runner access from any other private repository, meaning you can have one repository for all of your git actions that can be neatly called from any other repository (private or public) in the org.
- dboreham 4y agoAh ok. So "private component re-use" for CI is not possible with a free account, even though such an account _does_ allow private repos. Thanks.