mirror of
https://codeberg.org/Codeberg/Documentation.git
synced 2026-06-16 05:13:54 -07:00
Update links (#484)
Update Gitea link to Forgejo link. Add GNU link to ignore. Remove recommendation for Atom (no longer maintained) instead recommend VSCodium. Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/484 Co-authored-by: Gusted <postmaster@gusted.xyz> Co-committed-by: Gusted <postmaster@gusted.xyz>
This commit is contained in:
parent
3bd7c665c7
commit
b66ba78d58
4 changed files with 4 additions and 3 deletions
|
|
@ -6,3 +6,4 @@ file://** */
|
|||
https://codeberg.org/username/repo.git
|
||||
https://username.codeberg.page/**
|
||||
https://openclipart.org/**
|
||||
https://www.gnu.org/**
|
||||
|
|
|
|||
|
|
@ -207,7 +207,7 @@ You can start creating your own content by making a new reStructuredText file (.
|
|||
|
||||
You have just created an empty ".rst" file with the **`touch`** command. An ".rst" file is simply a plain text file that is written with reStructuredText as a markup language. To learn about how to use reStructuredText, follow the instructions provided in the article [reStructuredText Primer](https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html).
|
||||
|
||||
You will be more productive in your writing if you use a text editor that supports syntax highlighting such as [Emacs](https://www.gnu.org/software/emacs/download.html) or [Atom](https://atom.io/). Linux offers plenty of powerful text editors that support syntax highlighting and other advanced features for coding and authoring tasks.
|
||||
You will be more productive in your writing if you use a text editor that supports syntax highlighting such as [Emacs](https://www.gnu.org/software/emacs/download.html) or [VSCodium](https://vscodium.com/). Linux offers plenty of powerful text editors that support syntax highlighting and other advanced features for coding and authoring tasks.
|
||||
|
||||
{% admonition "info" %}
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ This article will guide you through creating your first repository on Codeberg,
|
|||
|
||||
{% admonition "warning" %}
|
||||
|
||||
Note for advanced users: The [Push To Create](https://docs.gitea.com/next/usage/push-to-create) feature is disabled on Codeberg.
|
||||
Note for advanced users: The [Push To Create](https://forgejo.org/docs/latest/user/push-to-create/) feature is disabled on Codeberg.
|
||||
|
||||
{% endadmonition %}
|
||||
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@ Let's finish configuring the OpenID Connect provider on Keycloak.
|
|||
|
||||
All other options can be left untouched. The [_discovery endpoint_](https://codeberg.org/.well-known/openid-configuration) will be used to fetch all metadata required for your Keycloak instance to work together with Codeberg.
|
||||
|
||||
You can also optionally enable the [_Proof Key for Code Exchange (PKCE)_](https://docs.gitea.com/next/development/oauth2-provider#supported-oauth2-grants) extension in the _Show metadata_ dropdown menu.
|
||||
You can also optionally enable the [_Proof Key for Code Exchange (PKCE)_](https://forgejo.org/docs/latest/user/oauth2-provider/#supported-oauth2-grants) extension in the _Show metadata_ dropdown menu.
|
||||
|
||||
In summary, this is what your configuration should look like:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue