-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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 Danger by using a subfolder #2532
Conversation
thanks! This is a lot safer :) |
If I get this green, I'll merge all the commits too 👍 and I totally get it |
Generated by 🚫 dangerJS |
Yep, that works. Everything is green except for Danger's fail. |
ok, let's try this one! Thanks so much @orta. |
OK, I expect this build to pass ( and I fixed the |
* Initial Dangerfile, adds a rule for including flow and the FB header * [Danger] Use a local path for jest-runtime instead of the downloaded NPM package * [Danger] Makes the FB copyright header check correct * just run danger * Update Danger * Use danger from a subfolder
* Initial Dangerfile, adds a rule for including flow and the FB header * [Danger] Use a local path for jest-runtime instead of the downloaded NPM package * [Danger] Makes the FB copyright header check correct * just run danger * Update Danger * Use danger from a subfolder
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Brings back Danger as discussed in #2525, but hopefully scopes the dependencies into the
/danger/
folder. I'm guessing right now that this is how it works, if not, I think it's probably fine to move the Dangerfile into the danger folder, but then file paths will need to be changed inside the Dangerfile.