Skip to content

docs(docs): clarify issue assignment requirement before starting work #299

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
katriendg merged 2 commits into from
Mar 18, 2026
Merged

docs(docs): clarify issue assignment requirement before starting work #299

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ced510b
Initial plan
Copilot Mar 18, 2026
d80ab64
docs(docs): clarify issue assignment requirement before starting work
Copilot Mar 18, 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
21 changes: 12 additions & 9 deletions docs/contributing/contribution-workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
sidebar_position: 4
title: Contribution Workflow
description: How to contribute including legal requirements, bug reports, enhancement suggestions, and documentation improvements
author: Microsoft Robotics-AI Team
ms.date: 2026-02-08
ms.date: 2026-03-18
ms.topic: how-to
keywords:
- contributing
Expand Down Expand Up @@ -148,14 +148,17 @@

### PR Workflow

1. Fork the repository to your GitHub account
2. Create a branch from `main` with descriptive name: `feature/private-endpoint-support` or `fix/gpu-scheduling-timeout`
3. Make changes following style guides and conventions
4. Open a draft PR early for maintainer feedback
5. Perform validation appropriate to your contribution type (see table below)
6. Mark PR ready for review after completing validation
7. Address review feedback promptly
8. Merge occurs after approval and passing maintainer integration tests
1. **Check the issue is open and unassigned.** Comment on the issue to request assignment before starting any work. Maintainers will assign you when confirmed.
* If the issue is already assigned to someone, do not open a competing PR without first coordinating with the assignee or a maintainer.
* Issues labelled `needs-triage` are not ready to be picked up. You are welcome to comment your interest in being assigned — maintainers will follow up once triage is complete.
2. Fork the repository to your GitHub account
3. Create a branch from `main` with descriptive name: `feature/private-endpoint-support` or `fix/gpu-scheduling-timeout`
4. Make changes following style guides and conventions
5. Open a draft PR early for maintainer feedback
6. Perform validation appropriate to your contribution type (see table below)
7. Mark PR ready for review after completing validation
8. Address review feedback promptly
9. Merge occurs after approval and passing maintainer integration tests

### Validation Expectations

Expand Down
Loading