While the developer can use /sql-run to detect the committed code, there is no way to preview the effect of the code until it is detected.Even if the submission is successful, there is still a barrier to participation for the vast majority of people.

We have a lot of diagrams written in UML format and we can render them with Hypertrons too. But if the UML file is edited from a PR, we can not easily check whether it is as expected or not.

For UML files in PR, maybe we can provide a component to render them in PR and comment back to check.

Now we already have the activity-repo-top SQL component, but we still don't add the text into the template file, so we need to add to report template to describe the SQL and show the result.

https://www.x-lab.info/github-analysis-report/#/data

This link is invaild. :(

Weekly Report of github-analysis-report

This is a weekly report of github-analysis-report. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 0 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report/blob/master/CONTRIBUTING.md .

Like Wuhan2020 project, I think we can also use Slack as the IM tool for collaberation, and an independent workspace is mroe suitable.

Any suggestions ?

Weekly Report of github-analysis-report

This is a weekly report of github-analysis-report. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 0 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report/blob/master/CONTRIBUTING.md .

As we use Clickhouse to finish all queries and the database is inside the campus. a solution about how to visit internal service from Internet is essential.

There are two approaches for this issue:

• Expose a public service to Internet, which means need to fill an application.
• If the internal machine has a stable network to visit Internet, we can use proxy like smee.io to forward requests to it.

The first one is preferred because according to current situation the visit to Internet is not stable and if the network broke, it is hard to reset the service without restart the app.

I think we need to a simple data mirroring for developers who want to test the SQL statement on their PC.
As @TechQuery said, that can also help us with simple automated tests.
I hope to use a script and a simple configuration file to connect the local project and the mirroring.
Thanks for your time.

Just like the activity report for global projects, we also need a SQL component to generate activity data for all projects in case study. May also include the count number of comments, issues, PRs and developer count.

Although we have a workflow in appendix of Workflow, I think the workflow should be placed in Contributing Guide and explained with text to help participants better understand the process of submitting PR especially with SQL files.

Maybe a specific case can help better.

Weekly Report of github-analysis-report

This is a weekly report of github-analysis-report. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 0 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report/blob/master/CONTRIBUTING.md .

The data description document need to be added, which may include data source, database, data structure, basic SQL guide and other things about the data to help developers understand how to use data.

We need a comprehensive contributing guide for developers both in English and in Chinese.

The contributing guide can be like a traditional one but with the custom workflow of this project.

I think we can make some minor changes for top repos and developers:

• The repo name is not determinate for every query as anyLast is indeterminate according to clickhouse docs, we may change to anyHeavy which will return most frequent name for each repo and user.
• repo_id can be removed from the result.
• We can add more details into the repos' result, like language information.
• We can also add more details into the repos and developers' result, like LOC additions, deletions and commits count from pull request.

We need an auto update report component for hypertrons to make sure we can automatically update the report by data and template regularly.

As CONTRIBUTORS file shows, @sunshinemingo is quite active for past two weeks in project discussion, I propose @sunshinemingo to be our new committer to approve PR.

In Apache Anual Report, there are a lot of fun stuffs. Like a working hour slots graph to show activities in a day.

We can also add this to the report to show events distribution all over the world.

Weekly Report of github-analysis-report

This is a weekly report of github-analysis-report. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 0 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report/blob/master/CONTRIBUTING.md .

I think we need to add a stable sort algorithm for developers if the score is same to avoid massive move of followers everyday. Maybe the socre can be sorted alphabetically by name.

We may need a Hypertrons component for case study report.

The files in the repo may include:

• A folder contains all case study files include a report template and a config file for the case study.
• A folder contains all SQL components for all case study report under SQL folder.

And the component should run every day to update all case study reports and create PR to submit all the reports. May refer to https://github.com/X-lab2017/github-analysis-report/tree/master/.github/hypertrons-components/auto_update_report .

Weekly Report of github-analysis-report-2020

This is a weekly report of github-analysis-report-2020. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 12 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report-2020 encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report-2020 team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report-2020/blob/master/CONTRIBUTING.md .

For now, we have sql, manifest.json and post-processor.js for every SQL component, the configs in manifest.json file is used to render SQL query and report text.

But as the template engine(pope) we use is not powerful enough to handle complex data structure, so we may need a pre-processor.js file to process the configs to strings that can be directly used by SQL renderer which will give us more ability to form complex SQL.

Related to #251

At start, I commit Apache 2.0 License for the project, I think it is OK for the code part which is the hypertrons workflow components and post processor for SQL components.

But we should also determine what License we use for the docs part which is the report, I think we should protect the report quite carefully, maybe one of CC-BY 4.0 can be considered.

WDYT?

People who "watch" this project may be overwhelmed by GitHub emails, for most conversations happen in the repository is about the analysis-report-bot updating the contributor .md file and merging PRs.

I think we should build a feasible solution to control the emails sent by bot, decrease redundant information so subscribed users can only focus on what's new in the project performed by "real people", and these new updates won't be rushed away by emails sent by bot.

Now we already have a global rank list for top 10 repos, but we still need a similar component to generate global developers rank list too. We may also use the traditional activity calculation method and add the result into the main report.

Weekly Report of github-analysis-report

This is a weekly report of github-analysis-report. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 2 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report/blob/master/CONTRIBUTING.md .

We need to support /sql-run command, which will trigger a pull request SQL request from Hypertrons and return the result by comment.

Weekly Report of github-analysis-report

This is a weekly report of github-analysis-report. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 0 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report/blob/master/CONTRIBUTING.md .

We need a SQL component to calculate all issues and PRs for every project in case study. We may also support multiple return values for SQL components(should be discussed).

I add a word cloud render into report and it works fine on the web site.

But we still need to add more description about the word cloud like what is the data source and how to implement.

As case study hypertrons component has been merged(#255 ) we need to add all repo id list to case study folders.

The format should be like ASF config (case-study/ASF/manifest.json).

• ASF
• CNCF
• LF AI & Data
• Wuhan2020

Weekly Report of github-analysis-report-2020

This is a weekly report of github-analysis-report-2020. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 7 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report-2020 encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report-2020 team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report-2020/blob/master/CONTRIBUTING.md .

Currently we only have activity score for top 10 repos, we may also add total issue count, pr count, comment count and review count and active developers' count for every repo too.

This is a test issue.

We need a basic framework and file structure of this report project.

We need a document to describe the workflow for commiting other files(excluding sql). Such as if the PR contains docs in the title, the bot will add area/document label.

Weekly Report of github-analysis-report

This is a weekly report of github-analysis-report. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 0 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report/blob/master/CONTRIBUTING.md .

Weekly Report of github-analysis-report

This is a weekly report of github-analysis-report. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 0 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report/blob/master/CONTRIBUTING.md .

Weekly Report of github-analysis-report

This is a weekly report of github-analysis-report. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 11 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report/blob/master/CONTRIBUTING.md .

A diagram of how the relationship works describing the CNCF.

As in GitHub report 2019 we also need to add Chinese projects analysis. In GitHub report 2019 we use a text file to indicate all main Chinese projects on GitHub to generate the report, we may use the same way to collect all Chinese projects.

But we may need to use repo_id rather than repo_name instead in case name change during 2020, and organization should be supported too.

Weekly Report of github-analysis-report

This is a weekly report of github-analysis-report. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 0 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report/blob/master/CONTRIBUTING.md .

Weekly Report of github-analysis-report

This is a weekly report of github-analysis-report. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 0 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report/blob/master/CONTRIBUTING.md .

Weekly Report of github-analysis-report-2020

This is a weekly report of github-analysis-report-2020. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 22 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report-2020 encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report-2020 team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report-2020/blob/master/CONTRIBUTING.md .

[description]
I want to know the data description and I got the 404 error after clicking the "data" link. In addition, the same problem occured if i switch to "data description" in "Contributing Guide" page.
[Snapshot]

Weekly Report of github-analysis-report

This is a weekly report of github-analysis-report. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 7 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report/blob/master/CONTRIBUTING.md .

We need a document to describe the architect of the infrastructure and workflow of the project, like hypertrons, database and etc.

We can use plantuml files to render the diagram, hypertrons may provide render ability of this kind of files.

Weekly Report of github-analysis-report

This is a weekly report of github-analysis-report. It summarizes what have changed in the project during the passed week, including pr merged, new contributors, and more things in the future.

Repo Overview

Basic data

Baisc data shows how the watch, star, fork and contributors count changed in the passed week.

Issues & PRs

Issues & PRs show the new/closed issues/pull requests count in the passed week.

PR Overview

Thanks to contributions from community, 0 pull requests was merged in the repository last week. They are:

Code Review Statistics

github-analysis-report encourages everyone to participant in code review, in order to improve software quality.
This robot would automatically help to count pull request reviews of single github user as the following every week. So, try to help review code in this project.

New Contributors

We have no new contributors in this project this week.
github-analysis-report team encourages everything about contribution from community.
For more details, please refer to https://github.com/X-lab2017/github-analysis-report/blob/master/CONTRIBUTING.md .

The report template is quite simple now, we can add more details into it, refer to GitHub Analysis Report 2019 and may involve several SQL components development.