add: Further explanation on how to run CI local #1131
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To run test and lint locally, in case lualine repo is not in the same path as plenary and web-dev-icon, we can simply change the relative path on tests/minimal_init.lua and push the original to the remote.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think that most people have
plenary,web-dev-icons, andlualine.nvimin a separate path. In my case, thelualinerepo that I use for development is in a development folder on my home, the plugins managed fromlazy.nvimis in.local/share/....To run CI locally is as simple as changing the path on the
tests/minimal_init.luafile, testing locally, and then removing the local configuration and push the original file to let CI work properly. Let people (especially new contributors) know about it!