MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 146 Pull Requests Releases 96 Wiki Activity

feat: cross-reference issues across repos within an org #224

New Issue
Open
opened 2026-05-26 20:23:47 +00:00 by jmiller · 0 comments
jmiller commented 2026-05-26 20:23:47 +00:00
Owner
Copy Link
Copy Source

Summary

Enable cross-repository issue references within an organization, so that mentioning OtherRepo#42 or MokoConsulting/OtherRepo#42 in an issue or PR comment automatically creates a bidirectional link visible on both issues.

Motivation

Work across MokoConsulting repos is highly interconnected (e.g. MokoGitea changes affect moko-platform, MokoWaaS, etc.). Currently, cross-repo references are plain text with no backlinks. Developers have to manually search for related issues across repos.

Proposed Behavior

  1. Short syntax within org: RepoName#123 resolves to an issue in the same org
  2. Full syntax: Org/Repo#123 works as it does today but adds backlinks
  3. Backlinks: When issue A references issue B, issue B shows a timeline entry like "Referenced by MokoGitea#220"
  4. Hover preview: Hovering a cross-repo reference shows the issue title and status
  5. Scope: Only repos the viewer has read access to show previews; others show as plain text

References

Opened by Claude Code on behalf of @jmiller

## Summary Enable cross-repository issue references within an organization, so that mentioning `OtherRepo#42` or `MokoConsulting/OtherRepo#42` in an issue or PR comment automatically creates a bidirectional link visible on both issues. ## Motivation Work across MokoConsulting repos is highly interconnected (e.g. MokoGitea changes affect moko-platform, MokoWaaS, etc.). Currently, cross-repo references are plain text with no backlinks. Developers have to manually search for related issues across repos. ## Proposed Behavior 1. **Short syntax within org**: `RepoName#123` resolves to an issue in the same org 2. **Full syntax**: `Org/Repo#123` works as it does today but adds backlinks 3. **Backlinks**: When issue A references issue B, issue B shows a timeline entry like "Referenced by MokoGitea#220" 4. **Hover preview**: Hovering a cross-repo reference shows the issue title and status 5. **Scope**: Only repos the viewer has read access to show previews; others show as plain text ## References - GitHub cross-repo references: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls - Gitea already supports same-repo `#123` references with backlinks; this extends to cross-repo within an org --- *Opened by Claude Code on behalf of @jmiller*
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
Type Feature
Status —
Priority —
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea#224
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?