-
Notifications
You must be signed in to change notification settings - Fork 2.7k
docs: Add running Goose in CI tutorial #1426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
documentation/docs/tutorials/cicd.md
Outdated
|
|
||
| ## Using Goose with CI-Specific MCP Servers | ||
|
|
||
| If your workflow involves custom environments or tools, you can extend Goose by integrating it with MCP servers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how? i think we should show a small example of how to configure one. i cant envision myself how to do it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Took it out for now. What I had in mind was much similar to the earlier, more manual GitHub CLI flow - to be able to get or act on the jobs / processes in the CI.
* main: feat: parallel processing in approve mode (#1575) Feat: support auto-including dirs in binary/bench-work-dir (#1576) refactor models component (#1535) docs: Add running Goose in CI tutorial (#1426) chore: remove logging of oauth config, just log where we output (#1573) feat: implement a tool permission store (#1516) minor typo (#1569) fix: open new session in working dir when hotkey is pressed (#1570) feat: store working directory for sessions (#1559) docs: extension timeout (#1567) fix: update openrouter referer website to point to github page site (#1566) feat(cli): add --debug flag to goose session / run (#1564)
Co-authored-by: angiejones <jones.angie@gmail.com>
Co-authored-by: angiejones <jones.angie@gmail.com>
Co-authored-by: angiejones <jones.angie@gmail.com>
This pull request includes substantial updates to the documentation, specifically adding a new tutorial for running Goose in CI/CD environments. It also includes a minor fix in the Docusaurus configuration file.
Documentation Updates:
documentation/docs/tutorials/running-goose-cicd.md: Added a comprehensive tutorial on setting up Goose in CI/CD pipelines, including use cases, GitHub CLI usage, GitHub Actions integration, and security considerations.