provide a mechanism to test rockspec upload.

[teto]

@mrcjkb has created an action to automatically push rockspecs to luarocks https://github.com/nvim-neorocks/luarocks-tag-release .

Currently it doesn't upload to luarocks in PRs but I would like to provide a way to do that so that users can see from the PR stage that it works. Otherwise you have to merge in master to fully test the github action.

Right now, I push the packages under a different name not to override the official releases, for instance "nvim-treesitter-pr42" instead of "nvim-treesitter". Apparently they end up in the root manifest, at least on the homepage as is the case for https://luarocks.org/modules/teto/nvim-treesitter-test
I wonder what's the best mechanism to test the upload without polluting the ecosystem/platform, eg:

• can I specify a custom manifest on luarocks upload so that the package doesn't end up in the root manifest ? and this manifest could be reset everyday for instance ?

cheers

[hishamhm]

I think this is more a feature request for https://github.com/luarocks/luarocks-site moreso than for the CLI tool, since most of the lift to get that to happen would to update the server API to accept a manifest parameter and behave accordingly... if we get this support on the server side, adding the client behavior on luarocks upload should be the easier part.