Feature request: Buttons for "next commit" and "former commit" in commit view #1673

New Issue

GiteaMirror · 2025-11-02T04:09:09-06:00

GiteaMirror commented

2025-11-02 04:09:09 -06:00

Originally created by @kernie on GitHub (Apr 3, 2018).

Gitea version (or commit ref): 1.4.0
Git version:
Operating system:
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

When opening the commit view to see code changes I would be happy to see somewhere a button which leads to the "next commit" and one that goes to the "former commit".

Reading thru commit changes involves too much clicks at the moment.

Thank you for this great software development tool!
Maarten
...

Screenshots

Originally created by @kernie on GitHub (Apr 3, 2018).  - Gitea version (or commit ref): 1.4.0 - Git version: - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description When opening the commit view to see code changes I would be happy to see somewhere a button which leads to the "next commit" and one that goes to the "former commit". Reading thru commit changes involves too much clicks at the moment. Thank you for this great software development tool! Maarten ... ## Screenshots

GiteaMirror added the type/enhancement issue/stale labels 2025-11-02 04:09:09 -06:00

GiteaMirror closed this issue

2025-11-02 04:09:09 -06:00

GiteaMirror commented

2025-11-02 04:09:09 -06:00

@vijfhoek commented on GitHub (Jun 4, 2018):

Note that the "former commit" button you mention already exists in the form of a "parent" button:

However, implementing the "next commit" button, or in git terminology browsing to a child commit, would be fairly more involved, considering a commit could have several children in case of branching.

I am not that well-versed in this part of git, but I can imagine it'd be fairly involved and maybe even quite an expensive operation, let alone the UI work needed to display all those children.

@vijfhoek commented on GitHub (Jun 4, 2018): Note that the "former commit" button you mention already exists in the form of a "parent" button: ![image](https://user-images.githubusercontent.com/345785/40945978-756a7d9a-685b-11e8-8567-d82c34b64d82.png) However, implementing the "next commit" button, or in git terminology browsing to a child commit, would be fairly more involved, considering a commit could have several children in case of branching. I am not that well-versed in this part of git, but I can imagine it'd be fairly involved and maybe even quite an expensive operation, let alone the UI work needed to display all those children.

GiteaMirror commented

2025-11-02 04:09:10 -06:00

@stale[bot] commented on GitHub (Jan 24, 2019):

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.

@stale[bot] commented on GitHub (Jan 24, 2019): 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.

GiteaMirror commented

2025-11-02 04:09:10 -06:00

@stale[bot] commented on GitHub (Feb 18, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 18, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 11:59:37 -06:00

[PR #1673] [CLOSED] Update Gitea SDK to latest version #15986

Sign in to join this conversation.