fix: 🔧 untrack machine-specific .mcp.json, ship portable template #264
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human-required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!264
Loading…
Reference in a new issue
No description provided.
Delete branch "synath/fix/untrack-local-mcp-json"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
.mcp.jsonis listed in.gitignore(line 47) but is still tracked in the repo. The two never reconcile, so a developer-specific config keeps shipping to everyone and overwrites local copies ongit pull.The committed copy also doesn't work on anyone else's machine:
codeberghardcodes/home/goern/go/bin/forgejo-mcp— an absolute path under a specific home directory.codeberg-develuses a relative./forgejo-mcpthat only resolves when the launcher's working directory is the repo root (notably breaks across git worktrees).Fix
git rm --cached .mcp.json— stop tracking it, which is what the existing.gitignoreentry already intends. Each developer keeps their own local copy..mcp.json.exampleas the portable reference:codeberg→ PATH-resolvedforgejo-mcpinstead of a hardcoded home dir (works for anyone who has it installed, including a~/go/binon PATH).codeberg-devel→${FORGEJO_MCP_BIN:-./forgejo-mcp}so a locally built binary can be referenced by absolute path from any directory/worktree, defaulting to the in-repo build.FORGEJO_ACCESS_TOKENenvironment variable rather than a--tokenargument, so it never appears in process listings (the binary already prefers this env var —cmd/cmd.go).DEVELOPER.md.Notes
No code changes — config and docs only. Existing checkouts that already have a tracked
.mcp.jsonkeep their working copy after pulling this (the file is untracked, not deleted).🤖 Generated with Claude Code
op1st Pipelines as Code is skipping this commit.
User synath is not allowed to trigger CI via pull_request in this repo.
/ok-to-test
op1st Pipelines as Code/forgejo-mcp-code-scans-zlzp9 is running.
Starting Pipelinerun forgejo-mcp-code-scans-zlzp9 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-zlzp9 -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-m5dbd is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-m5dbd in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-m5dbd -fop1st Pipelines as Code/forgejo-mcp-code-scans-zlzp9 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-on-pull-request-m5dbd has failed.
Task Statuses:
fetch-source
build-and-test
commit-title-check
Failure snippet:
task build-and-test has the status "Failed":/triage
op1st Pipelines as Code/forgejo-mcp-code-scans-bfcjg is running.
Starting Pipelinerun forgejo-mcp-code-scans-bfcjg in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-bfcjg -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-ldhs6 is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-ldhs6 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-ldhs6 -fop1st Pipelines as Code/forgejo-mcp-code-scans-bfcjg has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
Investigated the June CI failure: the
build-and-testtask failed at its gofmt-check step becauseoperation/hook/hook.gowas unformatted on the base branch at the time (misaligned const block from the then-new webhook tools) — not something this PR introduced. It was since fixed on main in16f807c, so the failure no longer reproduces.The branch has now been rebased onto current main (head
5af6226, same single commit); build, vet, mod-tidy, gofmt, and race tests all pass locally on it. Could you/ok-to-testagain?(Posted by synath's Claude agent on David's behalf — the investigation and rebase were agent work.)
op1st Pipelines as Code/forgejo-mcp-on-pull-request-ldhs6 has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.