Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can show some repositry statistics? #7392

Open
FalconWu2017 opened this issue Jul 9, 2019 · 3 comments
Open

Can show some repositry statistics? #7392

FalconWu2017 opened this issue Jul 9, 2019 · 3 comments
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@FalconWu2017
Copy link

Show some statistics in Overview inActivity.
For example Lines Count in all files,Size of repositry,Clone countCommit's count etc.

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Jul 9, 2019
@bestlinuxgamers
Copy link

Specifically, I would suggest the following statistics:

  1. a timeline showing contributor activity (global and per contributor).
    Example: https://github.com/go-gitea/gitea/graphs/contributors
    This could be combined with https://github.com/go-gitea/gitea/graphs/code-frequency.

  2. a timeline where the activity of the visitors is shown (number of views/visitors , number of [unique]clones, what is used [issues, code, ...]).
    Example:
    grafik

  3. a graph showing all public forks, its forks and so on, on the Gitea server.
    Example: https://github.com/go-gitea/gitea/network/members
    This could be combined with https://github.com/go-gitea/gitea/network.

@mmahmoudian
Copy link

Just to contribute to the discussion and reasoning:

Code frequency has multiple use cases:

  • shows activity status
  • shows inactive periods (e.g before and after adoption by a new maintainer)
  • shows deletion and addition of lines
  • shows if a project is really active or not (always my go-to measure on Github)

Also, on top of what @FalconWu2017 and @bestlinuxgamers suggested, it would be very informative to know some general statistics about number/ratio of code lines, comment lines, blank lines, blob/binary sizes. The former three would provide some metric about code readability (similar to what lok reports), and the latter would suggest if cloning the repo need some significant space (usually those are surprises that I only find out when cloning or going through the local clone with:

find ./ -type f -print0 \
    | xargs -0 -n 1 -I {} du -h '{}' \
    | sort -h  \
    | tail -n 10

@cabiamdos
Copy link

I would suggest statistics about how many people visited your gitea server per day in a chart.
Or which people logged in your gitea server per day.

And some other statistics for example how much data was additionally stored, how many GB of interner where used,
etc
etc

silverwind pushed a commit that referenced this issue Feb 23, 2024
### Overview
This is the implementation of Code Frequency page. This feature was
mentioned on these issues: #18262, #7392.


It adds another tab to Activity page called Code Frequency. Code
Frequency tab shows additions and deletions over time since the
repository existed.


Before:
<img width="1296" alt="image"
src="https://github.com/go-gitea/gitea/assets/32161460/2603504f-aee7-4929-a8c4-fb3412a7a0f6">

After:
<img width="1296" alt="image"
src="https://github.com/go-gitea/gitea/assets/32161460/58c03721-729f-4536-a663-9f337f240963">

---


#### Features
- See additions deletions over time since repository existed
- Click on "Additions" or "Deletions" legend to show only one type of
contribution
- Use the same cache from Contributors page so that the loading of data
will be fast once it is cached by visiting either one of the pages

---------

Co-authored-by: Giteabot <teabot@gitea.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

5 participants