Sometimes it's useful to store issues / PRs / etc if you want to analyze them later. This wouldn't be useful for generating changelogs (since you want to make sure you've got the latest activity for those) but it could be useful for generating datasets that one can analyze with, e.g., https://github.com/choldgraf/jupyter-activity-snapshot.
Perhaps this could keep a cache folder in ~/data_github_activity that would keep this data over time. A few points / questions:
- It could either be a single CSV files for all the data, a couple CSV files for different types of data (e.g.,
issues.csv, prs.csv, comments.csv), or sub-folders for different github orgs/repos
- When new data is downloaded, it could do simple joins on these CSV files and then drop the duplicates based on the unique ID of that item
@consideRatio what do you think about this? Useful or unnecessary complexity?
Sometimes it's useful to store issues / PRs / etc if you want to analyze them later. This wouldn't be useful for generating changelogs (since you want to make sure you've got the latest activity for those) but it could be useful for generating datasets that one can analyze with, e.g., https://github.com/choldgraf/jupyter-activity-snapshot.
Perhaps this could keep a cache folder in
~/data_github_activitythat would keep this data over time. A few points / questions:issues.csv,prs.csv,comments.csv), or sub-folders for different github orgs/repos@consideRatio what do you think about this? Useful or unnecessary complexity?