Git ECA Validation Status
Eclipse Intellectual Property Management:
Some contributions of code to be maintained by Eclipse Projects must be reviewed by the IP Team; in particular if they contain third party content and/or are over 1,000 Lines of Code. Further information can be read via the Eclipse Handbook.
About this project
- Eclipse Foundation Project: YES
- Eclipse Foundation Specification Project: YES
- Committer did not have a signed ECA on file. (laforge@osm*com DOT org)
SHA: 8bc66642f799c3be7dee80d4f1690133ac3a4d60
- Committer did not have a signed ECA on file. (laforge@osm*com DOT org)
Common troubleshooting tips
A common error experienced by users is that the email associated with commits do not align with the email set in the Eclipse Foundation account. If you have an Eclipse Foundation account and a signed ECA-equivalent document, there are ways to validate the users and email addresses associated with a commit.
Below are 3 sample commands that will display the committer and author emails for a given commit or range. The first command shows the latest commit, while the second command will show results for a given commit, replacing `<SHA>` with the commit SHA. The last example will render a range of sequential commits. As is, it will show the last 5 commits starting from HEAD for the current branch. Both sides of the range can be replaced with commit SHAs to represent a different range.
git show -s --format='Commit: %h, Committer: %ce, Author: %ae
git show -s --format='Commit: %h, Committer: %ce, Author: %ae' <SHA>
git show -s --format='Commit: %h, Committer: %ce, Author: %ae' HEAD...HEAD~5