Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: maintain rockspec with multiple users on https://luarocks.org/ #127

Open
kenhys opened this issue Nov 29, 2017 · 1 comment

Comments

@kenhys
Copy link

kenhys commented Nov 29, 2017

Problem

It seems that there is no way to maintain rockspec with multiple users on https://luarocks.org/

Actual

There is one solution to maintain rockspec with multiple users - share one account of https://luarocks.org/ with among them.
But I hope to maintain rockspec with multiple users - maintain rockspec by group.

Expected

Allow to join specific group and maintain rockspec with multiple users. (I assume that owner and permitted users to upload rockspec for https://luarocks.org/)
When some person can't maintain specific rockspec anymore, others can do if rockspec is maintained by group.

@kenhys kenhys changed the title Feature request: maintain rockspec with multiple users Feature request: maintain rockspec with multiple users on https://luarocks.org/ Nov 29, 2017
@Alloyed
Copy link

Alloyed commented Oct 18, 2020

yeah; I am finding myself in the same situation, where I would like to my projects that have joint maintainership the ability to upload their own versions of existing packages under my account.

here are some approaches I've been able to pull out of my brain, with more/less effort involved on either the repository maintainer or the luarocks side:

  1. Create API keys, then on the luarocks website restrict these API keys to only function for a given module. requires some work on the luarocks end, but then you can just hand a string to any given maintainer.
  2. New account per module: no feature work, but a bit of a pain. if a package is already listed under a specific account, switching accounts can break links to it.
  3. Write a bot that auto-picks-up rockspecs pushed to the repository and has an API key associated with my account. then anybody with write access or the ability to make a PR can make rockspec changes, but requires somebody to actually write that bot. may be a good way to (misuse) github actions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants