TapTap/FastSync
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Agents must never merge PRs onto main — use tea CLI instead #147

New Issue
Closed
opened 2026-07-29 18:12:07 +02:00 by TapTap · 1 comment
TapTap commented 2026-07-29 18:12:07 +02:00
Owner
Copy Link
Copy Source

Agents (AI/automation) must NEVER be allowed to merge a pull request onto the main branch. All merging must be done manually via the tea CLI tool.

Rules:

  1. No agent may issue a gh pr merge or any GitHub merge command.
  2. No agent may push directly to main.
  3. All PR merges must be performed by a human using tea (the Gitea CLI).
  4. CI must pass on the PR before merging.

This policy ensures that no automated system can bypass human review or break the main branch. Document this in AGENTS.md and enforce it in any agent instructions.

Agents (AI/automation) must NEVER be allowed to merge a pull request onto the `main` branch. All merging must be done manually via the `tea` CLI tool. Rules: 1. No agent may issue a `gh pr merge` or any GitHub merge command. 2. No agent may push directly to `main`. 3. All PR merges must be performed by a human using `tea` (the Gitea CLI). 4. CI must pass on the PR before merging. This policy ensures that no automated system can bypass human review or break the main branch. Document this in AGENTS.md and enforce it in any agent instructions.
TapTap commented 2026-07-29 18:27:25 +02:00
Author
Owner
Copy Link
Copy Source

This policy is now documented in AGENTS.md. Agents are instructed to never push to main and to use tea CLI for operations. Closing as resolved.

This policy is now documented in AGENTS.md. Agents are instructed to never push to main and to use tea CLI for operations. Closing as resolved.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Defect or bug
 enhancement
Feature or improvement
 memory
Memory safety issue
 needs-triage
Needs human review
 performance
Performance issue
 quality
Code quality improvement
 security
Security vulnerability
 threading
Threading or concurrency
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
TapTap
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: TapTap/FastSync#147
Delete Branch "%!s()"

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?