Rather than using a Team Bot, a GitHub App Integration can be used in GitHub (Cloud or Self-Hosted) to efficiently onboard new teams to Codecov.
This Github App integration is not a replacement for the Oauth Login setup, which is mandatory.
The App Integration will allow teams to add Codecov directly to their repositories via the GitHub user interface.
This integration is meant to be a replacement for the Team Bot for GitHub (Cloud or Self-Hosted). Using it will ensure that comments are posted to Pull Requests as Codecov, rather than a Team Bot user.
This Approach works for both GitHub and GitHub Enterprise
Regardless of which github version you're using this approach can work for either. However you will need to be mindful of adapting the code snippets to your particular scenario (i.e., github, or github_enterprise in the codecov.yml)
Creating a GitHub App Integration
Webhooks need to be enabled for the GitHub App to work. This is the method the app uses to connect and communicate with Codecov.
To create a GitHub App Integration for Codecov, first navigate to your organization in the GitHub UI.
You can use the drop down in the left sidebar of the Settings page in GitHub to access your organization.
Then from the Sidebar Click Developer Settings > GitHub Apps:
Choose "New GitHub App":
Create the App for your Organization
When creating the GitHub app, ensure that you're creating it for your organization, not your personal account. The URL on the app creation page should read: https://github.com/organizations/ - /settings/apps/new
And fill out the relevant fields for app creation:
It's important to set the proper callback URL. They should point to your Codecov Enterprise install as follows:
For the webhook URL:
You should provide a secret.
1github: 2 webhook_secret: "<some-secret>" 3
Once provided, you will want to ensure that you properly provide the secret in the Codecov Enterprise codecov.yml.
The following screenshot shows all permissions needed by the app integration, as well as the relevant events. For visibility permissions with a greater setting than "No Access" have been emphasized in green.
Required repository permissions.
Required organization permissions.
No user permissions are required. All can be set to "No Access"
Required user permissions.
Using http://GitHub.com ?
If you're not using GitHub Enterprise, make sure that you only publish this app for your organization.
Generate and Add a PEM file to Codecov.
After creating the GitHub App, Github will prompt you to create a .pem file from the github ui. This will result in a .pem file you can download. Once downloaded you will need to place this file in the same directory as your codecov.yml and docker-compose.yml and update your docker-compose.yml as follows:
1web: 2 #... other configuration 3 volumes: 4 - ./file.pem:/config/file.pem 5worker: 6 #... other configuration 7 volumes: 8 - ./file.pem:/config/file.pem 9
You will need to add the
webhook_secret sections to the
github_enterprise) section of your codecov.yml as follows:
1github: 2# ... 3 webhook_secret: "ff523b3162ef64604f03c94459" 4 5# values from the Github App integration 6 integration: 7 id: 63040 # App ID value shown on 8your integration's page in GitHub 9 pem: /config/file.pem # path to the pem file you 10created in the `web` and `worker` containers. 11
Install App Integration to your organizations
Depending on your GitHub settings, you may have to install the Codecov Github App on any organizations that you wish to use it with. This can be done from the app settings screen.
After installing the app you can verify installation on the organization's installed GitHub apps page.
If you don't receive comments on Pull Requests for Repositories with the App Integration installed, visit the repo settings page for that particular repository on your Codecov Enterprise install:
For http://GitHub.com :
For GitHub Enterprise:
Once there, check the "GitHub Webhook" section and press the "Create Web Hook" button if a webhook is not already set.
Was this article helpful?
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
We appreciate your effort and will try to fix the article