Repository navigation
Conversation
This was referenced Oct 18, 2026
robelsust
force-pushed
the
fix/issue-command-attachments
branch
from
October 22, 2026 15:52
68d1a0b to
df40ce0
Compare
Contributor
Member
|
Closing as a duplicate of #1159. Thanks for the work on this! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Typing
/bugor/featurehides attachment controls, but pasted and dropped images can still enter the draft. Issue submissions carry text only, so those images are silently omitted.Disable image attachment paths while an issue command is active, suppress the drop overlay, and prevent rejected file drops from navigating away. Preserve text editing and restore attachments when returning to a commit. Use the same rejection behavior for polls, which also do not accept images.
Validation: two new regression cases fail before the fix and pass afterward; all 13 composer tests pass. The standard frontend tests, TypeScript checks, lint, and client/SSR builds pass. Nine browser scenarios verify both commands, inline/dialog composers, text-only issue payloads, canceling, and normal/scheduled attachments. GitHub submissions were mocked.