Connect your code

Connect your code, and Adea checks your recent changes when a number moves: which commit, which pull request, and whether the timing fits.

Connecting code is included from the Start plan. See Credits and plans.

What you get

• Code as a cause. When Adea finds out why a number moved, it checks recent changes alongside prices, campaigns and the calendar, and says how well each one fits.
• What shipped. A list in plain words of what changed in your code, week by week, that anyone on the team can read.
• Better answers about your data. Adea reads the code that writes to your database, and learns what a status or a column really means.

Connect GitHub

1. Open Data and choose to add a source, then GitHub.
2. Install the Adea GitHub App on your account or organization. GitHub asks you to approve it.
3. Choose which repositories Adea may read. Choose only the ones that matter for the data you have connected.
4. Back in Adea, the repositories appear on the map next to your database.

If you can’t install apps on your GitHub, send the person who can the developer link. They install it without an Adea account.

What Adea does with your code

• Adea only reads. It never writes to your repositories, never opens a pull request and never changes a branch.
• It keeps no copy. Adea fetches a repository into memory when it needs it, and lets go of it a short while after.
• Secrets stay out. Files that usually hold secrets, such as .env files, keys, certificates and configuration with passwords, are never read. Anything Adea passes on is cleaned of values that look like keys or passwords first.
• What it remembers is small. Adea keeps short notes about what the code does and the few lines it quoted in an answer, not the files themselves.