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.

Sign up for GitHub

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

Jump to bottom

Check to see if a hotfix is opened to master, but not develop #32

Open
sean-clayton opened this issue Oct 17, 2017 · 2 comments
Open

Check to see if a hotfix is opened to master, but not develop #32

sean-clayton opened this issue Oct 17, 2017 · 2 comments

Comments

@sean-clayton
Copy link
Contributor

"id like to add a new rule which fails if you open a hotfix to master but not develop" - Sam
@sean-clayton sean-clayton self-assigned this Oct 17, 2017
@sean-clayton
Copy link
Contributor Author

sean-clayton commented Oct 17, 2017 •
edited
Loading

It looks like in the danger object we get the name of the current branch it's working on, but we will have to do a request to github to see all PRs and check if the same branch is also has a PR to develop and master

@daedalus28
Copy link
Contributor

pretty sure danger includes the raw github api object right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@daedalus28 @sean-clayton @jrubensteinsp