diff --git a/src/lib/icons/IconEmptyMug.svelte b/src/lib/icons/IconEmptyMug.svelte new file mode 100644 index 000000000..1883ddef7 --- /dev/null +++ b/src/lib/icons/IconEmptyMug.svelte @@ -0,0 +1,41 @@ + + + diff --git a/src/lib/icons/IconHelp.svelte b/src/lib/icons/IconHelp.svelte new file mode 100644 index 000000000..ed2c84e59 --- /dev/null +++ b/src/lib/icons/IconHelp.svelte @@ -0,0 +1,19 @@ + + + diff --git a/src/lib/icons/IconLock.svelte b/src/lib/icons/IconLock.svelte new file mode 100644 index 000000000..0e38787ca --- /dev/null +++ b/src/lib/icons/IconLock.svelte @@ -0,0 +1,19 @@ + + + diff --git a/src/lib/icons/IconNewBadge.svelte b/src/lib/icons/IconNewBadge.svelte new file mode 100644 index 000000000..31d48aac2 --- /dev/null +++ b/src/lib/icons/IconNewBadge.svelte @@ -0,0 +1,86 @@ + + + diff --git a/src/routes/repo/[projectId]/+page.svelte b/src/routes/repo/[projectId]/+page.svelte index 384e2531c..a34bb46ba 100644 --- a/src/routes/repo/[projectId]/+page.svelte +++ b/src/routes/repo/[projectId]/+page.svelte @@ -50,7 +50,7 @@
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".
diff --git a/src/routes/repo/[projectId]/Board.svelte b/src/routes/repo/[projectId]/Board.svelte
index 617404921..ef5c5c30e 100644
--- a/src/routes/repo/[projectId]/Board.svelte
+++ b/src/routes/repo/[projectId]/Board.svelte
@@ -6,6 +6,7 @@
import { BRANCH_CONTROLLER_KEY, BranchController } from '$lib/vbranches/branchController';
import { getContext } from 'svelte';
import type { getCloudApiClient } from '$lib/api/cloud/api';
+ import { Link } from '$lib/components';
export let projectId: string;
export let projectPath: string;
export let branches: Branch[];
@@ -91,5 +92,31 @@
{upstream}
/>
{/each}
-
+ 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. +
+ + Learn more + +Nothing on this branch yet.
++ Get some work done, then throw some files my way! +
+