-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: don't limit commit-graph to 100 commits #832
Comments
I will look into this. There is some points to consider:
I think my first approach would be something like fossil timeline: http://fossil-scm.org/index.html/timeline you can paginate by clicking "older", and user can set how many commits you want. |
@kjellkvinge, I love the Fossil timeline visualization. The graphics look so much more "orderly" than the current commitgraph in gitea. As you pointed to it, I wonder whether getting that type of visualization would be easy/possible/difficult/out-of-the-question? |
Pagination is required. But we can scroll-load the next page... |
I completely agree with @bkcsoft. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. You can re-open it if needed. |
Pull request commithgraph / timeline #428 adds a very useful graphical representation of the relationship between commits (and basically branches), but the current implementation is limited to the most recent 100 commits. Ideally, when scrolling down, the next commits should be added to the graph. Alternatively, paging could also be used (although the resulting graph doesn't give as good of an overview).
While at it, allowing to specify the ordering of the commits would be useful (switching between --date-order and --topo-order).
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: