Git Configuration

​

Overview

Git commit email can be configured at both the user level and the workspace level. Your user-level git email is set at Dashboard → Settings → Git. This is a per-user setting and only affects sessions mapped to your Blocks user. Workspaces can also set a global git email. That workspace-level value is used for unmapped sessions, or for mapped sessions where the workspace user has not set their own git commit email. If neither value is configured, Blocks falls back to task@blocks.team.

​

Precedence

Blocks resolves commit author email in this order:

1. Mapped user git email
2. Global workspace git email
3. task@blocks.team

​

Setting your commit email

1. Go to Dashboard → Settings → Git
2. Enter the email address you want to use for commits
3. Save

All new sessions mapped to your Blocks user will use this email as the commit author.

​

Workspace fallback

Workspace admins can configure a global git email for the workspace. This value is used when:

• A session cannot be mapped to a specific workspace user
• A session is mapped, but that user has not configured their own git email

Only a workspace admin can update the workspace-level git configuration.

​

GitHub considerations

​

PR approvals

If you want to ensure that PRs opened by Blocks are reviewed by another team member, enable “Require approval of the most recent reviewable push” in your GitHub branch protection rules. That setting prevents the author of the most recent push from approving the PR themselves, so another organization member must approve.

​

Vercel build previews

Setting your commit email to an email in your GitHub, GitLab, or Bitbucket organization allows Vercel to create build previews for PRs opened by Blocks.