Access Emerge Metadata

1. Navigate to the relevant build and click the Actions menu
2. Select "Emerge metadata" from the dropdown

3. The Emerge Metadata pop-up shows details about your upload, including build details and VCS metadata.
   To test your Git integration, click on the blue button to "Test Git Integration."

4. View the integration test result to diagnose any issues in your integration

Resolving Common Issues

1. Detached HEAD State

   • This usually happens when your CI/CD pipeline builds from a commit instead of a branch.
   • Ensure that your CI configuration explicitly checks out the branch instead of just the commit SHA.

2. Missing GitHub Access

   • If the test results indicate Emerge does not have access, ensure the Emerge GitHub App is installed and authorized for your repository.
   • Check GitHub repository settings → Installed GitHub Apps → Confirm Emerge Tools is listed and has access.

3. Incorrect SHA Format

   • GitHub sometimes displays abbreviated SHAs (e.g., af0d70b) while Emerge uses full-length SHAs (e.g., af0d70bf30bce7b869aaa82f5b9dc1b5cc33ea9e).
   • If there’s a mismatch, try manually confirming that the full SHA exists in your repo.