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 current commit activity display compares commits in the last (n) months to the previous (n) months. This statistic is valuable for understanding trends in commit activity over time. However, extending this timeframe to cover a more extended period without overloading the dashboard would be beneficial.
Proposed Solution
Implement a feature that allows users to select custom timeframes for commit activity comparison (e.g., last six months vs. previous six months, last 12 months vs. previous 12 months, etc.).
Ensure that the extended commit activity stats do not clutter or overload the dashboard by optimizing the display or providing options for users to toggle between different timeframes.
Benefits
Provides users with more in-depth insights into commit activity trends.
Enables users to analyze commit activity over custom timeframes.
Maintains a clean and user-friendly dashboard while adding more detailed statistics.
The text was updated successfully, but these errors were encountered:
We cannot support arbitrary "custom time range" we are pre-computing selected set of metrics and then UI only selects from already calculated values, we can eventually add a new set of possible selections - you would need to list them and eventually add a drop down allowing you to select one of them while hiding other ones. We need to keep this behaviour (pre-calculating all, not computing anyting on the fly from the raw data) to keep DevStats fast.
Also this kind of modification needs approval from @caniszczyk including approval of additional time-ranges and approach with drop-down to allow choosing which one should be displayed.
Issue Description
The current commit activity display compares commits in the last (n) months to the previous (n) months. This statistic is valuable for understanding trends in commit activity over time. However, extending this timeframe to cover a more extended period without overloading the dashboard would be beneficial.
Proposed Solution
Benefits
The text was updated successfully, but these errors were encountered: