Problem or use case

The Source Control panel currently uses a fixed group order: Changes, Staged Changes, then Untracked Files.

That order is useful because unresolved conflicts are assigned to the Changes area, so they stay near the top. However, the panel is also commit-oriented: the commit controls sit directly above the file list, and staged files are the files that will actually be committed.

Different users may reasonably prefer different workflows:

• Commit review workflow: Staged Changes, Changes, Untracked Files
• Conflict/change-first workflow: Changes, Staged Changes, Untracked Files
• Cleanup workflow: maybe Untracked Files earlier

A fixed order makes one workflow feel optimized and the others secondary.

Proposed solution

Add a setting to configure the Source Control group order.

The default can remain the current order to preserve existing behavior:

1. Changes
2. Staged Changes
3. Untracked Files

Users who prefer a commit-oriented panel could change it to:

1. Staged Changes
2. Changes
3. Untracked Files

Important constraint: unresolved conflicts should remain highly visible regardless of the configured order. A good implementation could keep conflict entries pinned above the normal groups, or otherwise ensure conflict visibility is not degraded when Staged Changes is configured first.

Alternatives or additional context

A simpler alternative would be to change the default order to Staged Changes, Changes, Untracked Files, but that may not fit every workflow and could reduce conflict visibility.

Related Source Control work:

• feat(source-control): add source control tree view #1658 added the Source Control tree view.
• feat(source-control): add Stage Files primary button #1670 added the Stage Files primary button.
• feat(source-control): full-row hover, tooltips, and staged discard-all #1407 improved Source Control section actions.