I propose that a special-snowflake self-merge policy be adopted for https://github.com/lsst/lsstsw/blob/master/etc/repos.yaml on that basis that:

• this file is CI configuration data in a simple format; there is no logic for a reviewer to evaluate
• modifications being merged into this file are in the critical path for many development activities
• a lint script (DM-3151) is run automatically by travis CI on all pushes & PRs to this repository

Proposed policy:

A developer may merge change(s) to the repos.yaml file in the lsstsw repo without formal code review if a github PR has been opened for the change(s) and travis CI has returned a success status for that PR.

(see attached images of github's CI status flags)