Skip to content

Document Copilot Git and PR workflow #1113

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

Closed
ebhills wants to merge 1 commit into from
Closed

Document Copilot Git and PR workflow #1113

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
15 changes: 15 additions & 0 deletions .github/copilot-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,21 @@ Some tests require cloud-based ML models and need credentials set as environment

Tests that require authentication will fail without these variables but this is expected in local development.

## Git and Pull Request workflow

- `main` is the production source of truth.
- `dev` is a staging destination, not a feature-branch source.
- Start every feature or fix branch from the latest `origin/main`.
- Never create feature branches from `dev`.
- The first pull request for a feature must target `dev` for staging validation.
- Never merge `dev` into a feature branch.
- After staging validation succeeds, open a second pull request from the same
feature branch into `main`.
- Never merge `dev` into `main`.
- Do not delete the feature branch until its pull request into `main` is merged.
- Before opening a pull request, verify its commits, changed files, and focused
tests.

## Building & Packaging

### Local Installation
Expand Down