Usage: A user (e.g., a student) setting up an online report of their open-source coding work.
Steps:
Forks a provided repo (e.g., https://github.com/reposense/code-report) to own GitHub account
Updates a config file in the fork to specify repos contributed to, author names used in each repo
After committing the change, and CI run, the report is available for viewing (and can be linked from their resume, home page etc.)
A further optimization is to show each ramp for the time period in which there are relevant commits. i.e., in the ramp chart below, show the part in the red box only.
This means each ramp chart will have its own timeline, and we'll have to show the timeline for each ramp chart.
ckcherry23
commented
8 months ago
Usage: A user (e.g., a student) setting up an online report of their open-source coding work.
Steps:
https://github.com/reposense/code-report) to own GitHub accountA further optimization is to show each ramp for the time period in which there are relevant commits. i.e., in the ramp chart below, show the part in the red box only.
This means each ramp chart will have its own timeline, and we'll have to show the timeline for each ramp chart.