Skip to content
Browse files

Merge pull request #121 from narfdotpl/trailing-whitespace

Killing trailing whitespace with ๐Ÿ”ฅ
  • Loading branch information...
2 parents adf3449 + c982911 commit 3efbd4c1dcfd7e832dbde7427fa0e25c6ae44b65 @pengwynn pengwynn committed Jun 27, 2012
View
2 content/v3/events/types.md
@@ -237,7 +237,7 @@ commits[][author][name]
commits[][author][email]
: **string** - The git author's email address.
-
+
commits[][url]
: **url** - Points to the commit API resource.
View
2 content/v3/git.md
@@ -19,7 +19,7 @@ Support](https://github.com/contact) if this response status persists.
![git db](http://git-scm.com/figures/18333fig0904-tn.png)
-For more information on the Git object database, please read the
+For more information on the Git object database, please read the
<a href="http://git-scm.com/book/ch9-0.html">Git Internals</a> chapter of
the Pro Git book.
View
2 content/v3/git/tags.md
@@ -22,7 +22,7 @@ Note that creating a tag object does not create the reference that
makes a tag in Git. If you want to create an annotated tag in Git,
you have to do this call to create the tag object, and then create
the `refs/tags/[tag]` reference. If you want to create a lightweight
-tag, you simply have to create the reference - this call would be
+tag, you simply have to create the reference - this call would be
unnecessary.
POST /repos/:user/:repo/git/tags
View
2 content/v3/pulls.md
@@ -159,7 +159,7 @@ state
## Merge a pull request (Merge Button&trade;)
PUT /repos/:user/:repo/pulls/:number/merge
-
+
### Input
commit\_message
View
2 content/v3/pulls/comments.md
@@ -7,7 +7,7 @@ title: Pull Request Comments | GitHub API
Pull Request Review Comments are comments on a portion of the unified
diff. These are separate from Commit Comments (which are applied
directly to a commit, outside of the Pull Request view), and Issue
-Comments (which do not reference a portion of the unified diff).
+Comments (which do not reference a portion of the unified diff).
Pull Request Review Comments leverage [these](#custom-mime-types) custom mime
types. You can read more about the use of mime types in the API
View
2 content/v3/repos/forks.md
@@ -33,7 +33,7 @@ forked into this organization.
### Response
Forking a Repository happens asynchronously. Therefore, you may have to wait
-a short period before accessing the git objects. If this takes longer than
+a short period before accessing the git objects. If this takes longer than
5 minutes, be sure to [contact Support](https://github.com/contact).
<%= headers 202 %>
View
10 content/v3/repos/hooks.md
@@ -25,7 +25,7 @@ request is tracking).
* `fork_apply` - Any time a patch is applied to the Repository from the
Fork Queue.
* `member` - Any time a User is added as a collaborator to a
- non-Organization Repository.
+ non-Organization Repository.
* `public` - Any time a Repository changes from private to public.
The payloads for all of the hooks mirror [the payloads for the Event
@@ -34,7 +34,7 @@ event](http://help.github.com/post-receive-hooks/).
For a Hook to go through, the Hook needs to be configured to trigger for
an event, and the Service has to listen to it. The Services are all
-part of the open source [github-services](https://github.com/github/github-services) project. Most of the Services only listen for `push` events. However, the generic [Web Service](https://github.com/github/github-services/blob/master/services/web.rb) listens for all events. Other services like the [IRC Service](https://github.com/github/github-services/blob/master/services/irc.rb) may only listen for `push`, `issues`, and `pull_request` events.
+part of the open source [github-services](https://github.com/github/github-services) project. Most of the Services only listen for `push` events. However, the generic [Web Service](https://github.com/github/github-services/blob/master/services/web.rb) listens for all events. Other services like the [IRC Service](https://github.com/github/github-services/blob/master/services/irc.rb) may only listen for `push`, `issues`, and `pull_request` events.
## List
@@ -119,11 +119,11 @@ for. This replaces the entire array of events. Default: `["push"]`.
`add_events`
: _Optional_ **array** - Determines a list of events to be added to the
-list of events that the Hook triggers for.
+list of events that the Hook triggers for.
`remove_events`
: _Optional_ **array** - Determines a list of events to be removed from the
-list of events that the Hook triggers for.
+list of events that the Hook triggers for.
`active`
: _Optional_ **boolean** - Determines whether the hook is actually
@@ -166,7 +166,7 @@ repository.
GitHub can also serve as a [PubSubHubbub][pubsub] hub for all repositories. PSHB is a simple publish/subscribe protocol that lets servers register to receive updates when a topic is updated. The updates are sent with an HTTP POST request to a callback URL. Topic URLs for a GitHub repository's pushes are in this format:
- https://github.com/:user/:repo/events/:event
+ https://github.com/:user/:repo/events/:event
The event can be any Event string that is listed at the top of this
document.
View
BIN static/favicon.ico
Binary file not shown.
View
42 static/shared/images/blacktocat.svg
@@ -95,27 +95,27 @@
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
<?xpacket end="w"?>
</metadata>
<path fill="#E6E6E7" d="M64.876,0.353c-35.654,0-64.527,28.935-64.527,64.644c0,35.724,28.873,64.649,64.527,64.649
View
42 static/shared/images/footer-logo.svg
@@ -91,27 +91,27 @@
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
<?xpacket end="w"?>
</metadata>
<g>
View
2 static/shared/js/documentation.js
@@ -46,7 +46,7 @@ $(function() {
$('#js-sidebar .js-accordion-list .js-topic h3 a').click(function(){
var clickedTopic = $(this).parents('.js-topic'),
topicGuides = clickedTopic.find('.js-guides li')
-
+
if(activeItem != clickedTopic.index()){
if(helpList.eq(activeItem)){
helpList.eq(activeItem).find('.js-guides li').toggle(100)

0 comments on commit 3efbd4c

Please sign in to comment.
Something went wrong with that request. Please try again.