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

Closed
opened 2023-02-13 11:37:45 +01:00 by Bastien Montagne · 4 comments

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).
@JulianEisel

for commits use @: angavrilov/blender@e8805a1a3f

for commits use @: angavrilov/blender@e8805a1a3ff

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
Type
Bug
label 2023-02-13 16:32:59 +01:00
Done https://github.com/go-gitea/gitea/issues/22894
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/blender-projects-platform#25
No description provided.