Skip to content

feature request: link issues to commits #7832

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

Open
steveschow opened this issue Aug 12, 2019 · 4 comments
Open

feature request: link issues to commits #7832

steveschow opened this issue Aug 12, 2019 · 4 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented

Comments

@steveschow
Copy link

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.

@lafriks
Copy link
Member

lafriks commented Aug 12, 2019

I think there is already PR for this #3695

@steveschow
Copy link
Author

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.

@lunny
Copy link
Member

lunny commented Aug 14, 2019

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

@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Oct 13, 2019
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Oct 13, 2019
@stale stale bot removed the issue/stale label Oct 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented
Projects
None yet
Development

No branches or pull requests

3 participants