• Home
  • Raw
  • Download

Lines Matching +full:create +full:- +full:issue +full:- +full:on +full:- +full:failure

5 - [1 Code of Conduct](#code-of-conduct)
6 - [2 Bugs](#bugs)
7 - [3 New Features](#new-features)
8 - [4 Contributing Code](#contributing-code)
9 - [4.1 Initial Setup](#initial-setup)
10 - [4.2 Contributor License Agreement (CLA)](#contributor-license-agreement--cla-)
11 - [4.3 Submitting a Pull Request](#submitting-a-pull-request)
12 - [5 Contributing Documentation](#contributing-documentation)
20Issue](https://github.com/openthread/ot-br-posix/issues/new). The best bug reports provide a detai…
24 You can request a new feature by [submitting a GitHub Issue](https://github.com/openthread/ot-br-po…
28 - _Large feature_: first [submit a GitHub Issue](https://github.com/openthread/ot-br-posix/issues/n…
30 - _Small feature_: can be implemented and directly [submitted as a Pull Request](#submitting-a-pull
34 The OpenThread Project follows the "Fork-and-Pull" model for accepting contributions.
38 Setup your GitHub fork and continuous-integration services:
40 …the [OpenThread repository](https://github.com/openthread/ot-br-posix) by clicking "Fork" on the w…
49 git remote add upstream git@github.com:openthread/ot-br-posix.git
54 …ver to <https://cla.developers.google.com/> to see your current agreements on file or to sign a ne…
62 For each new feature, create a working branch:
65 # Create a working branch for your new feature
66 git branch --track <branch-name> origin/main
69 git checkout <branch-name>
72 #### Create Commits
78 # Create a commit
88 …ould rebase your development branch so that merging it will be a simple fast-forward that won't re…
96 git checkout <branch-name>
103 # Rebase all commits on your development branch
105 git rebase -i main
112on all code, except for code located in [third_party](third_party). Use `script/make-pretty` and `…
114 As part of the cleanup process, you should also run `script/make-pretty check` to ensure that your …
120 git checkout <branch-name>
123 git push origin <branch-name>
126 This will trigger continuous-integration checks using GitHub Actions. You can view the status and l…
130-integration checks have passed, go to the page for your fork on GitHub, select your development b…
134-integration checks are triggered again. If some of these checks fail, it could be either problems…
136failure, please log an issue and attach any relevant artifacts. If the artifacts are too big, prov…
140 Documentation undergoes the same review process as code and contributions may be mirrored on our [o…
146 - [Codelabs](https://github.com/openthread/ot-docs/tree/main/site/en/codelabs)
147 - [Guides](https://github.com/openthread/ot-docs/tree/main/site/en/guides)
149 …ormation on how to author and format documentation for contribution, refer to the [Documentation S…
153 …s](https://www.doxygen.nl/manual/docblocks.html) to render the HTML output on [https://openthread.…
155 - @file
156 - @brief
157 - @param
158 - @returns
160 …the [Border Agent](https://openthread.io/reference/group/api-border-agent) reference topic on open…