Lines Matching refs:to
3 Thank you for your interest in contributing to our project. Whether it's a bug report, new feature,…
4 documentation, we welcome our community to be involved in this project.
6 …ugh this document before submitting any issues or pull requests to ensure we are able to help you …
19 Have a bug to report or feature to request? Follow these steps:
20 …](https://github.com/FreeRTOS/FreeRTOS/issues?utf8=%E2%9C%93&q=is%3Aissue) to be sure this hasn't …
21 … in the [forums](https://forums.freertos.org/) and work with the community to help clarify issues …
22 …community has had time to discuss and digest, we welcome you to create an [issue](https://github.c…
29 * Any modifications you've made relevant to the bug.
37 2. You check existing open, and recently merged, pull requests to make sure someone else hasn't add…
38 3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
43 …re contributing. If you also reformat all the code, it will be hard for us to focus on your change.
45 4. Commit to your fork using clear commit messages.
48 6. Pay attention to any automated CI failures reported in the pull request, and stay involved in th…
54 * Please ensure that your code complies to the [FreeRTOS coding style guidelines](https://www.FreeR…
58 …preciate your patience while pull requests are reviewed. The time it takes to review will depend o…
61 ## Finding contributions to work on
62 …to find something to contribute on. As our projects, by default, use the default GitHub issue labe…
70 We may ask you to sign a [Contributor License Agreement (CLA)](https://en.wikipedia.org/wiki/Contri…