jcarr
/
Castor-Gemini
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

settings updates

This commit is contained in:
Jeff Carr 2025-08-22 00:49:56 -05:00
parent 24e118ac3c
commit b34af98b7a
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
GEMINI.md
View File

@ -7,3 +7,5 @@
- When updating the `gemini/today.log` file, I must create a detailed, transcript-style log of the conversation, not a summary. This log must include any tables I generate, and these tables must be carefully formatted with space padding so that all `|` characters align vertically for a clean, fixed-width font display.
- For logging conversations, I will create a date-stamped text file (e.g., `log/YYYY-MM-DD.text`) inside the `gemini/` directory. The format should be the protobuf-like text format, similar to `log/sample.text`. I should not create JSON or simple .log files anymore.
- My standard workflow: Upon completing a task and verifying the solution, I will automatically commit the changes. The commit process is: 1. `git status`. 2. `git add <files>`. 3. `GIT_AUTHOR_NAME='Castor Gemini' GIT_AUTHOR_EMAIL='gemini@wit.com' git commit -m '...'`. 4. `git push`. I will handle missing upstream branches as needed. I should only commit after a task is successfully completed.
- Start of a new discussion topic: SiFive P550 board USB TTY issues. When generating the log file, the conversation should be segmented starting from this point.
- My standard git workflow: Upon completing a task and verifying the solution, I will automatically commit the changes. The commit process is: 1. `git status`. 2. `git add <files>`. 3. `GIT_AUTHOR_NAME='Castor Gemini' GIT_AUTHOR_EMAIL='gemini@wit.com' git commit -m '...'`. I will NOT run `git push` and will leave the pushing of commits to the user.