The "Signed-off-by" entry must be in the ''footer'' of the commit message. This is the last block of text in the commit message; it cannot contain blank lines. See {{Bug|412140}}.

The "Signed-off-by" entry must be in the ''footer'' of the commit message. This is the last block of text in the commit message; it cannot contain blank lines. See {{Bug|412140}}.

+

+

For example, pushing the following commit to Gerrit will fail because the "Signed-off-by" entry is not considered part of the footer (it is separated from the footer by a <span style="background:#FFCCCC">blank line</span>):

+

+

commit 862e6ff22ad56c10df6de3385ffa4c7d02363d1d

+

Author: Joe Somebody <somebody@someplace.net>

+

Date: Mon Jun 17 17:19:38 2013 -0700

+

+

[410937] Auto share multiple projects in single job

+

+

When multiple projects are imported together, perform all the necessary

+

auto shares in a single job rather than spawning a separate job for each

Be sure to use the same email address when you register for the account that you intend to use on Git commit records.

The Commit Record

If a project supports Gerrit, you can push directly to that project's repository. Alternatively, if you have a public Git repository, a project committer can pull your contribution.

Minimally, your Git commit record must have the following:

Your credentials (email address) captured in the "Author" field;

A single line summary in the message field, followed by a more detailed descriptive paragraph; and

A "Signed-off-by" entry with matching credentials in the message footer.

If applicable, a link to the Bug that is addressed by the commit should be included in the message footer. The id (bug number) of the bug should also be included in the message summary (in square braces).

You can specify additional authors using one or more "Also-by" entries in the message footer.

The "Signed-off-by" entry is required. By including this, you confirm that you are in compliance with the Certificate of Origin.

Note that the footer entries must occur at the bottom of the commit message and must not include any blank lines.

Signing off on a commit

Both Git and EGit have built-in support for signing off on a commit.

From command-line Git, add -s to the command:

git commit -s -m "Auto share multiple projects in single job"

From EGit, there is a handy button in the commit dialog box:

EGit can also be configured to sign-off all commits you create from EGit automatically:

click "Preferences > Team > Git > Commit Dialog"

check "Footers > Insert Signed-off-by"

Contributing via Bugzilla

If you cannot push to a project's Gerrit repository, or do not have a public Git repository from which a project committer can pull, you can submit your contribution as a patch attachment on a Bugzilla record.

A Word about Eclipse Foundation Accounts

The Eclipse Foundation maintains multiple separate forges. The same user account applies for all forges. If you, for example, create an account on eclipse.org, that same account can be used on LocationTech or PolarSys. A signed CLA is connected to your Eclipse Foundation account; this means that with the single valid CLA on file, you can contribute to any project on any of the forges.

Frequently Asked Questions

I have a CLA; why can't I push to Gerrit?

First check the email address that you're using on the commit record. It must match the email address you use on your Eclipse Foundation account.

We have noticed an issue with Gerrit caching that sometimes introduces latency in the ability for Gerrit to recognize that you have a CLA. This may affect you if you've very recently signed a CLA. Please see bug 407114.

The commit is properly signed-off; why is it being rejected?

The "Signed-off-by" entry must be in the footer of the commit message. This is the last block of text in the commit message; it cannot contain blank lines. See bug 412140.

For example, pushing the following commit to Gerrit will fail because the "Signed-off-by" entry is not considered part of the footer (it is separated from the footer by a blank line):