| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
We seem to need the parent commit of the earliest PR commit in order to
perform common git functionality to check which files were changed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If any commit message in the PR is either of type "feat" or is a
breaking change, then there's a high probability that news.txt should be
updated. Give an error if news.txt hasn't been updated in that case.
This workflow cannot 100% correctly determine if news.txt should be
updated even if the commit messages were exactly correct. The entries in
news.txt is determined by changes between releases, while the commit
messages are based on the master branch. While it is an approximation,
it is still a useful enough one that it's still valuable to have this
job as a reminder even if it gives an error if it shouldn't. In these
cases it is perfectly fine to ignore the failure for this job.
|
| | |
|
| |
|
|
| |
The advantages of using an action is that it reduces boilerplate and
repetition from the main ci.yml workflow.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Ref https://github.com/actions/runner-images/issues/6586
Some runners are using new images, while some others are using old
image. This is the only way I can find that makes it work on both.
|
| |
|
|
|
| |
The needs:response label should only be added and removed manually, and
the action's behavior of removing the label on any activity (e.g. title
change, removing reviewers) is unwanted.
|
| |
|
|
|
| |
Stale strategy is to never automatically stale anything. Only mark stale
issues or PRs if they get the `needs:response` label. In that case close
after 30 days if there hasn't been any activity.
|
| | |
|
| | |
|
| |
|
|
|
| |
The new recommended way to share values between Github Actions steps is
to use environment files:
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter
|
| |
|
|
| |
Main benefit is that this will return the correct exit code by default,
meaning the lengthy workarounds to properly fail a test aren't needed.
|
| | |
|
| |
|
|
|
|
|
| |
This reverts commit d7e2229b41748e84f525ee44cee19be81382ceab.
This workflow isn't required to pass to merge a PR any more. Using
pull_request_target to bypass the required check when using [skip ci] is
therefore no longer needed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's currently difficult to pinpoint the cause of a failure since all
tests are run even if the build steps fail. But since the build failed
the test will almost always fail as well as it's dependent on a
successful build, leading to many steps being marked as a failure even
though the real problem was the build step. Even worse, the default
behavior of GitHub Actions is to only automatically show the last failed
step, which is misleading if the build process fails since it'll show
the logs of the failing test step.
An easy solution would be to abort all subsequent steps if any steps
fail. This isn't optimal however, as we want all lint and test failures
to show on a single run instead of prematurely aborting on a single test
step.
We can solve both problems by dividing each job into two phases: the
build/installation phase and the test/lint phase, with a checkmark step
in between. The strategy is simple: if any step before the checkmark
step fails (the build phase), then abort all following steps. If any
step after the checkmark fails (the test phase), then show that test as
failed but continue running all tests.
|
| |
|
|
| |
This will silence the warning about needing to pin the version in the
Summary Page.
|
| |
|
|
| |
This will save around a minute of CI time for each run. Also clean up
build.ps1 by removing unnecessary code.
|
| |
|
|
|
|
| |
Default is currently clang 14. GHA images are updated at least once per year, so
we don't need to manually install a newer clang version.
Also remove step for installing clang-13 since it's not needed anymore.
|
| |
|
|
|
|
| |
This includes both the `lintpy` make target and for CI. We're actively
trying to reduce our python usage, so this only seems to give warnings
for unimportant things such as exceeding the line after deleting python
code.
|
| |
|
|
| |
There are 6 remaining 8.0.x patches, tracked in:
https://github.com/neovim/neovim/issues/5431
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
ci: Use ubuntu docker container to build appimage
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Switch back to Ubuntu 18.04 for buliding the appimage. This allows for
using the appimage on older systems that do not provide GLIBC_2.29.
Fixes #19711.
Fixes #20113.
|
| |/
|
|
|
|
| |
backport-action now uses "v0" tag to point to the latest stable version.
This helps us avoid having to manually bump the version to get bug
fixes.
|
| |
|
|
|
|
|
|
| |
Skipping the CI on documentation-only changes is no longer appropriate
as we now rely on CI to test parts of documentation, e.g.
test/functional/lua/help_spec.lua.
Ignore changes in contrib/ as it's for non-essential user contributions
that we don't need to test.
|
| |
|
| |
The nvim-lspconfig minimal_init.lua is not exactly minimal.
|
| | |
|
| |
|
|
| |
We only have one Windows release job, so the matrix setup isn't needed.
|
| |
|
|
| |
Build tree-sitter parsers for arm64 as well as x86
Check that all created binaries contain both architectures
|
| |
|
| |
Primary bug fix is allowing backports with empty PR description.
|
| |
|
|
| |
Changing the action version to v1 allows us to automatically get patch
updates as it points to the latest stable version.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Treesitter parsers are now a mandatory part of the installation and
should be tested on all platforms. Remove `pending_c_parser` helper.
|
| | |
|
| |
|
|
| |
replaces deprecated LGTM workflow:
https://github.blog/2022-08-15-the-next-step-for-lgtm-com-github-code-scanning/
|
| |
|
|
| |
All steps in lint now do now require a Neovim build.
|
| | |
|
| |
|
|
|
|
|
| |
lintcfull == lintc + uncrustify
We are already running uncrustify separately so can just run lintc
instead.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
It was never in action since migrating from travis to github actions.
|
