-
Notifications
You must be signed in to change notification settings - Fork 30
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
feat: jira toolkit #59
Merged
Merged
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
michaelneale
commented
Sep 11, 2024
@@ -0,0 +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. |
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.
this seemed to make a HUGE practical difference to goose.
baxen
approved these changes
Sep 12, 2024
src/goose/toolkit/jira.py
Outdated
|
||
def system(self) -> str: | ||
"""Retrieve detailed configuration and procedural guidelines for Jira operations""" | ||
return Message.load("prompts/jira.jinja").text |
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.
I think we need to pass os= here for the prompt jinja to work
Co-authored-by: Bradley Axen <baxen@squareup.com>
Kvadratni
added a commit
to Kvadratni/goose
that referenced
this pull request
Sep 23, 2024
* origin/main: docs: add in ollama (block#82) chore: add just command for releasing goose (block#55) feat: support markdown plans (block#79) feat: add version options (block#74) docs: fixing exchange url to public version (block#67) docs: Update CONTRIBUTING.md (block#69) chore: create mkdocs for goose (block#70) docs: fix broken link (block#71) feat: give commands the ability to execute logic (block#63) feat: jira toolkit (block#59) feat: run goose in a docker-style sandbox (block#44)
lily-de
pushed a commit
that referenced
this pull request
Oct 7, 2024
Co-authored-by: Bradley Axen <baxen@squareup.com>
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.
To try this out:
add this to your ~/.config/goose/profiles.yaml
Then run
uv run goose session start --profile jira
from this branch.This will give you a goose shell and you can tell it what dir you want to operate in, ask questions, mention JIRA things and see how it goes for you.
and you can ask it about backlogs, issues, even to look for issues it can work on and more.