Skip to content

chore: Greptile deep-label repo config (plan 028) - #7

Closed
zen-agents[bot] wants to merge 1 commit into
masterfrom
chore/greptile-config-20260724T062650Z
Closed

chore: Greptile deep-label repo config (plan 028)#7
zen-agents[bot] wants to merge 1 commit into
masterfrom
chore/greptile-config-20260724T062650Z

Conversation

@zen-agents

@zen-agents zen-agents Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Adds .greptile/config.json so Greptile only runs on review:deep App-authored PRs.

  • labels: review:deep only
  • includeAuthors: org App bots
  • excludeAuthors: non-implementation bots
  • triggerOnUpdates: false
  • commentTypes: logic, syntax
  • ignorePatterns: lockfiles/dist/.next/node_modules
  • autoApprove: off
  • statusCheck: on

Org Flex Usage Limit is $0. CodeRabbit remains the standard path (labels review:standard + review:deep via central coderabbit config).

Summary by CodeRabbit

  • Chores
    • Added repository review configuration, including review strictness, status checks, comment types, and review labels.
    • Configured automated review triggers, file-change limits, author filters, and ignored files.
    • Disabled automatic description updates and automatic approval.

Plan 028: org Reviews UI cannot set commentTypes/ignorePatterns.
Repo config enforces review:deep-only, App authors, no auto on updates,
status checks, and lockfile/dist ignores. Flex $0 already set org-wide.
@greptile-apps

greptile-apps Bot commented Jul 24, 2026

Copy link
Copy Markdown

Required label not found on this PR.

@zen-agents zen-agents Bot added the review:standard One CodeRabbit review at the ready tip label Jul 24, 2026
@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Adds a complete .greptile/config.json configuration with review settings, author filters, update triggers, file exclusions, status checks, description behavior, and disabled auto-approval.

Changes

Greptile configuration

Layer / File(s) Summary
Configure Greptile review behavior
.greptile/config.json
Defines review strictness, comment types, labels, author inclusion and exclusion lists, update triggering, status checks, file limits, ignore patterns, description updates, and auto-approval behavior.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly reflects the main change: adding Greptile repository config for deep review labeling.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/greptile-config-20260724T062650Z

Comment @coderabbitai help to get the list of available commands.

@zen-agents zen-agents Bot closed this Jul 24, 2026
@zen-agents
zen-agents Bot deleted the chore/greptile-config-20260724T062650Z branch July 24, 2026 06:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review:standard One CodeRabbit review at the ready tip

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants