h759bkyo4/Documentation
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

explain why the tag may look strange at times

Browse source
This commit is contained in:
Loïc Dachary 2023-03-02 22:14:49 +01:00 committed by Gitea
parent 109622e1ea
commit bb020e98e8
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/getting-started/faq.md
View file

@ -42,4 +42,4 @@ Codeberg is built on [Forgejo](https://forgejo.org), which is open-source. We ma
## What version of Forgejo is Codeberg currently running?
You can check the version of Forgejo that Codeberg uses through the [API here](https://codeberg.org/api/v1/version).
You will get a response like this: `{"version":"1.18.5+0-20-gb49f2abc5"}`. Here, 1.18.5 is the Forgejo version number, and 20 is the number of patches applied on top of the release (which includes upstream commits and patches by Codeberg), with b49f2abc5 being the commit ID of the last patch applied on [the default branch](https://codeberg.org/Codeberg/forgejo/branches) of Codeberg's Forgejo repository. Note that the commit ID is without the "g" at the beginning.
You will get a response like this: `{"version":"1.18.5+0-20-gb49f2abc5"}`. Here, 1.18.5 is the Forgejo version number, and 20 is the number of patches applied on top of the release (which includes upstream commits and patches by Codeberg), with b49f2abc5 being the commit ID of the last patch applied on [the default branch](https://codeberg.org/Codeberg/forgejo/branches) of Codeberg's Forgejo repository. Note that the commit ID is without the "g" at the beginning. Because Forgejo is a soft-fork, the tag may no be what you would expect when the branch we use does not have the tag in its history.