···55 2. Please ask questions or configuration/deploy problems on our Discord
66 server (https://discord.gg/gitea) or forum (https://discourse.gitea.io).
77 3. Please take a moment to check that your issue doesn't already exist.
88- 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq)
88+ 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.com/help/faq)
99 5. Please give all relevant information below for bug reports, because
1010 incomplete details will be handled as an invalid report.
1111-->
···2626 - [ ] No
2727- Log gist:
2828<!-- It really is important to provide pertinent logs -->
2929-<!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems -->
2929+<!-- Please read https://docs.gitea.com/administration/logging-config#collecting-logs-for-help -->
3030<!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini -->
31313232## Description
+3-3
.github/ISSUE_TEMPLATE/bug-report.yaml
···1414 server (https://discord.gg/gitea) or forum (https://discourse.gitea.io).
1515 3. Make sure you are using the latest release and
1616 take a moment to check that your issue hasn't been reported before.
1717- 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq)
1717+ 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.com/help/faq)
1818 5. Please give all relevant information below for bug reports, because
1919 incomplete details will be handled as an invalid report.
2020 6. In particular it's really important to provide pertinent logs. You must give us DEBUG level logs.
2121- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems
2121+ Please read https://docs.gitea.com/administration/logging-config#collecting-logs-for-help
2222 In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini
2323- type: textarea
2424 id: description
···5050 attributes:
5151 value: |
5252 It's really important to provide pertinent logs
5353- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems
5353+ Please read https://docs.gitea.com/administration/logging-config#collecting-logs-for-help
5454 In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini
5555- type: input
5656 id: logs
+2-2
.github/ISSUE_TEMPLATE/config.yml
···88 about: Please ask questions and discuss configuration or deployment problems here.
99 - name: Discourse Forum
1010 url: https://discourse.gitea.io
1111- about: Questions and configuration or deployment problems can also be discussed on our forum.
1111+ about: Questions and configuration or deployment problems can also be discussed on our forum.
1212 - name: Frequently Asked Questions
1313- url: https://docs.gitea.io/en-us/faq
1313+ url: https://docs.gitea.com/help/faq
1414 about: Please check if your question isn't mentioned here.
1515 - name: Crowdin Translations
1616 url: https://crowdin.com/project/gitea
+2-2
.github/ISSUE_TEMPLATE/ui.bug-report.yaml
···1313 2. Please ask questions or configuration/deploy problems on our Discord
1414 server (https://discord.gg/gitea) or forum (https://discourse.gitea.io).
1515 3. Please take a moment to check that your issue doesn't already exist.
1616- 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq)
1616+ 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.com/help/faq)
1717 5. Please give all relevant information below for bug reports, because
1818 incomplete details will be handled as an invalid report.
1919 6. In particular it's really important to provide pertinent logs. If you are certain that this is a javascript
2020 error, show us the javascript console. If the error appears to relate to Gitea the server you must also give us
2121- DEBUG level logs. (See https://docs.gitea.io/en-us/logging-configuration/#debugging-problems)
2121+ DEBUG level logs. (See https://docs.gitea.com/administration/logging-config#collecting-logs-for-help)
2222- type: textarea
2323 id: description
2424 attributes:
+1-1
CONTRIBUTING.md
···6060## Introduction
61616262This document explains how to contribute changes to the Gitea project. \
6363-It assumes you have followed the [installation instructions](https://docs.gitea.io/en-us/). \
6363+It assumes you have followed the [installation instructions](https://docs.gitea.com/category/installation). \
6464Sensitive security-related issues should be reported to [security@gitea.io](mailto:security@gitea.io).
65656666For configuring IDEs for Gitea development, see the [contributed IDE configurations](contrib/ide/).
+1-1
README.md
···86868787Parallelism (`make -j <num>`) is not supported.
88888989-More info: https://docs.gitea.io/en-us/install-from-source/
8989+More info: https://docs.gitea.com/installation/install-from-source
90909191## Using
9292
···77 dashboardTimezone: 'default',
88 dashboardRefresh: '1m',
991010- // please see https://docs.gitea.io/en-us/config-cheat-sheet/#metrics-metrics
1010+ // please see https://docs.gitea.com/administration/config-cheat-sheet#metrics-metrics
1111 // Show issue by repository metrics with format gitea_issues_by_repository{repository="org/repo"} 5.
1212 // Requires Gitea 1.16.0 with ENABLED_ISSUE_BY_REPOSITORY set to true.
1313 showIssuesByRepository: true,
+3-3
contrib/legal/privacy.html.sample
···37373838 <h3>With your Consent</h3>
39394040- <p>We share your User Personal Information, if you consent, after letting you know what information will be shared, with whom, and why. For example, if you allow third party applications to access your Account using <a href="https://docs.gitea.io/en-us/oauth2-provider/">OAuth2 providers</a>, we share all information associated with your Account, including private repos and organizations. You may also direct us through your action on Your Gitea Instance to share your User Personal Information, such as when joining an Organization.</p>
4040+ <p>We share your User Personal Information, if you consent, after letting you know what information will be shared, with whom, and why. For example, if you allow third party applications to access your Account using <a href="https://docs.gitea.com/development/oauth2-provider">OAuth2 providers</a>, we share all information associated with your Account, including private repos and organizations. You may also direct us through your action on Your Gitea Instance to share your User Personal Information, such as when joining an Organization.</p>
41414242 <h3>With Service Providers</h3>
4343···144144145145 <h3>Data Portability</h3>
146146147147- <p>As a Your Gitea Instance User, you can always take your data with you. You can clone your repositories to your computer, or you can <a href="https://docs.gitea.io/en-us/migrations-interfaces/">perform migrations using the provided interfaces</a>, for example.</p>
147147+ <p>As a Your Gitea Instance User, you can always take your data with you. You can clone your repositories to your computer, or you can <a href="https://docs.gitea.com/development/migrations-interfaces">perform migrations using the provided interfaces</a>, for example.</p>
148148149149 <h3>Data Retention and Deletion of Data</h3>
150150···183183184184 <h2>Changes to this Privacy Policy</h2>
185185186186- <p>Although most changes are likely to be minor, Your Gitea Instance may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your account.</p>
186186+ <p>Although most changes are likely to be minor, Your Gitea Instance may change our Privacy Statement from time to time. We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the primary email address specified in your account.</p>
187187188188 <h2>Contact</h2>
189189
+1-1
docker/README.md
···4455Docker image can be found on [docker hub](https://hub.docker.com/r/gitea/gitea)
6677-Documentation on using docker image can be found on [Gitea Docs site](https://docs.gitea.io/en-us/install-with-docker/)
77+Documentation on using docker image can be found on [Gitea Docs site](https://docs.gitea.com/installation/install-with-docker-rootless)
···3636Again `gitea help` will allow you review this variable and you can override it using the
3737`--config` option on the `gitea` binary.
38383939-- [Quick Cheat Sheet](https://docs.gitea.io/en-us/config-cheat-sheet/)
3939+- [Quick Cheat Sheet](administration/config-cheat-sheet.md)
4040- [Complete List](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini)
41414242If the `CustomPath` folder can't be found despite checking `gitea help`, check the `GITEA_CUSTOM`
···4444`GITEA_CUSTOM` might, for example, be set by an init script. You can check whether the value
4545is set under the "Configuration" tab on the site administration page.
46464747-- [List of Environment Variables](https://docs.gitea.io/en-us/environment-variables/)
4747+- [List of Environment Variables](administration/environment-variables.md)
48484949**Note:** Gitea must perform a full restart to see configuration changes.
5050···8484must be placed in `$GITEA_CUSTOM/options/gitignore/C++` (see about the location of the `CustomPath`
8585directory at the top of this document).
86868787-Every single page of Gitea can be changed. Dynamic content is generated using [go templates](https://golang.org/pkg/html/template/),
8787+Every single page of Gitea can be changed. Dynamic content is generated using [go templates](https://pkg.go.dev/html/template),
8888which can be modified by placing replacements below the `$GITEA_CUSTOM/templates` directory.
89899090To obtain any embedded file (including templates), the [`gitea embedded` tool](administration/cmd-embedded.md) can be used. Alternatively, they can be found in the [`templates`](https://github.com/go-gitea/gitea/tree/main/templates) directory of Gitea source (Note: the example link is from the `main` branch. Make sure to use templates compatible with the release you are using).
···108108To match the current style, the link should have the class name "item", and you can use `{{AppSubUrl}}` to get the base URL:
109109`<a class="item" href="{{AppSubUrl}}/assets/impressum.html">Impressum</a>`
110110111111-For more information, see [Adding Legal Pages](https://docs.gitea.io/en-us/adding-legal-pages).
111111+For more information, see [Adding Legal Pages](administration/adding-legal-pages.md).
112112113113You can add new tabs in the same way, putting them in `extra_tabs.tmpl`.
114114The exact HTML needed to match the style of other tabs is in the file
···371371## Customizing the look of Gitea
372372373373The default built-in themes are `gitea` (light), `arc-green` (dark), and `auto` (chooses light or dark depending on operating system settings).
374374-The default theme can be changed via `DEFAULT_THEME` in the [ui](https://docs.gitea.io/en-us/config-cheat-sheet/#ui-ui) section of `app.ini`.
374374+The default theme can be changed via `DEFAULT_THEME` in the [ui](administration/config-cheat-sheet.md#ui-ui) section of `app.ini`.
375375376376Gitea also has support for user themes, which means every user can select which theme should be used.
377377-The list of themes a user can choose from can be configured with the `THEMES` value in the [ui](https://docs.gitea.io/en-us/config-cheat-sheet/#ui-ui) section of `app.ini`.
377377+The list of themes a user can choose from can be configured with the `THEMES` value in the [ui](administration/config-cheat-sheet.md#ui-ui) section of `app.ini`.
378378379379To make a custom theme available to all users:
380380
···119119120120The security options in `app.ini` need to be adjusted to allow the interpretation of the headers
121121as well as the list of IP addresses and networks that describe trusted proxy servers
122122-(See the [configuration cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/#security-security) for more information).
122122+(See the [configuration cheat sheet](administration/config-cheat-sheet.md#security-security) for more information).
123123124124```
125125REVERSE_PROXY_LIMIT = 1
···1818# Mail templates
19192020To craft the e-mail subject and contents for certain operations, Gitea can be customized by using templates. The templates
2121-for these functions are located under the [`custom` directory](https://docs.gitea.io/en-us/customizing-gitea/).
2121+for these functions are located under the [`custom` directory](administration/customizing-gitea.md).
2222Gitea has an internal template that serves as default in case there's no custom alternative.
23232424Custom templates are loaded when Gitea starts. Changes made to them are not recognized until Gitea is restarted again.
···165165A default subject is used if the subject template fails, and whatever was rendered successfully
166166from the the _mail body_ is used, disregarding the rest.
167167168168-Please check [Gitea's logs](https://docs.gitea.io/en-us/logging-configuration/) for error messages in case of trouble.
168168+Please check [Gitea's logs](administration/logging-config.md) for error messages in case of trouble.
169169170170## Example
171171
···19192020## Setting up the repository indexer
21212222-Gitea can search through the files of the repositories by enabling this function in your [`app.ini`](https://docs.gitea.io/en-us/config-cheat-sheet/):
2222+Gitea can search through the files of the repositories by enabling this function in your [`app.ini`](administration/config-cheat-sheet.md):
23232424```ini
2525[indexer]
···21212222By default, `ENABLE_SWAGGER` is true, and
2323`MAX_RESPONSE_ITEMS` is set to 50. See [Config Cheat
2424-Sheet](https://docs.gitea.io/en-us/config-cheat-sheet/) for more
2424+Sheet](administration/config-cheat-sheet.md) for more
2525information.
26262727## Authentication
···76767777## OAuth2 Provider
78787979-Access tokens obtained from Gitea's [OAuth2 provider](https://docs.gitea.io/en-us/oauth2-provider) are accepted by these methods:
7979+Access tokens obtained from Gitea's [OAuth2 provider](development/oauth2-provider.md) are accepted by these methods:
80808181- `Authorization bearer ...` header in HTTP headers
8282- `token=...` parameter in URL query string
···148148149149 The `REDIRECT_URI` in the `access_token` request must match the `REDIRECT_URI` in the `authorize` request.
150150151151-3. Use the `access_token` to make [API requests](https://docs.gitea.io/en-us/api-usage#oauth2) to access the user's resources.
151151+3. Use the `access_token` to make [API requests](development/api-usage.md#oauth2-provider) to access the user's resources.
152152153153### Public client (PKCE)
154154···210210211211 The `REDIRECT_URI` in the `access_token` request must match the `REDIRECT_URI` in the `authorize` request.
212212213213-3. Use the `access_token` to make [API requests](https://docs.gitea.io/en-us/api-usage#oauth2) to access the user's resources.
213213+3. Use the `access_token` to make [API requests](development/api-usage.md#oauth2-provider) to access the user's resources.
···254254255255# Customization
256256257257-Customization files described [here](https://docs.gitea.io/en-us/customizing-gitea/) should
257257+Customization files described [here](administration/customizing-gitea.md) should
258258be placed in `/var/lib/gitea/custom` directory. If using host volumes, it's quite easy to access these
259259files; for named volumes, this is done through another container or by direct access at
260260`/var/lib/docker/volumes/gitea_gitea/_/var_lib_gitea`. The configuration file will be saved at
···313313 - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}"""
314314```
315315316316-To set required TOKEN and SECRET values, consider using Gitea's built-in [generate utility functions](https://docs.gitea.io/en-us/command-line/#generate).
316316+To set required TOKEN and SECRET values, consider using Gitea's built-in [generate utility functions](administration/command-line.md#generate).
317317318318# SSH Container Passthrough
319319···342342sudo usermod -s /usr/local/bin/gitea-shell git
343343```
344344345345-Now that all the SSH commands are forwarded to the container, you need to set up the SSH authentication on the host. This is done by leveraging the [SSH AuthorizedKeysCommand](https://docs.gitea.io/en-us/command-line/#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host:
345345+Now that all the SSH commands are forwarded to the container, you need to set up the SSH authentication on the host. This is done by leveraging the [SSH AuthorizedKeysCommand](administration/command-line.md#keys) to match the keys against those accepted by Gitea. Add the following block to `/etc/ssh/sshd_config`, on the host:
346346347347```bash
348348Match User git
···261261262262## Customization
263263264264-Customization files described [here](https://docs.gitea.io/en-us/customizing-gitea/) should
264264+Customization files described [here](administration/customizing-gitea.md) should
265265be placed in `/data/gitea` directory. If using host volumes, it's quite easy to access these
266266files; for named volumes, this is done through another container or by direct access at
267267`/var/lib/docker/volumes/gitea_gitea/_data`. The configuration file will be saved at
···309309 - GITEA__mailer__PASSWD="""${GITEA__mailer__PASSWD:?GITEA__mailer__PASSWD not set}"""
310310```
311311312312-Gitea will generate new secrets/tokens for every new installation automatically and write them into the app.ini. If you want to set the secrets/tokens manually, you can use the following docker commands to use of Gitea's built-in [generate utility functions](https://docs.gitea.io/en-us/command-line/#generate). Do not lose/change your SECRET_KEY after the installation, otherwise the encrypted data can not be decrypted anymore.
312312+Gitea will generate new secrets/tokens for every new installation automatically and write them into the app.ini. If you want to set the secrets/tokens manually, you can use the following docker commands to use of Gitea's built-in [generate utility functions](administration/command-line.md#generate). Do not lose/change your SECRET_KEY after the installation, otherwise the encrypted data can not be decrypted anymore.
313313314314The following commands will output a new `SECRET_KEY` and `INTERNAL_TOKEN` to `stdout`, which you can then place in your environment variables.
315315···553553554554Now all attempts to login as the `git` user on the host will be forwarded to the docker - including the `SSH_ORIGINAL_COMMAND`. We now need to set-up SSH authentication on the host.
555555556556-We will do this by leveraging the [SSH AuthorizedKeysCommand](https://docs.gitea.io/en-us/command-line/#keys) to match the keys against those accepted by Gitea.
556556+We will do this by leveraging the [SSH AuthorizedKeysCommand](administration/command-line.md#keys) to match the keys against those accepted by Gitea.
557557558558Add the following block to `/etc/ssh/sshd_config`, on the host:
559559
+1-1
docs/content/installation/with-docker.fr-fr.md
···103103104104# Personnalisation
105105106106-Les fichier personnalisés ([voir les instructions](https://docs.gitea.io/en-us/customizing-gitea/)) peuvent être placés dans le répertoire `/data/gitea`.
106106+Les fichier personnalisés ([voir les instructions](administration/customizing-gitea.md)) peuvent être placés dans le répertoire `/data/gitea`.
107107108108Le fichier de configuration sera sauvegardé à l'emplacement suivant : `/data/gitea/conf/app.ini`
109109
···112112113113In fact, your Gitea instance can serve as both the actions marketplace and the image registry.
114114You can mirror actions repositories from GitHub to your Gitea instance, and use them as normal.
115115-And [Gitea Container Registry](https://docs.gitea.io/en-us/usage/packages/container/) can be used as a Docker image registry.
115115+And [Gitea Container Registry](usage/packages/container.md) can be used as a Docker image registry.
116116117117### Connection 4, job containers to internet
118118
···6161Be careful, the `https://` or `http://` prefix is necessary!
62626363Alternatively, if you want your runners to download actions from GitHub or your own Gitea instance by default, you can configure it by setting `[actions].DEFAULT_ACTIONS_URL`.
6464-See [Configuration Cheat Sheet](https://docs.gitea.io/en-us/config-cheat-sheet/#actions-actions).
6464+See [Configuration Cheat Sheet](administration/config-cheat-sheet.md#actions-actions).
65656666This is one of the differences from GitHub Actions, but it should allow users much more flexibility in how they run Actions.
6767···69697070Runners have no more permissions than simply connecting to your Gitea instance.
7171When any runner receives a job to run, it will temporarily gain limited permission to the repository associated with the job.
7272-If you want to give more permissions to the runner, allowing it to access more private repositories or external systems, you can pass [secrets](https://docs.gitea.io/en-us/usage/secrets/) to it.
7272+If you want to give more permissions to the runner, allowing it to access more private repositories or external systems, you can pass [secrets](usage/secrets.md) to it.
73737474Refined permission control to Actions is a complicated job.
7575In the future, we will add more options to Gitea to make it more configurable, such as allowing more write access to repositories or read access to all repositories in the same organization.
···197197 field is set to `mail.com`, then Gitea will expect the `user email` field
198198 for an authenticated GIT instance to be `gituser@mail.com`.[^2]
199199200200-**Note**: PAM support is added via [build-time flags](https://docs.gitea.io/en-us/install-from-source/#build),
200200+**Note**: PAM support is added via [build-time flags](installation/install-from-source.md#build),
201201and the official binaries provided do not have this enabled. PAM requires that
202202the necessary libpam dynamic library be available and the necessary PAM
203203development headers be accessible to the compiler.
···181181[startpage]
182182app_desc = A painless, self-hosted Git service
183183install = Easy to install
184184-install_desc = Simply <a target="_blank" rel="noopener noreferrer" href="https://docs.gitea.io/en-us/install-from-binary/">run the binary</a> for your platform, ship it with <a target="_blank" rel="noopener noreferrer" href="https://github.com/go-gitea/gitea/tree/master/docker">Docker</a>, or get it <a target="_blank" rel="noopener noreferrer" href="https://docs.gitea.io/en-us/install-from-package/">packaged</a>.
184184+install_desc = Simply <a target="_blank" rel="noopener noreferrer" href="https://docs.gitea.com/installation/install-from-binary">run the binary</a> for your platform, ship it with <a target="_blank" rel="noopener noreferrer" href="https://github.com/go-gitea/gitea/tree/master/docker">Docker</a>, or get it <a target="_blank" rel="noopener noreferrer" href="https://docs.gitea.com/installation/install-from-package">packaged</a>.
185185platform = Cross-platform
186186platform_desc = Gitea runs anywhere <a target="_blank" rel="noopener noreferrer" href="http://golang.org/">Go</a> can compile for: Windows, macOS, Linux, ARM, etc. Choose the one you love!
187187lightweight = Lightweight
···23282328settings.tags.protection.allowed.noone = No One
23292329settings.tags.protection.create = Protect Tag
23302330settings.tags.protection.none = There are no protected tags.
23312331-settings.tags.protection.pattern.description = You can use a single name or a glob pattern or regular expression to match multiple tags. Read more in the <a target="_blank" rel="noopener" href="https://docs.gitea.io/en-us/protected-tags/">protected tags guide</a>.
23312331+settings.tags.protection.pattern.description = You can use a single name or a glob pattern or regular expression to match multiple tags. Read more in the <a target="_blank" rel="noopener" href="https://docs.gitea.com/usage/protected-tags">protected tags guide</a>.
23322332settings.bot_token = Bot Token
23332333settings.chat_id = Chat ID
23342334settings.thread_id = Thread ID
···28692869packages.published = Published
2870287028712871defaulthooks = Default Webhooks
28722872-defaulthooks.desc = Webhooks automatically make HTTP POST requests to a server when certain Gitea events trigger. Webhooks defined here are defaults and will be copied into all new repositories. Read more in the <a target="_blank" rel="noopener" href="https://docs.gitea.io/en-us/webhooks/">webhooks guide</a>.
28722872+defaulthooks.desc = Webhooks automatically make HTTP POST requests to a server when certain Gitea events trigger. Webhooks defined here are defaults and will be copied into all new repositories. Read more in the <a target="_blank" rel="noopener" href="https://docs.gitea.com/usage/webhooks">webhooks guide</a>.
28732873defaulthooks.add_webhook = Add Default Webhook
28742874defaulthooks.update_webhook = Update Default Webhook
2875287528762876systemhooks = System Webhooks
28772877-systemhooks.desc = Webhooks automatically make HTTP POST requests to a server when certain Gitea events trigger. Webhooks defined here will act on all repositories on the system, so please consider any performance implications this may have. Read more in the <a target="_blank" rel="noopener" href="https://docs.gitea.io/en-us/webhooks/">webhooks guide</a>.
28772877+systemhooks.desc = Webhooks automatically make HTTP POST requests to a server when certain Gitea events trigger. Webhooks defined here will act on all repositories on the system, so please consider any performance implications this may have. Read more in the <a target="_blank" rel="noopener" href="https://docs.gitea.com/usage/webhooks">webhooks guide</a>.
28782878systemhooks.add_webhook = Add System Webhook
28792879systemhooks.update_webhook = Update System Webhook
28802880···29792979auths.tip.openid_connect = Use the OpenID Connect Discovery URL (<server>/.well-known/openid-configuration) to specify the endpoints
29802980auths.tip.twitter = Go to https://dev.twitter.com/apps, create an application and ensure that the “Allow this application to be used to Sign in with Twitter” option is enabled
29812981auths.tip.discord = Register a new application on https://discordapp.com/developers/applications/me
29822982-auths.tip.gitea = Register a new OAuth2 application. Guide can be found at https://docs.gitea.io/en-us/oauth2-provider/
29822982+auths.tip.gitea = Register a new OAuth2 application. Guide can be found at https://docs.gitea.com/development/oauth2-provider
29832983auths.tip.yandex = Create a new application at https://oauth.yandex.com/client/new. Select following permissions from the "Yandex.Passport API" section: "Access to email address", "Access to user avatar" and "Access to username, first name and surname, gender"
29842984auths.tip.mastodon = Input a custom instance URL for the mastodon instance you want to authenticate with (or use the default one)
29852985auths.edit = Edit Authentication Source