Integration tests for key-vault certificate systems such as Azure require repository secrets (see #771). These secrets are not available for anybody using a fork. This will cause integration tests to be fail, so they have to be skipped.
This means that test failures will not be visible until after merging into main. This can cause errors to go unnoticed. Automatically creating an issue on test failures will provide visibility for when requests fail.
What should happen?
An issue should be created when tests fail after merging to main.
Checklist
What is the idea?
Add automatic issue creation when tests fail after pushing to
main, similar to what is being done forconda-libmamba-solver: https://github.com/conda/conda-libmamba-solver/blob/efa3b84141e4ff777928aaae952fac417b059091/.github/workflows/tests.yml#L680-L690Why is this needed?
Integration tests for key-vault certificate systems such as Azure require repository secrets (see #771). These secrets are not available for anybody using a fork. This will cause integration tests to be fail, so they have to be skipped.
This means that test failures will not be visible until after merging into
main. This can cause errors to go unnoticed. Automatically creating an issue on test failures will provide visibility for when requests fail.What should happen?
An issue should be created when tests fail after merging to
main.Additional Context
No response