aboutsummaryrefslogtreecommitdiff
path: root/.github/workflows/ci.yml
Commit message (Collapse)AuthorAge
* ci: enable CI_BUILD on windows (#21557)dundargoc2023-01-18
| | | | | | | | This will ensure warnings are treated as errors when using MSVC. Also fix const correctness warnings. The warnings in mbyte.c are false positives that triggers this warning on MSVC v19.32 and lower, which our CI still use. The (void *) casts can be removed once the CI MSVC version has been upgraded to v19.33 or higher.
* ci: run each linter once (#21825)dundargoc2023-01-16
| | | | | Running "make lintlua" will run both stylua and luacheck if both exist. But this is not necessary as we already lint with stylua with the stylua-action, so we only need to lint with luacheck on our own.
* ci: deduplicate TEST_FILE environment variable (#21667)dundargoc2023-01-15
|
* ci(tsan): run functionaltests instead of oldtests (#21744)zeertzjq2023-01-11
| | | | With TUI as an external process oldtests no longer involve threads, so TSAN isn't useful. Meanwhile functionaltests may involve threads.
* feat(lua)!: execute Lua with "nvim -l"Justin M. Keyes2023-01-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Nvim has Lua but the "nvim" CLI can't easily be used to execute Lua scripts, especially scripts that take arguments or produce output. Solution: - support "nvim -l [args...]" for running scripts. closes #15749 - exit without +q - remove lua2dox_filter - remove Doxyfile. This wasn't used anyway, because the doxygen config is inlined in gen_vimdoc.py (`Doxyfile` variable). - use "nvim -l" in docs-gen CI job Examples: $ nvim -l scripts/lua2dox.lua --help Lua2DoX (0.2 20130128) ... $ echo "print(vim.inspect(_G.arg))" | nvim -l - --arg1 --arg2 $ echo 'print(vim.inspect(vim.api.nvim_buf_get_text(1,0,0,-1,-1,{})))' | nvim +"put ='text'" -l - TODO? -e executes Lua code -l loads a module -i enters REPL _after running the other arguments_.
* ci: bump stylua action to v2 (#21455)dundargoc2022-12-17
|
* ci: use shell script to deduplicate workflow (#21079)dundargoc2022-12-05
|
* ci: use local action to make make cache keys consistent (#20538)dundargoc2022-12-05
| | | | The advantages of using an action is that it reduces boilerplate and repetition from the main ci.yml workflow.
* ci(windows): set $PSNativeCommandArgumentPassing = 'Legacy' (#21083)zeertzjq2022-11-17
| | | | | | 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.
* ci: install only necessary dependencies #20970dundargoc2022-11-06
|
* ci: remove ci/build.ps1 (#20891)dundargoc2022-11-05
| | | | 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.
* ci: skip tests if build fails (#20908)dundargoc2022-11-04
| | | | | | | | | | | | | | | | | | | | | | 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.
* ci(stylua): explicitly set the version to latest (#20869)dundargoc2022-10-30
| | | | This will silence the warning about needing to pin the version in the Summary Page.
* ci(windows): build dependencies with Ninja (#20800)dundargoc2022-10-30
| | | | This will save around a minute of CI time for each run. Also clean up build.ps1 by removing unnecessary code.
* ci: use GHA default clang for asan, tsan jobs #20846dundargoc2022-10-29
| | | | | | 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.
* build: remove python linting #20851dundargoc2022-10-29
| | | | | | 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.
* ci: bump ubuntu and macos to latest stable versions (#20479)dundargoc2022-10-17
|
* feat(cscope)!: removeLewis Russell2022-10-13
|
* ci: update which paths to ignore (#20510)dundargoc2022-10-06
| | | | | | | | 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.
* ci(stylua): change action version to v1 (#20273)dundargoc2022-09-22
| | | | Changing the action version to v1 allows us to automatically get patch updates as it points to the latest stable version.
* ci(lint): separate lintc from lintLewis Russell2022-08-14
| | | | All steps in lint now do now require a Neovim build.
* ci(lint): move some steps before buildLewis Russell2022-08-14
|
* ci(line): lintcfull -> lintcLewis Russell2022-08-14
| | | | | | | lintcfull == lintc + uncrustify We are already running uncrustify separately so can just run lintc instead.
* ci(lint): run uncrustify earlierLewis Russell2022-08-14
|
* ci(lint): generate PR suggestions from uncrustifyLewis Russell2022-08-14
|
* ci(cache): remove ccacheLewis Russell2022-08-12
| | | | It was never in action since migrating from travis to github actions.
* ci: test only a single macos version (#19418)dundargoc2022-07-18
| | | | The differences in MacOS releases are smaller since they're now upgraded yearly, meaning the need to test each version is reduced.
* ci: refactor build.ps1 #19336kylo2522022-07-17
| | | | | | | | | | | | Refactor `build.ps1` into a more modular design https://github.com/neovim/neovim/blob/9728f3b558c8cf9bd2bc331de8a5cc80ba0d3797/.github/workflows/ci.yml#L283-L296 - Separate CI steps. - Remove unneeded code related to setting up CMake. - Use parallel/incremental builds. - Fix github's cache. - Clear the way for the possibility of replacing this file with a cmake-preset: https://github.com/neovim/neovim/pull/19128
* ci: remove unnecessary file run_lint.shDundar Goc2022-07-11
| | | | | | It's a leftover artifact that currently just acts as an unnecessary intermediary script that calls the Makefile. It can be replaced by just calling the Makefile directly.
* build: rename build-related dirsJustin M. Keyes2022-06-28
| | | | | | | | | | | | | | Problem: Dirs "config", "packaging", and "third-party" are all closely related but this is not obvious from the layout. This adds friction for new contributors. Solution: - rename config/ to cmake.config/ - rename test/config/ to test/cmakeconfig/ because it is used in Lua tests: require('test.cmakeconfig.paths'). - rename packaging/ to cmake.packaging/ - rename third-party/ to cmake.deps/ (parallel with .deps/)
* build: add a cmake target for all used linters #18543dundargoc2022-06-09
| | | | | | | | | * build: move the logic for linters to cmake Cmake is our source of truth. We should have as much of our build process there as possible so everyone can make use of it. * build: remove redundant check for ninja generator The minimum cmake version as of writing this is 3.10, which has ninja support.
* ci: run tests with no treesitter parsers installedJames McCoy2022-06-08
|
* ci(uncrustify): show diff on failure #18780dundargoc2022-05-28
| | | | This will make it possible to see what needs to be fixed without having uncrustify installed locally.
* ci: bump github actions versions #18616dundargoc2022-05-20
|
* ci: lint with uncrustify #18563dundargoc2022-05-20
| | | | | | | This lint job will ensure that the C codebase is properly formatted at all times. This helps eliminate most of clint.py. To save CI time, it's faster to manually compile uncrustify and cache the binary instead of using homebrew (the apt-get package is too old).
* ci: remove mingw job #18580dundargoc2022-05-15
| | | | | | | | | | | | | | | | | | | | Unnecessary CI builds increase the change of spurious failures, which are costly noise. Of course, we should fix all legitimate bugs, but we also cannot micro-manage every platform, so there needs to be a clear motivation for the CI builds that we maintain. Reasons against maintaining a mingw CI job: 1. The windows mingw build is slow. 2. Failures: - https://github.com/neovim/neovim/issues/18494 - https://github.com/neovim/neovim/issues/18495 3. The mingw artifact is 10x bigger than the windows MSVC artifact: https://github.com/neovim/neovim/issues/10560 4. Our releases publish the MSVC (not mingw) artifact for Windows users: https://github.com/neovim/neovim/releases 5. Non-MSVCRT has limitations documented by libuv: http://docs.libuv.org/en/v1.x/process.html > On Windows file descriptors greater than 2 are available to the child process only if the child processes uses the MSVCRT runtime. Closes https://github.com/neovim/neovim/issues/18551
* ci: enable tests on drafts as well #18566dundargoc2022-05-15
| | | | | | | | | | | | | | | | | | | previous: https://github.com/neovim/neovim/pull/14123 CI tests were disabled on drafts #18566 to manage the large number of incoming jobs. While this did help, it had the drawback of making the purpose of the ready-for-review a bit fuzzier. It went from a clear "my PR is ready" signal to maintainers to somewhere between "my PR is ready but I need the tests to confirm" to "please don't merge yet, I just need to see the test results". Worse is that the specific case of wanting to see the test results but not wanting it merged is that this needs to be actively conveyed to the maintainers with a [DNM] or a comment to not merge the PR yet. All of this causes weird workarounds and noises which I believe isn't necessary. The reason why I don't think this workaround is needed anymore is that our CI now aborts a job if a new job from the same pull requests is created, which makes the "10 simultaneous jobs per PR" situations that triggered this not possible.
* ci: remove remnants of gperf #18550Justin M. Keyes2022-05-12
| | | | gperf was removed in 36613b888bae7df764a26a28ca1627a2c0c2edeb yay!
* ci: lint runtime with styluaChristian Clason2022-05-09
|
* ci: add a check with -funsigned-charzeertzjq2022-05-06
|
* ci: refactor and simplify CI processDundar Göc2022-03-10
|
* ci(macos): minimize log output from brew updateDundar Göc2022-03-07
| | | | | Also remove perl from brew install to prevent a warning that states it's already installed.
* ci: document the purpose of some non-obvious jobsDundar Göc2022-03-07
|
* ci(lint): re-add building of third-partyJames McCoy2022-02-27
|
* ci: add timeout to all jobsDundar Göc2022-02-26
|
* Merge pull request #17467 from dundargoc/ci/remove-failing-windowsJames McCoy2022-02-25
|\ | | | | ci: remove failing windows CI tests
| * ci: bump Windows image to windows-2019James McCoy2022-02-20
| | | | | | | | | | | | | | | | The VS 2019 CMake generator no longer has different generator types for different architectures. Now, the architecture is specified via CMake's `-A` switch. However, this requires we also propagate `${CMAKE_GENERATOR_PLATFORM}` to the bundled deps, so they build for the same architecture as Nvim.
* | ci: skip ci workflow on only documentation changesDundar Göc2022-02-21
| |
* | Merge pull request #17469 from jamessan/use-sysdeps-for-lint-ciJames McCoy2022-02-20
|\ \ | | | | | | Use system dependencies for lint CI
| * | ci(lint): explicity build nvimJames McCoy2022-02-19
| | | | | | | | | | | | | | | | | | “make clint-full” bypasses the normal mechanisms used to communicate build flags in the CI jobs, so explicitly build nvim before running the lint jobs.
generated by cgit (git 2.34.1) at 2026-10-21 00:52:36 +0000