aboutsummaryrefslogtreecommitdiff
path: root/.github
Commit message (Collapse)AuthorAge
* ci(vim-patches): fix failing workflowdundargoc2025-02-04
|
* ci!: store artifact shasums in a single shasum.txt filedundargoc2025-01-29
| | | | Users can parse this file to get the shasum they require.
* ci(release)!: remove backwards compatible releasesdundargoc2025-01-28
| | | | | | | Remove `nvim-linux64.tar.gz` and `nvim.appimage` as maintaining these is too much work. Also fix directory names to be consistent.
* ci(release): add linux-arm64 appimage and tarballChristian Clason2025-01-27
| | | | | | | Problem: No releases for ARM Linux. Solution: Provide appimages and tarballs for `linux-arm64`. Rename x86 releases to `linux-x86_64` for consistency.
* ci(tests): remove build-types jobsChristian Clason2025-01-24
| | | | | | | | Problem: Some CI jobs are redundant: `RelWithDebInfo` is already tested on Linux-Arm64; `MinSizeRel` and Ninja Multi Config are not sufficiently relevant in practice to spend CI cycles on. Solution: Remove `build-types` job.
* ci(tests): add arm64 runnerChristian Clason2025-01-24
| | | | | | | Problem: Linux `aarch64`/`arm64` builds are not tested. Solution: Add `ubuntu-arm` runners to test matrix (using `RelWithDebInfo` build).
* ci(news): treat deprecated.txt as part of news.txtdundargoc2025-01-20
| | | | | This is because we reference to deprecated.txt from news.txt, so deprecation news updates are made only in deprecated.txt.
* docs(gh): use new issue typesChristian Clason2025-01-17
|
* docs: misc #31867Justin M. Keyes2025-01-09
|
* ci(news): trigger job for `perf` commit typedundargoc2024-12-31
| | | | | There is a "performance" section in news.txt so it makes sense we should also give a reminder to update news for performance improvements.
* ci(build.yml): disable security restrictiondundargoc2024-12-16
| | | | | | A new security restriction in Ubuntu 24.04 prevents users from using `unshare`, so we need to disable it in order for the test to work properly.
* ci: run tests directly rather than via the MakefileJames McCoy2024-12-03
| | | | Since the Makefile is not used to build, running the tests via the Makefile causes cmake to reconfigure and revert the release build back to debug.
* ci(test): remove the .git directory for LinuxJames McCoy2024-12-03
| | | | | | | Tests should not rely on being run inside a git clone, so the Linux builds cover this use case. The macOS builds will continue running with the .git directory so there's still unix-ish coverage within a git clone.
* ci: run one set of tests with a release buildJames McCoy2024-12-03
| | | | | | This ensures that no tests fail due to differences between release and debug builds. The release build-type check is now unnecessary, too, so remove it.
* ci: remove myself from lsp reviewersMathias Fussenegger2024-11-27
|
* ci(win): remove python workaround (#31212)Christian Clason2024-11-15
| | | Explicitly installing Python 3.13 using (deprecated version of) `setup-python` looks to be no longer required for provider tests to pass.
* ci: downgrade to clang 19dundargoc2024-11-09
| | | | | Clang 20 is still in development at the time of this commit and is unsuitable for CI.
* ci: adjust reviewersdundargoc2024-11-06
|
* ci: work around flaky python tests (#31063)dundargoc2024-11-03
| | | | | It's the same workaround as 88ed9ffcd1c022811ebc8818e153fe94e4741671, which was later removed in f707ce76acb86e064d549dc762f5636af072d3c5 after it turned out to be stable after a while.
* docs: miscdundargoc2024-10-23
| | | | | | | Co-authored-by: David Pedersen <limero@me.com> Co-authored-by: Gregory Anders <greg@gpanders.com> Co-authored-by: Leo Schlosser <Leo.Schlosser@Student.HTW-Berlin.de> Co-authored-by: zeertzjq <zeertzjq@outlook.com>
* ci: bump Intel macOS runners to 13Christian Clason2024-10-19
| | | | | | Problem: macos-12 GH runners are deprecated and will be removed soon. Solution: use macos-13 runners instead.
* ci: bump macos runner version to macos-15dundargoc2024-10-06
|
* ci: bump ubuntu runner version to ubuntu-24.04dundargoc2024-10-05
| | | | Also bump clang to version 20.
* docs: lua error patterns #30240Justin M. Keyes2024-09-24
| | | | Co-authored-by: Mathias Fussenegger <f.mathias@zignar.net> Co-authored-by: Ananth Bhaskararaman <antsub@gmail.com>
* build: bump minimum cmake version to 3.16dundargoc2024-09-21
|
* docs: link to discussions instead of stackoverflowJustin M. Keyes2024-09-20
|
* docs: prefix LSP bug report titleJustin M. Keyes2024-09-20
|
* ci: skip automerge step if backport faileddundargoc2024-09-14
|
* ci: don't add reviewers for PRs created by a botdundargoc2024-09-13
| | | | | | | This will ensure automatic backports created by the backport action does not request reviewers (since the commit in question has already been vetted and merged), but manual backports created by users does request reviewers as these commits has not been vetted previously.
* ci: add `needs:backport` label on backport PRs with conflictdundargoc2024-09-13
| | | | | This makes it easy to keep track of which backport PRs have failed and need manual intervention to fix.
* ci: enable automerge by default when backportingdundargoc2024-09-13
| | | | | This will automatically merge backported PRs without human intervention if the tests pass.
* fix(build): issues with s390x CIbfredl2024-08-29
| | | | | Does not fix everything, but at least let's test run to finish before timeout
* feat(treesitter): add support for wasm parsersLewis Russell2024-08-26
| | | | | | | | | | | | | | | | | | | | Problem: Installing treesitter parser is hard (harder than climbing to heaven). Solution: Add optional support for wasm parsers with `wasmtime`. Notes: * Needs to be enabled by setting `ENABLE_WASMTIME` for tree-sitter and Neovim. Build with `make CMAKE_EXTRA_FLAGS=-DENABLE_WASMTIME=ON DEPS_CMAKE_FLAGS=-DENABLE_WASMTIME=ON` * Adds optional Rust (obviously) and C11 dependencies. * Wasmtime comes with a lot of features that can negatively affect Neovim performance due to library and symbol table size. Make sure to build with minimal features and full LTO. * To reduce re-compilation times, install `sccache` and build with `RUSTC_WRAPPER=<path/to/sccache> make ...`
* build(deps): vendor libvterm at v0.3.3Christian Clason2024-08-10
| | | | | | | | Problem: Adding support for modern Nvim features (reflow, OSC 8, full utf8/emoji support) requires coupling libvterm to Nvim internals (e.g., utf8proc). Solution: Vendor libvterm at v0.3.3.
* vim-patch:9.1.0661: the zip plugin is not tested. (#29993)zeertzjq2024-08-06
| | | | | | | | | | Problem: the zip plugin is not tested. Solution: include tests (Damien) closes: vim/vim#15411 https://github.com/vim/vim/commit/d7af21e746f3992c650caf6b76465880b96302b4 Co-authored-by: Damien <141588647+xrandomname@users.noreply.github.com>
* build(deps): remove libtermkey dependencyGregory Anders2024-08-05
| | | | It's been vendored since https://github.com/neovim/neovim/pull/25870.
* build(deps): remove msgpack-c dependencybfredl2024-08-05
|
* ci: always add `target:release` label when backportingdundargoc2024-07-21
| | | | | | Previously the label was not added if the backport PR was created manually. The new code is also easier to maintain as it's close to other label-related code.
* ci: skip lintcommit workflow on release branchesdundargoc2024-07-17
| | | | | | | | | | | Since lintcommit is a required check, it will always need to be run. However, the lintcommit script is not designed to work on PRs that doesn't target master branch (and it's not clear whether it's even desirable). To circumvent this we create a "dummy" lintcommit check that is run on release branches that always passes, thus fulfilling the condition of the required check.
* ci: remove "skip ci" tagdundargoc2024-07-17
| | | | | We can't skip CI runs as there are required checks that needs to always be run.
* ci: run workflows on release branchesdundargoc2024-07-16
| | | | | | | | | | | Github doesn't allow workflows to be run from the `github-actions` account, which is the default account. This caused the CI on backport PRs to not be run. The way to circumvent this is to use a token that essentially "pretends" to be another user, which in turn triggers the CI as desired. Also run lintcommit on release branches as that is now a required check, meaning it must always be run.
* ci: adjust workflows to enable required checksdundargoc2024-07-15
| | | | | | | | | | | | | | Auto-merging is a useful feature by github, but it requires required checks which requires a few adjustments. The primary change is that required checks can't use `paths` or `paths-ignore` as that risks not running the job, and required checks must always be run. A workaround for this is to introduce a dummy workflow which is used for every path not used in the real workflow. That way the required job is "always" run as far as github is concerned. The workaround is unweildly so it's only useful to do it for costly workflows where the potential benefits are big. If not it's better to simply remove any `paths` or `paths-ignore` from a workflow instead.
* feat(lsp): drop fswatch, use inotifywait (#29374)Andreas Schneider2024-07-06
| | | | | | | | | | | | | | This patch replaces fswatch with inotifywait from inotify-toools: https://github.com/inotify-tools/inotify-tools fswatch takes ~1min to set up recursively for the Samba source code directory. inotifywait needs less than a second to do the same thing. https://github.com/emcrisostomo/fswatch/issues/321 Also it fswatch seems to be unmaintained in the meantime. Signed-off-by: Andreas Schneider <asn@cryptomilk.org>
* ci: update labeler configuration and add reviewersdundargoc2024-05-30
|
* ci: bump backport action to version 3dundargoc2024-05-27
|
* build: remove nix flakes (#28863)dundargoc2024-05-24
| | | | | | | It does not work and we don't plan on maintaining these anymore. The flake files are being moved to https://github.com/nix-community/neovim-nightly-overlay/pull/516 instead.
* ci: change label `backport` to `target:release`dundargoc2024-05-17
| | | | | `backport` is too similar `ci:backport release-x.y` and causes confusion.
* ci(labeler): adjust configurationdundargoc2024-05-14
|
* ci(build): use latest over explicit image versiondundargoc2024-05-11
| | | | | These jobs should be safe to just use the latest as there's not many moving parts as opposed to `test.yml`.
* ci: don't try to label backport PR if it was not createddundargoc2024-05-02
|
generated by cgit (git 2.34.1) at 2025-04-28 21:54:17 +0000