Conversation
|
|
||
| **Usage:** | ||
| ```sh | ||
| goose session resume [NAME] [--profile PROFILE] |
There was a problem hiding this comment.
I don't remember if this exists, but if the profile doesn't have toolkits that were used in the session, there is potential for errors in the session. Maybe we put a warning here of this usage.
CONTRIBUTING.md
Outdated
| <p align="center"> | ||
| <a href="#prerequisites">Prerequisites</a> • | ||
| <a href="#evaluations">Evaluations</a> • | ||
| <a href="#developing-and-testing">Developing and testing</a> • | ||
| <a href="#building-from-source">Building from source</a> • | ||
| <a href="#developing-goose-plugins">Developing goose-plugins</a> • | ||
| <a href="#running-ai-exchange-from-source">Running ai-exchange from source</a> • | ||
| <a href="#evaluations">Evaluations</a> • | ||
| <a href="#conventional-commits">Conventional Commits</a> | ||
| </p> |
There was a problem hiding this comment.
This being centered throws be a bit off.
There was a problem hiding this comment.
was trying to save vertical space lol -- but don't disagree
CONTRIBUTING.md
Outdated
| **When to Add to Goose-Plugins:** | ||
|
|
||
| * Lighter Scrutiny: Plugins in goose-plugins undergo less thorough reviews compared to Goose. This repository is intended for more modular, optional, or experimental plugins that may not be critical to Goose’s core functionality. | ||
| * General, Reusable Plugins: If the plugin could be useful in a variety of contexts or is designed to extend Goose in a more optional way, it belongs in goose-plugins. This allows for faster iteration and easier contributions. |
There was a problem hiding this comment.
General, Reusable Plugins: If the plugin could be useful in a variety of contexts
I'm not sure if this is exactly correct - I think the difference is instead that plugins in Goose have to show value (via out eventual benchmarking performance), whereas ones in Goose-Plugins can be a bit more experimental and prove their worth there.
There was a problem hiding this comment.
Edited! lmk if that's better. Struggled with articulating this
zakiali
left a comment
zakiali
left a comment
There was a problem hiding this comment.
looks good! Happy to get this in and iterate
* origin/main: docs: add in ollama (block#82) chore: add just command for releasing goose (block#55) feat: support markdown plans (block#79) feat: add version options (block#74) docs: fixing exchange url to public version (block#67) docs: Update CONTRIBUTING.md (block#69) chore: create mkdocs for goose (block#70) docs: fix broken link (block#71) feat: give commands the ability to execute logic (block#63) feat: jira toolkit (block#59) feat: run goose in a docker-style sandbox (block#44)
3 participants
Created a symlink between
CONTRIBUTING.md(the one we should always update) anddocs/docs/contributing.md(so changes are reflected ?)