github / github/app

I ran into two usability problems in Copilot workspace sessions:

Open
#3,177 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
2.1k
Forks
153
PR merge metrics
No merged PRs in 30d

Description

I ran into two usability problems in Copilot workspace sessions:

1. Ignored files cannot be edited from the Files window
Files like app/etc/env.php are intentionally git-ignored because they configure the local environment. In Magento projects these files are essential for local development. The Files window/editor can hide or make ignored files read-only, which makes local environment setup harder than necessary. There should be a way to show and edit ignored local files, preferably with a clear warning that they are ignored/sensitive and should not be committed.

2. Changes window compares against master instead of the checked-out branch upstream
In a session checked out on a feature branch, the Changes window compares the branch against origin/master. That is not always useful. When working on an existing feature branch, I usually want to see only what changed locally after the last commit, or the difference between my local branch and origin/. Comparing everything to master shows the whole feature branch history and makes it hard to see my actual current changes.

---
| Field | Value |
| --- | --- |
| App version | 1.1.12 |
| OS | macOS 26.2.0 |
| Theme | Monochrome |
| Path | /chat |
| Tenure | Week 2 |

Contributor guide

Open the contributing guide

Research direction

Reproduce both reports in the Files and Changes windows using an ignored local file such as app/etc/env.php and a checked-out feature branch. Read the workspace session handling for file visibility/editability and branch comparison behavior; done means ignored files can be edited with a clear warning and Changes shows the selected branch's relevant local or upstream diff.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github
Domain
desktop, developer-experience
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.