chore: initialize fullsend per-repo installation - #96
Open
em-redhat wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds the fullsend scaffold files for per-repo installation.
Merge this PR to activate fullsend workflows.
Runtime
Agents in this repository run on claude (
runtime:in.fullsend/config.yaml). To change it later, edit that key, re-runfullsend github setup <owner/repo> --runtime <claude|pi>, or override a single run withfullsend run --runtime. To put one agent on another runtime or model, set runtime/model/effort on itsagents:entry in the same file (fullsend agent set <name> --runtime pi). See https://github.com/fullsend-ai/fullsend/blob/main/docs/runtimes.md.