Lines Matching +full:- +full:- +full:github +full:- +full:branch

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)
20 …GitHub Issue](https://github.com/openthread/openthread/issues/new). The best bug reports provide a…
24 You can request a new feature by [submitting a GitHub Issue](https://github.com/openthread/openthre…
28 - _Large feature_: first [submit a GitHub Issue](https://github.com/openthread/openthread/issues/ne…
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 1. Fork the [OpenThread repository](https://github.com/openthread/openthread) by clicking "Fork" on…
46 git clone git@github.com:<username>/openthread.git
49 git remote add upstream git@github.com:openthread/openthread.git
60 #### Branch  subsubsection
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
68 # Checkout the branch
69 git checkout <branch-name>
86 Prior to submitting your pull request, you might want to do a few things to clean up your branch an…
88 …been made to the upstream main branch, you should rebase your development branch so that merging i…
91 # Fetch upstream main and merge with your repo's main branch
95 # If there were any new commits, rebase your development branch
96 git checkout <branch-name>
103 # Rebase all commits on your development branch
105 git rebase -i main
112 …-pretty` and `script/make-pretty check` to automatically reformat code and check for code-style co…
114 As part of the cleanup process, you should also run `script/make-pretty check` to ensure that your …
119 # Checkout your branch
120 git checkout <branch-name>
122 # Push to your GitHub fork:
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…
136 …n, or it will be overwritten). Alternatively, upload the artifacts to a file-sharing service like …
140 …analyze the dumps locally. To analyze the dumps, download the artifact `core-xxx` and unzip it. Th…
143 |-- build
144 |   `-- cmake
145 |       `-- openthread-simulation-1.2
146 |           `-- examples
147 |               `-- apps
148 |                   `-- cli
149 |                       |-- ot-cli-ftd
150 |                       `-- ot-cli-mtd
151 |-- ot-core-dump
152 |   `-- corefile-ot-cli-ftd-11323-1606274703
153 `-- so-lib
154     |-- ld-linux-x86-64.so.2
155     |-- libc.so.6
156     `-- libgcc_s.so.1
162 2. Run `gdb build/cmake/openthread-simulation-1.2/examples/apps/cli/ot-cli-ftd ./ot-core-dump/coref…
163 …e path of `so-lib`. In gdb, run `set solib-absolute-prefix /ABSOLUTE/PATH/TO/so-lib/`, then run `s…
172 To review and contribute to OpenThread Codelabs and Guides, refer to the following GitHub repositor…
174 - [Codelabs](https://github.com/openthread/ot-docs/tree/main/site/en/codelabs)
175 - [Guides](https://github.com/openthread/ot-docs/tree/main/site/en/guides)
177 … contribution, refer to the [Documentation Style Guide](https://github.com/openthread/ot-docs/blob…
183 - @file
184 - @brief
185 - @param
186 - @returns
188 …github.com/openthread/openthread/tree/main/include/openthread). To review an example, refer to [`b…