Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions AGENTS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# Agent Guidelines

When you need to create branches, make commits, or open pull requests, read
[CONTRIBUTING.md](CONTRIBUTING.md) first. No need to read it for code exploration —
only when interacting with git.
1 change: 1 addition & 0 deletions CLAUDE.md
28 changes: 28 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# Contributing

## Overview

This repo contains the shared AI review GitHub Actions workflow used across Jitsu repos.

## Development Branch

The default development branch is `main`.

## Common Principles

**Branch naming:** Use a type prefix — `feat/`, `fix/`, `chore/`.
Example: `feat/add-security-checks`.

**Merging policy:** We avoid merge commits. Always rebase onto the default branch —
never merge the default branch into a branch. For PRs, merge with full history preserved
— no squash merge. It's fine to squash overly granular commits within a branch locally
before opening a PR.

**Commit style:** [Conventional commits](https://www.conventionalcommits.org/) —
`type(scope): description`. Common types: `fix`, `feat`, `chore`, `refactor`, `ci`.

## PRs vs Direct Commits

Trivial changes, bug fixes, and config updates go directly to `main`. Larger or riskier
changes use pull requests. The engineer decides based on complexity and risk. AI review
runs on every push and PR.
Loading