fix: resolve uvx when using a git client or IDE #98
Conversation
This file contains 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
lamchau
requested review from
lily-de,
baxen,
michaelneale,
salman1993,
zakiali,
ahau-square,
elenazherdeva,
lifeizhou-ap and
lukealvoeiro
lamchau
force-pushed
the
lam/commit-hooks
branch
from
d7fd39f to
dae22b1
Compare
ahau-square
approved these changes
Sep 30, 2024
lily-de
pushed a commit
that referenced
this pull request
Oct 7, 2024
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) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When using a client and/or IDE with
gitintegration built in, it's difficult to see a failedruffcommands until after a commit is pushed up. This change adds the ability to see those errors in your client and/or editors if you have the pre-commit hooks installed.Note: This is purely opt-in (
just install-hooks) and a user can bypass with--no-verifyafter it's installed. n.b. this pre-commit hook does have the potential to "lose" a commit message but many clients save the most recent commit (.git/COMMIT_EDITMSG) but this is generally a bug with thegitclient/implementation itself.git-fork
Before
After
lazygit