Skip to content

Clarify interactive and autonomous agent branch naming #4818

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

Draft
paulmedynski wants to merge 1 commit into from
+7 −9
Draft

Clarify interactive and autonomous agent branch naming #4818

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
5 changes: 3 additions & 2 deletions .github/copilot-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,8 +132,9 @@ When a new issue is created, follow these steps:
- Tag reviewers based on `CODEOWNERS` file

## 🌿 Branch Naming
- All branches created by AI agents **must** use the `dev/automation/` prefix (e.g. `dev/automation/fix-connection-timeout`).
- Do **not** create branches directly under `main`, `dev/`, or any other top-level prefix.
- **Interactive agents**, working under direct human guidance, may create and use branches under `dev/<name>/` when the human specifies or approves the namespace and branch name (e.g., `dev/paul/aot/phase-1.1`).
- **Autonomous agents**, working without interactive human direction, **must** create branches under `dev/automation/` (e.g., `dev/automation/fix-connection-timeout`).
- Do **not** create branches outside these namespaces or directly under `dev/`.

## 🧠 Contextual Awareness
- All source code is in `src/Microsoft.Data.SqlClient/src/`. Do NOT add code to legacy `netfx/src/` or `netcore/src/` directories.
Expand Down
2 changes: 1 addition & 1 deletion .github/prompts/ado-work-item-agent.prompt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ Perform the following steps to address the work item. Think step-by-step.
- Locate the relevant code in `src/` or `tests/`.

### 2. Planning and Branching
- Propose a descriptive branch name following the repository rule `dev/automation/<branch-name>` (e.g., `dev/automation/fix-connection-pool`).
- Propose a descriptive branch name following the [repository branch naming rules](../../AGENTS.md#branch-naming): interactive, human-directed agents may use an approved `dev/<name>/` branch; autonomous agents must use `dev/automation/`.
- Identify any dependencies or potential breaking changes.

### 3. Implementation
Expand Down
9 changes: 3 additions & 6 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,12 +74,9 @@ When using shell/terminal tools, follow these rules strictly:

## Branch Naming

All branches created by AI agents **must** live under the `dev/automation/` prefix. Use a descriptive suffix, for example:

- `dev/automation/fix-connection-timeout`
- `dev/automation/add-json-type-tests`

Do **not** create branches directly under `main`, `dev/`, or any other top-level prefix.
- **Interactive agents**, working under direct human guidance, may create and use branches under `dev/<name>/` when the human specifies or approves the namespace and branch name (e.g., `dev/paul/aot/phase-1.1`).
- **Autonomous agents**, working without interactive human direction, **must** create branches under `dev/automation/` (e.g., `dev/automation/fix-connection-timeout`).
- Do **not** create branches outside these namespaces or directly under `dev/`.

## Common Tasks

Expand Down
Loading