* ci: set timeout on testground job
* ci: use testground action which exits early on scheduling failures
Note: this will be continued in https://github.com/ipfs/go-ipfs/issues/8731
* only copy files from dist.ipfs.io which have associated checksum files (also copy the checksum files)
* verify checksums before copying
* also, ignore path from sha512sum output, which sometimes has absolute path on dist.ipfs.io website
Co-authored-by: Marcin Rataj <lidel@lidel.org>
tar.gz got mangled because of reasons known to github,
this does the correct upload every time by forcing github to interpret
payload as an opaque stream of bytes without anything fancy
- Add a basic testground plan for bitswap
- Showcases how to emit regressions stats from a testplan
- Add CI plumbing to run testplans on push
As a result of this PR, also:
- Created the ipfs/go-ipfs-regressions repo, which defines stats structures for the output of testplans and the input to regression analysis and tests
This change converts go-ipfs to the new issue forms.
Initial implementation by @RubenKelvera in
https://github.com/ipfs/go-ipfs/pull/7967. The version here:
1. Converts all forms.
2. Asks fewer questions (for bug reports). We can expand the form later,
but I always hated bugzilla bug report forms.
* Give a few tips on linking relevant discussions, self reviews, additional
reviews and code contribution guidelines
* Be explicit about the next steps and what to expect.
* Remove question template: links to help have been added
* Add need/triage labels
* Do not ask users to open issues in ipfs/ipfs (issues heavily discouraged there).
This way:
1. Contributors have to click _something_ so they're more likely to read this.
2. Each issue gets correctly labeled.
3. We can customize the template for different types of issues so contributors
don't have to read as much.
License: MIT
Signed-off-by: Steven Allen <steven@stebalien.com>
