Conversation
Contributor
lamchau
reviewed
Oct 7, 2024
lily-de
force-pushed
the
ldelalande/fix-deploy-docs
branch
from
9faf206 to
4ec2279
Compare
lily-de
commented
Oct 8, 2024
lily-de
commented
Oct 8, 2024
lily-de
commented
Oct 8, 2024
lily-de
commented
Oct 8, 2024
lily-de
commented
Oct 8, 2024
baxen
approved these changes
Oct 8, 2024
Collaborator
baxen
left a comment
baxen
left a comment
There was a problem hiding this comment.
LGTM!
Can be a separate PR but i think in the future we should try to use https://facelessuser.github.io/pymdown-extensions/extensions/snippets/
to include the readme literal so we don't risk them growing out of sync
Contributor
Author
|
Added a follow up ticket to better sync the readme and docs homepage: linear (for internal tracking); github issue |
lukealvoeiro
added a commit
that referenced
this pull request
Oct 9, 2024
* main: (41 commits) chore: Add goose providers list command (#116) docs: working ollama for desktop (#125) docs: format and clean up warnings/errors (#120) docs: update deploy workflow (#124) feat: Implement a goose run command (#121) feat: saved api_key to keychain for user (#104) docs: add callout plugin (#119) chore: add a page to docs for Goose application examples (#117) fix: exit the goose and show the error message when provider environment variable is not set (#103) fix: Update OpenAI pricing per https://openai.com/api/pricing/ (#110) fix: update developer tool prompts to use plan task status to match allowable statuses update_plan tool call (#107) fix: removed the panel in the output so that the user won't have unnecessary pane borders in the copied content (#109) docs: update links to exchange to the new location (#108) chore: setup workspace for exchange (#105) fix: resolve uvx when using a git client or IDE (#98) ci: add include-markdown for mkdocs (#100) chore: fix broken badge on readme (#102) feat: add global optional user goosehints file (#73) docs: update docs (#99) chore(release): release 0.9.3 (#97) ...
ahau-square
pushed a commit
that referenced
this pull request
Oct 10, 2024
* main: feat: add groq provider (#134) feat: add a deep thinking reasoner model (o1-preview/mini) (#68) fix: use concrete SessionNotifier (#135) feat: add guards to session management (#101) fix: Set default model configuration for the Google provider. (#131) test: convert Google Gemini tests to VCR (#118) chore: Add goose providers list command (#116) docs: working ollama for desktop (#125) docs: format and clean up warnings/errors (#120) docs: update deploy workflow (#124) feat: Implement a goose run command (#121)
ahau-square
pushed a commit
that referenced
this pull request
May 2, 2025
Co-authored-by: damienrj <damien@squareup.com>
cbruyndoncx
pushed a commit
to cbruyndoncx/goose
that referenced
this pull request
Jul 20, 2025
Co-authored-by: damienrj <damien@squareup.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was wrong
Solution
thanks @lamchau @lukealvoeiro and @damienrj for working with me on this!