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

Add Danger by using a subfolder #2532

Merged
merged 11 commits into from
Jan 8, 2017
Merged

Add Danger by using a subfolder #2532

merged 11 commits into from
Jan 8, 2017

Conversation

orta
Copy link
Member

@orta orta commented Jan 8, 2017

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.

@cpojer
Copy link
Member

cpojer commented Jan 8, 2017

thanks! This is a lot safer :)

@orta
Copy link
Member Author

orta commented Jan 8, 2017

If I get this green, I'll merge all the commits too 👍

and I totally get it

@jest-bot
Copy link
Contributor

jest-bot commented Jan 8, 2017

Fails
🚫 New JS files do not have the Facebook copyright header: dangerfile.js
Warnings
⚠️ Please ensure that @flow and 'use strict' are enabled on: dangerfile.js
⚠️ Changes were made to package.json, but not to yarn.lock - Perhaps you need to run `yarn install`?

Generated by 🚫 dangerJS

@orta
Copy link
Member Author

orta commented Jan 8, 2017

Yep, that works. Everything is green except for Danger's fail.

@cpojer
Copy link
Member

cpojer commented Jan 8, 2017

ok, let's try this one! Thanks so much @orta.

@orta
Copy link
Member Author

orta commented Jan 8, 2017

OK, I expect this build to pass ( and I fixed the Yarn.lock issue )

@cpojer cpojer merged commit a414e73 into jestjs:master Jan 8, 2017
skovhus pushed a commit to skovhus/jest that referenced this pull request Apr 29, 2017
* 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
tushardhole pushed a commit to tushardhole/jest that referenced this pull request Aug 21, 2017
* 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
@github-actions
Copy link

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants