Ensure inactive branches are periodically reviewed and removed

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.

For each code repository in use, verify that all existing Git branches are active or have yet to be checked for inactivity by performing the next steps: 1. On GitHub.com, navigate to the main page of the repository. 2. Above the list of files, click Branches. 3. Use the navigation at the top of the page to view the Stale branches. The Stale view shows all branches that no one has committed to in the last three months, ordered by the branches with the oldest commits first. 4. If the list is empty, you are compliant.

How it is fixed

Fix method: Guidance or infrastructure patch

For each code repository in use, review existing Git branches and remove those which have not been active for a period of time by performing the following: 1. On GitHub.com, navigate to the main page of the repository. 2. Above the list of files, click Branches. 3. Use the navigation at the top of the page to view the Stale branches. The Stale view shows all branches that no one has committed to in the last three months, ordered by the branches with the oldest commits first. 4. For each branch listed, either delete it by clicking the trash bin icon, or find the valid reason it still exists. You can perform the next steps to prevent pull request branches from becoming stale branches: 1.