Tracker: compose and edit workflow polish #168

Closed
opened 2026-04-12 17:22:05 +00:00 by barrettruth · 0 comments
barrettruth commented 2026-04-12 17:22:05 +00:00

Status

Some of the original rough edges are already resolved:

  • issue creation no longer aborts on an empty body (#188)
  • issue edit parity landed in #197
  • explicit abandon behavior landed in #200 / #204
  • direct :Forge pr edit <num> now uses fetched head/base metadata (#201 / #203)
  • PR compose metadata fields were removed in #215
  • compose/edit metadata should follow a gitcommit-style commented scaffold rather than virtual read-only UI

Remaining follow-ups

  • #228 Restore and display compose metadata from templates and fetched details
  • #198 Improve compose buffer syntax and highlight treatment
  • verify and document per-backend template/metadata support across GitHub, GitLab, and Codeberg/Gitea/Forgejo

Resolved direction

  • compose/edit buffers should remain normal editable buffers
  • non-authored metadata/help should live in the commented scaffold block
  • forge.nvim should not pursue fake line-level read-only behavior in normal compose buffers

Expected

The remaining compose and edit workflows should feel visually polished, easier to scan, and more deliberate about their editing surface.

## Status Some of the original rough edges are already resolved: - issue creation no longer aborts on an empty body (#188) - issue edit parity landed in #197 - explicit abandon behavior landed in #200 / #204 - direct `:Forge pr edit <num>` now uses fetched head/base metadata (#201 / #203) - PR compose metadata fields were removed in #215 - compose/edit metadata should follow a gitcommit-style commented scaffold rather than virtual read-only UI ## Remaining follow-ups - [ ] #228 Restore and display compose metadata from templates and fetched details - [ ] #198 Improve compose buffer syntax and highlight treatment - [ ] verify and document per-backend template/metadata support across GitHub, GitLab, and Codeberg/Gitea/Forgejo ## Resolved direction - compose/edit buffers should remain normal editable buffers - non-authored metadata/help should live in the commented scaffold block - forge.nvim should not pursue fake line-level read-only behavior in normal compose buffers ## Expected The remaining compose and edit workflows should feel visually polished, easier to scan, and more deliberate about their editing surface.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
barrettruth/forge.nvim#168
No description provided.