Amending a pushed commit puts the repository in a stuck state.

[Da-Buche]

I often use the "Amend Last Commit" feature to add small changes to my previous commit.
However, if the previous commit has already been pushed, then the amended commit cannot be pushed anymore.

Is it possible to disable the "Amend Last Commit" button if the previous commit has already been pushed?

[j6t]

I don't know if it is possible with reasonable effort. At any rate, it should not be disabled, but protected with a warning. Changes to local history must always be possible.

These need to be considered, too:

• What does it mean that a commit is pushed? Which refs count as "pushed"? All remotes? Only some?
• Should the restriction not apply more generally under certain specifiable conditions, not just "pushed" commits?
• Commits that are ancestors of refs from the list in the previous items must not be amended, either.

[carenas]

if the previous commit has already been pushed, then the amended commit cannot be pushed anymore

but it can be "force" pushed, and indeed some workflows (ex: GitHub's PRs) usually suggest that as a part of the "normal" workflow.