Skip to content

Update token for wiby-bot in the wiby repo #629

Open
nodejs/admin
#986

Description

@bjohansebas

As part of reactivating that package, which will later be used in Express, it's necessary to update the token that integrates with the @wiby-test test organization, which communicates with the @wiby-bot.

I'd like to know who has access to these resources so they can help me re-enable the integration.

cc: @dominykas @ljharb @mhdawson

Activity

  1. mhdawson commented on May 12, 2025

    @mhdawson
    Member

    I don't see anything in 1 password that looks like it iss related to the wiby. @BethGriggs, @dominykas, @ghinks do either of you have any context on where credentials might have been stored

  2. dominykas commented on May 13, 2025

    @dominykas
    Member

    I think I probably have the credentials. Was meant to share it with someone, but I'm not sure we ever went through with that. What's an appropriate procedure to do that?

    We should probably also add more people to https://github.com/wiby org.

  3. mhdawson commented on May 13, 2025

    @mhdawson
    Member

    @dominykas if you can share with me I'll add to the projects 1password account and then we can share with others through that.

  4. dominykas commented on May 14, 2025

    @dominykas
    Member

    I have the password. The 2FA is associated with one of my emails for now (but it also says it needs to set up proper 2FA within 8 days - I'll leave it as is).

    What's a secure way to send that password over @mhdawson?

  5. mhdawson commented on May 14, 2025

    @mhdawson
    Member

    @dominykas the best way is likely for me to create a vault, invite you and then have you add it there. Will do that now

  6. mhdawson commented on May 14, 2025

    @mhdawson
    Member

    Invite sent

  7. bjohansebas commented on May 15, 2025

    @bjohansebas
    MemberAuthor

    We should probably also add more people to https://github.com/wiby org.

    I'm glad to be part of those organizations so we can keep moving forward, but I don’t quite understand why there are two (@wiby and @wiby-test). Wouldn’t one be enough?

  8. dominykas commented on May 15, 2025

    @dominykas
    Member

    I don’t quite understand why there are two

    One is a bot account (i.e. something that can perform things), another one is an org for repos (we mostly just reserved the name, just in case we want to ever move it out of pkgjs).

  9. dominykas commented on May 15, 2025

    @dominykas
    Member

    @mhdawson I signed up, but I'm not sure I have access to some shared space there?

  10. mhdawson commented on May 15, 2025

    @mhdawson
    Member

    I shared whe Wiby Vault with you earlier and I can see that you are listed with view,edit,export,print and share so I think you should be able to view/add to the vault. On the left hand side of the default page I think you should see an option called "Vaults", and then you should see one called "wiby" in your list.

  11. dominykas commented on May 17, 2025

    @dominykas
    Member

    Cool, yeah - it wasn't there yesterday (or I somehow missed it). But it's there now, so the password is shared. It's still associated with my email though (and will probably require me to click through a link to log-in) - is there some shared email group I could set it to? I could also set up email forwarding for it. Or possibly just setting up 2FA would do the trick, but not sure how to go about that for shared accounts?

  12. bjohansebas commented on May 25, 2025

    @bjohansebas
    MemberAuthor

    An email address was suggested a long time ago for the administrative members

    #441 (comment)

  13. mhdawson commented on May 26, 2025

    @mhdawson
    Member

    @dominykas we can set up an alias in https://github.com/nodejs/email/blob/main/iojs.org/aliases.json. If you could PR in in an appropriate email name (will be whatever you choose @iojs.org)

  14. dominykas commented on Jun 3, 2025

    @dominykas
    Member
  15. mhdawson commented on Jun 4, 2025

    @mhdawson
    Member

    @dominykas landed and deployed. Once you update to have it associated with that new email can you add the credentials to the vault and let us know?

  16. dominykas commented on Jun 9, 2025

    @dominykas
    Member

    OK, the email is now changed and the 2FA info is in 1password (although keeping both - the password and the 2FA in the same place kind of defeats the purpose of 2FA? Out of scope for a discussion here, but I can't not say it 😁).

  17. ljharb commented on Jun 9, 2025

    @ljharb
    SponsorMember

    as long as 1password access has 2fa, then it's fine imo

  18. bjohansebas commented on Jun 10, 2025

    @bjohansebas
    MemberAuthor

    Great, @mhdawson or @dominykas can fix the token, please.

  19. wiby-bot commented on Jun 10, 2025

    @wiby-bot
  20. bjohansebas commented on Jun 10, 2025

    @bjohansebas
    MemberAuthor

    I'm not sure that's the right way, that file is only for nodejs-bot, but I can try to request it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions