You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For projects with dependencies that are private repositories, it's necessary to set up a secret token to authenticate Git.
369
+
370
+
- Create a [fine-grained personal token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-fine-grained-personal-access-token)
371
+
- Go to developer settings, select Personal Access Tokens, then Fine-grained tokens.
372
+
- Click "Generate new token"
373
+
- Change the resource owner to the organization `TangibleInc`
374
+
- Allow cloning all repositories inside your github action.
375
+
- Add this token as a repository-level secret
376
+
- Go to repository's Settings -> Security -> Secrets and variables -> Actions
377
+
- Add a new repository secret with the name `TANGIBLE_PIPELINE_ACCESS_TOKEN`
378
+
- The value is the newly generated personal token
379
+
- Pass the token in GitHub Actions, for example `.github/workflows/release.yml`
0 commit comments