mirror of
https://gitea.com/gitea/docs.git
synced 2026-09-17 19:55:34 +00:00
Use docusaurus warning/note syntax instead markdown
This commit is contained in:
@@ -345,4 +345,6 @@ If set `ENABLE_REVERSE_PROXY_FULL_NAME=true`, a user full name expected in `X-WE
|
||||
|
||||
You can also limit the reverse proxy's IP address range with `REVERSE_PROXY_TRUSTED_PROXIES` which default value is `127.0.0.0/8,::1/128`. By `REVERSE_PROXY_LIMIT`, you can limit trusted proxies level.
|
||||
|
||||
Notice: Reverse Proxy Auth doesn't support the API. You still need an access token or basic auth to make API requests.
|
||||
:::note
|
||||
Reverse Proxy Auth doesn't support the API. You still need an access token or basic auth to make API requests.
|
||||
:::
|
||||
|
||||
@@ -37,7 +37,9 @@ For an existing remote repository, you can set up pull mirroring as follows:
|
||||
|
||||
The repository now gets mirrored periodically from the remote repository. You can force a sync by selecting **Synchronize Now** in the repository settings.
|
||||
|
||||
:exclamation::exclamation: **NOTE:** You can only set up pull mirroring for repos that don't exist yet on your instance. Once the repo is created, you can't convert it into a pull mirror anymore. :exclamation::exclamation:
|
||||
:::warning
|
||||
:exclamation::exclamation: You can only set up pull mirroring for repos that don't exist yet on your instance. Once the repo is created, you can't convert it into a pull mirror anymore. :exclamation::exclamation:
|
||||
:::
|
||||
|
||||
## Pushing to a remote repository
|
||||
|
||||
@@ -50,7 +52,9 @@ For an existing repository, you can set up push mirroring as follows:
|
||||
|
||||
The repository now gets mirrored periodically to the remote repository. You can force a sync by selecting **Synchronize Now**. In case of an error a message displayed to help you resolve it.
|
||||
|
||||
:exclamation::exclamation: **NOTE:** This will force push to the remote repository. This will overwrite any changes in the remote repository! :exclamation::exclamation:
|
||||
:::warning
|
||||
:exclamation::exclamation: This will force push to the remote repository. This will overwrite any changes in the remote repository! :exclamation::exclamation:
|
||||
:::
|
||||
|
||||
### Setting up a push mirror from Gitea to GitHub
|
||||
|
||||
|
||||
@@ -39,7 +39,9 @@ a/b/c/d.json
|
||||
**.[bB][aA][tT]
|
||||
```
|
||||
|
||||
**NOTE:** The `template` file will be removed from the `.gitea` directory when a repository is generated from the template.
|
||||
:::note
|
||||
The `template` file will be removed from the `.gitea` directory when a repository is generated from the template.
|
||||
:::
|
||||
|
||||
## Variable Expansion
|
||||
|
||||
|
||||
@@ -32,12 +32,14 @@ All event pushes are POST requests. The methods currently supported are:
|
||||
|
||||
### Event information
|
||||
|
||||
**WARNING**: The `secret` field in the payload is deprecated as of Gitea 1.13.0 and will be removed in 1.14.0: https://github.com/go-gitea/gitea/issues/11755
|
||||
:::warning
|
||||
The `secret` field in the payload is deprecated as of Gitea 1.13.0 and will be removed in 1.14.0: https://github.com/go-gitea/gitea/issues/11755
|
||||
:::
|
||||
|
||||
The following is an example of event information that will be sent by Gitea to
|
||||
a Payload URL:
|
||||
|
||||
```
|
||||
```http
|
||||
X-GitHub-Delivery: f6266f16-1bf3-46a5-9ea4-602e06ead473
|
||||
X-GitHub-Event: push
|
||||
X-Gogs-Delivery: f6266f16-1bf3-46a5-9ea4-602e06ead473
|
||||
@@ -131,7 +133,7 @@ In your repository Settings, under Webhooks, Setup a Gitea webhook as follows:
|
||||
|
||||
Now on your server create the php file webhook.php
|
||||
|
||||
```
|
||||
```php
|
||||
<?php
|
||||
|
||||
$secret_key = '123';
|
||||
|
||||
Reference in New Issue
Block a user