-
Improvement
-
Resolution: Unresolved
-
Major
Currently configuration changes at the GitHub Organization folder level are coupled with Full Scans in order to propagate to the underlying jobs. With hard rate limits to github.com of 5000/hr and it is very expensive to require a scan across the entire org for a config change.
Config changes should take effect against what is currently indexed and roll out against incremental scans for each underlying job or the next scheduled full scan wherever possible.