Issue

When trying to set up the GitHub app, PRs won't push to this repo even though the App Integration test has succeeded.

Resolution

If starting with a completely empty repository, commit and push at least one file to your repository and then try creating a new detection in the Console to trigger the app to publish a PR to the repo.

If you are trying to modify an existing detection in the Console, double-check that the detection exists in the repository. If it is missing, download the detection using the triple dot menu in the upper right-hand corner and add it to the repo manually first.

Cause

This issue occurs when:

1. Setting up the GitHub app with a completely blank repository, or

   1. The app requires at least one file to exist in the repo as an initial seed to have the sync work.

2. Editing an existing detection in the Panther Console that is not present in the linked repository.

   1. Panther's app will try to find the detection in the repository using it's Rule ID. If an exact match is not found, the app will not post a PR to the repo as its associated detection files do not exist.

It is recommended that users moving to a CI/CD workflow download all entities from their Console to seed their new detection repository as a first step.

For new users just starting out, it's a good idea to push a README.md file to the repo to start and then continue using PAT to init, explore, and install Panther-managed content prior to working in the Console.