-
Notifications
You must be signed in to change notification settings - Fork 31
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 support for Danger #85
Comments
@kgellci IS this something you need to do? Or could I do this? |
Go for it!
…On Tue, Mar 5, 2019 at 10:30 AM Robert J. Clegg ***@***.***> wrote:
@kgellci <https://github.com/kgellci> IS this something you need to do?
Or could I do this?
I'd love to give this a go as I haven't used Danger before.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#85 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACbk2b_p6vB8WphorZtVWW8KGuLKpDuOks5vTrfEgaJpZM4bZTKq>
.
|
After looking into this (And setting it up on another project) I am in agreement with @squarefrog - This needs to be setup by the project owner. @kgellci Do you want to take over this task? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As noted in #83 (comment) it may be useful for someone to setup Danger.
This would automate the initial QA of a Pull Request. It's easy to forget things sometimes, so this could automatically check the following:
This would probably need the project owner to setup, as it relies on a GitHub bot to run automatically. See Getting Started.
The text was updated successfully, but these errors were encountered: