SVIG/pricer
7
0
Fork 0
Code Issues 5 Pull Requests Releases Wiki Activity

Update page '6-14-2023 Cohort 1 Sync Notes'

j
2023-06-14 23:35:07 +02:00
parent 319c764024
commit 45cd678208
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
6-14-2023 Cohort 1 Sync Notes.md
+2 -1
@@ -9,5 +9,6 @@ Sloetjes is still unable to connect to the docker container, see #3
* Mentioned the MacOS text extraction feature * Mentioned the MacOS text extraction feature
* Asked to paste text instead of screenshots * Asked to paste text instead of screenshots
* Mentioned the issue number syntax convention (#number means an issue, repository#number means an issue in that repository) * Mentioned the issue number syntax convention (#number means an issue, repository#number means an issue in that repository)
* Mentioned that git commit messages should reference issues (#number), and issues should reference commits if necessary. * 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. * 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.