diff options
| author | 6543 <6543@obermui.de> | 2020-11-28 07:12:22 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-11-28 01:12:22 -0500 |
| commit | e7b47c521523099826f42b166f7b562741c07834 (patch) | |
| tree | 11915204151e179a47c33dc300ec727cc93fada4 /docs/content/doc/developers | |
| parent | 742e21aeba5c02935269a2a3681f4486019ce542 (diff) | |
| download | gitea-e7b47c521523099826f42b166f7b562741c07834.tar.gz gitea-e7b47c521523099826f42b166f7b562741c07834.zip | |
Format files (#13698)
* align "make help"
* format
* untouch build/generate-svg.js
* untouch .eslintrc
* combine editorconfig's
* rm editorconfig
Co-authored-by: Lauris BH <lauris@nix.lv>
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
Diffstat (limited to 'docs/content/doc/developers')
| -rw-r--r-- | docs/content/doc/developers/hacking-on-gitea.en-us.md | 2 | ||||
| -rw-r--r-- | docs/content/doc/developers/integrations.en-us.md | 8 | ||||
| -rw-r--r-- | docs/content/doc/developers/oauth2-provider.md | 4 |
3 files changed, 7 insertions, 7 deletions
diff --git a/docs/content/doc/developers/hacking-on-gitea.en-us.md b/docs/content/doc/developers/hacking-on-gitea.en-us.md index b80ce889a1..6eda456ce2 100644 --- a/docs/content/doc/developers/hacking-on-gitea.en-us.md +++ b/docs/content/doc/developers/hacking-on-gitea.en-us.md @@ -82,7 +82,7 @@ from within the `$GOPATH`, hence the `go get` approach is no longer recommended. ## Forking Gitea -Download the master Gitea source code as above. Then, fork the +Download the master Gitea source code as above. Then, fork the [Gitea repository](https://github.com/go-gitea/gitea) on GitHub, and either switch the git remote origin for your fork or add your fork as another remote: diff --git a/docs/content/doc/developers/integrations.en-us.md b/docs/content/doc/developers/integrations.en-us.md index bc8c62637c..3c38d16d41 100644 --- a/docs/content/doc/developers/integrations.en-us.md +++ b/docs/content/doc/developers/integrations.en-us.md @@ -15,12 +15,12 @@ menu: # Integrations -Gitea has a wonderful community of third-party integrations, as well as first-class support in various other +Gitea has a wonderful community of third-party integrations, as well as first-class support in various other projects. We are curating a list over at [awesome-gitea](https://gitea.com/gitea/awesome-gitea) to track these! -If you are looking for [CI/CD](https://gitea.com/gitea/awesome-gitea#devops), -an [SDK](https://gitea.com/gitea/awesome-gitea#sdk), -or even some extra [themes](https://gitea.com/gitea/awesome-gitea#themes), +If you are looking for [CI/CD](https://gitea.com/gitea/awesome-gitea#devops), +an [SDK](https://gitea.com/gitea/awesome-gitea#sdk), +or even some extra [themes](https://gitea.com/gitea/awesome-gitea#themes), you can find them listed in the [awesome-gitea](https://gitea.com/gitea/awesome-gitea) repository! diff --git a/docs/content/doc/developers/oauth2-provider.md b/docs/content/doc/developers/oauth2-provider.md index 87d636d376..81c77e680d 100644 --- a/docs/content/doc/developers/oauth2-provider.md +++ b/docs/content/doc/developers/oauth2-provider.md @@ -30,7 +30,7 @@ Access Token Endpoint | `/login/oauth/access_token` ## Supported OAuth2 Grants At the moment Gitea only supports the [**Authorization Code Grant**](https://tools.ietf.org/html/rfc6749#section-1.3.1) standard with additional support of the [Proof Key for Code Exchange (PKCE)](https://tools.ietf.org/html/rfc7636) extension. - + To use the Authorization Code Grant as a third party application it is required to register a new application via the "Settings" (`/user/settings/applications`) section of the settings. @@ -46,7 +46,7 @@ Currently Gitea does not support scopes (see [#4300](https://github.com/go-gitea ```curl https://[YOUR-GITEA-URL]/login/oauth/authorize?client_id=CLIENT_ID&redirect_uri=REDIRECT_URI& response_type=code&state=STATE -``` +``` The `CLIENT_ID` can be obtained by registering an application in the settings. The `STATE` is a random string that will be send back to your application after the user authorizes. The `state` parameter is optional but should be used to prevent CSRF attacks. |