Summary:
Starting to have a play with forgejo, on this platform you cannot define
secrets that have a prefix of `GITHUB_`. I still want to maintain CI on github
for any pull requests that may come in.
The plan in to use the `GITHUB_TOKEN` when we are running on github and use the
`GH_TOKEN` when we are running on forgejo
Test Plan:
Run the CI on github and forgejo, this will need to be a manual process to
validate this works.
Summary:
Right now we are only running the tests on the nightly build of nvim. I would
like to try and maintain support for a few releases. One of the goals of this
project is to be stable. This means trying our best to maintain BC, for this I
have setup running the tests on older versions of nvim.
Right now we have:
- *nightly* Make sure we support the new releases, we can hopefully fix issues
before this gets releases.
- *stable* This is the main version we support
- *v0.9.5* Maintain the old stable, some OSs like Ubuntu lack behind, would be
nice to maintain that.
Test Plan:
CI, I have done a quick run before finalizing the change
Summary:
Now we are running the tests in neovim we get some output printed to stderr.
This is not helpful in the test output, and obfuscate errors.
This throws any unneeded output to `/dev/null` so we can focus of the tests
that have failed. It also moves over to using TAP output for a more descriptive
out put in CI.
Test Plan:
CI, running the test will validate this
Summary:
This runs the new tests in our existing CI. We will remove the old tests later
when we know everything runs together so we know everything works.
Test Plan:
CI
This is getting set to latest. The docs say this could break CI due to
changes in stylua bit right now I think that is better than maintain the
version manually.
