Add longer activity periods #3791

New Issue

GiteaMirror · 2025-11-02T05:25:21-06:00

GiteaMirror commented

2025-11-02 05:25:21 -06:00

Originally created by @noerw on GitHub (Aug 15, 2019).

Gitea version (or commit ref): 1.9.1

It would be great to have an activity overview for longer periods (yearly, all time) to get a feel for a projects scope over its full life time.

Was the maximum value of 1 month a performance consideration?

Originally created by @noerw on GitHub (Aug 15, 2019). - Gitea version (or commit ref): 1.9.1 It would be great to have an activity overview for longer periods (yearly, all time) to get a feel for a projects scope over its full life time. Was the maximum value of 1 month a performance consideration?

GiteaMirror added the type/proposal label 2025-11-02 05:25:21 -06:00

GiteaMirror closed this issue

2025-11-02 05:25:21 -06:00

GiteaMirror commented

2025-11-02 05:25:21 -06:00

@hamarb123 commented on GitHub (Aug 17, 2020):

I would like an all time activity period please, I am not bothered about the performance of it, I also do not mind if it has to be enabled in a setting somewhere.

Thanks :)

@hamarb123 commented on GitHub (Aug 17, 2020): I would like an all time activity period please, I am not bothered about the performance of it, I also do not mind if it has to be enabled in a setting somewhere. Thanks :)

GiteaMirror commented

2025-11-02 05:25:22 -06:00

@lafriks commented on GitHub (Aug 17, 2020):

This is already fixed by #8829. It added yearly period. All-time period would be performance overkill

@lafriks commented on GitHub (Aug 17, 2020): This is already fixed by #8829. It added yearly period. All-time period would be performance overkill

GiteaMirror commented

2025-11-02 05:25:22 -06:00

@noerw commented on GitHub (Aug 17, 2020):

This is not a fix. To reiterate @hamarb123:
Can we let users (i.e. admins of small personal instances) decide what a performance overkill is? i.e. make 1 month the default max, but give the option to specify higher time ranges.

(Also: To make this view scalable, we could compute & store its state on each push, instead of an expensive query. Though I'm not sure about the complexity-usefulness tradeoff here.)

@noerw commented on GitHub (Aug 17, 2020): This is not a fix. To reiterate @hamarb123: Can we let users (i.e. admins of small personal instances) decide what a performance overkill is? i.e. make 1 month the default max, but give the option to specify higher time ranges. (Also: To make this view scalable, we could compute & store its state on each push, instead of an expensive query. Though I'm not sure about the complexity-usefulness tradeoff here.)

GiteaMirror referenced this issue

2025-11-02 12:25:56 -06:00

[PR #3791] [CLOSED] Add new option to allow only OAuth2/OpenID user registration #17084

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#3791