inconsistencies in git-hash-based links between organizations #25
Labels
No Label
Service
Buildbot
Service
Chat
Service
Gitea
Service
Translate
Type
Bug
Type
Config
Type
Deployment
Type
Feature
Type
Setup
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-projects-platform#25
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@JulianEisel
for commits use @: angavrilov/blender@e8805a1a3f
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.
Done https://github.com/go-gitea/gitea/issues/22894