Skip to content

Add git workspace hygiene and Epoch data tracking rules#5

Merged
simongonzalezdc merged 1 commit into
mainfrom
add-git-hygiene-epoch-tracking
May 3, 2026
Merged

Add git workspace hygiene and Epoch data tracking rules#5
simongonzalezdc merged 1 commit into
mainfrom
add-git-hygiene-epoch-tracking

Conversation

@simongonzalezdc
Copy link
Copy Markdown
Member

@simongonzalezdc simongonzalezdc commented May 3, 2026

Org-wide rules: git cleanup discipline and Epoch data tracking mandate.


View in Codesmith
Need help on this PR? Tag @codesmith with what you need.

  • Let Codesmith autofix CI failures and bot reviews

@simongonzalezdc simongonzalezdc merged commit 02ab1f3 into main May 3, 2026
@simongonzalezdc simongonzalezdc deleted the add-git-hygiene-epoch-tracking branch May 3, 2026 19:39
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0d9f3a37be

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread AGENTS.md
### Git Workspace Hygiene
Agents must leave the repository in the same clean state they found it. No exceptions.

- **Delete feature branches** after merge — whether you merged via PR or locally. A merged branch that still exists is a failure.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Exempt pipeline-managed branches from cleanup rule

This new blanket requirement to delete all feature branches after merge conflicts with the existing Pipeline Awareness rule (AGENTS.md earlier section) that says fix/issue-* branches are pipeline-managed and must not be deleted. Keeping both rules will cause agents to follow contradictory guidance, and in the pipeline case can remove branches the automation expects to keep managing.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant