It was quite painful yesterday to try to figure out why my workflow didn't work anymore after the Forgejo migration. Turns out that `gitea/act_runner` used a different default Docker image. With this PR, it should be clearer to other people what is the meaning of the labels.
Co-authored-by: Rik Huijzer <github@huijzer.xyz>
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/475
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Rik Huijzer <rikh@noreply.codeberg.org>
Co-committed-by: Rik Huijzer <rikh@noreply.codeberg.org>
(cherry picked from commit 05f8dd4b77)
This PR extends the examples that were provided by @earl-warren in https://codeberg.org/forgejo/runner. I've tested this configuration twice today on two completely separate servers. For more information about the whole process that I've used, see https://huijzer.xyz/posts/forgejo-setup/.
I'll try to extract upstream a bit more information to the Forgejo docs. Feel free to take anything from my blog that seems useful and don't worry about credits. Feel free to copy whatever seems useful.
Co-authored-by: Rik Huijzer <github@huijzer.xyz>
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/474
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Rik Huijzer <rikh@noreply.codeberg.org>
Co-committed-by: Rik Huijzer <rikh@noreply.codeberg.org>
(cherry picked from commit 4ff026d3ed)
Preview: https://forgejo.codeberg.page/@docs_pull_427/docs/next/admin/customization/
---
The previous version of this document insinuated that you need to be
familiar with Forgejo's source code and compile Forgejo from source
for custom branding changes. As of the most recent Forgejo version,
this is not necessarily true, as custom files can be served from
the CustomPath.
Administrators that were not developers therefore dismissed the
other guide and its contents without reading this, and I was one
of them. I thought it would make sense for this file to provide
information on where to put a custom logo. This change does not
fix it (this will be done later), but it will reduce the confusion
for now.
This warning confused me personally and other Forgejo users, as I
had one person tell me IRL that they thought that it was not possible
to serve a custom logo.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/427
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-committed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
(cherry picked from commit d12a9fee60)
The Table under "Contact Link" has two rows labeled `name` with exactly the same content, it should only occur once.
(cherry picked from commit 4b8db5a048)
- Improve introductory paragraph
- Explain Agit's use cases briefly
- Add required parameter markers
- Explain caveats
- Minor grammar improvements
add remark about empty titles
add git internals book reference
fix error in example
improve background information and examples
add information for gerrit users, improve caveats
improve topic stuff, break examples into multiple lines
fix typo
improve typo
Clean things up, address review comments
- Improve background information
- Move Caveat information to parameter explanations
- Add <session> example
\
wrong "
Capitalization error, s/instructions/information
Reiterate caveats, again
'For clarity reasons' instead of 'For reasons of clarity'
small language improvements
change order of push options
remove half-finished line
topic is optional when <session> exists
topic -> `topic`
Change title to 'AGit Workflow Usage'
OK, I know I said that I'd drop this for now like a thousand times
... but there was this sentence that I just read again and
it annoyed me :(
retrospectively -> retroactively
fix small markdown error
Clarify the differences between session and topic better
Change topic branch example to avoid confusion
instead of keeping a backup within the container itself, trigger the
backup external to the container to make sure it reflects the state of
the container after Forgejo is shutdown in case it needs to be
retrieved.
(cherry picked from commit 73d1ff084b)
* hint to use `make help` for target information
* require Go v1.21
* remove some redundant / obsolete strings
* `TAGS='sqlite sqlite_unlock_notify' make watch` because it is not
much use without sqlite
(cherry picked from commit 2288a5dc4e)
