uses treeless fetches instead of `--depth`. This is not supported by
`actions/checkout`, so it was implemented as a short script (staying
with `actions/checkout@v1` does not seem like a good idea because of
its age, and updating to `actions/checkout@v3` would require adding
`libstdc++` to any CI workflows that run in void containers because
of node's requirements)
see also: https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/
this can't be implemented as a script in `common/travis/` because the
repo doesn't exist on the runner (yet!)
also fix indentation in cycle check
This fixes a bug where a stale issue/PR that gets updated without a comment
remains stale indefinitely and never gets closed (actions/stale#715).
The only "breaking" change in that upadate is that the default close reason has
changed to "not planned". That seems like a more desirable default anyways.
From chroot-git 2.33.1, we always have an executable named git
for other build infrastructure and lints.
Let's remove the shenanegan to find which git to be used, prepend the
path to chroot-git's git into $PATH, and let's the shell call the
correct git for us instead.
By setting `ascending` to `true`, the most stale issues and PRs will be
caught first. By increasing the operations limit from the default (30)
to 250, more stale issues/PRs will be caught each run, increasing the
speed of the burndown.
* CI will stop whenever a step is failing.
* We always want to enforce commit message lint
* `xlint` is reporting some false positive for license with " WITH "
Let's make the lint-commits part of xlint.sh
Closed PRs will be locked after 90 days of inactivity, to avoid comments
on old inactive threads and encourage people to create new ones, which
will receive the proper attention.
Inspired by hook from fish-shell:
a36dbad3b8/.github/workflows/lockthreads.yml
When a PR is marked as ready for review (no longer a draft), CI isn't
re-run automatically, so no tests are run until the PR is updated. Even
trying to manually re-run the jobs doesn't fix this, since GH appears to
remember the PR state instead of using the current one.