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

Create a GitHub issue if compatibility breaks #30

Open
SeanNaren opened this issue Jan 24, 2022 · 3 comments
Open

Create a GitHub issue if compatibility breaks #30

SeanNaren opened this issue Jan 24, 2022 · 3 comments
Labels
CI/CD Continues Integration / delivery enhancement New feature or request RFC Ready for Comments

Comments

@SeanNaren
Copy link
Contributor

SeanNaren commented Jan 24, 2022

🚀 Feature

It would be awesome if we could set the CI up to make an issue on the corresponding CI if something was to break.

Even better would be to have a stack trace showing what broke! Something like below:

Hi! I'm the PyTorchLightning EcoSystem-CI bot.

I've detected an incompatibility with your repository and Lightning's release (1.5.x). I've attached the stack trace below for help in debugging.

Stack Trace (24/01/22)
``` stack_trace ```

Any additional breakages could update the same issue!

@SeanNaren SeanNaren added the enhancement New feature or request label Jan 24, 2022
@Borda
Copy link
Member

Borda commented Jan 24, 2022

we can you can create an issue about it but a challenge would be balancing how many new issues are created if the previous was not resolved... imagine having new issue every 24h just because you have not reacted yet

well there would be a smart way to create a new of none related EcoCI exists and if there is just comment on existing issue

@Borda Borda added the CI/CD Continues Integration / delivery label Jan 24, 2022
@SeanNaren
Copy link
Contributor Author

Yes thank you @Borda :) I think it would be great that it would make one issue, and somehow pile all the failures onto the same issue.

Maybe like as suggested, it is able to add the stack trace in drop downs, with the date corresponding to the failure. At the end of the day, we only care about the latest one (nightly I assume).

@Borda Borda added the RFC Ready for Comments label Feb 13, 2022
@Borda
Copy link
Member

Borda commented Feb 14, 2022

let's explore this API: https://github.com/fastai/ghapi 🐰 thx @aribornstein

@stale stale bot added the wontfix This will not be worked on label Apr 16, 2022
@Lightning-AI Lightning-AI deleted a comment from stale bot Apr 16, 2022
@stale stale bot removed the wontfix This will not be worked on label Apr 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/CD Continues Integration / delivery enhancement New feature or request RFC Ready for Comments
Projects
None yet
Development

No branches or pull requests

2 participants