Skip to content

docs: require fresh branches for PR contributions #749

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
grantmcdermott merged 2 commits into from
Nov 4, 2026
Merged

docs: require fresh branches for PR contributions #749

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3153554
docs: require fresh branches for PR contributions
grantmcdermott Nov 4, 2026
6c3e079
docs: use --no-track when branching from origin/main
grantmcdermott Nov 4, 2026
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
8 changes: 7 additions & 1 deletion CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,7 +159,7 @@ tinytest::run_test_file("inst/tinytest/test-legend.R")
```

### Continuous Integration
All contributions should go through a pull request. PRs against `main` automatically trigger GitHub Actions CI, which runs `R CMD check` (including the full test suite) on Ubuntu with both R-release and R-devel. Snapshot tests are included in this CI run, so even if you can't run them locally, CI will catch any regressions.
PRs against `main` automatically trigger GitHub Actions CI, which runs `R CMD check` (including the full test suite) on Ubuntu with both R-release and R-devel. Snapshot tests are included in this CI run, so even if you can't run them locally, CI will catch any regressions.

### CRAN Submissions
The test suite (snapshot SVGs in particular) adds significant size to the installed package. Tests are only intended to run locally and on CI — not on CRAN.
Expand Down Expand Up @@ -189,6 +189,12 @@ Some features require manual testing, particularly:
- Positron IDE compatibility
- Interactive device behaviour

## Contributing

All contributions should go through a pull request against `main`.

- **Always work on a fresh branch.** Every PR-based contribution must start on a new branch created from the latest `origin/main` (`git fetch && git switch --no-track -c <branch> origin/main`, then `git push -u origin <branch>` on first push). The `--no-track` matters: without it the branch tracks `origin/main`, so a plain `git push` or an IDE "sync" pushes straight to `main`. Never commit directly to `main`, and never reuse or stack work onto an existing feature branch. Overriding this requires explicit opt-in from the maintainer.

## Development Workflow

### Makefile Commands
Expand Down
Loading