Register tokens for npm, gh and others

[g-cheishvili]

Need NPM_TOKEN for publishing the library GH_TOKEN for releases on gh side GH_NAME and GH_EMAIL NX_CLOUD_AUTH_TOKEN for Nx cloud

[petermuessig]

For publishing releases on GH side, you can just use a proper GH action and rely on the internal provisioning of the GITHUB_TOKEN, e.g. https://github.com/actions/create-release:

        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # This token is provided by Actions, you do not need to create your own token

I assume with this approach we also do not need a GH_NAME and GH_EMAIL.

For the NPM_TOKEN, we can reuse on of our NPM bot accounts for the publishing process of the library.

But for the NX_CLOUD_AUTH_TOKEN, I don't know yet - something to be clarified...

[g-cheishvili]

For publishing releases on GH side, you can just use a proper GH action and rely on the internal provisioning of the GITHUB_TOKEN, e.g. https://github.com/actions/create-release:

        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # This token is provided by Actions, you do not need to create your own token

I assume with this approach we also do not need a GH_NAME and GH_EMAIL.

For the NPM_TOKEN, we can reuse on of our NPM bot accounts for the publishing process of the library.

But for the NX_CLOUD_AUTH_TOKEN, I don't know yet - something to be clarified...

When it is up, I will generate the token again and then we will register account in nx cloud and register project with that token

[petermuessig]

NPM_TOKEN repository secret has been created!

[g-cheishvili]

All the needed tokens are done for now