fix: switch to development branch before adding issue comments
The MCP server's branch-aware security blocks write operations on protected branches (main, fix/*, etc). After pushing a feature branch and creating a PR, we must switch back to development before adding comments to issues via MCP tools.
This commit is contained in:
@@ -312,7 +312,12 @@ git push -u origin fix/issue-[NUMBER]-[brief-description]
|
|||||||
|
|
||||||
3. Create PR via API or MCP tools
|
3. Create PR via API or MCP tools
|
||||||
|
|
||||||
4. Add comment to original issue:
|
4. **Switch back to development branch** (required for MCP issue operations):
|
||||||
|
```bash
|
||||||
|
git checkout development
|
||||||
|
```
|
||||||
|
|
||||||
|
5. Add comment to original issue:
|
||||||
```
|
```
|
||||||
mcp__plugin_projman_gitea__add_comment(
|
mcp__plugin_projman_gitea__add_comment(
|
||||||
repo=REPO_NAME,
|
repo=REPO_NAME,
|
||||||
|
|||||||
Reference in New Issue
Block a user