Lines Matching full:in

11 In typical development, every commit should compile, be covered by the test suite, and pass all tests.
15 It is useful to create a WIP (work in progress) pull request for any long-running development so that others can be aware of your work and help to avoid creating merge conflicts.
17 Write commit messages for a reviewer of your pull request and for a future developer (maybe you) that bisects and finds that a bug was introduced in your commit.
18 The assumptions that are clear in your mind while committing are likely not in the mind of whomever (possibly you) needs to understand it in the future.
24 When contributors make a major contribution and support it, their names are included in the automatically generated user-manual documentation.
26 Please avoid "merging from upstream" (like merging 'main' into your feature branch) unless there is a specific reason to do so, in which case you should explain why in the merge commit.
39 (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
41 (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
53 1. make significant contributions to libCEED (in implementation, documentation, conceptualization, review, etc.) and
58 Authors of publications about libCEED as a whole, including DOI-bearing archives, shall offer co-authorship to all individuals listed in the `AUTHORS` file.
59 Authors of publications claiming specific libCEED contributions shall evaluate those listed in `AUTHORS` and offer co-authorship to those who made significant intellectual contributions to the work.
61 Note that there is no co-authorship expectation for those publishing about use of libCEED (versus creation of new features in libCEED), but see the [citing section](https://libceed.org/en/latest/gettingstarted/#how-to-cite) and use your judgment regarding significance of support/advice you may have received in developing your use case and interpreting results.