Compare commits
2 commits
4d799b1c0a
...
3b88cac922
| Author | SHA1 | Date | |
|---|---|---|---|
| 3b88cac922 | |||
| 85e6cb50c2 |
2 changed files with 36 additions and 0 deletions
10
INBOX
Normal file
10
INBOX
Normal file
|
|
@ -0,0 +1,10 @@
|
||||||
|
[Judah]
|
||||||
|
Put any questions for me in here!
|
||||||
|
|
||||||
|
[Jesse]
|
||||||
|
05.22.25 Judah
|
||||||
|
Instead of going with a separate 'arch' module, I
|
||||||
|
think we can roll that into the future 'platform'
|
||||||
|
module instead. There's enough overlap that I
|
||||||
|
think it makes sense. Let me know what you think,
|
||||||
|
thanks!
|
||||||
26
STYLEGUIDE
26
STYLEGUIDE
|
|
@ -37,6 +37,32 @@ message should only say 'finish [id]'.
|
||||||
start 034
|
start 034
|
||||||
|
|
||||||
|
|
||||||
|
Communication
|
||||||
|
-------------
|
||||||
|
|
||||||
|
If direction is needed, create a single commit with an
|
||||||
|
entry in 'INBOX' under that person's section; the commit
|
||||||
|
message should roughly say 'message for [name]'.
|
||||||
|
|
||||||
|
Use this as a base plate to write new messages:
|
||||||
|
|
||||||
|
[ToName]
|
||||||
|
05.22.25 FromName ** This is a question **
|
||||||
|
Lorem ipsum dolor sit amet, consectetur
|
||||||
|
adipisicing elit, sed do eiusmod tempor
|
||||||
|
incididunt ut labore et dolore magna aliqua.
|
||||||
|
05.22.25 ToName ** This is a response **
|
||||||
|
Excepteur sint occaecat cupidatat non proident,
|
||||||
|
sunt in culpa qui officia deserunt mollit anim
|
||||||
|
id est laborum.
|
||||||
|
|
||||||
|
If an immediate response is needed, opt for a direct
|
||||||
|
message.
|
||||||
|
|
||||||
|
Additionally, it is your responsibility to check and push
|
||||||
|
to 'INBOX'. Think of it like an email.
|
||||||
|
|
||||||
|
|
||||||
Writing Code
|
Writing Code
|
||||||
------------
|
------------
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue