How to configure your repository to be ignored

Question

What if my repository is new and does not contain code, or the code is no longer in use anywhere?

This is Step #1 for configuring CodeQL scans for both GitHub CI and Jenkins CI. This step is performed before the updating the emass.json file step.

Answer

Some repositories should be ignored altogether. This may be because your repository is new and you have not yet delivered code to production, or because your repository is no longer used anywhere. In this instance you may add a .emass-repo-ignore file (no contents in the file) to the .github directory in your repository. Once you’ve added this file to your repository, you may simply close the CodeQL enablement pull request with no additional work necessary.

If in the future your repository should no longer be ignored, you may simply delete the .emass-repo-ignore file from your repository and re-open the CodeQL enablement pull request.

---

Return to enable CodeQL using GitHub CI or using Jenkins CI to continue with the next step.