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

Documented Dangerfile gems. #107

Merged
merged 1 commit into from
Sep 3, 2016
Merged

Documented Dangerfile gems. #107

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 6 additions & 7 deletions static/source/guides/faq.html.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,14 +22,13 @@ Then Danger would not show that message, and would not fail the build if it were

#### I want to run Danger across multiple repos

To have consistent rules across the repos in your organisation, you can use a shared `danger.import_dangerfile "[repo]"`:
For any significant number of repos we recommend you package your Dangerfile in a gem, release it and use it via `danger.import_dangerfile(gem: "name")`. This allows you to specify versioned plugin dependencies and share rules.

1. create a repo on your GitHub organization called `danger` (or `Danger`)
1. Add a `Dangerfile` to the root of that repo
1. The new `Dangerfile` is ran after the current repo's `Dangerfile`
See [ruby-grape/danger](https://github.com/ruby-grape/danger) for an example.

Then, assuming Danger can reach the other repo, she will download the Dangerfile from that
repo and parse it in-place. This gives access to the same local and other environment variables.
Alternatively you can also use a shared Dangerfile and import it via `danger.import_dangerfile(github: "org/repo")`. Assuming Danger can reach the other repo, she will download the Dangerfile from that repo and parse it in-place.

This gives access to the same local and other environment variables.

#### Multiple Dangers

Expand Down Expand Up @@ -60,4 +59,4 @@ Understandably, applying a gender to a genderless concept comes with it's own co

#### Danger is not posting to GitHub PRs, but everything looks fine?

Try logging in to your account that is writing the messages, it's possible that your account has triggered the bot detection algorithm on GitHub. This means that messages are sent correctly, but do not show up for anyone except the sender. This makes it more or less impossible to detect.
Try logging in to your account that is writing the messages, it's possible that your account has triggered the bot detection algorithm on GitHub. This means that messages are sent correctly, but do not show up for anyone except the sender. This makes it more or less impossible to detect.