{"owner":"velero-io","repo":"velero","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":[".github/copilot-instructions.md"],"skills":{".github/copilot-instructions.md":"# GitHub Copilot instructions for velero-io/velero\n\n## Changelog requirement\n\nVelero uses per-PR changelog fragments that are assembled into release notes.\n\n### File naming convention\n\nEvery shipping PR must add exactly **one** file at:\n\n```\nchangelogs/unreleased/<PR_NUMBER>-<github_username>\n```\n\n- `<PR_NUMBER>` is the pull request number (e.g. `10200`).\n- `<github_username>` is the GitHub login of the PR author (e.g. `jdoe`).\n- The file has **no extension**.\n- The file content is a single line describing the change (the PR title is a\n  sensible default).\n\n**Example:** PR #10200 by `jdoe` → `changelogs/unreleased/10200-jdoe`\n\nThe easiest way to create this file is:\n\n```bash\nmake new-changelog CHANGELOG_BODY=\"Brief description of the change\"\n```\n\n`make new-changelog` reads the PR number and author from `gh pr view`; the file\nis written automatically to the correct path with the correct name.\n\nThe CI check (`hack/changelog-check.sh`) looks for\n`changelogs/unreleased/<PR_NUMBER>-*` and fails if no file is found.\n\n### When a changelog is NOT required\n\nA changelog entry is **not** required when a PR exclusively changes non-shipping\ncontent, i.e. the only files touched belong to one or more of these categories:\n\n| Category | Paths |\n|---|---|\n| GitHub Actions / CI workflows | `.github/**` |\n| Documentation | `site/content/docs/**`, `site/**`, `docs/**`, `*.md` |\n| Website (non-docs) | `site/**` (excluding `site/content/docs/**`) |\n\nWhen you open or review a PR that falls into one of the above categories (and does\n**not** modify `pkg/`, `internal/`, `cmd/`, `vendor/`, `hack/`, `Makefile`,\n`go.mod`, `go.sum`, or `changelogs/**`), apply the label\n**`kind/changelog-not-required`** instead of requesting a changelog entry.  The\n`labeler.yml` auto-labeler handles this automatically for most cases; apply the\nlabel manually if the auto-labeler did not.\n\n## Backport / cherry-pick workflow\n\nVelero uses `.github/workflows/backport.yml` to automate cherry-picks onto release\nbranches.\n\n- **Before merge:** comment `/backport release-1.17` (or `/cherrypick release-1.17`)\n  to add the label `backport release-1.17` to the PR.  Multiple branches can be\n  space-delimited: `/backport release-1.17 release-1.18`.  The label causes the\n  backport to run automatically when the PR merges.\n- **After merge:** the same comment immediately creates the backport PR.\n- Only repository **owners, members, and collaborators** may trigger these commands.\n\n## General coding guidelines\n\n- Follow the existing code style of the file being edited.\n- Add unit tests for new exported functions in `pkg/`.\n- Do not commit secrets, credentials, or API tokens.\n- Keep PRs focused; prefer small, reviewable changes over large omnibus PRs.\n"},"files":{".github/copilot-instructions.md":"# GitHub Copilot instructions for velero-io/velero\n\n## Changelog requirement\n\nVelero uses per-PR changelog fragments that are assembled into release notes.\n\n### File naming convention\n\nEvery shipping PR must add exactly **one** file at:\n\n```\nchangelogs/unreleased/<PR_NUMBER>-<github_username>\n```\n\n- `<PR_NUMBER>` is the pull request number (e.g. `10200`).\n- `<github_username>` is the GitHub login of the PR author (e.g. `jdoe`).\n- The file has **no extension**.\n- The file content is a single line describing the change (the PR title is a\n  sensible default).\n\n**Example:** PR #10200 by `jdoe` → `changelogs/unreleased/10200-jdoe`\n\nThe easiest way to create this file is:\n\n```bash\nmake new-changelog CHANGELOG_BODY=\"Brief description of the change\"\n```\n\n`make new-changelog` reads the PR number and author from `gh pr view`; the file\nis written automatically to the correct path with the correct name.\n\nThe CI check (`hack/changelog-check.sh`) looks for\n`changelogs/unreleased/<PR_NUMBER>-*` and fails if no file is found.\n\n### When a changelog is NOT required\n\nA changelog entry is **not** required when a PR exclusively changes non-shipping\ncontent, i.e. the only files touched belong to one or more of these categories:\n\n| Category | Paths |\n|---|---|\n| GitHub Actions / CI workflows | `.github/**` |\n| Documentation | `site/content/docs/**`, `site/**`, `docs/**`, `*.md` |\n| Website (non-docs) | `site/**` (excluding `site/content/docs/**`) |\n\nWhen you open or review a PR that falls into one of the above categories (and does\n**not** modify `pkg/`, `internal/`, `cmd/`, `vendor/`, `hack/`, `Makefile`,\n`go.mod`, `go.sum`, or `changelogs/**`), apply the label\n**`kind/changelog-not-required`** instead of requesting a changelog entry.  The\n`labeler.yml` auto-labeler handles this automatically for most cases; apply the\nlabel manually if the auto-labeler did not.\n\n## Backport / cherry-pick workflow\n\nVelero uses `.github/workflows/backport.yml` to automate cherry-picks onto release\nbranches.\n\n- **Before merge:** comment `/backport release-1.17` (or `/cherrypick release-1.17`)\n  to add the label `backport release-1.17` to the PR.  Multiple branches can be\n  space-delimited: `/backport release-1.17 release-1.18`.  The label causes the\n  backport to run automatically when the PR merges.\n- **After merge:** the same comment immediately creates the backport PR.\n- Only repository **owners, members, and collaborators** may trigger these commands.\n\n## General coding guidelines\n\n- Follow the existing code style of the file being edited.\n- Add unit tests for new exported functions in `pkg/`.\n- Do not commit secrets, credentials, or API tokens.\n- Keep PRs focused; prefer small, reviewable changes over large omnibus PRs.\n"},"items":[{"name":"copilot-instructions.md","path":".github/copilot-instructions.md","title":"copilot-instructions.md","content":"# GitHub Copilot instructions for velero-io/velero\n\n## Changelog requirement\n\nVelero uses per-PR changelog fragments that are assembled into release notes.\n\n### File naming convention\n\nEvery shipping PR must add exactly **one** file at:\n\n```\nchangelogs/unreleased/<PR_NUMBER>-<github_username>\n```\n\n- `<PR_NUMBER>` is the pull request number (e.g. `10200`).\n- `<github_username>` is the GitHub login of the PR author (e.g. `jdoe`).\n- The file has **no extension**.\n- The file content is a single line describing the change (the PR title is a\n  sensible default).\n\n**Example:** PR #10200 by `jdoe` → `changelogs/unreleased/10200-jdoe`\n\nThe easiest way to create this file is:\n\n```bash\nmake new-changelog CHANGELOG_BODY=\"Brief description of the change\"\n```\n\n`make new-changelog` reads the PR number and author from `gh pr view`; the file\nis written automatically to the correct path with the correct name.\n\nThe CI check (`hack/changelog-check.sh`) looks for\n`changelogs/unreleased/<PR_NUMBER>-*` and fails if no file is found.\n\n### When a changelog is NOT required\n\nA changelog entry is **not** required when a PR exclusively changes non-shipping\ncontent, i.e. the only files touched belong to one or more of these categories:\n\n| Category | Paths |\n|---|---|\n| GitHub Actions / CI workflows | `.github/**` |\n| Documentation | `site/content/docs/**`, `site/**`, `docs/**`, `*.md` |\n| Website (non-docs) | `site/**` (excluding `site/content/docs/**`) |\n\nWhen you open or review a PR that falls into one of the above categories (and does\n**not** modify `pkg/`, `internal/`, `cmd/`, `vendor/`, `hack/`, `Makefile`,\n`go.mod`, `go.sum`, or `changelogs/**`), apply the label\n**`kind/changelog-not-required`** instead of requesting a changelog entry.  The\n`labeler.yml` auto-labeler handles this automatically for most cases; apply the\nlabel manually if the auto-labeler did not.\n\n## Backport / cherry-pick workflow\n\nVelero uses `.github/workflows/backport.yml` to automate cherry-picks onto release\nbranches.\n\n- **Before merge:** comment `/backport release-1.17` (or `/cherrypick release-1.17`)\n  to add the label `backport release-1.17` to the PR.  Multiple branches can be\n  space-delimited: `/backport release-1.17 release-1.18`.  The label causes the\n  backport to run automatically when the PR merges.\n- **After merge:** the same comment immediately creates the backport PR.\n- Only repository **owners, members, and collaborators** may trigger these commands.\n\n## General coding guidelines\n\n- Follow the existing code style of the file being edited.\n- Add unit tests for new exported functions in `pkg/`.\n- Do not commit secrets, credentials, or API tokens.\n- Keep PRs focused; prefer small, reviewable changes over large omnibus PRs.\n","category":".github","tokens":683}]}