You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[ ] In the `_config_automation.yml` file, make sure that `refresh-citations` is set to "yes".
64
-
-[ ] Optionally, if you are saving data to google, specify a googlesheet ID in `citation_googlesheet` if you'd like the citation data to be saved to. This will only be relevant if you've set `data_dest` to `google`.
65
-
66
-
67
-
## Customizing Citation Data
68
-
69
-
In order to customize the data you are downloading from Google Scholar you can modify the
70
-
`refresh-scripts/refresh-citations.R` script in your repository.
71
-
72
-
You can take a look at the [`metricminer` R package documentation](https://hutchdatascience.org/metricminer/articles/getting-started.html) for more details about the functions and what is possible.
73
-
74
-
If you have a metric need that is not currently fulfilled by `metricminer` or `metricminer-dashboard` we encourage you to [file a GitHub issue with us and let us know about your new feature idea (or bug report)](https://github.com/fhdsl/metricminer/issues/new/choose).
ggplot(aes(x = repo_name, y = total_contributions)) +
35
-
geom_bar(stat = "identity", fill = "lavender") +
29
+
github_overall %>%
30
+
ggplot(aes(x = repo_name, y = total_contributions)) +
31
+
geom_bar(stat = "identity", fill = "lavender") +
36
32
theme_classic()
37
33
```
38
34
39
-
Views of a GitHub Repository over time
35
+
Views of a GitHub Repository over time
40
36
41
37
```{r echo = FALSE, hide = TRUE, message=FALSE}
42
-
github_timecourse %>%
43
-
ggplot(aes(x = timestamp, y = count_views, fill = repo, color = repo)) +
44
-
geom_line(stat = "identity") +
45
-
theme_classic() +
38
+
github_timecourse %>%
39
+
ggplot(aes(x = timestamp, y = count_views, fill = repo, color = repo)) +
40
+
geom_line(stat = "identity") +
41
+
theme_classic() +
46
42
ylab("date")
47
43
```
48
44
49
-
## Data information
45
+
## Data information
50
46
51
47
Data information for `github overall data`:
52
48
53
-
-`num_forks` shows the number of times this repo has been forked. NA means it has never been forked.
49
+
-`num_forks` shows the number of times this repo has been forked. NA means it has never been forked.
54
50
-`num_contributors` how many people have contributed to this repo
55
51
-`num_stars` how many people have starred this repo?
56
-
-`health_percentage` what percentage of ["good software health" items as described by GitHub](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories) does this repo have?
52
+
-`health_percentage` what percentage of ["good software health" items as described by GitHub](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories) does this repo have?
57
53
58
54
```{r, message=FALSE}
59
55
knitr::kable(github_overall)
@@ -62,36 +58,11 @@ knitr::kable(github_overall)
62
58
Data information for `github timecourse`:
63
59
64
60
-`timestamp` shows the date the counts correspond to
65
-
-`count_clones` tells the number of clones made on this day. NAs generally indicate no one cloned the repository that day.
61
+
-`count_clones` tells the number of clones made on this day. NAs generally indicate no one cloned the repository that day.
66
62
-`unique_clones` tells how many people did these clones come from? NAs generally indicate no one cloned the repository that day.
67
63
-`count_views` how many views did the repo get on this day? NAs generally indicate no one viewed the repository that date
68
64
-`unique_views` how many people were those views from? NAs generally indicate no one viewed the repository that date
69
65
70
66
```{r, message=FALSE}
71
67
knitr::kable(github_timecourse)
72
68
```
73
-
74
-
## Setting up GitHub
75
-
76
-
At this point you should already have your GitHub authorization set up for your metricminer dashboard by having [followed the instructions above.](#setting-up-your-dashboard-repository).
77
-
78
-
In the `_config_automation.yml` you will need to specify items in the GitHub section.
-[ ] In the `_config_automation.yml` file, make sure that `refresh-github` is set to "yes".
87
-
-[ ] In `github_repos` of your `_config_automation.yml`, specify the names of the repositories you'd like to collect data from in `github_repos`. Make sure it includes the `owner/repository` e.g. `fhdsl/metricminer` not just `metricminer`. Commas need to separate the repositories. Delete the example repositories we put there.
88
-
-[ ] Optionally, if you are saving data to Google, specify a googlesheet ID in `github_googlesheet` you'd like the GitHub data to be saved to. This will only be relevant if you've set `data_dest` to `google`.
89
-
90
-
## Customizing GitHub Data
91
-
92
-
In order to customize the data you are downloading from GitHub you can modify the
93
-
`refresh-scripts/refresh-github.R` script in your repository.
94
-
95
-
You can take a look at the [`metricminer` R package documentation](https://hutchdatascience.org/metricminer/articles/getting-started.html) for more details about the functions and what is possible.
96
-
97
-
If you have a metric need that is not currently fulfilled by `metricminer` or `metricminer-dashboard` we encourage you to [file a GitHub issue with us and let us know about your new feature idea (or bug report)](https://github.com/fhdsl/metricminer/issues/new/choose).
0 commit comments