Lines Matching +full:repo +full:- +full:token
1 .. _west-workspaces:
7 :ref:`west-basics` in more detail.
9 .. _west-manifest-rev:
11 The ``manifest-rev`` branch
14 West creates and controls a Git branch named ``manifest-rev`` in each
16 specified for the project at the time :ref:`west-update` was last run.
17 Other workspace management commands may use ``manifest-rev`` as a reference
19 purposes, the ``manifest-rev`` branch allows the manifest file to use SHAs
22 Although ``manifest-rev`` is a normal Git branch, west will recreate and/or
27 rebase it on top of a new ``manifest-rev``, or merge ``manifest-rev`` into
32 West does not create a ``manifest-rev`` branch in the manifest repository,
40 ``manifest-rev``, these refs are not regular branches. West's behavior here is
48 west-specific about this.
51 when a project's ``manifest-rev`` branch must be updated to a newly fetched
56 no need for a west-specific feature.
62 https://git-scm.com/docs/gitcredentials
73 credential helper. See the `git-credential-store`_ manual page for details.
77 .. code-block:: shell
79 west forall -c "git config credential.helper store"
83 .. code-block:: shell
85 west forall -c "git config credential.helper store" foo bar
89 .. code-block:: shell
91 git config --global credential.helper store
93 On GitHub, you can set up a `personal access token`_ to use in place of your
94 account password. (This may be required if your account has two-factor
96 in plain text even if two-factor authentication is disabled.)
99 (Personal Access Token) like so:
101 .. code-block:: shell
103 echo "https://x-access-token:$GH_TOKEN@github.com" >> ~/.git-credentials
106 them in memory temporarily using `git-credential-cache`_ instead.
111 .. code-block:: shell
113 git config --global url."git@github.com:".insteadOf "https://github.com/"
115 .. _git-credential-store:
116 https://git-scm.com/docs/git-credential-store#_examples
117 .. _git-credential-cache:
118 https://git-scm.com/docs/git-credential-cache
119 .. _personal access token:
120 https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token
126 password, you can avoid entering it manually every time using `ssh-agent`_.
131 .. _ssh-agent:
134 https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh
149 .. _west-topologies:
156 - T1: star topology, zephyr is the manifest repository
157 - T2: star topology, a Zephyr application is the manifest repository
158 - T3: forest topology, freestanding manifest repository
163 - The zephyr repository acts as the central repository and specifies
165 - Analogy with existing mechanisms: Git submodules with zephyr as the
166 super-project
168 This is the default. See :ref:`west-workspace` for how mainline Zephyr is an
171 .. _west-t2:
176 - Useful for those focused on a single application
177 - A repository containing a Zephyr application acts as the central repository
180 - Analogy with existing mechanisms: Git submodules with the application as
181 the super-project, zephyr and other projects as submodules
185 .. code-block:: none
187 west-workspace/
202 # Only the 'manifest-rev' version can be imported.
206 :ref:`west-manifest-import`, available since west 0.7, to import Zephyr v2.5.0
209 .. code-block:: yaml
214 - name: zephyrproject-rtos
215 url-base: https://github.com/zephyrproject-rtos
217 - name: zephyr
218 remote: zephyrproject-rtos
225 ``import:`` in this way; see :ref:`west-manifest-ex1.3` for an example.
231 .. code-block:: yaml
236 - name: zephyrproject-rtos
237 url-base: https://github.com/zephyrproject-rtos
239 remote: zephyrproject-rtos
241 - name: zephyr
243 west-commands: scripts/west-commands.yml
244 - name: net-tools
245 revision: some-sha-goes-here
246 path: tools/net-tools
251 (The ``west-commands`` is there for :ref:`west-build-flash-debug` and other
252 Zephyr-specific :ref:`west-extensions`. It's not necessary when using
264 - Useful for those supporting multiple independent applications or downstream
266 - A dedicated manifest repository which contains no Zephyr source code,
268 - Analogy with existing mechanisms: Google repo-based source distribution
272 .. code-block:: none
274 west-workspace/
285 ├── manifest-repo/ # .git/ never modified by west
294 # Only the 'manifest-rev' version can be imported.
296 Here is an example T3 :file:`manifest-repo/west.yml` which uses
297 :ref:`west-manifest-import`, available since west 0.7, to import Zephyr
300 .. code-block:: yaml
304 - name: zephyrproject-rtos
305 url-base: https://github.com/zephyrproject-rtos
306 - name: your-git-server
307 url-base: https://git.example.com/your-company
309 remote: your-git-server
311 - name: zephyr
312 remote: zephyrproject-rtos
315 - name: app1
317 - name: app2
320 path: manifest-repo
323 as shown :ref:`above <west-t2>` for the T2 topology, with the same caveats.