You cannot correct commits that you have already pushed. Comment on
the commit's GitHub page instead. (Modifying your local history causes
it to diverge from the public history. Publishing this alternate
history would require force-pushing, which we disallow because it's
However this does NOT hold for pull requests and we really need to clarify this.
> For pull requests, you are not pushing to the MacPorts repository,
> but to the repository of the user who opened the pull request...
Yes, but the documentation is not clear about this. It does not say that
the project is ok with force-pushing in PRs. Some projects are not ok
with it and require you to close the PR and open a new one (or to add
commits to change previous ones).
> It seems like it would be easier to correct these kind of things if
> we allowed squashing commits in the GitHub UI when accepting a pull
> request, instead of only allowing rebase.
Yep, but it's also more error prone. You could easily squash commits
which are not supposed to be squashed.