gitea/gitea-mcp
Fork 22
Code Issues 14 Pull Requests 2 Actions Projects Releases 15 Activity

docs(readme): rename interactive with insecure (#22)
All checks were successful
release-nightly / release-image (push) Successful in 3m19s
Details

Browse Source 
After #20, `GITEA_INSECURE` flag is introduced. However, the READMEs referred to the wrong name. Replace GITEA_INTERACTIVE terms with `GITEA_INSECURE`. Reviewed-on: #22 Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com> Co-authored-by: Flynn Hou <flynnhou7@gmail.com> Co-committed-by: Flynn Hou <flynnhou7@gmail.com>
This commit was merged in pull request #22.
This commit is contained in:
Flynn Hou
2025-04-08 05:20:16 +00:00
committed by techknowlogick
parent 1fecc1df30
commit 7cfa1fa218
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -109,7 +109,7 @@ To configure the MCP server for Gitea, add the following to your MCP configurati
],
"env": {
// "GITEA_HOST": "https://gitea.com",
// "GITEA_INTERACTIVE": "true",
// "GITEA_INSECURE": "true",
"GITEA_ACCESS_TOKEN": "<your personal access token>"
}
}

2
README.zh-cn.md
View File

@@ -109,7 +109,7 @@ cp gitea-mcp /usr/local/bin/
],
"env": {
// "GITEA_HOST": "https://gitea.com",
// "GITEA_INTERACTIVE": "true",
// "GITEA_INSECURE": "true",
"GITEA_ACCESS_TOKEN": "<your personal access token>"
}
}

2
README.zh-tw.md
View File

@@ -109,7 +109,7 @@ cp gitea-mcp /usr/local/bin/
],
"env": {
// "GITEA_HOST": "https://gitea.com",
// "GITEA_INTERACTIVE": "true",
// "GITEA_INSECURE": "true",
"GITEA_ACCESS_TOKEN": "<your personal access token>"
}
}