Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
305 changes: 0 additions & 305 deletions .github/actions/setup-port-forwarding/action.yml

This file was deleted.

45 changes: 45 additions & 0 deletions .github/copilot-instructions.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,33 @@ The code review agent will:
- Emit events for significant state changes
- Use finalizers for cleanup operations

## Issue Triage & Priority

**Priority is tracked via GitHub Projects, not labels.** Do not create `P0`/`P1`/`P2` labels; the repo intentionally doesn't use them.

- Planning board: [DocumentDB k8s operator planning board](https://github.com/orgs/documentdb/projects/6) (project number `6`, owner `documentdb`)
- Issue tracking board: [DocumentDB issue tracking](https://github.com/orgs/documentdb/projects/4) (project number `4`)
- Both boards have a single-select `Priority` field with values `P0`, `P1`, `P2`.

### Setting priority on a new issue

1. Add the issue to the relevant project:
```bash
gh project item-add 6 --owner documentdb --url <issue-url>
```
2. Set the Priority field using `gh project item-edit` with the project + field + option IDs (obtainable via `gh project field-list 6 --owner documentdb --format json` and the GraphQL `options` query). Example:
```bash
gh api graphql -f query='
mutation($project:ID!,$item:ID!,$field:ID!,$opt:String!){
updateProjectV2ItemFieldValue(input:{projectId:$project,itemId:$item,fieldId:$field,value:{singleSelectOptionId:$opt}}){projectV2Item{id}}
}' -F project=PVT_kwDODDbYls4BIeDc -F item=<ITEM_ID> -F field=PVTSSF_lADODDbYls4BIeDczg4658Q -F opt=<OPTION_ID>
```

### Assignment

- Reviewers / maintainers are listed in `CODEOWNERS` and `MAINTAINERS.md`. Rayhan Hossain's GitHub handle is `hossain-rayhan`.
- Use `gh issue edit <n> --repo documentdb/documentdb-kubernetes-operator --add-assignee <handle>` rather than editing through the UI so the change is auditable.

## Commit Messages

Follow conventional commits format:
Expand All @@ -75,3 +102,21 @@ Follow conventional commits format:
- `test:` for test additions/changes
- `refactor:` for code refactoring
- `chore:` for maintenance tasks

### DCO Sign-off (Required)

Every commit **must** carry a `Signed-off-by:` trailer — the repo enforces the
[Developer Certificate of Origin](../contribute/developer-certificate-of-origin)
via a DCO check on PRs, and unsigned commits block the merge.

- Use `git commit -s` (or `git commit --signoff`) for new commits.
- To retrofit sign-offs onto commits you already made on the current branch:
```bash
GIT_SEQUENCE_EDITOR=: git rebase -i \
--exec 'git commit --amend --no-edit --signoff' <upstream>
```
(Plain `git rebase --signoff` is a no-op when commits don't need to be replayed.)
- Verify before pushing: `git log -n <N> --format='%(trailers:key=Signed-off-by)'`
must print a trailer for every commit.
- The sign-off is in addition to the `Co-authored-by: Copilot …` trailer, not a
replacement for it.
Loading