Add Danger support

The primary need for this is to forbid changes to the data/team.yml file.

See: #10507 (closed) and !73139 (merged)

Once !73139 (merged) is merged, we want to force all edits to go through the split files.

  1. The first step is to forbid edits to data/team.yml
  2. Then we add a job that builds the data/team.yml every 30min using a bot that commits directly to master.

At this point, normal users must not edit the built file, and their edits will become visible within an hour of merging into master.

example MR failure:

1612390733

NOT TO BE MERGED UNTIL !73139 (merged) IS MERGED

Edited by Alex Kalderimis

Merge request reports

Loading