|F4s~jZaZC46x_|R}^CSTuL|k1#VbAiki8(YwO*kJ+W9w
zJ1-=h-1dj*{AQF#drC@zPdxz4IC24)QDiv~HvpR+BVYYHrD>GBJ5F+5ztALV@hvLr
zzT3XefU$*cjIm#ENGe~t5s4!vA4$vzJiMsC8$^OoPhpr6;f_iaUJ}_u^_GW%Y;5CL{KB5%m_2zAuv;7uu|h%ULHAS2F@f4GmBS6g5oK%fb-0^8?bWlW9_p%V~b!fgLgdl9O`BgILN{H
zF_>6OPNGI({!`Q;ue;ZV;H9T98N8SJ#F$9_R
zRn05%o`B{etWm7O1lVKx()1z`4apcTi@17gI?^%?x|_-zZU{dxXU%@l3fsD8u9UTS~l~0G7cjs49P1sfQ@A
zvfjgr!5`;T1s70a-pB@6C>gL)LXUWx`DclK3!)q<2|-`x;s;CS72yf#U)WUk1)8#(g1@9pcws*S>^bA1
z721ts94!BQL1RutFJCW?Z>X$QZcfNx3~KxK@Eeehf^wFn*TeAX&J
zcqb&_g?3U;SKgtWLP1A6)C1v`0#5Te5utn;L+s=!>C{KaQ2q)A$`m3Yg`ng=JeXj{
zpG}@2RE4MZ_k)9Baq{wqC<7@|r+Z?6AQnku=1T-VX3FT?_^}Xw8=TxaQCid-1Oq3q
zpoTp`DjU=TP_P03iAHppgf3Cpb&9(77{Ig2u)iJSOopT^lc#y$CRG=z8_yzJE7@af
z3KRdt+Jqt(sYk@83OAw0gK64~5u(-4f<2ZN>ZHR2QC_CVT={>{wf-YuL11r)%F0(W
zjnS(@zbJ%uHU`$7BxGc-
z&wyKrVy^#a?q(yi>%0(_=1r6GR+WG4kAMD6*xmjNIFDAe`wy(|pD4_mUM$jS`>c!w
zoxc>!e}XnY|1)5VENA0?k$
Date: Tue, 11 Oct 2022 11:13:44 -0400
Subject: [PATCH 2/5] docs: sync fork
---
README.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/README.md b/README.md
index ef6cc64..dfea619 100644
--- a/README.md
+++ b/README.md
@@ -63,6 +63,8 @@ If your lab plans on deploying this task to your onw Firebase, but you do not ex
. When forking the repository you may be asked to install GitHub Desktop App. This is a convenient way to do it, so follow those instructions.
+2. If your fork is out of sync, you can syn it following [these instructions](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)
+
2. Create a Firebase project
3. Install the Firebase Command Line Tools . Instructions [here](https://firebase.google.com/docs/cli)
From 911e1b746a30fa566dcc088003dfab7ec62b95eb Mon Sep 17 00:00:00 2001
From: Maria Isabel Restrepo
Date: Tue, 11 Oct 2022 11:47:34 -0400
Subject: [PATCH 3/5] docs: firebase details
---
README.md | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/README.md b/README.md
index dfea619..99c4abd 100644
--- a/README.md
+++ b/README.md
@@ -59,10 +59,15 @@ Once you have deleted both of these .json files, you should be able to use a Sub
If your lab plans on deploying this task to your onw Firebase, but you do not expect to develop further changes and only deploy changes as developed by Brown, follow the following instructions
-1. Fork the repository https://github.com/lnccbrown/task-effort.git. Forking only the main branch should is sufficient
+1. Fork the repository https://github.com/lnccbrown/task-effort.git.
+
. When forking the repository you may be asked to install GitHub Desktop App. This is a convenient way to do it, so follow those instructions.
+* Forking only the main branch is sufficient
+* When forking it will ask you how you'll be using this fork. Select, for my own purposes
+
+
2. If your fork is out of sync, you can syn it following [these instructions](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)
2. Create a Firebase project
@@ -79,6 +84,8 @@ In Github Desktop App, select Branch -> New. Type your lab name, and select to s
6. Fill-in the details for your Firebase project in the `env/.env.firebase-` file
+You can follow the instructions detailed [here](https://brown-ccv.github.io/honeycomb-docs/docs/firebase#3-copying-web-app-credentials)
+
7. Commit and push your changes.
8. Use Firebase CLI to create a service account
From 9308b74861eb4b53697d4dee4575e407d7e7ad88 Mon Sep 17 00:00:00 2001
From: Maria Isabel Restrepo
Date: Tue, 11 Oct 2022 11:57:53 -0400
Subject: [PATCH 4/5] docs: firebaserc changes
---
README.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/README.md b/README.md
index 99c4abd..d0a6bc5 100644
--- a/README.md
+++ b/README.md
@@ -86,6 +86,8 @@ In Github Desktop App, select Branch -> New. Type your lab name, and select to s
You can follow the instructions detailed [here](https://brown-ccv.github.io/honeycomb-docs/docs/firebase#3-copying-web-app-credentials)
+7. Change the project-id inside the `.firebaserc` file to correspond to your firebase project
+
7. Commit and push your changes.
8. Use Firebase CLI to create a service account
From f58486b70290879f0a6f0ac19a99d2f09a86eb86 Mon Sep 17 00:00:00 2001
From: Maria Isabel Restrepo
Date: Wed, 26 Oct 2022 15:27:40 -0400
Subject: [PATCH 5/5] docs: moved firebase instructions to Wiki
---
README.md | 66 +++++-----------------------------------------
create-branch.png | Bin 21563 -> 0 bytes
fork.png | Bin 26264 -> 0 bytes
3 files changed, 7 insertions(+), 59 deletions(-)
delete mode 100644 create-branch.png
delete mode 100644 fork.png
diff --git a/README.md b/README.md
index d0a6bc5..2ee9a7a 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@
This repo contains the Effort task. It is a [jspsych](https://www.jspsych.org/) task built with React and Electron. This task uses the [HoneyComb V1](https://brown-ccv.github.io/honeycomb-docs/docs/1.1.0).
-## Running Desktop Task
+## Desktop Task
### Behavioral Only
@@ -21,7 +21,7 @@ Go to the releases tab (https://github.com/lnccbrown/task-effort/releases) and d
In addition, follow instructions on the repo Wiki to set the port name:
https://github.com/lnccbrown/task-effort/wiki/Task-Effort-Running-Notes-(EEG)
-## Quitting the task
+### Quitting the task
If you want to quit in the middle of the task, you can use these keyboard shortcuts:
@@ -35,7 +35,7 @@ Cmd+Q (for Mac)
Partial data will be saved.
-## Reusing participant ID
+### Reusing participant ID
If you want to overwrite a subject's data file:
@@ -55,64 +55,12 @@ Once you have succesfully navigated to the corresponding location, delete the .j
Once you have deleted both of these .json files, you should be able to use a SubjectID you have used in the past.
-# Deploying identical task to your own Firebase project
+## Firebase
-If your lab plans on deploying this task to your onw Firebase, but you do not expect to develop further changes and only deploy changes as developed by Brown, follow the following instructions
+This task is deployed via GitHub Actions to Firebase. During development (on this repository), when you open a PR, a preview link of the app is deployed to Firebase. When you merge to `main` branch, the main URL gets updated
-1. Fork the repository https://github.com/lnccbrown/task-effort.git.
-
-
-. When forking the repository you may be asked to install GitHub Desktop App. This is a convenient way to do it, so follow those instructions.
-
-* Forking only the main branch is sufficient
-* When forking it will ask you how you'll be using this fork. Select, for my own purposes
-
-
-2. If your fork is out of sync, you can syn it following [these instructions](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)
-
-2. Create a Firebase project
-
-3. Install the Firebase Command Line Tools . Instructions [here](https://firebase.google.com/docs/cli)
-
-4. Make a new branch to host your Firebase details
-
-In Github Desktop App, select Branch -> New. Type your lab name, and select to start it from `main`
-
-
-
-5. Open the repository, and make sure you are in your lab's branch
-
-6. Fill-in the details for your Firebase project in the `env/.env.firebase-` file
-
-You can follow the instructions detailed [here](https://brown-ccv.github.io/honeycomb-docs/docs/firebase#3-copying-web-app-credentials)
-
-7. Change the project-id inside the `.firebaserc` file to correspond to your firebase project
-
-7. Commit and push your changes.
-
-8. Use Firebase CLI to create a service account
-
-With the terminal open in your branch, type
-
-```
-firebase login
-```
-
-Then type:
-
-```
-firebase init hosting:github
-```
-
-This will alter existing actions. You will need to discard those changes. However, this will create a service account as a secret in your github project that will be used for deployment. To confirm, in GitHub visit Settings -> Secrets
-
-9. Deploy
-
-Go to the actions Tab.
-
-Hit firebase-deploy-merge-demand
-
-Choose your lab's branch. If you are testing choose `qa` channel. If you want to go live, choose `live` channel.
+### Information for labs other than LNCC
+If your lab plans on deploying this task to your own Firebase, but you do not expect to develop further changes and only deploy changes as developed by LNCC, follow [these instructions in the Wiki](https://github.com/lnccbrown/task-effort/wiki/Deploying-a-fork-to-Firebase)
# Developer only Instructions
diff --git a/create-branch.png b/create-branch.png
deleted file mode 100644
index d99f945ffb71769881ca95aea2ff637256b86b00..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001
literal 21563
zcmdqIWmsHMvo1(*3Bldn-KFv1?k>TCyERS-1ShyV!686!hu{`GxVyW?K#hHTP%_p(}5wQ9Zfu1%P-q7*VBJ|YAJ1hR~@genBYyD-rGH9Rcn|3X=WS_lZl
zbt`dkWf^gCQe|fc3oBc52ngx0#AG;iwL$!V-IXiJfM9rOgf@gp1X8Li2*^oMbun~l
zS~6;An3kHxpt7KEoNn*5K4R({ysIX|E~n)_LaL#qJ^a)aGGw@h=6;)byW;fYK6hYXLrQH9?4uQA9Xw}$(!@xF^>E=5KD$