-
Notifications
You must be signed in to change notification settings - Fork 40
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
Add badge to Readme showing the status of the "next" build #123
Comments
@JonasHelming I think the mailing list would be too noisy if we start sending emails when the build fails, perhaps whoever is interested can turn on their settings for failed builds? The only issue is that it might not be granular to which repo they want notifications for: We could also add a badge in the main-repo's readme (similarly to vscode-builtin-extensions) to display the build status of the generator. |
@vince-fugnitto Do you get notifications on this repo? If so, if it is at least you and me, I believe we are good already. |
@JonasHelming I believe so, and I agree that it's likely enough, we would not want to add noise to the mailing list about failed builds in the generator 👍 |
OK let us wait until the tree editor is fixed then |
Depending on the outcome of the discussion here: eclipse-theia/theia-ide#186 |
If the build on main fails, it is likely that the underlying Theia project has some API breakage. We should notify interested parties, either some committer or a mailing list in this case. @vince-fugnitto @marcdumais-work Any thoughts on this?
see also #122 introducing a build against "next"
The text was updated successfully, but these errors were encountered: