inconsistencies in git-hash-based links between organizations #25

New Issue

Bastien Montagne · 2023-02-13T11:37:45+01:00

Bastien Montagne commented

2023-02-13 11:37:45 +01:00

Task #104582 (#104582) on blender/blender has a git-hash link to commit #e8805a1a3f which links to https://projects.blender.org/blender/blender/commit/e8805a1a3ff.

However, #e8805a1a3f exists in a different fork, https://projects.blender.org/angavrilov/blender/commit/e8805a1a3ff, and not in blender/blender.

I don't think we can expect gitea to find references to tasks of commits across repositories and forks, but at the very least it should not present a commit in a organization/repo where it does not exists.

Note:
One can create a cross-reference to issues like that: blender/blender#104582 (blender/blender#104582).
But it does not seem to work for commits: angavrilov/blender#e8805a1a3ff (angavrilov/blender#e8805a1a3ff).

Task #104582 ([#104582](https://projects.blender.org/blender/blender/issues/104582)) on `blender/blender` has a git-hash link to commit #e8805a1a3f which links to https://projects.blender.org/blender/blender/commit/e8805a1a3ff. However, #e8805a1a3f exists in a different fork, https://projects.blender.org/angavrilov/blender/commit/e8805a1a3ff, and not in `blender/blender`. I don't think we can expect gitea to find references to tasks of commits across repositories and forks, but at the very least it should not present a commit in a organization/repo where it does not exists. > Note: > One can create a cross-reference to issues like that: `blender/blender#104582` (blender/blender#104582). > But it does not seem to work for commits: `angavrilov/blender#e8805a1a3ff` (angavrilov/blender#e8805a1a3ff).

Bastien Montagne commented

2023-02-13 11:38:52 +01:00

@JulianEisel

Sybren A. Stüvel commented

2023-02-13 14:47:53 +01:00

for commits use @: angavrilov/blender@e8805a1a3f

for commits use @: angavrilov/blender@e8805a1a3ff

Brecht Van Lommel commented

2023-02-13 16:32:35 +01:00

After discussion with others involved in the Gitea migration, we are not planning to track general Gitea bugs ourselves unless they are critical bugs that block us from doing something. Otherwise we just end up replicating a part of the Gitea bug tracker. So this should be reported to the Gitea project instead.

Things can be added to the list of feature requests in #12 and #13 if they slow down your workflow.

After discussion with others involved in the Gitea migration, we are not planning to track general Gitea bugs ourselves unless they are critical bugs that block us from doing something. Otherwise we just end up replicating a part of the Gitea bug tracker. So this should be reported to the Gitea project instead. Things can be added to the list of feature requests in #12 and #13 if they slow down your workflow.

Brecht Van Lommel added the

bug

label 2023-02-13 16:32:59 +01:00

Bastien Montagne commented

2023-02-13 17:26:07 +01:00

Done https://github.com/go-gitea/gitea/issues/22894

Bastien Montagne closed this issue

2023-02-13 17:26:07 +01:00

Sign in to join this conversation.