This has been adapted from
https://codeberg.org/Codeberg/Documentation/src/branch/main/content/git/using-tags.md,
and updated to document the changes from
https://codeberg.org/forgejo/forgejo/pulls/1445.
Co-authored-by: n <n@noreply.codeberg.org>
Co-authored-by: Gerhard Beck <gerhard.beck@elkb.de>
Co-authored-by: Jeremy <jeremytbaxter@protonmail.com>
Co-authored-by: Jeremy <jtbx@duck.com>
Co-authored-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-authored-by: William Davis <unbeatable-101@noreply.codeberg.org>
Co-authored-by: crapStone <crapstone01@gmail.com>
Co-authored-by: f0sh <f0sh@mailbox.org>
Co-authored-by: fnetx <git@fralix.ovh>
Co-authored-by: mutluyuz <mutluyuz@noreply.codeberg.org>
Co-authored-by: n0toose <git@n0toose.net>
- it is related to installation instructions
- mention SQLite in the guide
- reduce the complexity of the guide (I think we don't need to cover all the details here, there are better guides available)
As of forgejo/forgejo#2869, console logging implements three adaptations
for running forgejo under systemd/journald:
- forgejo learned to emit printk-style log level prefixes that are
picked up by journald and saved as the severity level of this line
(e.g., `<3>some text\n` means that "some text" will be saved as an
error entry);
- forgejo learned a new pseudo-flag "journaldflags" which is supposed to
replace "stdflags" when running under journald to reduce log clutter
(specifically, it removes date/time from log entries since the
time information is automatically saved by journald and displayed by
journalctl, and replaces the textual log level by the above-described
machine-parsable log level prefix);
- finally, forgejo will try to automatically detect whether it is
running under journald by parsing `$JOURNAL_STREAM` environment
variable and use "journalflags" as default flags if that is the case).
Document those.
Signed-off-by: Ivan Shapovalov <intelfx@intelfx.name>
This changes terminal command blocks to always use the multiline formatting,
as the leading octothorpe looks very strange when displaying a command inline.
Two consecutive inline commands at the start was very difficult to read in the
generated html. See:
https://forgejo.org/docs/latest/admin/installation-binary/
`HTTP_PORT` has been highlighted as a code term. This also means we don't need
to worry about another underscore in the same line being added and interpreted
as syntax.
Simplifies and fixes sentence structure in a few places. I've seen arguments
for and against the use of "just" in technical writing, but I think here it's
better without?
Reworded some paragraphs so that the command comes at the end.
Rename Developer to Contributor guide
- I believe this sounds more inclusive and likely improves the diversity of contributors.
Separate translation section
clarify external resources
Add links to UI/UX and user research repos
Separate issue tracker and discussions
- I imagine this is part of the confusion for people who report bugs to the discussion tracker.
Add welcome section
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/821
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: Otto Richter <git@otto.splvs.net>
Co-committed-by: Otto Richter <git@otto.splvs.net>
There was a lot of false information in that section and the
examples did not do what was described in the text.
This change extracts the perhaps-useful reminder that push still
behaves like push and allows to specify arbitrary local references.
Some points to note (which were wronged previously):
* refspec for push has the dst part optional, not the other way
around (and it's thus either `src` or `src:dest` in syntax)
* HEAD always points to the checked-out reference, so all examples
were still pushing the checked-out reference
This PR
- adds more details regarding the nature of the secret used when registering runners offline using `forgejo-cli actions register`,
- explains how to change the secret for an existing runner ([Forgejo PR #4619](https://codeberg.org/forgejo/forgejo/pulls/4619)),
- explains how to keep the Forgejo-side command idempotent if the labels aren't known ([Forgejo PR #4610](https://codeberg.org/forgejo/forgejo/pulls/4610))
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/769
Reviewed-by: twenty-panda <twenty-panda@noreply.codeberg.org>
Co-authored-by: Emmanuel BENOÎT <tseeker@nocternity.net>
Co-committed-by: Emmanuel BENOÎT <tseeker@nocternity.net>
There is no need to duplicate the information here, it is all in
detail in the checklist and changes from release to release. Just keep
the sections that provide general background information that helps
understand the meaning of the steps of the checklist.
