Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EGit/New and Noteworthy/6.2
Contents
EGit
Commit Messages
EGit 6.1 had introduced support for git config commit.cleanup, including syntax coloring comment lines in commit messages, and a preview of the final commit message after cleaning.
EGit 6.2 adds support for git config core.commentChar. It enables users to change the default comment character # to some other ASCII character. EGit 6.2 takes this setting into account and determines comment lines in commit messages accordingly, for instance with core.commentChar = ; as:
Git Staging View
The Git Staging View has a new "Push Settings" button with a cogwheel icon, providing a way to customize some settings for the push part of the Commit & Push operation.
There are options to perform a force push, or to open a push dialog instead of just pushing automatically. If the "Force Push" option is active, the button's icon shows a little green plus sign top-right.
Settings made here are persisted; they are stored separately per repository, and they will be in effect for any Commit & Push operation on a repository until changed again via this "Push Settings" button.
Commit & Push performs the equivalent of
git push <remote> HEAD:<upstream branch>
The remote is determined via git configs branch.<name>.pushRemote, remote.pushDefault, branch.<name>.remote, "origin". The upstream branch is determined from the branch.<name>.merge git configuration of the currently checked out branch; if none is set, the upstream branch is assumed to have the same name as the current local branch.
Activating the "Force Push" option changes this to
git push <remote> +HEAD:<upstream branch>
Note: if the repository is configured for Gerrit and the Commit & Push operation will attempt pushing to Gerrit, then the "Push Settings" button is not available. First, the command will in that case always use a dialog, and second, force pushing a commit as a new change or patch set to Gerrit makes no sense.
Other Changes
The complete list of new features and bug fixes is available in the release notes.
Contributors
The following X developers worked on this release:
<TBD: list of contributors, number>
See Also
See also the new features in JGit for additional information.