source: rtems-central/formal/promela/src/src/modules/comment_filter/ @ 13ed9da

Last change on this file since 13ed9da was 13ed9da, checked in by Andrew Butterfield <Andrew.Butterfield@…>, on 01/13/23 at 15:36:54

forked from
commit 9cfb52318e5f71af56b5808e280a9b089b9abc32

  • Property mode set to 100644
File size: 3.6 KB
1## Contributing to Comment Filter
3Hi there!
4We’re thrilled that you’d like to contribute to this project.
5Your help is essential for keeping this project great and for making it better.
7## Branching Strategy
9In general, contributors should develop on branches based off of `master` and pull requests should be made against `master`.
11## Submitting a pull request
131. Please read our [code of conduct](] and [license](LICENSE.txt).
141. [Fork]( and clone the repository.
151. Create a new branch based on `master`: `git checkout -b <my-branch-name> master`.
161. Make your changes, add tests, and make sure the tests still pass.
171. Push to your fork and [submit a pull request]( from your branch to `master`.
181. Pat yourself on the back and wait for your pull request to be reviewed.
20Here are a few things you can do that will increase the likelihood of your pull request to be accepted:
22- Follow the existing style where possible. We try and adhere to [pep8](
23- Write tests.
24- Keep your change as focused as possible.
25  If you want to make multiple independent changes, please consider submitting them as separate pull requests.
26- Write a [good commit message](
29## Developer Certification of Origin (DCO)
30Comment Filter requires the Developer Certificate of Origin (DCO) process to be followed.
32The DCO is an attestation attached to every contribution made by every developer. In the commit message of the contribution, the developer simply adds a Signed-off-by statement and thereby agrees to the DCO, which you can find below or at
34Comment Filter does not merge any pull requests made until each commit has been signed for the DCO.
37Developer Certificate of Origin
38Version 1.1
40Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
411 Letterman Drive
42Suite D4700
43San Francisco, CA, 94129
45Everyone is permitted to copy and distribute verbatim copies of this
46license document, but changing it is not allowed.
49Developer's Certificate of Origin 1.1
51By making a contribution to this project, I certify that:
53(a) The contribution was created in whole or in part by me and I
54    have the right to submit it under the open source license
55    indicated in the file; or
57(b) The contribution is based upon previous work that, to the best
58    of my knowledge, is covered under an appropriate open source
59    license and I have the right under that license to submit that
60    work with modifications, whether created in whole or in part
61    by me, under the same open source license (unless I am
62    permitted to submit under a different license), as indicated
63    in the file; or
65(c) The contribution was provided directly to me by some other
66    person who certified (a), (b) or (c) and I have not modified
67    it.
69(d) I understand and agree that this project and the contribution
70    are public and that a record of the contribution (including all
71    personal information I submit with it, including my sign-off) is
72    maintained indefinitely and may be redistributed consistent with
73    this project or the open source license(s) involved.
74 ```
76### DCO commit example
78After committing your changes with `git commit -s`, your message should look something like:
80commit 442deae270bf585052be012b064ed92299e221c4
81Author: Random Developer <>
82Date:   Sat Oct 21 08:33:15 2017 -0700
84    My example commit message
86    Signed-off-by: Random Developer <>
Note: See TracBrowser for help on using the repository browser.