How to manage the authentication

[Eomm]

Check how to manage the authentication process. The problems to face are 3:

• github auth to interact with repo
• npm for the publishing of the module
• a little thought to CI/CD - we don't want to close this door too soon

I used already the Github API but I used a token:

https://github.com/Eomm/next-node-bot/blob/b5dc70255d9bf5d97fac780224e9788a0b9fddf3/index.js#L13

But I know it is only for private usage.. for what I know now I should go deeper

[mcollina]

The tool should work with zero setup on the repo side. We have 30+ repositories in this repo, and we should really avoid to configure them all.

[Eomm]

Yes, sure!!

I was thinking that there are 3 auth we could use:

• git client, using the spawn.. so we don't' have to manage anything
• npm client, using the spawn.. so we don't' have to manage anything
• Github API, we need to deal with it because there isn't a "build a release" command in the cli, but only a tag

In this way, it should be quite simple to do, but for sure we can't think on CI/CD because nobody installs git client on the CI server 😅

[mcollina]

You don’t need to auth the git client, nor npm. You just need to auth github with a personal access token.

[mcollina]

(auth for git and npm isngoing to be done by the user separately)

[Eomm]

Does someone know if there is some "dev" environment to try the GitHub Rest API?

I have googled a bit but I don't find anything more than the test-env for GH APP

[mcollina]

Yes there is! Create a personal repo!

[Eomm]

Solved