chore(stryker): Switch to dashboard owned by org #292
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I will land this now and in case it fails I will file a second PR. |
|
It works like a charm 🎉 |
brodybits
reviewed
Aug 24, 2021
| @@ -4,7 +4,7 @@ | |||
| [](https://www.npmjs.com/package/@xmldom/xmldom) | |||
| [](https://github.com/xmldom/xmldom/issues?q=is%3Aissue+is%3Aopen+label%3Abug) | |||
| [](https://github.com/xmldom/xmldom/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) | |||
| [](https://dashboard.stryker-mutator.io/reports/github.com/brodybits/xmldom/master) | |||
| [](https://dashboard.stryker-mutator.io/reports/github.com/xmldom/xmldom/master) | |||
There was a problem hiding this comment.
minor nit: I would have kept the the alt text as "Mutation report" here, will raise a PR to fix this.
Merged
This was referenced Dec 25, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #80
I already updated the API key in the github secrets management with the one I received, so landing this PR should trigger the first report to the proper location.