Appwrite pr-workflow

Name: pr-workflow
Author: appwrite

PR Workflow for Appwrite

install

source · Clone the upstream repo

git clone https://github.com/appwrite/appwrite

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/appwrite/appwrite "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/pr-workflow" ~/.claude/skills/appwrite-appwrite-pr-workflow && rm -rf "$T"

manifest: .claude/skills/pr-workflow/SKILL.md

PR Workflow for Appwrite

Branch Targeting

Important: Appwrite does NOT use

main

as the primary development branch.

PRs should target the current version branch (e.g.,

1.8.x

1.9.x

), not

main

How to determine the correct target branch

Check which version branch you're currently on:
```
git branch --show-current
```
Look for branches matching the pattern
```
X.Y.x
```
(e.g.,
```
1.8.x
```
,
```
1.9.x
```
)
The current active development branch is typically the highest version number with the
```
.x
```
suffix

When creating PRs

Always use the version branch as the base:

# Correct - targets the version branch
gh pr create --base 1.8.x --title "Your PR title" --body "..."

# Wrong - do not target main
gh pr create --base main ...

Branch naming convention

```
X.Y.x
```
branches (e.g.,
```
1.8.x
```
) - Active development branches for each minor version
```
main
```
- Not used for regular PRs; reserved for release management
Feature branches should be created from and merged back into the current version branch