Skip to main content
When Ana learns something new — a better way to calculate a metric, a data quality caveat, a new table — she can write that knowledge back to the repository. Instead of writing directly to the main branch, Ana:
  1. Creates a new branch
  2. Writes or updates the relevant files
  3. Opens a pull request with a description of the changes
A human reviewer (typically a data admin or data champion) reviews the diff, approves or requests changes, and merges when satisfied. Once merged, the new context is immediately available to all users in the next conversation.
Always review pull requests manually. Context that is wrong is often worse than no context at all — Ana will confidently apply the wrong rule. Never auto-merge PRs from Ana without human review.

​
Why the PR workflow matters

The PR workflow puts a human checkpoint between Ana’s proposed changes and the live context that all users see. It also creates a natural audit trail — if Ana starts giving unexpected answers, you can look at the context history to see what changed and when.

​
Practical setup

  • Give Ana a personal access token with read access to the repository and write access to branches
  • Configure Ana not to merge her own PRs — require a human approval
  • Designate one or two people as context reviewers who get notified when Ana opens a PR
  • Start with a small repository and let it grow organically as Ana encounters questions that require new context

​
Triggering context saves

Once configured, you can tell Ana to save context explicitly:
  • “Ana, remember this metric definition for future sessions”
  • “Save this analysis approach to the context repo”
  • “Keep in mind that we always exclude internal accounts from revenue calculations”
Ana will create a branch, write the relevant files, and open a PR for your review.

GitHub Integration Setup

Set up the GitHub connection, access token, and system prompt

Dynamic Context Loading

How Ana navigates your repository to fetch relevant files per question