This adds a feature where maintainers can add themselves to an array in the source to receive notifications whenever the target fails.
The way this works is via GitHub, I created a new repository https://github.com/Noratrieb/does-it-build-notifications where an app will create issues that ping the respective users. This is the easiest option for me and also fits nicely into people's workflows on GitHub.
Whenever a target fails, an issue is created for it. This issue is kept open (with a new comment every day that it continues to fail), and then closed when the target builds again.
This should be more reliable (not building with `cfg(miri)` and more
accurately knowing whether a target supports std).
Known targets affected by this change:
- cygwin: should now build since it only breaks in `cfg(miri)`
- i686-pc-nto-qnx700: officially doesn't support std
closes#4
This is necessary for AVR and AMDGPU. We currently just hardcode some
flags in the binary, which is good enough. There's a new column which
keeps track of the used flags and shows them for a build.
A migration makes sure that the older results are properly backfilled
with the flags to make them build.
