diff options
| author | dundargoc <33953936+dundargoc@users.noreply.github.com> | 2023-05-15 00:08:57 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-05-15 00:08:57 +0200 |
| commit | e71c7898ca3cf3af1243227ff3cba526d48897e8 (patch) | |
| tree | 4142088c12e6f50232480f32d3c93d5e77dca5a0 /runtime/lua/vim/treesitter/_fold.lua | |
| parent | ecd6d679a020ff97156de2fd3c443a77a671ac3d (diff) | |
| download | rneovim-e71c7898ca3cf3af1243227ff3cba526d48897e8.tar.gz rneovim-e71c7898ca3cf3af1243227ff3cba526d48897e8.tar.bz2 rneovim-e71c7898ca3cf3af1243227ff3cba526d48897e8.zip | |
ci: trigger tests when pushing
This will allow contributors to test changes in their own fork when
pushing without needing to make a pull request. This can be useful when
wanting to test out an idea before initiating a review process.
Make the following assumptions when defining concurrency:
- Pull request will work the same.
- Pushes to the neovim repo will work the same: each unique commit will
trigger a test run that won't cancel each other.
- Pushes to forks will cancel older CI runs on the same branch, similar
to how pull requests work.
This will create duplicate CI runs when doing a pull request, one in the
neovim repo for the pull request event and one in the fork for the push
event. This is an acceptable trade as the runs in the fork doesn't count
towards the CI limit of neovim. Contributors are also free to disable
these actions in their own fork if they wish.
Diffstat (limited to 'runtime/lua/vim/treesitter/_fold.lua')
0 files changed, 0 insertions, 0 deletions