github / github/app

Add configuration to include org/owner name in project's default display name

オープン
#2,513 コメント 10 件 リアクション 0 件 担当者 0 名 GitHub で見る
主要言語
言語のデータがありません
スター
2.1k
フォーク
153
PR マージ指標
30日以内にマージされた PR はありません

説明

### Feature summary

Add a setting to optionally use the full `owner/repo` name as a project's default display name in the Copilot app.

### What problem are you trying to solve?

Projects currently display only the repository name (e.g. `app`), dropping the owner/org. When a user works across multiple organizations that have same-named repositories (e.g. `github/app` vs `acme/app`), the sidebar shows ambiguous, duplicate-looking project entries. There is no built-in way to disambiguate them short of manually renaming each project.

### Proposed solution

Provide a configuration option (global preference, and/or per-project) that controls how a project's default display name is derived:

- Default (current): repo name only — `app`
- New option: full `owner/repo` — `github/app`

When enabled, newly created projects would default to the `owner/repo` display name. Ideally this could also be applied to existing projects. Manual project renaming should still override the derived name.

### Workflow impact

Anyone managing projects across multiple orgs/owners with overlapping repo names benefits. It removes ambiguity in the project list/sidebar, reduces the need for manual renaming, and makes it clear which org a session belongs to at a glance.

### Installation context

N/A — this is a Copilot app project-display/config request, not tied to a specific install scope.

### Additional context

The full repository (`owner/repo`) is already stored internally per project (`project_github_repo`); this request is about surfacing the owner in the default display name via a configurable option.

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

Start by tracing the project default display-name derivation and the existing project_github_repo value. Determine where global or per-project configuration and manual rename precedence belong, then verify behavior for new projects, existing projects if supported, and duplicate owner/repo names with focused tests.

索引モデルが issue の本文から書いたものです。

評価

領域
desktop
issue の種類
機能追加
難易度
4/5
見積もり時間
3〜5日
活発さ
静か
明瞭さ
おおむね明確
初心者へのやさしさ
52/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。