-
### Context
A sequence concept (which enables branching) seems required.
Conflicting changes are stored in the change table. Given that conflicting changes should not be displayed by apps, apps are …
-
Hi all would appreciate any confirmation on my understanding on why things went wrong and suggestions on how I may attempt to fix this predicament.
I branched out to branch-level-7 at commit A.
Bu…
-
Hi @mirzak can you create the relevant branch for kirkstone? Such as all Yocto related layers do, so as to have it clearer which Yocto release your board is supporting, aside from https://github.com/m…
-
![bilde](https://github.com/user-attachments/assets/b2467a29-02ad-4952-862b-d89199472715)
-
Opening to express interest in a new feature for having different target branches for specific virtual branches instead of just one global target branch for all virtual branches.
-
Adjust branch names to have a common approach:
* developing on "main"
* cutting a branch for each main release to be able to maintain and backport there
This causes following renaming of branch…
-
### Description
Until now we’ve been suggesting to enable branch protection so that this feature doesn’t kick in. This advice is still very much valid, but I think we can at least skip auto-deletion …
-
Maybe it would help to streamline the content contribution to have a branching strategy.
This could be e.g. to protect the 'main' of 'prod' branch with auto-deployment and allow merging only after …
-
For ida john, etc
-
Using `branches` or `b` will not work in the case where the is a remote branch. Path looks like `remotes/origin/`. In this case,
the `git checkout ` should be used.
2024-08-31T20:12:23Z