Skip to content

Confirm org-wide issue forms and the team listing with the frontend owner #12

Open

Description

@zaebee

Follow-up of #8.

  • What remains — two questions for @ReD1KC: (1) the org-default .github/ISSUE_TEMPLATE/config.yml sets blank_issues_enabled: false, and no repository has its own templates, so blank issues are now off in the web UI of every repo, owner-web, booking-web and rider-app included (gh issue create --body is unaffected); (2) is it fine to be listed as Frontend in the public profile.
  • Why — both affect a colleague's repositories or name; docs: refresh the org profile and add community health files #8 merged without asking.
  • When — next conversation with him.
  • Done when — answers recorded here; if either is a no, a PR flips blank_issues_enabled or removes the row.

Activity

  1. added
    tailLoose end left by a finished task: what remains, why, when to check
    questionFurther information is requested
    on Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requestedtailLoose end left by a finished task: what remains, why, when to check

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions