|
| 1 | +# Contributing to OASGraph |
| 2 | + |
| 3 | +This document lists the differences between the contribution guidelines for |
| 4 | +this repository and the general [**Contributing to LoopBack**](http://loopback.io/doc/en/contrib/index.html) guidelines. |
| 5 | + |
| 6 | +### Developer Certificate of Origin |
| 7 | + |
| 8 | +This repository uses a [Developer Certificate of Origin (DCO)](https://developercertificate.org/) instead of a |
| 9 | +[Contributor License Agreement](https://cla.strongloop.com/agreements/strongloop/loopback.io) like most other LoopBack repositories. DCO |
| 10 | +is an easier process to adhere to. [Full text of DCO](https://developercertificate.org/) can be found below, formatted |
| 11 | +for readability. |
| 12 | + |
| 13 | +> By making a contribution to this project, I certify that: |
| 14 | +> |
| 15 | +> (a) The contribution was created in whole or in part by me and I |
| 16 | + have the right to submit it under the open source license |
| 17 | + indicated in the file; or |
| 18 | +> |
| 19 | +> (b) The contribution is based upon previous work that, to the best |
| 20 | + of my knowledge, is covered under an appropriate open source |
| 21 | + license and I have the right under that license to submit that |
| 22 | + work with modifications, whether created in whole or in part |
| 23 | + by me, under the same open source license (unless I am |
| 24 | + permitted to submit under a different license), as indicated |
| 25 | + in the file; or |
| 26 | +> |
| 27 | +> (c) The contribution was provided directly to me by some other |
| 28 | + person who certified (a), (b) or (c) and I have not modified |
| 29 | + it. |
| 30 | +> |
| 31 | +> (d) I understand and agree that this project and the contribution |
| 32 | + are public and that a record of the contribution (including all |
| 33 | + personal information I submit with it, including my sign-off) is |
| 34 | + maintained indefinitely and may be redistributed consistent with |
| 35 | + this project or the open source license(s) involved. |
| 36 | + |
| 37 | +Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages. |
| 38 | + |
| 39 | +``` |
| 40 | +This is my commit message |
| 41 | +
|
| 42 | +Signed-off-by: Random J Developer <[email protected]> |
| 43 | +``` |
| 44 | + |
| 45 | +Git even has a -s command line option to append this automatically to your commit message: |
| 46 | + |
| 47 | +```sh |
| 48 | +$ git commit -s -m 'This is my commit message' |
| 49 | +``` |
| 50 | + |
| 51 | +#### Fixing Commit Messages |
| 52 | + |
| 53 | +If you've pushed a commit and forgot to sign it, fear not, you can sign it as follows: |
| 54 | + |
| 55 | +``` |
| 56 | +git commit --amend -s |
| 57 | +``` |
| 58 | + |
| 59 | +Modify the commit message (if desired) -- do not modify the `Signed-off-by` line. Exit edit mode (`esc` followed by `:x` and then `Enter`). |
| 60 | + |
| 61 | +Now force-push the changes by running: |
| 62 | +``` |
| 63 | +git push origin +[branch-name] |
| 64 | +``` |
| 65 | + |
| 66 | +Refer to the [official documentation](https://help.github.com/articles/changing-a-commit-message/#amending-older-or-multiple-commit-messages) for modifying multiple commits or an example with screenshots. |
| 67 | + |
| 68 | +If all else fails, ask the LoopBack team for help :) |
| 69 | + |
0 commit comments