(administrivia: please don't top-post) Lukas Gross wrote: > I had intended to stage commits but forgot to do so. Git responded > with a normal commit creation message, so I pushed to the remote to > begin a CI build. When the build failed for the same reason, I > realized I had forgotten to stage the changes. An additional line in > the response to the effect of “Warning: did you mean to amend with no > changes?” would be very helpful to shorten this feedback loop. Ah, I see. You passed --no-edit so you didn't see the usual --dry-run style output that "git commit" shows. You forgot to run "git add" before amending, and this is what you'd like commit to assist you with. That said, this is sometimes an operation people perform intentionally. Ideas: * Can the documentation do a better job of steering people away from --no-edit? The hints shown when "git commit --amend" (and --no-amend, for that matter) open a text editor tend to be very helpful for understanding what is going to happen. If any documentation is leading people to forgo that tool, we should fix it. * Should "git commit --no-edit" say a little more about what it did, since it knows that the user didn't get to see the text editor? * Should we have a special option (e.g. "git commit --amend --refresh") for a no-op amend? That ways, when a user doesn't pass that option, it would be more clear that it is a mistake, allowing a warning or even an error. Of these three, the first seems most compelling to me. Others may have other ideas. Thoughts? Thanks, Jonathan
