Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically create issue on test failure after merging to main #775

Closed
2 tasks done
marcoesters opened this issue Apr 22, 2024 · 0 comments · Fixed by #776
Closed
2 tasks done

Automatically create issue on test failure after merging to main #775

marcoesters opened this issue Apr 22, 2024 · 0 comments · Fixed by #776
Assignees
Labels
locked [bot] locked due to inactivity type::feature request for a new feature or capability

Comments

@marcoesters
Copy link
Contributor

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

Add automatic issue creation when tests fail after pushing to main, similar to what is being done for conda-libmamba-solver: https://github.com/conda/conda-libmamba-solver/blob/efa3b84141e4ff777928aaae952fac417b059091/.github/workflows/tests.yml#L680-L690

Why 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

@marcoesters marcoesters added the type::feature request for a new feature or capability label Apr 22, 2024
@marcoesters marcoesters self-assigned this Apr 22, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Apr 22, 2024
@github-project-automation github-project-automation bot moved this from 🆕 New to 🏁 Done in 🧭 Planning Apr 23, 2024
@github-actions github-actions bot added the locked [bot] locked due to inactivity label Oct 21, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity type::feature request for a new feature or capability
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant