Skip to content

add command running warning #4

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.

Sign up for GitHub

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

Merged
michaelneale merged 2 commits into from
Aug 24, 2024
Merged

add command running warning #4

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c85112
Update README.md
michaelneale Aug 24, 2024
89f9acc
command note
michaelneale Aug 24, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,7 @@ Here are some collected tips we have for working efficiently with Goose

- **goose can and will edit files**. Use a git strategy to avoid losing anything - such as staging your
personal edits and leaving goose edits unstaged until reviewed. Or consider using indivdual commits which can be reverted.
- **goose can and will run commands**. You can ask it to check with you first if you are concerned. It will check commands for safety as well.
- You can interrupt goose with `CTRL+C` to correct it or give it more info.
- goose works best when solving concrete problems - experiment with how far you need to break that problem
down to get goose to solve it. Be specific! E.g. it will likely fail to `"create a banking app"`,
Expand Down