Expose Danger report results #89
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
f-meloni
changed the title
|
I'm not sure of why is not passing the CI. command that was added on the previous PR. |
|
Weird, the CI says its green but classed as pending, maybe GitHub issues? |
|
Anyway, I'm cool with this |
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.
I thought it would be valuable to allow who is writing the Dangerfile to access the current report results.
An example of usage could be the ruby LGTM plugin that uses it to understand if show or not the LGTM image. https://github.com/leonhartX/danger-lgtm/blob/master/lib/lgtm/plugin.rb#L33