From 1002cd85a9e5a02d41211d7dc31c1c991895e23b Mon Sep 17 00:00:00 2001 From: j Date: Wed, 14 Jun 2023 23:46:00 +0200 Subject: [PATCH] Update page '6-14-2023 Cohort 1 Sync Notes' --- 6-14-2023 Cohort 1 Sync Notes.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/6-14-2023 Cohort 1 Sync Notes.md b/6-14-2023 Cohort 1 Sync Notes.md index 54c5085..870f385 100644 --- a/6-14-2023 Cohort 1 Sync Notes.md +++ b/6-14-2023 Cohort 1 Sync Notes.md @@ -12,3 +12,5 @@ Sloetjes is still unable to connect to the docker container, see #3 * Mentioned that git commit messages should reference issues (#number). Issues are linked to commits automatically when they're referenced in a commit message, and the commit appears in the issue timeline. * Don't begin a git comment with an issue reference, because `#` is a comment character in that context. * Tested issue linking from git commit comments, it works fine and appears in the issue timeline. +* Mystery: why do the issue numbers in the repository's issue view sometimes have a green background? We all refreshed the page, and saw it flip from green to black for some reason. +* Karen somehow got X Windows running *by herself* to remote the Chrome windows onto her Windows desktop. Impressive. I mentioned that having documentation on how to set it up in the wiki, or even better, a Powershell script to automate the setup, would be better than just doing it. \ No newline at end of file