Skip to main content
Connect Athenian to GitHub

Integrate your Athenian account with GitHub and configure the right repositories

José Caldeira avatar
Written by José Caldeira
Updated over a week ago

To use Athenian you need to connect it with your GitHub account. In this article we will describe how to create an Athenian account and how to later on fine tune it.

Create a new account

1. Request a demo and we will get back to you with an invite to create an account;

2. Ask a Github admin to create your Athenian account using the link we sent you;

We will now import and pre-compute your data to make sure you have a smoother experience when using Athenian. Depending on the number of repositories this can take up to 48 hours.

Congratulations! You are on the way to data-driven engineering with GitHub empowered analytics.

Configure your account

1. Go to GitHub and select the Athenian Owl;

2. Configure Athenian Owl in the account you want to track;

3. During configuration/installation you can pick all repositories, or specify only the repos you want to track (don't worry, you'll be able to change this later);

We will now re-import and pre-compute your data to make sure you have a smoother experience when using Athenian. Depending on the number of repositories this can take up to 48 hours.

What if I have multiple GitHub organizations?

In this case, if your team works across multiple GitHub organizations that are in practice part of the whole software development process, you may want to bring them together under your Athenian account.

  1. ⚠️ Important ⚠️: This step needs to be performed by a person that is both: an existing user of your current Athenian account + an Owner of the new GitHub organization to be added.

  2. Go to the Athenian Owl application, select the right organization to be added to your Athenian account, add it as described in the previous section Configure your account.

  3. After the data from the new organization is fetched, in the Athenian dashboards you will see all repositories and data of both GitHub organizations together, as if they are part of a single organization, ensuring that you have a consistent view of your whole development process.

Did this answer your question?