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

Reason for remote url? #29

Closed
clementop opened this issue Feb 18, 2015 · 2 comments
Closed

Reason for remote url? #29

clementop opened this issue Feb 18, 2015 · 2 comments
Assignees
Milestone

Comments

@clementop
Copy link

I'm curious about your decision for making the remote url of the repository a requirement for a git stats record.

When I read "...but locally, with all your git commits.", I imagined that the graph would be aggregating data across all of my commits (at least the repositories I have imported). Many of my repositories are just kept locally -- they are not connected to any remotes.

Is git-stats intended to only aggregate public contributions?

@IonicaBizau
Copy link
Owner

Because in the future I may add more stats, maybe listing the repositories and how active was their development in the time.

So, having a remote url is probably the best technique to namespace the repositories.

I was also thinking at something like:

{
    "config": { /* defaults */}
  , "commits": { "hash": "date" }
  , "urls": { "remote-url": ["hash1", "hash2", ... ] }
}

Maybe we will change it this way. See this related discussion too: IonicaBizau/git-stats-importer#1

@IonicaBizau
Copy link
Owner

And sure, if you have any ideas post comments here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants