๐ŸŽซ Let tag crowd do your GitHub {repo}rting โ˜๏ธ

adriens - Dec 27 '22 - - Dev Community

โ” About

Have you ever been challenged to explain/report within a few seconds what has been done on a project ?... and most important where did you actually put your efforts.

Based on the fact that your highly us issues to manage any task on your project and has achieved some automation around them, then it's a treasure that only asks to be shown.

โ˜๏ธ Let the clouds help

As part of our activities reporting we could produce some very useful content that help understand a project activity within less than a second... and even perform some classification.

๐Ÿ“Š Output samples

๐Ÿง‘โ€๐Ÿ’ผ Division activity

Assuming you want to have a look at the issues accross all your repos, here is what we got:

Image description

๐Ÿงฐ Maintenance milestone (Angular App)

We also wanted to focus on a specific project. You can immediately see that activity was focused on Angular upgrade:

Image description

๐Ÿ›ค๏ธ Quarkus app (standard maintenance phasis)

Sometimes you have running projects with few or no enhancements, this is what you can immediately see:

Image description

๐Ÿ’ฆ Better understand stack and efforts

On this one, we got a glance on what has been achieved and about the stack we used:

Image description

๐Ÿ’ฐ Conclusion

These charts at first looked futile but as soon as we saw them, we found them profoundly useful as they make it possible to

explain within a single image what kind of activity has been achieved, under which proportion and with which stack.

Finally it really worth a thousand mails with explanations... and it's fully driven by real code activity.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .