Skip to main content

How to configure the date for Version Control testing

Written by Brady Price

Since Pull Requests (PRs) should not be altered after they have been merged to production, it's likely your organization will have historical PRs that did not follow compliance requirements. When testing PRs for compliance purposes, it's best to choose a sample selection date that falls after the implementation date so you do not return outdated results.

To change the date from which our integration pulls its results, follow these steps:

  1. On the Monitoring dashboard, click Integrations in the left navbar.

  2. On the Integrations page, scroll down to find the row for the connected integration you'd like to configure.

  3. Click Settings.

  4. Click the Testing start date field to adjust the date.

Can I set a different Testing start date for one GitHub repository?

  • No. The Testing start date applies to all repositories in that version-control integration (for example GitHub), not to a single repository.

  • If one repository should only be evaluated from a later date (for example after a migration), mark PRs merged before that cutoff as ignored evidence on each affected test, such as Code pull request approvals (GitHub) and Code static application security testing (GitHub).

  • Add a short justification when ignoring them, such as the migration timeline.

  • That leaves the start date unchanged for your other repositories. PRs merged on or after the cutoff are still evaluated.

Did this answer your question?