| Commit message (Collapse) | Author | Files | Lines |
|
Because setup-go fails to pick it up. It usually happens within 24h
and this commit can be reverted then.
|
|
Per https://pkg.go.dev/vuln/GO-2024-2687
|
|
|
|
- Currently the parsing of the push options require that `=` is present
in the value, however we shouldn't be that strict and assume if that's
not set the value is `true`.
- This allow for more natural commands, so become `-o force-push=true`
simply `-o force-push`.
- Add unit test.
|
|
Fixes https://codeberg.org/forgejo/forgejo/issues/2947
|
|
- Don't show the 'View at this point in history' button for wikis as
wikis don't have this feature.
- Adds integration test
- Resolves https://codeberg.org/forgejo/forgejo/issues/2995
|
|
- Follows a579a0f318b9d6b975e2b6feac1aa0a9054f4945
- Remove `--color-code-sidebar-bg`.
- `--color-active-line` -> `--color-highlight-bg`.
- Add `--color-highlight-fg`.
- Resolves #2964
|
|
|
|
Per https://codeberg.org/forgejo/forgejo/pulls/2983#issuecomment-1730756
|
|
* Behaves as it should with merge & squashed pull requests
* Cherry-pick commits with -x for traceability
Refs: https://github.com/kiegroup/git-backporting/issues/113
|
|
|
|
|
|
- Reading the code of this delay writer implemenation, it looks like
that it should only actually write content to the `io.Writer` if x
amount of time has passed by. However in practice it was always printing
the buffer even if the X amount of time didn't pass yet. This is in line
with what was being said in the issue that this was to help with
https://github.com/go-gitea/gitea/issues/9610.
- This was caused by the extra `Close()` calls which in turn caused that
when the second `Close` is called (which is done in a defer already) it
would've printed the buffer anyway. So remove the extra calls to `Close()`.
- Add unit test.
|
|
Move the signed tag verification line above the release notes, don't
disable the bottom margin, and make sure the verification line's box is
properly rounded like other boxes.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
|
|
- improves contrast
- looks good
- improves consistency with other label-y elements
|
|
Following https://codeberg.org/forgejo/forgejo/pulls/2528#issuecomment-1721846
- simplify the code
- allow to have custom format in translations
- provide proper Russian translation because test depends on it
|
|
- Use the correct template that was given when there's an error in
retrieving which git identity should be used.
- Remove the error from the exception list.
|
|
- If the database returns a error in integration tests, it should be
marked as a failure of the test.
- Ref: https://codeberg.org/forgejo/forgejo/issues/2962 (this should
help with logging the SQL that is resulting in the error).
|
|
Translations update from [Weblate](https://translate.codeberg.org) for [Forgejo/forgejo](https://translate.codeberg.org/projects/forgejo/forgejo/).
Current translation status:
![Weblate translation status](https://translate.codeberg.org/widget/forgejo/forgejo/horizontal-auto.svg)
Co-authored-by: Fjuro <fjuro@alius.cz>
Co-authored-by: Wuzzy <Wuzzy@users.noreply.translate.codeberg.org>
Co-authored-by: Salif Mehmed <mail@salif.eu>
Co-authored-by: Dirk <Dirk@users.noreply.translate.codeberg.org>
Co-authored-by: earl-warren <earl-warren@users.noreply.translate.codeberg.org>
Co-authored-by: 0ko <0ko@users.noreply.translate.codeberg.org>
Co-authored-by: yeziruo <yeziruo@users.noreply.translate.codeberg.org>
Co-authored-by: Mormegil <Mormegil@users.noreply.translate.codeberg.org>
Co-authored-by: Gusted <postmaster@gusted.xyz>
Co-authored-by: hankskyjames777 <hankskyjames777@users.noreply.translate.codeberg.org>
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/2937
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Codeberg Translate <translate@noreply.codeberg.org>
Co-committed-by: Codeberg Translate <translate@noreply.codeberg.org>
|
|
|
|
|
|
|
|
- Uh self explanatory? Fix a typo.
- Regression of https://codeberg.org/forgejo/forgejo/commit/365bb77a5497d492836bf823cf780c823db27e8c
- Resolves https://codeberg.org/Codeberg/Community/issues/1526
|