@@ -123,8 +123,22 @@ your local instance. Here is one approach for running a local server:
123123- Set up the web hook following the instructions in [ Enabling a
124124 Repo] ( #enabling-a-repo ) , substituting your local Highfive IP address
125125 or domain name and port (if necessary).
126+ - Obtain an OAuth token. In the account you are creating the token in,
127+ go to https://github.com/settings/tokens . Grant access to the repo
128+ scope.
129+ - Put the authorization information obtained in the previous step into
130+ a file named config in the top of the repository (i.e., the
131+ directory containing this file). Here's a template of what it should
132+ look like:
133+ ```
134+ [github]
135+ user: OAUTH_TOKEN_USER
136+ token: OAUTH_TOKEN
137+ ```
138+ _ Do not check in this file or commit your OAuth token to a
139+ repository in any other way. It is a secret._
126140
127- Here are couple things to watch out for :
141+ Here are some details to be aware of :
128142
129143- The beginning of ` choose_reviewer ` in
130144 [ highfive/newpr.py] ( /highfive/newpr.py ) contains logic that causes
@@ -134,6 +148,8 @@ Here are couple things to watch out for:
134148- For Highfive to know how to select reviewers for your repository,
135149 you need a configuration file in
136150 [ highfive/configs] ( /highfive/configs ) .
151+ - Highfive ignores comments from the integration user near the top of
152+ ` new_commment ` in [ highfive/newpr.py] ( /highfive/newpr.py ) .
137153
138154[ rustcontrib] : https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md
139155
0 commit comments