Uploaded image for project: 'Community Linux Engineering'
  1. Community Linux Engineering
  2. CLE-2964

Refactor internal APIs for public vs. private issue identity

SetAsigneesSync from "Extern...update-metadata-from-f...XMLWordPrintable

    • 5
    • Forgejo Deployment EOY, Forgejo 2026 Sprint 02

      Original reporter: nphilipp@redhat.com

      The issue:

      1. Story

      As a Forgejo developer,
      I want that I can succinctly express public or private issue identity,
      so that function calls and intermediary data structures are clear and concise.

      1. Acceptance Criteria
      • [ ] Internal APIs using issue IDs (integer numbers corresponding to DB primary keys) are converted to pointers to `Issue` structs.
      1. Background

      In many places in the code, numerical IDs of issues are used to identify them. With private issues stored in a separate table, the ID values don’t identify issues uniquely anymore. [Gusted commented in favor of this](https://codeberg.org/forgejo/design/issues/2#issuecomment-8405379) in the design ticket.

              Unassigned Unassigned
              cle_bot CLE bot
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: