Changes between Version 8 and Version 9 of code-review

Timestamp:

Nov 30, 2015, 11:44:15 PM (9 years ago)

Author:

jgross@mit.edu

Comment:

capitalize GitHub

code-review

@@ -34 +34 @@
    general, happen at least largely over email (to
    barnowl-dev@mit.edu).  Pull requests made on
-   github (http://github.com/barnowl/barnowl/pulls) automatically
+   GitHub (http://github.com/barnowl/barnowl/pulls) automatically
    send email to barnowl-dev@mit.edu, as do comments on the pull
    request itself.  (Comments on individual commits, or on specific
@@ -40 +40 @@
    furthermore, are lost if the developer updates the pull request.
    Therefore, please make all comments on the pull request itself.)
-   Note that github emails show up, at least some of the time,
+   Note that GitHub emails show up, at least some of the time,
    as being from notifications@github.com and to
    barnowl@noreply.github.com.
 </p></li>
 <li><p>
- Review requests made by any medium other than github pull requests should include at least one of:</p>
+ Review requests made by any medium other than GitHub pull requests should include at least one of:</p>
  <ul>
    <li>The location of a git repository containing the changes.</li>
@@ -56 +56 @@
    way within seven days from time of sending, the developer may, at
    their option, merge it to master without review.  As pull requests
-   on github now send email to the mailing list, this timeout policy
-   also applies to github pull requests made after May 20, 2013.  There is no such
+   on GitHub now send email to the mailing list, this timeout policy
+   also applies to GitHub pull requests made after May 20, 2013.  There is no such
    timeout for review requests communicated in any other way.
 </p></li>