I would like to review my GitHub activities for the past 12 months. On my public profile I can see as much as one month only. I can go to an individual repository and review all the commits for any period of time, of course, but this becomes unfeasible when I have to interleave data from dozens of repositories.
Is there an advanced query or page that allows me to see or download this aggregated data?
Looks like GitHub does not allow viewing contribution data for more than a Month by default but if you use it's apis you can build something that can keep track of your contribution for how ever long you want it to.
Here's where GitHub talks about contribution.
https://help.github.com/articles/viewing-contributions-on-your-profile-page/
Related
Github provides nice feature to manage feature completeness OR sprint completeness. It's called Milestones and it's really nice.
However, sometimes we need to track both completeness of the feature (e.g. "Refactoring payment systems integration") and completeness of the sprint (e.g. "Sprint week 15").
Is there any way to do so using Github issues?
GitHub does not currently allow you to assign multiple milestones to an issue. There is an issue tracking this feature request, but there seems to be little movement on it.
There's a couple of workarounds possible. The simplest one is to use Milestones to track sprints, and labels to track features. While labels do not give you the nice "X% completed" overview that Milestones do, you can quickly (single click) get an overview of all issues tagged with a label, and see how many are open vs. closed.
Another possibility is that you use Task Lists (see GitHub Markdown guide) to your advantage. Instead of having each issue belonging to a particular feature as an independent GitHub issue, you track the entire feature as a single issue, and add a Task List to the issue to track individual items. The advantage of this is that you get a nice progress bar in your issue overview, showing you feature completeness. A disadvantage is that you cannot assign individual tasks to separate developers any longer.
The company I work for uses GitHub extensively. Is there is a way to compare my team's individual contributions to specific repositories on a weekly basis?
Apart from loading their individual GitHub profiles and comparing the statistics?
My team is growing at quite a rapid pace, and soon it will be difficult to find the time to manually compare them. We also work in 4 different times zones thus it can be difficult to sync up with everyone effectively.
The current main view which offer user activity comparison is the Graphs view:
(That and the Pulse view)
I have several projects on GitHub, and they all have the traffic graph where I can view how much traffic my repository is getting.
The blog post I had linked is very vague about visitors. It states:
..how many unique visitors it's had..
I just find it odd that some of my repositories have daily activity, but I'm not sure if most of those views are me, and if they are, why does it say "unique visitors" when i would be the only unique visitor
Question:
Does the traffic graph used on GitHub include yourself when navigating through your own source? It's very minor, but I'm genuinely curious if the views I'm getting is myself navigating through the source, or if I have people that are actually browsing through my source.
In specific, the line that shows "Views", not "Unique visitors" because unique visitors will obviously mean new people browsing the repository.
For those who think this is offtopic, re-read the on-topic post.
Most notably:
but if your question generally covers… software tools commonly used by programmers
OK I just contacted support and received a response:
Hello -
> Do the numbers in the traffic graphs include your own views? What about the view of contributors?
Thanks for getting in touch! Yes, the numbers include everyone's
views including repository owners and contributors. There's no way to
filter this information at the moment, but I can definitely add that
as a feature request for the team to consider.
Hope that answers your question - thanks!
So it does include your own views, but they might add the option to filter it later.
It looks like this behavior has changed, and now the traffic by the repository owner's views does not count when the owner is logged in.
A recent support question asked this, among others, and received the following reply from a member of staff:
My visit to my repository also count as a visit?
No, viewing your own repository while signed in doesn’t count towards this data.
I have checked that his holds by checking one of my repositories: the graph shows no views even on days when I visited the repository several times.
It is latest update as on 22nd Dec 2021 from GIT support that it is still recording owner's own views on owner's repository
From what I have experienced, as of November 2021, it does count the owner as a viewer. It is unclear as to why it counts as a unique viewer.
To be specific, I have seven repositories in GitHub, to which all of them have been inactive. On the 8th of November, 2021, I decided to check the traffic from all of them. Besides the portfolio, none of them gained traffic. The next day, all of them from yesterday gained traffic. Coincidence? No.
Yep, it appears that Github counts your own visits to your repositories too. In this image, the "Traffic' page has 8 views from 1 visitor. Given that, the Traffic page is available only to the owner of the repository, you can deduct that Github counts your own visits too.
Im using Jira with Bitbucket, and I wonder - can I somehow store info about that one or more revisions are related to some ticket, without writing ugly prefixes like ABC-123 in commit-messages?
The only other solution is to login to JIRA UI and create an issue link to the commit page in Bitbucket.
Obviously, this is somewhat more work than just adding ABC-123 in the commit.
Short answer: not really
The problem is that most version control systems don't allow you to store extra structured data related to a commit. The least common denominator is the commit message, so it tends to get used for all kinds of logically separate data, e.g. JIRA issue keys, change the status directions etc. The git notes feature might be used for this.
I need an index-page, that shows links to all gitHub repositories.
I think that is the reason, why many repos are not found by crawlers like the Waybackmachine
I think if there was such a site with a high ranking, they would start crawling it
The developer site sais, there is an Api for getting all repos
Warning: GitHub hosts a huge number of repositories. You'll have to take this into account when designing your index.
I can think of a few options:
The legacy GitHub search API. You'll have to cope with the API rate limit though.
This StackOverflow answer could be a good start to get a rough grasp of the number of repos per language.
Leveraging the GitHub Archive project which records the public GitHub timeline. (Note: As the project only exposes events back from February 12, 2011, you won't get any data about repositories showing no activity since this date.)