GitHub pass follow-up #161
Labels
No labels
bug
documentation
duplicate
enhancement
fugitive
good first issue
help wanted
invalid
question
v0.1.0
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
barrettruth/forge.nvim#161
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to the earlier
bugfixesissue. If we want to post this verbatim, swap in the real issue number/title reference.The GitHub regression pass turned up a mix of hard bugs, stale docs, and workflow polish problems. The main pattern is that the core command surface mostly works, but several picker and compose flows still need tighter state handling and cleaner UX.
The main buckets are:
See the tracker for the full list.
Tracker: #176
Superseded by #176, which now reflects the remaining open follow-up work from the GitHub regression pass.