ways to run luarocks-tag-release locally / easier way to test generated rockspec #465
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
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.
when I tried to add a plugin on NURR, I worried it wouldn't work (because it generated or needed C libraries etc and it was not possible to see the generated rockspec: "Push and prey". I would like to be able to see the generated rockspec before merging and I find it hard to run the action locally.
I quickly hacked something to be able to generate the rockspec bypassing the github action:
jq '.plugins[] | select(.name == nvim-telescope/telescope-fzf-native.nvim)' ~/nurr/plugins.json | ~/luarocks-tag-release/bin/rockspec-generator-json.lua.I imagined 2 new executables:
rockspec-generator-jsonto generate a rockspec for nurr.rockspec-generator-clithat one could run from cli with an argparse interface, akarockspec-generator-cli --name toto --version 0.1 --dependency=plenary.nvim --dependency=nui.nvim.What is your opinion on that ? is it something worth pursuing ?