You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The original proof-of-concept for the Peloton was a custom web page. This included two graphs:
Number of items closed each week, for the last 5 weeks, split by repo
Total number of open items each week, for the last 5 weeks, split by repo
These graphs could still be generated from the Pandas DataFrame that is used during the automated querying and updating. The images could be added as drafts, set to appear in particular views. The benefit vs effort here is unclear, I am recording since it is a feature we have lost by transferring to a Github project.
The text was updated successfully, but these errors were encountered:
If we were to go for this I reckon it would be simplest to store the graphs as actual issues in this repo, since they will then be automatically included in the Peloton project. Would be workable to give them some property ensuring they appear at the top of sorted lists e.g. an updated date far in the future.
The original proof-of-concept for the Peloton was a custom web page. This included two graphs:
These graphs could still be generated from the Pandas DataFrame that is used during the automated querying and updating. The images could be added as drafts, set to appear in particular views. The benefit vs effort here is unclear, I am recording since it is a feature we have lost by transferring to a Github project.
The text was updated successfully, but these errors were encountered: