From ef5c9a49cd33d9c0e9e1fd218e2484c246ebdcf1 Mon Sep 17 00:00:00 2001
From: Walter Lozano <walter.lozano@collabora.com>
Date: Thu, 12 Aug 2021 15:32:07 -0300
Subject: [PATCH] Fix branch names on component guide
In order to follow the best practices when upgrading components, change
branch name prefixes from wip to proposed-updates to trigger a license
scan.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
---
content/guides/component_guide.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/guides/component_guide.md b/content/guides/component_guide.md
index e922c0ed5..648fe576c 100644
--- a/content/guides/component_guide.md
+++ b/content/guides/component_guide.md
@@ -367,7 +367,7 @@ packages taken from stable or even testing releases.
do this via a development branch that can be pushed for review.
$ APERTIS_RELEASE=v2021
- $ PROPOSED_BRANCH=wip/${GITLAB_GROUP}/${APERTIS_RELEASE}-update-from-${DESIRED_UPSTREAM}
+ $ PROPOSED_BRANCH=proposed-updates/${GITLAB_GROUP}/${APERTIS_RELEASE}-update-from-${DESIRED_UPSTREAM}
$ git checkout -b ${PROPOSED_BRANCH} apertis/${APERTIS_RELEASE}
$ apertis-pkg-merge-updates --upstream=debian/${DESIRED_UPSTREAM} --downstream=${PROPOSED_BRANCH}
--
GitLab