Cancel 'MSG_TYPE_RESAVE' info bar if still open in function 'document_reload_force'.

[lpaulsen93]

Fixes #1330.

[codebrainz]

Will try to test soon. Requested review from @kugel- since he worked on this code a lot.

[kugel-]

LGBI. The change makes sense since after reload the buffer and on-disk file are in sync.

Just the commit message could be improved.

[lpaulsen93]

To what? Take the title from issue 1330?

[elextr]

@LarsGit223 Git takes the first line of the commit description as the title of the commit, so it should be a short but complete one line summary. Full details then go on the following lines which are taken as the body of the commit message. Don't continue the title line into the message body.

[lpaulsen93]

I created a new PR with a different commit message, see #1628. So this can be closed.

[codebrainz]

@LarsGit223 you can also do a "force push" to your existing branch to reword it, something like these steps:

$ git checkout issue1330
$ git commit --amend # and then reword the message
$ git push <your-remote-here> +issue1330

This will also update the associated PR.

[lpaulsen93]

Ahh...thanks. The info that I had was that git commit --amend could only be used if the change was not pushed yet. So that info seems to be wrong.

[elextr]

@LarsGit223 its correct that you should not force push changes to public repositories that lots of people will pull from, but for a pull request in its own branch its fairly safe.