The following doc describes SCM authentication as is applicable to Gitpod
Classic Pay-As-You-Go (
gitpod.io
). For Enterprise users, please refer to
the Enterprise SCM documentation.FAQs
”Email address already used in another account” when trying to login into Gitpod
Send us a message through the contact form with your Gitpod account email. After you reach out, we will delete your account so that you can sign up again, which should resolve your issue.How to get SCM API token from Gitpod’s GitLab, GitHub or Bitbucket integration as an environment variable
Rungp init
on your terminal or manually create a file called .gitpod.yml
- Put the following line in your
.gitpod.yml
:
- Create a file called
.gitpod.Dockerfile
and put the following content in it:
- Validate your configuration changes by running
gp validate
in your workspace. - Apply your .gitpod.yml changes by committing and restarting a new workspace.
$SCM_TOKEN
environment variable after you commit and create a new workspace, this variable will contain an API token based on the Git context (i.e. Gitlab/GitHub/Bitbucket)
How to use a private GitHub email or custom email for Git commits
At the variables page, create two variables[1] called:GIT_COMMITTER_EMAIL
GIT_AUTHOR_EMAIL
*/*
as the scope.
Now all of your new workspaces should use them for Git commits. If you have a workspace running, you can restart it or run eval "$(gp env -e)"
in it.