Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/assets/nvf-logo-work.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 2 additions & 2 deletions .github/workflows/cachix.yml
Original file line number Diff line number Diff line change
Expand Up @@ -36,13 +36,13 @@ jobs:
with:
authToken: ${{ secrets.CACHIX_TOKEN }}
extraPullNames: nix-community
name: neovim-flake
name: nvf

- name: Set default git branch (to reduce log spam)
run: git config --global init.defaultBranch main

- name: Validate Flakes
run: nix flake check

- name: Build neovim-flake with default settings
- name: Build nvf with default settings
run: nix build .#${{ matrix.package }} --print-build-logs
3 changes: 3 additions & 0 deletions .github/workflows/check.yml
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,9 @@ jobs:
runs-on: ubuntu-latest
if: "!contains(github.event.pull_request.title, '[skip ci]')"
strategy:
# avoid having 2 jobs building ndg when no cache is available
# TODO: there is probably a better way
max-parallel: 1
Comment on lines +87 to +89
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@NotAShelf if it's okay with you, I'd like to get rid of the matrix strategy here and just do nix build .#docs .#docs-html .#docs-manpages .#docs-json so I can just not worry about redundant ndg builds in parallel

matrix:
package:
- docs
Expand Down
2 changes: 0 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -243,8 +243,6 @@ better prepare for breaking changes.

**A**: Quite possibly. **nvf** started as "neovim-flake", which does mean it is
and will remain flakes-first but we might consider non-flakes compatibility.
Though keep in mind that **nvf** under non-flake environments would lose
customizability of plugin inputs, which is one of our primary features.

**Q**: I prefer working with Lua, can I use nvf as a plugin manager while I use
an imperative path (e.g., `~/.config/nvim`) for my Neovim configuration instead
Expand Down
Loading