Skip to content

submit: add --fill-from parameter for stack submission commands#1158

Open
water-sucks wants to merge 2 commits into
abhinav:mainfrom
water-sucks:add-fill-from-parameter
Open

submit: add --fill-from parameter for stack submission commands#1158
water-sucks wants to merge 2 commits into
abhinav:mainfrom
water-sucks:add-fill-from-parameter

Conversation

@water-sucks

Copy link
Copy Markdown
Contributor

When submitting stacks, it is impossible to pass custom information for each change request non-interactively. While this is possible for the gs branch submit command, passing a title and body for each change request is impossible to do non-interactively.

This is especially useful for facilitating AI agents that automatically submit change requests using git-spice, since they can now autofill intelligent CR titles and descriptions instead of relying on default --fill output, which isn't that useful.

@water-sucks water-sucks force-pushed the add-fill-from-parameter branch 2 times, most recently from 0bbe644 to 285536f Compare May 13, 2026 18:38
water-sucks and others added 2 commits May 13, 2026 11:44
When submitting stacks, it is impossible to pass custom information
for each change request non-interactively. While this is possible for
the `gs branch submit` command, passing a title and body for each change
request is impossible to do non-interactively.

This is especially useful for facilitating AI agents that automatically
submit change requests using `git-spice`, since they can now autofill
intelligent CR titles and descriptions instead of relying on default
`--fill` output, which isn't that useful.
@water-sucks water-sucks force-pushed the add-fill-from-parameter branch from 2d01d55 to 07aa2a6 Compare May 13, 2026 18:44
@abhinav

abhinav commented May 17, 2026

Copy link
Copy Markdown
Owner

Thanks, @water-sucks. I'll go over this as soon as I'm able.
I think I might want a different UX for this—here's JSON for all branches doesn't quite match how I'd like for this to work. I'm going to have to think about this a bit more, but regardless, thanks for the change.

@water-sucks

Copy link
Copy Markdown
Contributor Author

Yeah it's all good! I'd also like to talk about what UX is best for this. This is a patch I wrote on my own that my team is using at work so it's not buried in stone or anything haha

@ed-irl

ed-irl commented May 18, 2026

Copy link
Copy Markdown
Collaborator

Relatedly, I have been using an AI based extension of the --fill command for a month or two now; just posted it #1170

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants