Skip to content

Add Greptile review config with UW Lab coding conventions - #34

Merged
UW-Lab-Bot merged 2 commits into
mainfrom
feature/greptile
Aug 29, 2026
Merged

Add Greptile review config with UW Lab coding conventions#34
UW-Lab-Bot merged 2 commits into
mainfrom
feature/greptile

Conversation

@UW-Lab-Bot

Copy link
Copy Markdown
Contributor

Description

Add a .greptile/ directory for Greptile to review PRs.

Type of change

  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read and understood the contribution guidelines
  • I have run the pre-commit checks with ./uwlab.sh --format
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • I have updated the changelog and the corresponding version in the extension's config/extension.toml file
  • I have added my name to the CONTRIBUTORS.md or my name already exists there

Add a .greptile/ directory so Greptile reviews PRs against the project's
conventions instead of only generic checks:

- config.json: restrict comments to logic/syntax (formatting is handled by
  pre-commit), set review priorities, and add scoped rules for extension
  version + CHANGELOG bumps, cross-script CLI flag consistency, vectorized
  mdp terms, gym registration entry points, self-contained task packages,
  new-task docs, optional research dependencies, submodule policy,
  machine-specific paths, committed artifacts, type hints, TYPE_CHECKING
  imports, bash shebangs, and new dependencies.
- rules.md: coding conventions adapted from Isaac Lab's contributing guide
  (file/class structure, type hints and docstrings, manager-based env
  conventions, task registration, adding a new task or publication,
  changelog format, tests, portability).
- files.json: point the reviewer at the PR template, pre-commit config,
  and .gitattributes for context.
@github-actions github-actions Bot added the enhancement New feature or request label Aug 29, 2026
Run ./uwlab.sh --format over the repository and commit the result so the
pre-commit CI check passes. Whitespace, import order, and end-of-file
fixes only; no functional changes.
@patrickhaoy
patrickhaoy requested a review from zoctipus as a code owner August 29, 2026 00:11
@github-actions github-actions Bot added documentation Improvements or additions to documentation core infrastructure labels Aug 29, 2026
@greptile-apps

greptile-apps Bot commented Aug 29, 2026

Copy link
Copy Markdown

Greptile Summary

Adds repository-level Greptile configuration and UW Lab review guidance.

  • Configures review categories, priorities, scoped rules, and ignored paths.
  • Provides contextual descriptions for the PR template, pre-commit configuration, and Git LFS attributes.
  • Documents conventions for scripts, extensions, tasks, dependencies, tests, versioning, and portability.

Confidence Score: 5/5

The PR appears safe to merge with no concrete actionable issues identified.

The changes add review-tool configuration and documentation, and the investigated claims about repository conventions did not establish a reachable incorrect behavior.

Important Files Changed

Filename Overview
.greptile/config.json Defines review behavior, priorities, ignore patterns, and repository-specific rules without an established actionable defect.
.greptile/files.json Registers three relevant repository files as additional review context.
.greptile/rules.md Documents UW Lab’s coding, task, dependency, testing, and release conventions consistently with the checked repository context.

Reviews (1): Last reviewed commit: "Add Greptile review config with UW Lab c..." | Re-trigger Greptile

@UW-Lab-Bot
UW-Lab-Bot merged commit f75eeaf into main Aug 29, 2026
3 of 7 checks passed
@UW-Lab-Bot
UW-Lab-Bot deleted the feature/greptile branch August 29, 2026 00:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core documentation Improvements or additions to documentation enhancement New feature or request infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants