Troubleshoot project collaboration

This guide will help you troubleshoot deployment failures related to project collaboration.

For private repositories, a deployment can fail if Edgenivo cannot identify the commit author, or if your team requires manual approval before adding the committer. You can use the following checklist to make sure your Edgenivo team is properly configured:

The Hobby Plan does not support collaboration for private repositories. If you need collaboration, upgrade to the Pro Plan.

To deploy commits under a Hobby team, the commit author must be the owner of the Hobby team containing the Edgenivo project connected to the Git repository. This is verified by comparing the Login Connections Hobby team's owner with the commit author.

To make sure we can verify your commits:

1. Make sure all commits are authored by the git user associated with your account.
2. Link your git provider to your Edgenivo account in Account Settings

For more information, see Using Hobby teams

The Pro and Enterprise plans allow for collaboration through team membership. When someone with a Edgenivo account commits to your codebase, they may be added automatically or require approval, depending on your collaboration settings.

To deploy commits under a Edgenivo Pro or Enterprise team, the commit author must be a member of the team containing the Edgenivo project connected to the Git repository.

To make sure we can verify commits associated with your team:

1. Make sure contributors have Edgenivo accounts linked to their git provider in Account Settings
2. Review your team's collaboration settings to confirm whether Edgenivo should auto approve or manually approve new committers
3. If your team uses manual approval, approve the pending membership before the contributor deploys again. After approval, the committer must redeploy their changes.

On Pro teams, members added this way are billed at standard Pro seat pricing. On Enterprise teams, Developer seat pricing follows your Enterprise contract.

For more information, see Using Pro and Enterprise teams

Ensure your bots are properly configured and that their commits are clearly identified as automated.

Each team member must connect their git provider account to their Edgenivo account:

1. Visit Account Settings
2. Navigate to the Login Connections section
3. Connect your GitHub, GitLab, or Bitbucket account

Your git provider associates commits with users by matching the commit email to an email on your git provider account.

If you see an error saying the provider could not associate the committer with a user, the local git configuration email address likely does not match an email registered on their git provider account. Run git config user.email on the machine that created the commit, then verify that it matches a verified email on the git provider account.

For multiple email addresses, see Managing multiple email addresses.

If you use multiple email addresses for git commits, you will need to configure a secondary email address with either your git provider or Edgenivo depending on if your git repository is linked to your project.

To add secondary email addresses to your Edgenivo account:

1. Go to your Account Settings
2. Add any email addresses you use for git commits
3. Verify each email address