Skip to content

Commit

Permalink
doc(yegor256#227): fetch topics too, document /steps in steps/README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
h1alexbel committed Apr 15, 2024
1 parent 874f45d commit 8d5d963
Show file tree
Hide file tree
Showing 2 changed files with 17 additions and 1 deletion.
15 changes: 15 additions & 0 deletions steps/README.md
@@ -0,0 +1,15 @@
### How it Works?
The entire process of gathering metrics from GitHub repos consists of these
steps:
* **Discovering**. Get the list of repos from GitHub and then create directories for them.
* **Polishing**. Delete directories that don't exist in the list of required repositories.
* **Unregistering**. Clean directories from the CSV register if their clones are absent.
* **Cloning**. In this step we run `git clone` on found repositories.
* **JPEEK**. Here, we build those gathered repositories and run
[jpeek](https://github.com/cqfn/jpeek) on them.
* **Filtering**. Is where we apply [all the filters](https://github.com/yegor256/cam/tree/master/filters)
in order to get rid of irrelevant classes (such as `*Test`, `*ITCase`, invalid
files and so on). Whole filtering process will be printed in the final report,
you can check it [here](http://cam.yegor256.com/cam-2024-03-02.pdf).
* **Measuring**. We calculate metrics for each file using these [metrics](https://github.com/yegor256/cam/tree/master/metrics).
* **Aggregating**. Finally, we aggregate all metrics in summary CSV files.
3 changes: 2 additions & 1 deletion steps/discover-repos.rb
Expand Up @@ -88,7 +88,8 @@
created_at: i[:created_at].iso8601,
size: i[:size],
open_issues_count: i[:open_issues_count],
description: i[:description]
description: i[:description],
topics: i[:topics]
}
puts "Found #{i[:full_name].inspect} GitHub repo ##{found.count} \
(#{i[:forks_count]} forks, #{i[:stargazers_count]} stars)"
Expand Down

0 comments on commit 8d5d963

Please sign in to comment.