Add Gitea / Forgejo Issues backlog manager#512
Open
SimonBlancoE wants to merge 1 commit intomattpocock:mainfrom
Open
Add Gitea / Forgejo Issues backlog manager#512SimonBlancoE wants to merge 1 commit intomattpocock:mainfrom
SimonBlancoE wants to merge 1 commit intomattpocock:mainfrom
Conversation
|
Someone is attempting to deploy a commit to the Matt Pocock's projects Team on Vercel. A member of the Team first needs to authorize it. |
This was referenced May 1, 2026
|
Awesome. There is also a seperate |
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
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.
Summary
Adds a new
Gitea / Forgejo Issuesbacklog manager forsandcastle init, powered by theteaCLI.This lets users scaffold the existing Sandcastle issue-based workflows against Gitea-compatible forges, including Forgejo, without manually rewriting generated prompts or sandbox setup.
What changed
Adds a
gitea-issuesbacklog manager option.Installs the
teaCLI in generated Dockerfile/Containerfile output.Generates
.sandcastle/.env.exampleentries for:Runs
tea logininside the sandbox at startup, after.sandcastle/.envhas been loaded.Substitutes generated prompt commands for listing, viewing, commenting on, and closing issues via
tea.Supports optional
Sandcastlelabel creation for Gitea / Forgejo.Keeps the existing GitHub Issues and Beads flows intact.
Documents the new backlog manager and adds a patch changeset.
Setup note
After running
sandcastle initwithGitea / Forgejo Issues, users need to set these values in.sandcastle/.env:The generated sandbox setup uses those values to authenticate
teabefore the agent reads or updates issues.Manual testing
I manually tested this successfully against a project hosted on Forgejo. The generated setup was able to authenticate with
tea, read issues from the Forgejo project, and use the generated workflow as the issue tracker backend.Test plan
npx vitest run src/InitService.test.tsnpx prettier --check README.md src/InitService.ts src/InitService.test.ts src/cli.ts .changeset/gitea-forgejo-tea-backlog.mdgit diff --check origin/main..HEADNotes
I found no
CONTRIBUTING.mdor pull request template in the repository. I followed the local repository guidance inCLAUDE.mdby adding a patch changeset and updating the README for the user-facing behavior.