forgejo/forgejo
forgejo/forgejo
120
4.9k
Çatalla 842
Kod Konular 1.3k Değişiklik istekleri 151 Projeler Sürüm 106 Paketler 1 Aktivite İşlemler 21

WIP: feat: better parsing of duration in config #10273

Taslak
Gusted gusted/forgejo-parsing-duration 'nden gelen 3 değişiklikleri(commit'leri) forgejo ile birleştirmek istiyor AGit
şuradan çek: gusted/forgejo-parsing-duration
birleştir: forgejo:forgejo
Sohbet 11 İşleme 3 Değiştirilen Dosyalar 14 +456 -29
Gusted 2025-12-01 03:51:24 +01:00 yorum yaptı
Sahibi
Bağlantıyı Kopyala
  • Parse strict, if there's non-zero value it must be valid.
  • The new duration parser has more units.

Release notes

  • Features
    • PR: feat: better parsing of duration in config
- Parse strict, if there's non-zero value it must be valid. - The new duration parser has more units. <!--start release-notes-assistant--> ## Release notes <!--URL:https://codeberg.org/forgejo/forgejo--> - Features - [PR](https://codeberg.org/forgejo/forgejo/pulls/10273): <!--number 10273 --><!--line 0 --><!--description ZmVhdDogYmV0dGVyIHBhcnNpbmcgb2YgZHVyYXRpb24gaW4gY29uZmln-->feat: better parsing of duration in config<!--description--> <!--end release-notes-assistant-->
forgejo-release-notes-assistant 2025-12-01 03:53:02 +01:00 yorum yaptı
Üye
Bağlantıyı Kopyala
Where does that come from? The following is a preview of the release notes for this pull request, as they will appear in the upcoming release. They are derived from the content of the `release-notes/10273.md` file, if it exists, or the title of the pull request. They were also added at the bottom of the description of this pull request for easier reference.

This message and the release notes originate from a call to the release-notes-assistant.

@@ -1,2 +1,10 @@
 - Parse strict, if there's non-zero value it must be valid.
-- The new duration parser has more units.
\ No newline at end of file
+- The new duration parser has more units.
+
+<!--start release-notes-assistant-->
+
+## Release notes
+<!--URL:https://codeberg.org/forgejo/forgejo-->
+- Features
+  - [PR](https://codeberg.org/forgejo/forgejo/pulls/10273): <!--number 10273 --><!--line 0 --><!--description ZmVhdDogYmV0dGVyIHBhcnNpbmcgb2YgZHVyYXRpb24gaW4gY29uZmln-->feat: better parsing of duration in config<!--description-->
+<!--end release-notes-assistant-->

Release notes

  • Features
    • PR: feat: better parsing of duration in config
<details> <summary>Where does that come from?</summary> The following is a preview of the release notes for this pull request, as they will appear in the upcoming release. They are derived from the content of the `release-notes/10273.md` file, if it exists, or the title of the pull request. They were also added at the bottom of the description of this pull request for easier reference. This message and the release notes originate from a call to the [release-notes-assistant](https://code.forgejo.org/forgejo/release-notes-assistant). ```diff @@ -1,2 +1,10 @@ - Parse strict, if there's non-zero value it must be valid. -- The new duration parser has more units. \ No newline at end of file +- The new duration parser has more units. + +<!--start release-notes-assistant--> + +## Release notes +<!--URL:https://codeberg.org/forgejo/forgejo--> +- Features + - [PR](https://codeberg.org/forgejo/forgejo/pulls/10273): <!--number 10273 --><!--line 0 --><!--description ZmVhdDogYmV0dGVyIHBhcnNpbmcgb2YgZHVyYXRpb24gaW4gY29uZmln-->feat: better parsing of duration in config<!--description--> +<!--end release-notes-assistant--> ``` </details> <!--start release-notes-assistant--> ## Release notes <!--URL:https://codeberg.org/forgejo/forgejo--> - Features - [PR](https://codeberg.org/forgejo/forgejo/pulls/10273): <!--number 10273 --><!--line 0 --><!--description ZmVhdDogYmV0dGVyIHBhcnNpbmcgb2YgZHVyYXRpb24gaW4gY29uZmln-->feat: better parsing of duration in config<!--description--> <!--end release-notes-assistant-->
0ko 2025-12-01 07:31:31 +01:00 incelendi
modules/duration/parse.go
@ -0,0 +1,184 @@
// Copyright 2010 The Go Authors. All rights reserved.
// Copyright 2025 The Forgejo Authors. All rights reserved.
// SPDX-License-Identifier: BSD-3-Clause
0ko 2025-12-01 07:31:31 +01:00 yorum yaptı
Sahibi
Bağlantıyı Kopyala

Link to upstream so it's easier to follow

https://cs.opensource.google/go/go/+/refs/tags/go1.25.4:src/time/format.go;l=1621

Link to upstream so it's easier to follow https://cs.opensource.google/go/go/+/refs/tags/go1.25.4:src/time/format.go;l=1621
Gusted bu konuşmayı çözümlenmiş olarak işaretledi
0ko 2025-12-01 07:33:02 +01:00 incelendi
modules/setting/lfs.go
@ -74,1 +74,3 @@
LFS.HTTPAuthExpiry = sec.Key("LFS_HTTP_AUTH_EXPIRY").MustDuration(24 * time.Hour)
LFS.HTTPAuthExpiry, err = sec.Key("LFS_HTTP_AUTH_EXPIRY").MustDuration(24 * time.Hour)
if err != nil {
return fmt.Errorf("could not parse duration for [server].LFS_HTTP_AUTH_EXPIRY: %w", err)
0ko 2025-12-01 07:33:02 +01:00 yorum yaptı
Sahibi
Bağlantıyı Kopyala

Is there a semantic difference between could not parse duration and Failed to parse duration? They seem like an inconsistency to me.

Is there a semantic difference between `could not parse duration` and `Failed to parse duration`? They seem like an inconsistency to me.
Gusted 2025-12-01 16:47:13 +01:00 yorum yaptı
Yazar
Sahibi
Bağlantıyı Kopyala

Not really.

Not really.
0ko bu konuşmayı çözümlenmiş olarak işaretledi
0ko 2025-12-01 07:34:33 +01:00 incelendi
modules/duration/parse.go
@ -0,0 +73,4 @@
"h": uint64(time.Hour),
// Added, take a common definition.
"d": uint64(time.Hour * 24),
0ko 2025-12-01 07:34:33 +01:00 yorum yaptı
Sahibi
Bağlantıyı Kopyala

LOGIN_REMEMBER_DAYS could make use of this, but this can be scoped out.

...also USERNAME_COOLDOWN_PERIOD, [log] MAX_DAYS, [actions].ARTIFACT_RETENTION_DAYS, [actions].LOG_RETENTION_DAYS

`LOGIN_REMEMBER_DAYS` could make use of this, but this can be scoped out. ...also `USERNAME_COOLDOWN_PERIOD`, `[log] MAX_DAYS`, `[actions].ARTIFACT_RETENTION_DAYS`, `[actions].LOG_RETENTION_DAYS`
0ko bu konuşmayı çözümlenmiş olarak işaretledi
0ko 2025-12-01 11:20:02 +01:00 yorum yaptı
Sahibi
Bağlantıyı Kopyala

Have you considered attempting to upstream these changes, or you're expecting that Google will reply with "parsing d, w and returning error for invalid values is not in scope of this package"? Or making it an external package and importing it?

Have you considered attempting to upstream these changes, or you're expecting that Google will reply with "parsing `d`, `w` and returning error for invalid values is not in scope of this package"? Or making it an external package and importing it?
👀 2
fnetX 2025-12-01 12:08:02 +01:00 incelendi
fnetX bir yorum yaptı
Bağlantıyı Kopyala

Thank you very much. I think this is great to allow admins to calculate longer values (mostly in days) without the need to convert it into and from hours.

What happens if a unit is not understood. Does it fail (my preferred behaviour) or silently fall back to the default value (current behaviour)?

Thank you very much. I think this is great to allow admins to calculate longer values (mostly in days) without the need to convert it into and from hours. What happens if a unit is not understood. Does it fail (my preferred behaviour) or silently fall back to the default value (current behaviour)?
modules/duration/parse.go
@ -0,0 +75,4 @@
// Added, take a common definition.
"d": uint64(time.Hour * 24),
"w": uint64(time.Hour * 24 * 7),
"mo": uint64(time.Hour * 24 * 31),
fnetX 2025-12-01 12:06:18 +01:00 yorum yaptı
Sahibi
Bağlantıyı Kopyala

Is this commonly used to configure software? I haven't encountered it yet. If it is used, is 31 the common unit?

I am used to configuring software in days or years, and if using days, mostly multiples of 30 (e.g. 30, 60, 90, 120, 180 days etc).

Is this commonly used to configure software? I haven't encountered it yet. If it is used, is 31 the common unit? I am used to configuring software in days or years, and if using days, mostly multiples of 30 (e.g. 30, 60, 90, 120, 180 days etc).
nachtjasmin 2025-12-01 12:47:18 +01:00 yorum yaptı
Katılımcı
Bağlantıyı Kopyala

I'm also not sure about the mo and y durations. If we just add the interpretations for days and weeks, users could use 4w as a rough equivalent for a month and either 365d or 52w for the year. Thinking further about it, the only useful addition (at least from my point of view) is the unit for days. Using days as the unit ensures no ambiguity when dealing with months.

For example, if someone expects to cleanup old stuff every month, 1mo could end up in a lot of confusion after February 28th. 30d on the other hand as a configuration value leaves much less room for interpretation.

I'm also not sure about the `mo` and `y` durations. If we just add the interpretations for days and weeks, users could use `4w` as a rough equivalent for a month and either `365d` or `52w` for the year. Thinking further about it, the only useful addition (at least from my point of view) is the unit for days. Using days as the unit ensures no ambiguity when dealing with months. For example, if someone expects to cleanup old stuff every month, `1mo` could end up in a lot of confusion after February 28th. `30d` on the other hand as a configuration value leaves much less room for interpretation.
fnetX 2025-12-01 12:53:14 +01:00 yorum yaptı
Sahibi
Bağlantıyı Kopyala

I think years could make sense for configuring multi-year retention. E.g. clean up action logs and artifacts after 2 years, recorded activities after 3 years. Calculating multiple years in days is also very inconvenient.

I am not sure if any Forgejo admin ever configured it like this, though. The most important addition is probably days.

I think years could make sense for configuring multi-year retention. E.g. clean up action logs and artifacts after 2 years, recorded activities after 3 years. Calculating multiple years in days is also very inconvenient. I am not sure if any Forgejo admin ever configured it like this, though. The most important addition is probably days.
Gusted 2025-12-01 13:00:10 +01:00 yorum yaptı
Yazar
Sahibi
Bağlantıyı Kopyala

I can drop month and week.

The PR is WIP because the documentation still has to be written that will clearly state that these are just shorthand for other durations and will not take into account any logic regarding dates.

I can drop month and week. The PR is WIP because the documentation still has to be written that will clearly state that these are just shorthand for other durations and will not take into account any logic regarding dates.
Gusted bu konuşmayı çözümlenmiş olarak işaretledi
Gusted 2025-12-01 12:55:50 +01:00 yorum yaptı
Yazar
Sahibi
Bağlantıyı Kopyala

@0ko wrote in #10273 (yorum):

Have you considered attempting to upstream these changes, or you're expecting that Google will reply with "parsing d, w and returning error for invalid values is not in scope of this package"? Or making it an external package and importing it?

https://github.com/golang/go/issues/17767#issuecomment-258167205

@0ko wrote in https://codeberg.org/forgejo/forgejo/pulls/10273#issuecomment-8623950: > Have you considered attempting to upstream these changes, or you're expecting that Google will reply with "parsing `d`, `w` and returning error for invalid values is not in scope of this package"? Or making it an external package and importing it? https://github.com/golang/go/issues/17767#issuecomment-258167205
0ko 2025-12-01 13:06:58 +01:00 yorum yaptı
Sahibi
Bağlantıyı Kopyala

Well that was 9 years ago but another issue was closed just recently with same reasoning, so that clarifies it. What about an external package? Or developers who would like to reuse this could just import codeberg.org/forgejo/forgejo/duration if they want?

Well that was 9 years ago but [another issue](https://github.com/golang/go/issues/74813) was closed just recently with same reasoning, so that clarifies it. What about an external package? Or developers who would like to reuse this could just import `codeberg.org/forgejo/forgejo/duration` if they want?
Gusted 2025-12-01 13:16:33 +01:00 yorum yaptı
Yazar
Sahibi
Bağlantıyı Kopyala

@0ko wrote in #10273 (yorum):

What about an external package? Or developers who would like to reuse this could just import codeberg.org/forgejo/forgejo/duration if they want?

Yes maybe, but given the small amount of code there's a proverb that applies here https://www.youtube.com/watch?v=PAAkCSZUG1c&t=9m28s. IIRC @fogti had a similar question regarding making the modules directory a importable package. I'm afraid this would be a larger discussion.

@0ko wrote in https://codeberg.org/forgejo/forgejo/pulls/10273#issuecomment-8625075: > What about an external package? Or developers who would like to reuse this could just import `codeberg.org/forgejo/forgejo/duration` if they want? Yes maybe, but given the small amount of code there's a proverb that applies here https://www.youtube.com/watch?v=PAAkCSZUG1c&t=9m28s. IIRC @fogti had a similar question regarding making the `modules` directory a importable package. I'm afraid this would be a larger discussion.
👍 2
Gusted gusted/forgejo-parsing-duration e429d04d9a
Bazı kontroller başarısız oldu
issue-labels / backporting (pull_request_target) Has been skipped
Ayrıntılar
issue-labels / cascade (pull_request_target) Has been skipped
Ayrıntılar
testing / frontend-checks (pull_request) Successful in 1m0s
Ayrıntılar
requirements / merge-conditions (pull_request) Successful in 1s
Ayrıntılar
issue-labels / release-notes (pull_request_target) Successful in 31s
Ayrıntılar
testing / backend-checks (pull_request) Failing after 2m32s
Ayrıntılar
testing / test-unit (pull_request) Has been skipped
Ayrıntılar
testing / test-e2e (pull_request) Has been skipped
Ayrıntılar
testing / test-mysql (pull_request) Has been skipped
Ayrıntılar
testing / test-pgsql (pull_request) Has been skipped
Ayrıntılar
testing / test-sqlite (pull_request) Has been skipped
Ayrıntılar
testing / test-remote-cacher (redis) (pull_request) Has been skipped
Ayrıntılar
testing / test-remote-cacher (valkey) (pull_request) Has been skipped
Ayrıntılar
testing / test-remote-cacher (garnet) (pull_request) Has been skipped
Ayrıntılar
testing / test-remote-cacher (redict) (pull_request) Has been skipped
Ayrıntılar
testing / security-check (pull_request) Has been skipped
Ayrıntılar
hedefinden dd2a5820fb
Bazı kontroller başarısız oldu
requirements / merge-conditions (pull_request) Successful in 5s
Ayrıntılar
issue-labels / release-notes (pull_request_target) Successful in 1m1s
Ayrıntılar
testing / frontend-checks (pull_request) Successful in 2m3s
Ayrıntılar
testing / backend-checks (pull_request) Failing after 4m46s
Ayrıntılar
testing / test-unit (pull_request) Has been skipped
Ayrıntılar
testing / test-e2e (pull_request) Has been skipped
Ayrıntılar
testing / test-mysql (pull_request) Has been skipped
Ayrıntılar
testing / test-pgsql (pull_request) Has been skipped
Ayrıntılar
testing / test-sqlite (pull_request) Has been skipped
Ayrıntılar
testing / test-remote-cacher (redis) (pull_request) Has been skipped
Ayrıntılar
testing / test-remote-cacher (valkey) (pull_request) Has been skipped
Ayrıntılar
testing / test-remote-cacher (garnet) (pull_request) Has been skipped
Ayrıntılar
testing / test-remote-cacher (redict) (pull_request) Has been skipped
Ayrıntılar
testing / security-check (pull_request) Has been skipped
Ayrıntılar
hedefine zorla gönderildi 2025-12-01 16:50:23 +01:00 Karşılaştır
Gusted gusted/forgejo-parsing-duration dd2a5820fb
Bazı kontroller başarısız oldu
requirements / merge-conditions (pull_request) Successful in 5s
Ayrıntılar
issue-labels / release-notes (pull_request_target) Successful in 1m1s
Ayrıntılar
testing / frontend-checks (pull_request) Successful in 2m3s
Ayrıntılar
testing / backend-checks (pull_request) Failing after 4m46s
Ayrıntılar
testing / test-unit (pull_request) Has been skipped
Ayrıntılar
testing / test-e2e (pull_request) Has been skipped
Ayrıntılar
testing / test-mysql (pull_request) Has been skipped
Ayrıntılar
testing / test-pgsql (pull_request) Has been skipped
Ayrıntılar
testing / test-sqlite (pull_request) Has been skipped
Ayrıntılar
testing / test-remote-cacher (redis) (pull_request) Has been skipped
Ayrıntılar
testing / test-remote-cacher (valkey) (pull_request) Has been skipped
Ayrıntılar
testing / test-remote-cacher (garnet) (pull_request) Has been skipped
Ayrıntılar
testing / test-remote-cacher (redict) (pull_request) Has been skipped
Ayrıntılar
testing / security-check (pull_request) Has been skipped
Ayrıntılar
hedefinden ad591407bc
Bazı kontroller başarısız oldu
requirements / merge-conditions (pull_request) Successful in 2s
Ayrıntılar
testing / frontend-checks (pull_request) Successful in 1m35s
Ayrıntılar
testing / backend-checks (pull_request) Successful in 4m10s
Ayrıntılar
issue-labels / release-notes (pull_request_target) Successful in 45s
Ayrıntılar
testing / test-unit (pull_request) Successful in 7m10s
Ayrıntılar
testing / test-remote-cacher (redis) (pull_request) Successful in 2m12s
Ayrıntılar
testing / test-remote-cacher (valkey) (pull_request) Successful in 2m4s
Ayrıntılar
testing / test-remote-cacher (garnet) (pull_request) Successful in 2m5s
Ayrıntılar
testing / test-remote-cacher (redict) (pull_request) Successful in 1m49s
Ayrıntılar
testing / test-e2e (pull_request) Failing after 19m34s
Ayrıntılar
testing / test-mysql (pull_request) Successful in 27m30s
Ayrıntılar
testing / test-sqlite (pull_request) Successful in 32m15s
Ayrıntılar
testing / test-pgsql (pull_request) Successful in 37m49s
Ayrıntılar
testing / security-check (pull_request) Successful in 1m11s
Ayrıntılar
hedefine zorla gönderildi 2025-12-01 16:58:10 +01:00 Karşılaştır
Gusted gusted/forgejo-parsing-duration ad591407bc
Bazı kontroller başarısız oldu
requirements / merge-conditions (pull_request) Successful in 2s
Ayrıntılar
testing / frontend-checks (pull_request) Successful in 1m35s
Ayrıntılar
testing / backend-checks (pull_request) Successful in 4m10s
Ayrıntılar
issue-labels / release-notes (pull_request_target) Successful in 45s
Ayrıntılar
testing / test-unit (pull_request) Successful in 7m10s
Ayrıntılar
testing / test-remote-cacher (redis) (pull_request) Successful in 2m12s
Ayrıntılar
testing / test-remote-cacher (valkey) (pull_request) Successful in 2m4s
Ayrıntılar
testing / test-remote-cacher (garnet) (pull_request) Successful in 2m5s
Ayrıntılar
testing / test-remote-cacher (redict) (pull_request) Successful in 1m49s
Ayrıntılar
testing / test-e2e (pull_request) Failing after 19m34s
Ayrıntılar
testing / test-mysql (pull_request) Successful in 27m30s
Ayrıntılar
testing / test-sqlite (pull_request) Successful in 32m15s
Ayrıntılar
testing / test-pgsql (pull_request) Successful in 37m49s
Ayrıntılar
testing / security-check (pull_request) Successful in 1m11s
Ayrıntılar
hedefinden c8a22db9c6
Tüm denetlemeler başarılı oldu
requirements / merge-conditions (pull_request) Successful in 3s
Ayrıntılar
issue-labels / release-notes (pull_request_target) Successful in 40s
Ayrıntılar
testing / semgrep/ci (pull_request) Successful in 19s
Ayrıntılar
testing / frontend-checks (pull_request) Successful in 1m59s
Ayrıntılar
testing / backend-checks (pull_request) Successful in 7m20s
Ayrıntılar
testing / test-unit (pull_request) Successful in 6m8s
Ayrıntılar
testing / test-remote-cacher (redis) (pull_request) Successful in 2m25s
Ayrıntılar
testing / test-remote-cacher (valkey) (pull_request) Successful in 2m35s
Ayrıntılar
testing / test-remote-cacher (garnet) (pull_request) Successful in 2m39s
Ayrıntılar
testing / test-remote-cacher (redict) (pull_request) Successful in 2m22s
Ayrıntılar
testing / test-mysql (pull_request) Successful in 31m40s
Ayrıntılar
testing / test-e2e (pull_request) Successful in 32m44s
Ayrıntılar
testing / test-sqlite (pull_request) Successful in 37m41s
Ayrıntılar
testing / test-pgsql (pull_request) Successful in 42m35s
Ayrıntılar
testing / security-check (pull_request) Successful in 2m14s
Ayrıntılar
hedefine zorla gönderildi 2026-04-01 03:45:07 +02:00 Karşılaştır
limiting-factor 2026-05-16 07:40:47 +02:00 yorum yaptı
Üye
Bağlantıyı Kopyala

@Gusted can this pull request be considered ready for review and WIP: removed?

@Gusted can this pull request be considered ready for review and `WIP:` removed?
Gusted 2026-05-16 13:36:13 +02:00 yorum yaptı
Yazar
Sahibi
Bağlantıyı Kopyala

@limiting-factor wrote in #10273 (yorum):

@Gusted can this pull request be considered ready for review and WIP: removed?

The PR is ready, but I hadn't got around to write the necessary documentation PR for it.

@limiting-factor wrote in https://codeberg.org/forgejo/forgejo/pulls/10273#issuecomment-15049845: > @Gusted can this pull request be considered ready for review and `WIP:` removed? The PR is ready, but I hadn't got around to write the necessary documentation PR for it.
Tüm denetlemeler başarılı oldu
requirements / merge-conditions (pull_request) Successful in 3s
Ayrıntılar
issue-labels / release-notes (pull_request_target) Successful in 40s
Ayrıntılar
testing / semgrep/ci (pull_request) Successful in 19s
Ayrıntılar
testing / frontend-checks (pull_request) Successful in 1m59s
Gerekli
Ayrıntılar
testing / backend-checks (pull_request) Successful in 7m20s
Gerekli
Ayrıntılar
testing / test-unit (pull_request) Successful in 6m8s
Gerekli
Ayrıntılar
testing / test-remote-cacher (redis) (pull_request) Successful in 2m25s
Ayrıntılar
testing / test-remote-cacher (valkey) (pull_request) Successful in 2m35s
Ayrıntılar
testing / test-remote-cacher (garnet) (pull_request) Successful in 2m39s
Ayrıntılar
testing / test-remote-cacher (redict) (pull_request) Successful in 2m22s
Ayrıntılar
testing / test-mysql (pull_request) Successful in 31m40s
Gerekli
Ayrıntılar
testing / test-e2e (pull_request) Successful in 32m44s
Ayrıntılar
testing / test-sqlite (pull_request) Successful in 37m41s
Gerekli
Ayrıntılar
testing / test-pgsql (pull_request) Successful in 42m35s
Gerekli
Ayrıntılar
testing / security-check (pull_request) Successful in 2m14s
Ayrıntılar
Bu değişiklik isteğinde, hedef dalla çakışan değişiklikler var.
  • modules/setting/database.go
Komut satırı talimatlarını görüntüleyin.

Elle(manuel) birleştirme yardımcısı

Birleştirme işlemini kendiniz elle(manuel olarak) tamamlarken bu birleştirmenin değişiklik(commit) mesajını kullanın.

Çekme

Proje deponuzdan yeni bir dalı çekin ve değişiklikleri test edin.
git fetch -u origin +refs/pull/10273/head:gusted/forgejo-parsing-duration
git switch gusted/forgejo-parsing-duration
Bu konuşmaya katılmak için oturum aç.
Gözden Geçirenler
Değerlendirici yok
Etiketler
Etiketleri temizle   
arch
riscv64

Arşivlenmiş

  
backport/v1.19
Scheduled for backport to Forgejo v1.19

Arşivlenmiş

  
backport/v1.20
Scheduled for backport to Forgejo v1.20

Arşivlenmiş

  
backport/v1.21/forgejo
Scheduled for backport to Forgejo v1.21

Arşivlenmiş

  
backport/v10.0/forgejo
Automated backport to v10.0

Arşivlenmiş

  
backport/v11.0/forgejo
Automated backport to v11.0

  
backport/v12.0/forgejo
Automated backport to v12.0

Arşivlenmiş

  
backport/v13.0/forgejo
Automated backport to v13.0

Arşivlenmiş

  
backport/v14.0/forgejo
Automated backport to v14.0

Arşivlenmiş

  
backport/v15.0/forgejo
Automated backport to v15.0

  
backport/v7.0/forgejo
Scheduled for backport to Forgejo v7.0

Arşivlenmiş

  
backport/v8.0/forgejo
Scheduled for backport to Forgejo v8.0

Arşivlenmiş

  
backport/v9.0/forgejo
Scheduled for backport to Forgejo v9.0

Arşivlenmiş

  
breaking
The release containing this change is not backward compatible

  
bug
Something is not working

Arşivlenmiş

  
bug
confirmed
 it can be reproduced

  
bug
duplicate
 bug has already been reported in the Forgejo tracker

  
bug
needs-more-info
 the information provided does not contain enough details

  
bug
new-report
 bug has just been reported and need triage (default label on issue creation)

  
bug
reported-upstream
 bug cannot be fixed within Forgejo easily, it has been reported upstream

  
code/actions
Forgejo Actions feature

  
code/api
API

  
code/auth
Forgejo Authentication

  
code/auth/faidp
Forgejo as Identity Provider (in OAuth/OIDC flow)

  
code/auth/farp
Forgejo as Relying Party / Client (in OAuth/OIDC flow)

  
code/email
Everything related to email in Forgejo

  
code/federation
Federation

  
code/git
Related to the Git backend in Forgejo

  
code/migrations
Migration between Git forges (i.e. for GitHub, GitLab, Gitea, Forgejo, etc.). NOT for database migrations.

  
code/packages
Forgejo package and container registry

  
code/wiki
  
database
MySQL
 https://www.mysql.com/

  
database
PostgreSQL
 https://www.postgresql.org/

  
database
SQLite
 https://sqlite.org/

  
dependency-upgrade
https://codeberg.org/forgejo/forgejo/issues/2779

  
dependency
Chi
 https://github.com/go-chi/chi/

Arşivlenmiş

  
dependency
Chroma
 https://github.com/alecthomas/chroma/

Arşivlenmiş

  
dependency
F3
 https://f3.forgefriends.org/

  
dependency
ForgeFed
 https://forgefed.org

  
dependency
garage
 https://git.deuxfleurs.fr/Deuxfleurs/garage

  
dependency
Gitea
 https://github.com/go-gitea/gitea

Arşivlenmiş

  
dependency
Golang
 https://go.dev/

  
Discussion

   
duplicate
This issue or pull request already exists

  
enhancement/feature
New feature

  
forgejo/accessibility
Accessibility (a11y)

  
forgejo/branding
Branding (logo, name, tagline etc.)

  
forgejo/ci
Forgejo Actions CI configuration

  
forgejo/commit-graph
The commit graph feature and page.

  
forgejo/documentation

   
forgejo/furnace cleanup
Keeping Forgejo in sync with its dependencies and contributing back to them

Arşivlenmiş

  
forgejo/i18n
t9n/translation, l10n/localization, and i18n/internationalization of Forgejo

  
forgejo/interop
Interoperability with other services: Webhooks, bridges, integrations

  
forgejo/moderation
Moderation

  
forgejo/privacy
Privacy first

  
forgejo/release
Release management

  
forgejo/scaling
Performance and scaling

  
forgejo/security
Security (please disclose responsibly)

  
forgejo/ui
User interface

  
Gain
High
 User research provides indicators that this would be good to have, interested contributors are encouraged to pick this.

  
Gain
Nice to have
 This is likely worth having, but the assumption is not backed by user research data (it might benefit a small amount of users only.) Unlikely to receive much attention, but feel free to pick.

  
Gain
Undefined
 Not enough information to assess the request's benefits. This issue may be closed if no gain is established: You can help by giving us more input.

  
Gain
Very High
 User research indicates that this is an important improvement for Forgejo users. Contributions very welcome!

  
good first issue
Optimal for first-timers! Make sure to look for further explanations and ask for help if needed. If you want, you can consider the person who added this label as a point of contact.

  
i18n/backport-stable
This PR needs to be backported to stable branch of Forgejo safely and manually, using a migration script.

  
impact
large
 Large impact: Potential data loss, many users affected, major degradation in UX.

  
impact
medium
 Medium impact: Several users affected, degradation in UX, workarounds might be available but inconvenient.

  
impact
small
 Small impact: No data loss, workarounds might be available, affects few users.

  
impact
unknown
 Report was not yet triaged to assess impact.

  
Incompatible license
This pull request contains changes that are not (yet) compatible with the current Forgejo license

  
issue
closed
 The issue was resolved in the repository of the dependency

  
issue
do-not-exist-yet
 An issue should be created in the respository of the dependency

  
issue
open
 An open issue exists in the upstream repository of the dependency

  
manual test
Pull requests that have been merged with a manual test

Arşivlenmiş

  
Manually tested during feature freeze
The manual test instructions were followed

  
OS
FreeBSD
 Specific to the FreeBSD Operating System

  
OS
Linux
 Specific to (GNU/)Linux Operating Systems

  
OS
macOS
 Specific to the MacOS Operating System

  
OS
Windows
 Specific to the Windows Operating System

  
problem
A user report about a problem. Needs to be triaged to find potential solutions.

  
QA

   
regression
found in the version of the milestone and not before

  
release blocker
Issues that must be fixed before the release can be published

  
Release Cycle
Feature Freeze
 Only bug fixes with automated tests (except for CSS/JavaScript)

  
release-blocker
v7.0
 Issues that must be fixed before Forgejo v7.0 can be released 17 April 2024

Arşivlenmiş

  
release-blocker
v7.0.1
 Issues that must be fixed before Forgejo v7.0.1 can be released

Arşivlenmiş

  
release-blocker
v7.0.2
 Issues that must be fixed before Forgejo v7.0.2 can be released

Arşivlenmiş

  
release-blocker
v7.0.3
 Issues that must be fixed before Forgejo v7.0.3 can be released

Arşivlenmiş

  
release-blocker
v7.0.4
 Issues that must be fixed before Forgejo v7.0.4 can be released

Arşivlenmiş

  
release-blocker
v8.0.0
 Issues that must be fixed before Forgejo v8.0.0 can be released

Arşivlenmiş

  
release-blocker/v9.0.0
Issues that must be fixed before Forgejo v9.0.0 can be released

Arşivlenmiş

  
run-all-playwright-tests
Add this label to a PR to run all playwright tests manually.

  
run-end-to-end-tests
Trigger additional tests on the PR when it is ready to be merged

  
stage
2-research
 Needs research to moe on.

  
stage
3-design
 Needs design to move on

  
stage
4-implementation
 This is actionable and waits for implementation

  
test
manual
 manual testing has been documented

  
test
needed
 test should be added

  
test
needs-help
 help needed to add a test

  
test
not-needed
 no additional test is needed

  
test
present
 test has been added

  
untested
Pull requests that have been merged with no test and submitted as is to the dependency where they belong

Arşivlenmiş

  
User research - time-tracker
Time tracking feature for issues and the JS stopwatch.

  
valuable code
This PR was closed because the implementation is incomplete

  
worth a release-note
Add this PR to the release notes

  
User research - Accessibility
Requires input about accessibility features, likely involves user testing.

  
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.

  
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.

  
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.

  
User research - Errors
How to deal with errors in the application and write helpful error messages.

  
User research - Filters
How filter and search is being worked with.

  
User research - Future backlog
The issue might be inspiring for future design work.

  
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc

  
User research - Labels
Active research about Labels

  
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research

  
User research - Needs input
Use this label to let the User Research team know their input is requested.

  
User research - Notifications/Dashboard
Research on how users should know what to do next.

  
User research - Rendering
Text rendering, markup languages etc

  
User research - Repo creation
Active research about the New Repo dialog.

  
User research - Repo units
The repo sections, disabling them and the "Add more" button.

  
User research - Security

   
User research - Settings (in-app)
How to structure in-app settings in the future?

Etiket Yok
arch
riscv64
backport/v1.19
backport/v1.20
backport/v1.21/forgejo
backport/v10.0/forgejo
backport/v11.0/forgejo
backport/v12.0/forgejo
backport/v13.0/forgejo
backport/v14.0/forgejo
backport/v15.0/forgejo
backport/v7.0/forgejo
backport/v8.0/forgejo
backport/v9.0/forgejo
breaking
bug
bug
confirmed
bug
duplicate
bug
needs-more-info
bug
new-report
bug
reported-upstream
code/actions
code/api
code/auth
code/auth/faidp
code/auth/farp
code/email
code/federation
code/git
code/migrations
code/packages
code/wiki
database
MySQL
database
PostgreSQL
database
SQLite
dependency-upgrade
dependency
Chi
dependency
Chroma
dependency
F3
dependency
ForgeFed
dependency
garage
dependency
Gitea
dependency
Golang
Discussion
duplicate
enhancement/feature
forgejo/accessibility
forgejo/branding
forgejo/ci
forgejo/commit-graph
forgejo/documentation
forgejo/furnace cleanup
forgejo/i18n
forgejo/interop
forgejo/moderation
forgejo/privacy
forgejo/release
forgejo/scaling
forgejo/security
forgejo/ui
Gain
High
Gain
Nice to have
Gain
Undefined
Gain
Very High
good first issue
i18n/backport-stable
impact
large
impact
medium
impact
small
impact
unknown
Incompatible license
issue
closed
issue
do-not-exist-yet
issue
open
manual test
Manually tested during feature freeze
OS
FreeBSD
OS
Linux
OS
macOS
OS
Windows
problem
QA
regression
release blocker
Release Cycle
Feature Freeze
release-blocker
v7.0
release-blocker
v7.0.1
release-blocker
v7.0.2
release-blocker
v7.0.3
release-blocker
v7.0.4
release-blocker
v8.0.0
release-blocker/v9.0.0
run-all-playwright-tests
run-end-to-end-tests
stage
2-research
stage
3-design
stage
4-implementation
test
manual
test
needed
test
needs-help
test
not-needed
test
present
untested
User research - time-tracker
valuable code
worth a release-note
User research - Accessibility
User research - Blocked
User research - Community
User research - Config (instance)
User research - Errors
User research - Filters
User research - Future backlog
User research - Git workflow
User research - Labels
User research - Moderation
User research - Needs input
User research - Notifications/Dashboard
User research - Rendering
User research - Repo creation
User research - Repo units
User research - Security
User research - Settings (in-app)
Kilometre Taşı
Kilometre Taşlarını Temizle
Öge yok
Kilometre Taşı Yok
Projeler
Projeleri temizle
Öge yok
Proje yok
Atananlar
Atamaları Temizle
Atanan Kişi Yok
6 katılımcı
Bildirimler
Bitiş Tarihi
Bitiş tarihi geçersiz veya aralık dışında. Lütfen 'yyyy-aa-gg' biçimini kullanın.

Bitiş tarihi atanmadı.

Bağımlılıklar

Bağımlılık yok.

Referans
forgejo/forgejo!10273
Herhangi bir açıklama sağlanmadı.