`make sort` won't usually *fail*, even if it sorts stuff (it'll
only fail if it actually can't sort for some reason). So when
either the PR or the existing state of the repo isn't properly
sorted, what we get is the "git status failed!" case. I *think*
this is likely the only time we'll get that, I don't think
"make validate" would actually change files without failing. So
let's gloss that a git status failure probably means a sorting
issue.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is only really useful for debugging the script itself, it's
not useful information for typical execution (especially now I
made it show which test(s) fail more clearly).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This will tell us which checks failed, and how many. It also
suppresses some useless spammy output from `make sort` (we never
need to see any actual output, as it never tells us anything
useful; the useful info is what it changes).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Per https://pagure.io/fedora-ci/general/issue/404 , as things are
right now, having CI files with the same names as those in other
repos can cause clashes. Let's rename all of ours to avoid this.
Also drop a path element in validate-comps.yaml that broke the
tests...
Signed-off-by: Adam Williamson <awilliam@redhat.com>
