Let’s say, you are working on a new feature, and you’re working on a feature branch. On each commit, you run a workflow ‘Test’, building and running your UTs; everything is green. You have finished developing the feature, you create a pull request, triggering a build for your QA Team to validate. In the meanwhile, you have a workflow triggered to run you Non Regressions Auto Tests, and this will fail => You will receive an email saying that you project has failed on the given branch, but QA will want to know quickly that feature needs to go back to dev, and the email needs to contain the workflow for the QA to be able to identify this.
Other case : you want to do a Beta Build every night, but one night it fails; it’s critical, and your team will want to know what happened.
Do you think these are good reasons ?