Merge remote-tracking branch 'origin/main' into o1-reasoner

.github/workflows/deploy_docs.yaml

@@ -0,0 +1,36 @@
+name: Deploy MkDocs
+
+on:
+  push:
+    branches:
+      - main  # Trigger deployment on pushes to main
+    paths:
+      - 'docs/**'
+      - 'mkdocs.yml'
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v3
+
+    - name: Set up Python
+      uses: actions/setup-python@v4
+      with:
+        python-version: '3.x'
+
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install mkdocs mkdocs-material
+
+    - name: Build the documentation
+      run: mkdocs build
+
+    - name: Deploy to GitHub Pages
+      uses: peaceiris/actions-gh-pages@v3
+      with:
+        github_token: ${{ secrets.GITHUB_TOKEN }}
+        publish_dir: ./site

.goosehints

@@ -1,3 +1,3 @@
 This is a python CLI app that uses UV. Read CONTRIBUTING.md for information on how to build and test it as needed.
 Some key concepts are that it is run as a command line interface, dependes on the "ai-exchange" package, and has the concept of toolkits which are ways that its behavior can be extended. Look in src/goose and tests.
-Once the user has UV installed it should be able to be used effectively along with uvx to run tasks as needed
+Once the user has UV installed it should be able to be used effectively along with uvx to run tasks as needed

CHANGELOG.md

@@ -5,6 +5,32 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.9.3] - 2024-09-25
+
+- feat: auto save sessions before next user input (#94)
+- fix: removed the diff when default profile changes (#92)
+- feat: add shell-completions subcommand (#76)
+- chore: update readme! (#96)
+- chore: update docs again (#77)
+- fix: remove overly general match for long running commands (#87)
+- fix: default ollama to tested model (#88)
+- fix: Resize file in screen toolkit (#81)
+- fix: enhance shell() to know when it is interactive (#66)
+- docs: document how to run goose fully from source from any dir (#83)
+- feat: track cost and token usage in log file (#80)
+- chore: add link to docs in read me (#85)
+- docs: add in ollama (#82)
+- chore: add just command for releasing goose (#55)
+- feat: support markdown plans  (#79)
+- feat: add version options (#74)
+- docs: fixing exchange url to public version (#67)
+- docs: Update CONTRIBUTING.md (#69)
+- chore: create mkdocs for goose (#70)
+- docs: fix broken link (#71)
+- feat: give commands the ability to execute logic (#63)
+- feat: jira toolkit (#59)
+- feat: run goose in a docker-style sandbox (#44)
+
 ## [0.9.0] - 2024-09-10
 
 This also updates the minimum version of exchange to 0.9.0.

CONTRIBUTING.md

@@ -2,7 +2,6 @@
 
 <p>
 <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> •
@@ -37,7 +36,7 @@ Plugins added directly to Goose are subject to rigorous review. This is because
 
 Plugins in `goose-plugins` undergo less detailed reviews and are more modular or experimental. They can prove their value through usage or iteration over time and may be eventually moved over to Goose.
 
-To see how to add a toolkit, see the [toolkits documentation][toolkits].
+To see how to add a toolkit, see the [toolkits documentation][adding-toolkit].
 
 ### Running tests
 ```sh
@@ -56,7 +55,7 @@ If you want to develop features on `goose`:
 
 1. Clone Goose:
  ```bash
- git clone [email protected]:square/goose.git ~/Development/goose
+ git clone [email protected]:block-open-source/goose.git ~/Development/goose
  ```
 2. Get `uv` with `brew install uv`
 3. Set up your Python virtualenv:
@@ -83,7 +82,7 @@ When you build from source you may want to run it from elsewhere.
 
 1. Clone the `goose-plugins` repo:
 ```bash
- git clone [email protected]:square/goose-plugins.git ~/Development/goose-plugins
+ git clone [email protected]:block-open-source/goose-plugins.git ~/Development/goose-plugins
 ```
 2. Follow the steps for creating a virtualenv in the `goose` section above
 3. Install `goose-plugins` in `goose`. This means any changes to `goose-plugins` in this folder will immediately be reflected in `goose`:
@@ -116,11 +115,11 @@ Additions to the [developer toolkit][developer] change the core performance, and
 
 This project follows the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification for PR titles. Conventional Commits make it easier to understand the history of a project and facilitate automation around versioning and changelog generation.
 
-[issues]: https://github.com/square/goose/issues
-[goose-plugins]: https://github.com/square/goose-plugins
+[issues]: https://github.com/block-open-source/goose/issues
+[goose-plugins]: https://github.com/block-open-source/goose-plugins
 [ai-exchange]: https://github.com/square/exchange
 [developer]: src/goose/toolkit/developer.py
 [uv]: https://docs.astral.sh/uv/
 [ruff]: https://docs.astral.sh/ruff/
 [just]: https://github.com/casey/just
-[toolkits]: docs/docs/toolkits.md
+[adding-toolkit]: https://block-open-source.github.io/goose/configuration.html#adding-a-toolkit