#307 Traffic to a repository

Open
opened 1 week ago by azzamsa · 2 comments
azzamsa commented 1 week ago

Some people are less likely to star. Other way to know how popular our repo is by knowing how much unique cloner and unique visitor in specific time span.

Is Codberg will support traffic to a repository?

The GitHub equivalent looks like this:

image

Some people are less likely to star. Other way to know how popular our repo is by knowing how much *unique cloner* and *unique visitor* in specific time span. Is Codberg will support **traffic to a repository**? The GitHub equivalent looks like this: ![image](/attachments/a505c957-5930-4b64-a74c-bb0e9e0cdb43)
112 KiB
6543 added the
enhancement
label 1 week ago
6543 added the
gitea-related issue
label 1 week ago
6543 commented 1 week ago
Collaborator

I think there are two solutions:

  • codeberg add some analytics js + custom template (bad idear in my opinion)
  • gitea itself profide this fuction -> pleace create a “feature request” upstream :)
I think there are two solutions: * codeberg add some analytics js + custom template (bad idear in my opinion) * gitea itself profide this fuction -> pleace create a "feature request" upstream :)
azzamsa commented 1 week ago
Poster

I’ve opened an issue at Gitea upstream for this feature: https://github.com/go-gitea/gitea/issues/13104

I’ve opened an issue at Gitea upstream for this feature: https://github.com/go-gitea/gitea/issues/13104
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.