feature request: link issues to commits #3766

Open
opened 2025-11-02 05:24:31 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @steveschow on GitHub (Aug 12, 2019).

I really like gitea and am considering to switchover from fossil for my SCM. One thing that fossil does that still keeps me there is that when I commit file changes, I can include the id# of an "issue" and fossil creates internal links between the issue and that commit. More than one commit can be linked to an issue. Then when looking at an issue, there is one click to see a list of all commits that have been done related to it, and because it displays a timeline also I can quickly diff between the first and the last commit to see essentially all the file changes related to that issue#.

Fossil could do it better, it still requires some poking around, but gitea can't really do it at all. I would really like to be able to associate a group of commits to a single issue# and then later on I can refer to that issue and see exactly what files were changed for it.

Originally created by @steveschow on GitHub (Aug 12, 2019). I really like gitea and am considering to switchover from fossil for my SCM. One thing that fossil does that still keeps me there is that when I commit file changes, I can include the id# of an "issue" and fossil creates internal links between the issue and that commit. More than one commit can be linked to an issue. Then when looking at an issue, there is one click to see a list of all commits that have been done related to it, and because it displays a timeline also I can quickly diff between the first and the last commit to see essentially all the file changes related to that issue#. Fossil could do it better, it still requires some poking around, but gitea can't really do it at all. I would really like to be able to associate a group of commits to a single issue# and then later on I can refer to that issue and see exactly what files were changed for it.
GiteaMirror added the issue/confirmed label 2025-11-02 05:24:31 -06:00
Author
Owner

@lafriks commented on GitHub (Aug 12, 2019):

I think there is already PR for this #3695

@lafriks commented on GitHub (Aug 12, 2019): I think there is already PR for this #3695
Author
Owner

@steveschow commented on GitHub (Aug 12, 2019):

how long ago was the pull request given? If it hasn't been merged in by now there must be some reason its not quite what they want. Anyway, here's a request for SOMETHING like that. That pull request looks like it added a lot of different things, I would have to install it and try it out to find out if it even does what I'm asking for.

@steveschow commented on GitHub (Aug 12, 2019): how long ago was the pull request given? If it hasn't been merged in by now there must be some reason its not quite what they want. Anyway, here's a request for SOMETHING like that. That pull request looks like it added a lot of different things, I would have to install it and try it out to find out if it even does what I'm asking for.
Author
Owner

@lunny commented on GitHub (Aug 14, 2019):

#3695 has been marked as 1.10, but it still depends on author's time.

@lunny commented on GitHub (Aug 14, 2019): #3695 has been marked as 1.10, but it still depends on author's time.
Author
Owner

@stale[bot] commented on GitHub (Oct 13, 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 (Oct 13, 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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3766