Problem
The issues gathered by the repo don't have the date the Issue was created. This means that the user don't have an easy way to check how old the issue is. This can provide a better understanding combined with the number of comments it has if the issues is valuable for them or not.
Solution
- Collect the issue date
- Add it to the README template
- Add it to the output file.
Context
GitHub API has bothcreated_at and updated_at. Probably adding both is the logical move, since it can give more context to the contributor.
Ideas
Probably adding it into IssueManager.extract_issue_data is the most straightforward solution. A helper function may or may not be needed.
Happy to discuss options and different points of view onthis one if neded!
Problem
The issues gathered by the repo don't have the date the Issue was created. This means that the user don't have an easy way to check how old the issue is. This can provide a better understanding combined with the number of comments it has if the issues is valuable for them or not.
Solution
Context
GitHub API has both
created_atandupdated_at. Probably adding both is the logical move, since it can give more context to the contributor.Ideas
Probably adding it into
IssueManager.extract_issue_datais the most straightforward solution. A helper function may or may not be needed.Happy to discuss options and different points of view onthis one if neded!