This simplifies the PR template, which is a bit cumbersome, and instead
replaces it with a simpler notice that includes a template sign-off and
a new `CONTRIBUTING.md` document.
Signed-off-by: Neil Twigg <neil@nats.io>
Co-authored-by: Byron Ruth <byron@nats.io>
Bump various GitHub Actions versions to move away from those using the
deprecated node.js 12 runtime, and so remove the warnings.
For the coveralls action, I switched to just `@v2`, per their example docs and
as we do for most actions, instead of major.minor.patch.
For Golang, update one 1.16 to 1.19, and quote the remaining unquoted
instances, even though they had `.x` in there so had to parse as strings,
because we're just switching to always-quoting for consistency.
We're currently using Go 1.19; we'll switch to 1.20 when the NATS Maintainers
make the call to switch. Prepare by making sure that 1.20 won't turn into 1.2
instead, by quoting the string to be updated and adding a warning.
We are ok with a flapper or two, because they should not affect
code coverage that much, so it is better to have those and publish
code coverage than to have to recycle the whole test suite until
we get no test failure.
However, if there is a test panic, then all other tests within this
package will NOT run, which then would have possibly a massive
impact in the code coverage percentage.
These changes will ensure that the run fails if one of the code
coverage output is "empty" (it is actually not empty, but the
initial content is "mode: atomic" and then whe code coverage is
complete, it gets filled with actual code coverage data).
On failure, the push to coverall will not happen.
Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
- Remove code coverage from Travis and add it to a GitHub Action
that will be run as a nightly.
- Use tag builds to exclude some tests, such as the "norace" or
JS tests. Since "go test" does not support "negative" regexs, there
is no other way.
Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
Since we have never released with goreleaser and GO111MODULE=on
and have removed vendor directory, we are going to push a
v2.7.0-rc1 tag. If the goreleaser process works fine and submit
the draft release correctly, we will not do an actual v2.7.0-rc1
release. Instead, we will follow up immediately with the v2.7.0
tag and the proper release.
Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
* We've renamed our default branch from 'master' to 'main'
* We switched some time ago from 'gnatsd' to 'nats-server' and some temporary
redirects no longer work, so fix those too
goreleaser now only function with GO111MODULES on, as will
much of the go eco system soon and we will need to move also.
For now use a version that still supports it
Signed-off-by: R.I.Pienaar <rip@devco.net>
