Remove secret_detection_default_branch job from Secret-Detection
secret_detection_default_build from the Secret Detection template. We can move the logic for determining when/how to run the secret detection jobs from
script. This should clear up some of the confusion that comes with having two different secret detection jobs.
This is a breaking change for %14.0
In the Secret Detection vendored template, consolidate
secret_detectioninto one job,
scriptwhich will determine how the
secret_detectionjob is ran (historic, on a branch, commits, etc).
Update Secret Detection documentation
Draft release notes