Skip to content

Commit 5e597ff

Browse files
gjtorikiangjtorikian
committed
Merge pull request github#730 from github/add-2.1-docs
Add 2.1 menu item
2 parents c29c8b6 + daa2208 commit 5e597ff

File tree

3,784 files changed

+254
-724972
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

3,784 files changed

+254
-724972
lines changed

‎enterprise/2.1/css/documentation.css

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,10 @@ h1 {
2121
font-weight: normal;
2222
}
2323

24+
body:not(.enterprise) .enterprise-only {
25+
display: none;
26+
}
27+
2428
.content h1 {
2529
font-weight: 300;
2630
-webkit-backface-visibility: hidden;

‎enterprise/2.1/guides/building-a-ci-server/index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,7 @@ <h2 id="writing-your-server">Writing your server</h2>
143143
HTTP header. We’ll only care about the PR events for now. From there, we’ll
144144
take the payload of information, and return the title field. In an ideal scenario,
145145
our server would be concerned with every time a pull request is updated, not just
146-
when it’s updated. That would make sure that every new push passes the CI tests.
146+
when it’s opened. That would make sure that every new push passes the CI tests.
147147
But for this demo, we’ll just worry about when it’s opened.</p>
148148

149149
<p>To test out this proof-of-concept, make some changes in a branch in your test

‎enterprise/2.1/guides/getting-started/index.html

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -259,7 +259,7 @@ <h3 id="oauth">OAuth</h3>
259259
to create an OAuth token. Try pasting and running the following command:</p>
260260

261261
<pre class="terminal">
262-
$ curl -i -u &lt;your_username&gt; -d '{"scopes": ["repo"], "note": "getting-started"}' \
262+
$ curl -i -u &lt;your_username&gt; -d '{"scopes": ["repo", "user"], "note": "getting-started"}' \
263263
https://api.github.com/authorizations
264264

265265
HTTP/1.1 201 Created
@@ -268,7 +268,8 @@ <h3 id="oauth">OAuth</h3>
268268

269269
{
270270
"scopes": [
271-
"repo"
271+
"repo",
272+
"user"
272273
],
273274
"token": "5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4",
274275
"updated_at": "2012-11-14T14:04:24Z",
@@ -293,7 +294,9 @@ <h3 id="oauth">OAuth</h3>
293294
a new token, we include an optional array of <a href="/enterprise/2.1/v3/oauth/#scopes"><em>scopes</em></a>, or access
294295
levels, that indicate what information this token can access. In this case,
295296
we’re setting up the token with <em>repo</em> access, which grants access to read and
296-
write to private repositories. See <a href="/enterprise/2.1/v3/oauth/#scopes">the scopes docs</a> for a full list of
297+
write to public and private repositories, and <em>user</em> scope, which grants read
298+
and write access to public and private user profile data. See
299+
<a href="/enterprise/2.1/v3/oauth/#scopes">the scopes docs</a> for a full list of
297300
scopes. You should <strong>only</strong> request scopes that your application actually needs,
298301
in order to not frighten users with potentially invasive actions. The <code>201</code>
299302
status code tells us that the call was successful, and the JSON returned
@@ -306,7 +309,7 @@ <h3 id="oauth">OAuth</h3>
306309

307310
<pre class="terminal">
308311
$ curl -i -u &lt;your_username&gt; -H "X-GitHub-OTP: &lt;your_2fa_OTP_code&gt;" \
309-
-d '{"scopes": ["repo"], "note": "getting-started"}' \
312+
-d '{"scopes": ["repo", "user"], "note": "getting-started"}' \
310313
https://api.github.com/authorizations
311314
</pre>
312315

‎enterprise/2.1/output/CNAME

Lines changed: 0 additions & 1 deletion
This file was deleted.

‎enterprise/2.1/output/changes.atom

Lines changed: 0 additions & 1284 deletions
This file was deleted.

‎enterprise/2.1/output/changes/2012-10-14-rate-limit-changes/index.html

Lines changed: 0 additions & 167 deletions
This file was deleted.

‎enterprise/2.1/output/changes/2012-10-17-org-members-redirection/index.html

Lines changed: 0 additions & 169 deletions
This file was deleted.

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy