Skip to content

chore: remove repo-level PR template #75

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
nickolas-dimitrakas merged 1 commit into from
Sep 17, 2026
Merged

chore: remove repo-level PR template #75

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
28 changes: 0 additions & 28 deletions .github/PULL_REQUEST_TEMPLATE.md
View file
Open in desktop

This file was deleted.

2 changes: 1 addition & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@ The default branch requires two checks, `build` and `trunk-check`.
- Base work on `main`. `development` sits behind it and is not where PRs merge.
- Branch names follow `<type>/<description>` and PR titles Conventional Commits, by convention; no
ruleset enforces either. `main` merges by squash only, so the PR title becomes the commit message.
- Describe PRs using `.github/PULL_REQUEST_TEMPLATE.md`. Code-owner review is required
- Describe PRs using the org-wide default template published at `mParticle/.github`. Code-owner review is required
(`.github/CODEOWNERS`), threads must be resolved, and a push dismisses approvals.

## Changelog, migration notes and versioning
Expand Down
Loading