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

Don't post PR comment on errors when triggering Lite-CI #241

Merged
merged 1 commit into from
Jun 17, 2019

Conversation

phillipj
Copy link
Member

@phillipj phillipj commented Jun 15, 2019

As the bot does not have permission to trigger Jenkins Lite-CI builds for some reason at the moment, and there's feedback about these error comments not being useful to collaborators anyways, those comments are muted for now.

Ideally github-bot maintainers should get notified about these errors, as they're obviously not meant to be raised at all. But using node core collaborators as proxy, manually telling bot maintainers about errors surely isn't ideal either.

Refs #238
Refs #235 (comment)

/cc @nodejs/github-bot @cjihrig @sam-github

As the bot is does not have permission to trigger Jenkins Lite-CI builds
for some reason at the moment, and there's feedback about these error
comments not being useful to collaborators anyways, those comments are
muted for now.

Ideally github-bot maintainers should get notified about these errors,
as they're obviously not meant to be raised at all. But using
node core collaborators as proxy, manually telling bot maintainers about
errors surely isn't idealy either.

Refs nodejs#238
Refs nodejs#235 (comment)
@phillipj
Copy link
Member Author

Taking the liberty of rolling this out as no objections has been made and quite a few has asked for this to happen, in fact no one has said this is actually useful.

@phillipj phillipj merged commit c749007 into nodejs:master Jun 17, 2019
@phillipj phillipj deleted the mute-ci-trigger-errors branch June 17, 2019 09:34
@sam-github
Copy link

Belated LGTM, thanks @phillipj

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants