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

Let's put aiohttp-devtools under the aio-libs org on PyPI #634

Open
webknjaz opened this issue Dec 20, 2023 · 5 comments
Open

Let's put aiohttp-devtools under the aio-libs org on PyPI #634

webknjaz opened this issue Dec 20, 2023 · 5 comments

Comments

@webknjaz
Copy link
Member

See the details @ https://github.com/orgs/aio-libs/discussions/26.

For this, we'll need somebody with Owner privileges to either give me access on PyPI (the username there is the same — webknjaz) or be invited to the org by me (for that I'd need the username of such an individual).

As a bonus, this will also allow us to set up secretless publishing from GHA to PyPI and get rid of the in-repo secrets.

cc @samuelcolvin

@samuelcolvin
Copy link
Member

Happy to do whatever you prefer, let me know what I need to do.

@webknjaz
Copy link
Member Author

@samuelcolvin
Could do both. I'll invite you and you give me the Owner access.

@webknjaz
Copy link
Member Author

Invitation sent.

@webknjaz webknjaz changed the title Let's put aiohttp-admin under the aio-libs org on PyPI Let's put aiohttp-devtools under the aio-libs org on PyPI Dec 21, 2023
@samuelcolvin
Copy link
Member

done.

@webknjaz
Copy link
Member Author

Great, I moved it. Also note that I reduced privileges of the regular user accounts, so that the higher privileges are only available through the org. Though, if you need an Owner privilege for some reason, I can create an org team for that. Let me know!

I'll keep this issue open until the bot account is replaced with secretless publishing.

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