Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add CI check to make sure River CLI is installable
Pertaining to the problem described in #35, seems like a good idea to have a CI check make sure that nothing we've done with Go modules has made the CLI not installable. We have two variants: * Install within a Go Module. This is theoretically nice because it'd get the same version of the River CLI as the River you're using, but has a very large downside currently in that it requires you to add the CLI's dependencies to your stack before it works. e.g. Cobra. * Install outside a Go Module with the equivalent of `@latest` (uses the ref of the branch being built in CI). This is currently broken until a fix like #35 can come in. Long term, this job may become too much of a maintenance headache because Go has some really annoying caching behavior around modules, but I didn't experience that while writing it, so it might be worthwhile seeing whether this turns out to be valuable.
- Loading branch information