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

create `forge-` groups and inherited membership for the last remaining groups

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

    • 2
    • Forgejo 2026 Sprint 01

      Original reporter: rlerch@redhat.com

      The issue:

      Before we started using group inherticance to clean up the forge groups, we permitted some teams to not follow the naming scheme.

      now we can do the group inheritance, we need to make these groups, and update the group mapping. The teams will not notice a difference.

      these are the ones needing updating and new groups:

      • `"council": {"council":["Members"]}

        ,`

      • `"server-wg": {"server":["Members"]}

        ,`

      • `"qa-tools-sig": {"quality":["Members"]}

        ,`

      • `"qa-admin": {"quality":["Owners"]}

        ,`

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

                Created:
                Updated:
                Resolved: