This works by specifying a "base branch" that represents the state of production, normally
- something like "origin/master". All of your virtual branches are based off of this branch
- and need to be kept up to date with this branch to ensure they are working with the latest
- code.
+ something like "origin/master".
Ownership, Committing and Pushing
diff --git a/src/routes/repo/[projectId]/Board.svelte b/src/routes/repo/[projectId]/Board.svelte
index d5509295b..715a2531e 100644
--- a/src/routes/repo/[projectId]/Board.svelte
+++ b/src/routes/repo/[projectId]/Board.svelte
@@ -7,6 +7,7 @@
import { getContext } from 'svelte';
import { BRANCH_CONTROLLER_KEY } from '$lib/vbranches/branchController';
import type { CloudApi } from '$lib/api';
+ import { Link } from '$lib/components';
export let projectId: string;
export let projectPath: string;
@@ -93,5 +94,31 @@
{upstream}
/>
{/each}
-
+
+ {#if branches.length == 0}
+
+
+
You are up to date
+
+ This means that your working directory looks exactly like your base branch. There isn't
+ anything locally that is not in your production code.
+
+
+ If you start editing files in your working directory, a new virtual branch will
+ automatically be created and you can manage it here.
+