| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
- Removed NSIS installer.
- Prevents undefined behaviour when two installations are performed to the same directory (NSIS + MSI).
- Reduced cost of maintaining two installers that do the same thing.
- Chose Wix MSI due to its better integration with Windows.
- Added Wix patch file to add neovim binaries to the system path during installation.
- Replaced neovim installer icons with better looking versions.
- Renamed neovim installer icons from logo.ico -> neovim.ico for all
icons to better reflect contents.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
Makefiles are used for builds, so why not label changes to these
files as build
|
|\ \
| |/
|/| |
ci(doc): improve missing docs workflow
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1. Add new pattern `runtime/doc/**`. This is a common case were the
contributor modifies only the help file but the doc gen would discard
their changes.
2. Add to the output what the changes after running doc gen would be.
[skip ci]
|
|\ \
| |/
|/| |
ci: automatic breaking change label
|
| |
| |
| |
| |
| | |
When the PR title contains the breaking change format apply the
breaking-change label.
|
|/
|
|
| |
Co-authored-by: Jordan Haine <jhaine@securitycompass.com>
|
|
|
|
| |
After #17623 this pattern is no longer necessary.
|
|
|
|
|
| |
Also error on the side of security adding an extra check on the
automatic PR step.
|
|
|
|
|
|
|
|
| |
Repurpose the api-docs workflow to also run in all PR's but work only as
a check, if the changes in the PR introduce doc changes that are not
committed fail.
[skip ci]
|
| |
|
|
|
|
|
| |
Also remove perl from brew install to prevent a warning that states it's
already installed.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
ci: remove failing windows CI tests
|
| |
| |
| |
| |
| |
| |
| |
| | |
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: improve cpack packaging
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Addresses: #12571
- Added the following installers through CMake files:
- Windows NSIS.
- Windows MSI.
- Windows zip.
- MacOs tarball.
- Linux tarball.
- Linux Deb package.
- Tweaked pipeline CPack commands to build using new CMakeLists.txt configuration file.
- Added icons and relevant packaging files.
- Updated notes.md to reflect new installation instructions.
This isn't meant to be the perfect solution, it's simply a first pass at using a
simple packaging system to build Windows installers. A Debian package has also
been added since it's very easy but other packages have been left out due to
limiting the scope. Hopefully we can build further upon this and improve it
over time with code signing, better icons and more user-friendly installation
graphics and so on.
|
| | | |
|
|\ \ \
| | | |
| | | | |
Use system dependencies for lint CI
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
“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.
|
| | | | |
|
| | |/
| |/| |
|
|/ / |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | | |
This makes testing the workflows much smoother.
|
|\ \ \
| | | |
| | | | |
ci: run each test suite in a separate github step
|
| |/ /
| | |
| | |
| | |
| | | |
This should help combat some of the lagginess when looking at the CI
logs in the browser.
|
|/ / |
|
| | |
|
| | |
|
| |
| |
| |
| | |
This reverts commit a91a5c1880dcb7718aed4e19ff2757be0948e7d5.
|
| | |
|
| | |
|
|\ \
| | |
| | | |
ci: only request review on open non-draft PRs
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
ci(reviews): upgrade github-script version to v6
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 559aa4179c639f5ebd45474a36361343ac2371cf.
I mistakenly believed both ways of writing were equivalent; this is
untrue. Setting continue-on-error to true will make the job pass, but
an error annotation will still be created which is misleading since it's
not actually an error.
|
| | |
|
| | |
|
| | |
|
| | |
|