Lines Matching refs:a

5 Please use a pull request to the appropriate branch ('release' for backward-compatible bug fixes fo…
9 If adding a new feature, please add or extend a test so that your new feature is tested.
15 It is useful to create a WIP (work in progress) pull request for any long-running development so th…
17 Write commit messages for a reviewer of your pull request and for a future developer (maybe you) th…
20 …tps://help.github.com/en/github/committing-changes-to-your-project/creating-a-commit-with-multiple…
21 Please use a real name and email for your author information (`git config user.name` and `user.emai…
24 When contributors make a major contribution and support it, their names are included in the automat…
26 …om upstream" (like merging 'main' into your feature branch) unless there is a specific reason to d…
31 By submitting a pull request, you are affirming the following.
35 By making a contribution to this project, I certify that:
37 (a) The contribution was created in whole or in part by me and I have the right to submit it under …
39 …, under the same open source license (unless I am permitted to submit under a different license), …
41 (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c)…
43 (d) I understand and agree that this project and the contribution are public and that a record of t…
49 Status as a named author on the users manual and HONEE software publications will be granted for th…
56 Authors of publications about HONEE as a whole, including DOI-bearing archives, shall offer co-auth…