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

More maintainers for agenda-rest + npm package #74

Open
keyvan-m-sadeghi opened this issue Mar 11, 2020 · 27 comments
Open

More maintainers for agenda-rest + npm package #74

keyvan-m-sadeghi opened this issue Mar 11, 2020 · 27 comments

Comments

@keyvan-m-sadeghi
Copy link
Member

Would be cool if we can have a couple more maintainers with write access to the repo as well as the npm package for faster publish, as it seems I've been a bit neglectful in this regard.

Anyone feeling like it, your help is very much appreciated.

I'd need npm usernames.

@geosp
@sampathBlam

@sampathBlam
Copy link
Contributor

@keyvan-m-sadeghi : That's awesome. I am in !!

@keyvan-m-sadeghi
Copy link
Member Author

@sampathBlam great, can I have your NPM username?

@OmgImAlexis
Copy link
Member

I really don't get why more users is the right idea here. I would highly suggest you reconsider this and instead use Github actions to publish the package.

If any of the users get their accounts compromised they'll be able to publish, automated publishing avoids this.

@keyvan-m-sadeghi
Copy link
Member Author

Very good suggestion @OmgImAlexis, I wasn't aware that GitHub actions supports this use case. Also I noticed that I actually don't have admin rights over the repo. Could you please help with setting this up with best practices?

@OmgImAlexis
Copy link
Member

Don't have a great deal of spare time but this should help and I'm free to answer questions you have. I'd suggest making the publish happen on new commit to master that way it'll only happen when we merge a PR, or push directly to master.

@geosp
Copy link
Collaborator

geosp commented Oct 9, 2020

I'm available too. I can help with setting up Github actions.

@keyvan-m-sadeghi
Copy link
Member Author

Great @geosp, I really haven't found the time to go about it.

@OmgImAlexis appreciate if you can give @geosp write access to the repo, I can do the npm side.

@geosp
Copy link
Collaborator

geosp commented Oct 9, 2020

@keyvan-m-sadeghi and @OmgImAlexis I will do my best to help. I notice that the build was failing for a long time so I took the time to fix that too in my latest PR #93 . Thank you.

@keyvan-m-sadeghi
Copy link
Member Author

Looks good @geosp, what's your username on npm?

@geosp
Copy link
Collaborator

geosp commented Oct 10, 2020

It is gffajardo.

@geosp
Copy link
Collaborator

geosp commented Oct 12, 2020

@keyvan-m-sadeghi and @OmgImAlexis Any word regarding access or PR #93 ? I know you are busy, please let me know. Thank you.

@OmgImAlexis
Copy link
Member

Invite should have been sent on GitHub sorry for it taking so long.

@geosp
Copy link
Collaborator

geosp commented Oct 14, 2020

Thank you @OmgImAlexis

@geosp
Copy link
Collaborator

geosp commented Oct 14, 2020

@keyvan-m-sadeghi Any word in regards to NPM access?

@keyvan-m-sadeghi
Copy link
Member Author

Sorry @geosp been away for a few days. I just checked npm and noticed I no longer have admin access there.

@OmgImAlexis can you give write access to @geosp on npm? Username is gffajardo.

Great work on refactoring @geosp 🎉 👍

@geosp
Copy link
Collaborator

geosp commented Oct 17, 2020

Thank you @keyvan-m-sadeghi. I want to use this PR to test deploying to npm using GitHub actions. I assume you approve of the changes in #94 .

@keyvan-m-sadeghi
Copy link
Member Author

Yeah all good 👌
Did you get the npm access? I have write access but not admin, let me know if I can help with anything @geosp

@keyvan-m-sadeghi
Copy link
Member Author

@geosp I'm trying to give you access through the "teams" feature of npm, check your email for an invite from "assister" org and let me know if that gives you write access to the agenda-rest package

@keyvan-m-sadeghi
Copy link
Member Author

@geosp give me a hint when you accepted the invite, apparently there's an additional step I need to take before you actually get write access (adding you to agenda-rest-write team, which requires being a member of the assister org first, I'm not sure even @OmgImAlexis can add new members now, seems I've created this package under this username first then changed it to an org at some point, which is causing all this trouble).

@geosp
Copy link
Collaborator

geosp commented Oct 17, 2020

@keyvan-m-sadeghi Thank you for your assistance. I'm in the org now.

@keyvan-m-sadeghi
Copy link
Member Author

@geosp done, you now have write access to the npm package. You need to enable 2FA in your npm account to publish though.

Feel free to merge pull requests as they come in, welcome aboard!

@geosp
Copy link
Collaborator

geosp commented Oct 29, 2020

Thank you, guys. I got really busy there for a while. I will be working on the GitHub-actions task now.

@geosp
Copy link
Collaborator

geosp commented Oct 30, 2020

@keyvan-m-sadeghi and @OmgImAlexis Hello guys. I created an issue for the implementation of GitHub actions and a PR to resolve the issue. Please take look at PR #96 .

@geosp
Copy link
Collaborator

geosp commented Nov 4, 2020

@OmgImAlexis Can you please add the NPM security token to GitHub so that the workflow is able to publish the library to NPM. Thank you so much for your help.

@geosp
Copy link
Collaborator

geosp commented Nov 5, 2020

I was able to publish the new version manually, but it will be nice to have it done automatically.

@keyvan-m-sadeghi
Copy link
Member Author

Sorry that I've been away @geosp, it is indeed nice to automate publishing, hope @OmgImAlexis reads this as I don't have admin rights for the repo to give you the keys.

@keyvan-m-sadeghi
Copy link
Member Author

Also thanks for the great work on updating everything @geosp 🎉

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

4 participants