move images to content dir and use relative paths
This is necessary for the website upgrade to Astro v3, which has a new built-in image API.
Before Width: | Height: | Size: 121 KiB After Width: | Height: | Size: 121 KiB |
Before Width: | Height: | Size: 43 KiB After Width: | Height: | Size: 43 KiB |
Before Width: | Height: | Size: 72 KiB After Width: | Height: | Size: 72 KiB |
Before Width: | Height: | Size: 35 KiB After Width: | Height: | Size: 35 KiB |
Before Width: | Height: | Size: 154 KiB After Width: | Height: | Size: 154 KiB |
Before Width: | Height: | Size: 101 KiB After Width: | Height: | Size: 101 KiB |
Before Width: | Height: | Size: 50 KiB After Width: | Height: | Size: 50 KiB |
Before Width: | Height: | Size: 31 KiB After Width: | Height: | Size: 31 KiB |
Before Width: | Height: | Size: 3.5 KiB After Width: | Height: | Size: 3.5 KiB |
Before Width: | Height: | Size: 2.6 KiB After Width: | Height: | Size: 2.6 KiB |
Before Width: | Height: | Size: 201 KiB After Width: | Height: | Size: 201 KiB |
Before Width: | Height: | Size: 24 KiB After Width: | Height: | Size: 24 KiB |
Before Width: | Height: | Size: 35 KiB After Width: | Height: | Size: 35 KiB |
Before Width: | Height: | Size: 21 KiB After Width: | Height: | Size: 21 KiB |
Before Width: | Height: | Size: 219 KiB After Width: | Height: | Size: 219 KiB |
Before Width: | Height: | Size: 47 KiB After Width: | Height: | Size: 47 KiB |
Before Width: | Height: | Size: 50 KiB After Width: | Height: | Size: 50 KiB |
Before Width: | Height: | Size: 53 KiB After Width: | Height: | Size: 53 KiB |
Before Width: | Height: | Size: 31 KiB After Width: | Height: | Size: 31 KiB |
|
@ -14,11 +14,11 @@ To create a new repository, you need be logged in to your account.
|
|||
|
||||
When you're logged in, you can use one of the two buttons shown in the two following screenshots to create a new repository:
|
||||
|
||||

|
||||

|
||||
|
||||
This will lead you to this page below.
|
||||
|
||||

|
||||

|
||||
|
||||
Here's an explanation of the form's fields:
|
||||
|
||||
|
@ -39,7 +39,7 @@ After filling out the fields, click the green "Create Repository" button on the
|
|||
|
||||
You should now see a screen similar to the one below. If you haven't chosen to generate `LICENSE`, `README` and `.gitignore` the screen might show instructions instead, which will vanish after [your first commit](#making-your-first-commit/).
|
||||
|
||||

|
||||

|
||||
|
||||
Here's what the most important buttons do:
|
||||
|
||||
|
@ -88,7 +88,7 @@ knut@iceberg:~/repositories$
|
|||
|
||||
To clone your newly created repository, execute `git clone` with the URL that is shown in your repository:
|
||||
|
||||

|
||||

|
||||
|
||||
```bash
|
||||
knut@iceberg:~/repositories$ git clone https://codeberg.org/knut/foobar
|
||||
|
@ -253,6 +253,6 @@ When connecting via HTTPS, Git will ask you for your username and password, whic
|
|||
|
||||
After refreshing the repository page, you should now see something similar to this:
|
||||
|
||||

|
||||

|
||||
|
||||
Congratulations - you've just made your first source code contribution on Forgejo!
|
||||
|
|
|
@ -11,7 +11,7 @@ direction, ask questions and much more.
|
|||
|
||||
### The Issue Tracker
|
||||
|
||||

|
||||

|
||||
|
||||
You can access the issue tracker of a project by clicking its "Issues" tab **(1)**.
|
||||
|
||||
|
|
|
@ -10,7 +10,7 @@ You can use labels to classify issues and pull requests and to improve your over
|
|||
|
||||
For repositories, labels can be created by going to `Issues` and clicking on `Labels`.
|
||||
|
||||

|
||||

|
||||
|
||||
For organizations, you can define organization-wide labels that are shared with all organization repositories, including both already-existing repositories as well as newly created ones. Organization-wide labels can be created in the organization `Settings`.
|
||||
|
||||
|
@ -18,7 +18,7 @@ Labels have a mandatory name, a mandatory color, an optional description, and mu
|
|||
|
||||
When you create a repository, you can ensure certain labels exist by using the `Issue Labels` option. This option lists a number of available label sets that are configured globally on your instance. Its contained labels will all be created as well while creating the repository.
|
||||
|
||||

|
||||

|
||||
|
||||
When you create a repository, you can ensure certain labels exist by using the `Issue Labels` option. This option lists a number of available label sets that are configured globally on your instance. Its contained labels will all be created as well while creating the repository.
|
||||
|
||||
|
@ -26,7 +26,7 @@ When you create a repository, you can ensure certain labels exist by using the `
|
|||
|
||||
Scoped labels are used to ensure at most a single label with the same scope is assigned to an issue or pull request. For example, if labels `kind/bug` and `kind/enhancement` have the Exclusive option set, an issue can only be classified as a bug or an enhancement.
|
||||
|
||||

|
||||

|
||||
|
||||
A scoped label must contain `/` in its name (not at either end of the name). The scope of a label is determined based on the **last** `/`, so for example the scope of label `scope/subscope/item` is `scope/subscope`.
|
||||
|
||||
|
|
|
@ -5,10 +5,10 @@ license: 'CC-BY-SA-4.0'
|
|||
|
||||
A project is a [kanban board](<https://en.wikipedia.org/wiki/Kanban_(development)>) to organize issues.
|
||||
|
||||

|
||||

|
||||
|
||||
## Card previews images
|
||||
|
||||
If the card preview in the project is set to **Images and Text**, the card preview displays images found in the corresponding issue. The most recent is displayed first, up to five images.
|
||||
|
||||

|
||||

|
||||
|
|
|
@ -13,7 +13,7 @@ request.
|
|||
To protect a branch, you need to go to the repository’s **Settings** >
|
||||
**Branch** page and add a new rule.
|
||||
|
||||

|
||||

|
||||
|
||||
The name of the branch can be a glob where / is the separator and **
|
||||
spans accross separators. For instance `main`, `release/**`or`precious\*`.
|
||||
|
|
|
@ -183,6 +183,6 @@ There is a Test Delivery button in the webhook settings that allows to test the
|
|||
|
||||
Forgejo webhooks can be configured to send an [authorization header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Authorization) to the target.
|
||||
|
||||

|
||||

|
||||
|
||||
The authentication string is stored encrypted in the database.
|
||||
|
|
|
@ -32,7 +32,7 @@ After you have enabled the wiki you are prompted to create the initial page `Hom
|
|||
|
||||
The web UI in your browser is currently limited to adding, updating, and deleting pages; you can't manage assets like images this way.
|
||||
|
||||

|
||||

|
||||
|
||||
## Adding content via a local Git client
|
||||
|
||||
|
|