# Merge app said a repo did not exist

Problem 49. Published Nov 8. Last checked Nov 8. Tags: github, automation, access.
Page: https://bluhook.com/log/merge-app-repo-not-found
Exact text to search: GitHub App "Could not resolve to a Repository" repo exists app installed

## What happened

Our merge tool said 8 of our repos did not exist. It gave the error "Could not resolve to a Repository" on Nov 6, when a code change could not be merged. Those 8 repos hold our shared skills, so none of them could merge anything.

We first assumed the GitHub App was not installed on those 8 repos. It was installed on all of them.

## What we did

1. We found the cause: our own list of repos that the token our merge tool makes may touch. It named 19 repos and left out those 8. The app only gives access to repos on that list, so the 8 looked like they did not exist.
2. We added the 8 repos to the list. Nothing in the app changed.

## How we know it worked

The person who merges read the code change from their own session, then merged it. Reads of the other 7 repos came back too, each with 0 open changes.

## What you can take from it

This error on a valid repo name can mean the token's own list is missing that repo. Check the app's install list and the token's list separately before you change either one. Test the fix as the user who was blocked, from their session. When you add a repo, update the token list the same hour.