Skip to content
Merged
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
2 changes: 1 addition & 1 deletion .claude/commands/handoff-plan.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,7 @@ The plan's last step writes the plan's entries, for every plan:

When the repository has a `version.json` at its root, which Nerdbank.GitVersioning builds each package's version from, and the plan has a `Release:` line, the same last step also sets that file's `version` to the `Release:` version without its leading `v`, such as `"1.4.0"` for `v1.4.0`, changing nothing else, and lists `version.json` on its Files line: a release tag whose commit holds another version publishes no package. When that version starts a new major version and the file's `assemblyVersion` names a `version`, the step also sets `assemblyVersion` to `{ "precision": "major" }`. The state script prints `version-file: match` when the file holds the plan's version, `mismatch <version>` when it holds another, and `-` without the file or a `Release:` line.

When the repository has `.github/workflows/raise-baseline.yml`, that workflow opens the pull request that raises `PackageValidationBaselineVersion` once nuget.org lists a release: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.
When the repository has `.github/workflows/raise-baseline.yml`, that workflow pushes the branch that raises `PackageValidationBaselineVersion` once nuget.org lists a release and opens an issue whose link opens its pull request: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.

Write the step so the executor copies text: it gives the heading, each entry under its group, and each link line in full. In a pre-release project, it gives each entry to add in full, and each entry to rewrite or delete by its first words and, for a rewrite, its new text in full. Only `<date>` is left to the executor, with the `Get-Date` command. Never reformat a changelog in another format, or an older section of any changelog, unless the request asks for it, as an adopted project's follow-up does; a heading that `changelog-duplicates` names in an older release section stays as it is. A plan that converts a changelog keeps every entry's text. It dates each version's heading with its tag's date (`git log -1 --format=%as <tag>`), puts each entry in one group, and adds the preamble, `## [Unreleased]` and the link reference definitions.

Expand Down
2 changes: 1 addition & 1 deletion .claude/commands/plan-bugfix.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,7 @@ The plan's last step writes the plan's entries, for every plan:

When the repository has a `version.json` at its root, which Nerdbank.GitVersioning builds each package's version from, and the plan has a `Release:` line, the same last step also sets that file's `version` to the `Release:` version without its leading `v`, such as `"1.4.0"` for `v1.4.0`, changing nothing else, and lists `version.json` on its Files line: a release tag whose commit holds another version publishes no package. When that version starts a new major version and the file's `assemblyVersion` names a `version`, the step also sets `assemblyVersion` to `{ "precision": "major" }`. The state script prints `version-file: match` when the file holds the plan's version, `mismatch <version>` when it holds another, and `-` without the file or a `Release:` line.

When the repository has `.github/workflows/raise-baseline.yml`, that workflow opens the pull request that raises `PackageValidationBaselineVersion` once nuget.org lists a release: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.
When the repository has `.github/workflows/raise-baseline.yml`, that workflow pushes the branch that raises `PackageValidationBaselineVersion` once nuget.org lists a release and opens an issue whose link opens its pull request: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.

Write the step so the executor copies text: it gives the heading, each entry under its group, and each link line in full. In a pre-release project, it gives each entry to add in full, and each entry to rewrite or delete by its first words and, for a rewrite, its new text in full. Only `<date>` is left to the executor, with the `Get-Date` command. Never reformat a changelog in another format, or an older section of any changelog, unless the request asks for it, as an adopted project's follow-up does; a heading that `changelog-duplicates` names in an older release section stays as it is. A plan that converts a changelog keeps every entry's text. It dates each version's heading with its tag's date (`git log -1 --format=%as <tag>`), puts each entry in one group, and adds the preamble, `## [Unreleased]` and the link reference definitions.

Expand Down
2 changes: 1 addition & 1 deletion .claude/commands/plan-docs.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,7 @@ The plan's last step writes the plan's entries, for every plan:

When the repository has a `version.json` at its root, which Nerdbank.GitVersioning builds each package's version from, and the plan has a `Release:` line, the same last step also sets that file's `version` to the `Release:` version without its leading `v`, such as `"1.4.0"` for `v1.4.0`, changing nothing else, and lists `version.json` on its Files line: a release tag whose commit holds another version publishes no package. When that version starts a new major version and the file's `assemblyVersion` names a `version`, the step also sets `assemblyVersion` to `{ "precision": "major" }`. The state script prints `version-file: match` when the file holds the plan's version, `mismatch <version>` when it holds another, and `-` without the file or a `Release:` line.

When the repository has `.github/workflows/raise-baseline.yml`, that workflow opens the pull request that raises `PackageValidationBaselineVersion` once nuget.org lists a release: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.
When the repository has `.github/workflows/raise-baseline.yml`, that workflow pushes the branch that raises `PackageValidationBaselineVersion` once nuget.org lists a release and opens an issue whose link opens its pull request: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.

Write the step so the executor copies text: it gives the heading, each entry under its group, and each link line in full. In a pre-release project, it gives each entry to add in full, and each entry to rewrite or delete by its first words and, for a rewrite, its new text in full. Only `<date>` is left to the executor, with the `Get-Date` command. Never reformat a changelog in another format, or an older section of any changelog, unless the request asks for it, as an adopted project's follow-up does; a heading that `changelog-duplicates` names in an older release section stays as it is. A plan that converts a changelog keeps every entry's text. It dates each version's heading with its tag's date (`git log -1 --format=%as <tag>`), puts each entry in one group, and adds the preamble, `## [Unreleased]` and the link reference definitions.

Expand Down
2 changes: 1 addition & 1 deletion .claude/commands/plan-feature.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,7 @@ The plan's last step writes the plan's entries, for every plan:

When the repository has a `version.json` at its root, which Nerdbank.GitVersioning builds each package's version from, and the plan has a `Release:` line, the same last step also sets that file's `version` to the `Release:` version without its leading `v`, such as `"1.4.0"` for `v1.4.0`, changing nothing else, and lists `version.json` on its Files line: a release tag whose commit holds another version publishes no package. When that version starts a new major version and the file's `assemblyVersion` names a `version`, the step also sets `assemblyVersion` to `{ "precision": "major" }`. The state script prints `version-file: match` when the file holds the plan's version, `mismatch <version>` when it holds another, and `-` without the file or a `Release:` line.

When the repository has `.github/workflows/raise-baseline.yml`, that workflow opens the pull request that raises `PackageValidationBaselineVersion` once nuget.org lists a release: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.
When the repository has `.github/workflows/raise-baseline.yml`, that workflow pushes the branch that raises `PackageValidationBaselineVersion` once nuget.org lists a release and opens an issue whose link opens its pull request: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.

Write the step so the executor copies text: it gives the heading, each entry under its group, and each link line in full. In a pre-release project, it gives each entry to add in full, and each entry to rewrite or delete by its first words and, for a rewrite, its new text in full. Only `<date>` is left to the executor, with the `Get-Date` command. Never reformat a changelog in another format, or an older section of any changelog, unless the request asks for it, as an adopted project's follow-up does; a heading that `changelog-duplicates` names in an older release section stays as it is. A plan that converts a changelog keeps every entry's text. It dates each version's heading with its tag's date (`git log -1 --format=%as <tag>`), puts each entry in one group, and adds the preamble, `## [Unreleased]` and the link reference definitions.

Expand Down
2 changes: 1 addition & 1 deletion .claude/commands/plan-issue.md
Original file line number Diff line number Diff line change
Expand Up @@ -292,7 +292,7 @@ The plan's last step writes the plan's entries, for every plan:

When the repository has a `version.json` at its root, which Nerdbank.GitVersioning builds each package's version from, and the plan has a `Release:` line, the same last step also sets that file's `version` to the `Release:` version without its leading `v`, such as `"1.4.0"` for `v1.4.0`, changing nothing else, and lists `version.json` on its Files line: a release tag whose commit holds another version publishes no package. When that version starts a new major version and the file's `assemblyVersion` names a `version`, the step also sets `assemblyVersion` to `{ "precision": "major" }`. The state script prints `version-file: match` when the file holds the plan's version, `mismatch <version>` when it holds another, and `-` without the file or a `Release:` line.

When the repository has `.github/workflows/raise-baseline.yml`, that workflow opens the pull request that raises `PackageValidationBaselineVersion` once nuget.org lists a release: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.
When the repository has `.github/workflows/raise-baseline.yml`, that workflow pushes the branch that raises `PackageValidationBaselineVersion` once nuget.org lists a release and opens an issue whose link opens its pull request: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.

Write the step so the executor copies text: it gives the heading, each entry under its group, and each link line in full. In a pre-release project, it gives each entry to add in full, and each entry to rewrite or delete by its first words and, for a rewrite, its new text in full. Only `<date>` is left to the executor, with the `Get-Date` command. Never reformat a changelog in another format, or an older section of any changelog, unless the request asks for it, as an adopted project's follow-up does; a heading that `changelog-duplicates` names in an older release section stays as it is. A plan that converts a changelog keeps every entry's text. It dates each version's heading with its tag's date (`git log -1 --format=%as <tag>`), puts each entry in one group, and adds the preamble, `## [Unreleased]` and the link reference definitions.

Expand Down
2 changes: 1 addition & 1 deletion .claude/commands/plan-migration.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,7 @@ The plan's last step writes the plan's entries, for every plan:

When the repository has a `version.json` at its root, which Nerdbank.GitVersioning builds each package's version from, and the plan has a `Release:` line, the same last step also sets that file's `version` to the `Release:` version without its leading `v`, such as `"1.4.0"` for `v1.4.0`, changing nothing else, and lists `version.json` on its Files line: a release tag whose commit holds another version publishes no package. When that version starts a new major version and the file's `assemblyVersion` names a `version`, the step also sets `assemblyVersion` to `{ "precision": "major" }`. The state script prints `version-file: match` when the file holds the plan's version, `mismatch <version>` when it holds another, and `-` without the file or a `Release:` line.

When the repository has `.github/workflows/raise-baseline.yml`, that workflow opens the pull request that raises `PackageValidationBaselineVersion` once nuget.org lists a release: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.
When the repository has `.github/workflows/raise-baseline.yml`, that workflow pushes the branch that raises `PackageValidationBaselineVersion` once nuget.org lists a release and opens an issue whose link opens its pull request: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.

Write the step so the executor copies text: it gives the heading, each entry under its group, and each link line in full. In a pre-release project, it gives each entry to add in full, and each entry to rewrite or delete by its first words and, for a rewrite, its new text in full. Only `<date>` is left to the executor, with the `Get-Date` command. Never reformat a changelog in another format, or an older section of any changelog, unless the request asks for it, as an adopted project's follow-up does; a heading that `changelog-duplicates` names in an older release section stays as it is. A plan that converts a changelog keeps every entry's text. It dates each version's heading with its tag's date (`git log -1 --format=%as <tag>`), puts each entry in one group, and adds the preamble, `## [Unreleased]` and the link reference definitions.

Expand Down
2 changes: 1 addition & 1 deletion .claude/commands/plan-performance.md
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ The plan's last step writes the plan's entries, for every plan:

When the repository has a `version.json` at its root, which Nerdbank.GitVersioning builds each package's version from, and the plan has a `Release:` line, the same last step also sets that file's `version` to the `Release:` version without its leading `v`, such as `"1.4.0"` for `v1.4.0`, changing nothing else, and lists `version.json` on its Files line: a release tag whose commit holds another version publishes no package. When that version starts a new major version and the file's `assemblyVersion` names a `version`, the step also sets `assemblyVersion` to `{ "precision": "major" }`. The state script prints `version-file: match` when the file holds the plan's version, `mismatch <version>` when it holds another, and `-` without the file or a `Release:` line.

When the repository has `.github/workflows/raise-baseline.yml`, that workflow opens the pull request that raises `PackageValidationBaselineVersion` once nuget.org lists a release: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.
When the repository has `.github/workflows/raise-baseline.yml`, that workflow pushes the branch that raises `PackageValidationBaselineVersion` once nuget.org lists a release and opens an issue whose link opens its pull request: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.

Write the step so the executor copies text: it gives the heading, each entry under its group, and each link line in full. In a pre-release project, it gives each entry to add in full, and each entry to rewrite or delete by its first words and, for a rewrite, its new text in full. Only `<date>` is left to the executor, with the `Get-Date` command. Never reformat a changelog in another format, or an older section of any changelog, unless the request asks for it, as an adopted project's follow-up does; a heading that `changelog-duplicates` names in an older release section stays as it is. A plan that converts a changelog keeps every entry's text. It dates each version's heading with its tag's date (`git log -1 --format=%as <tag>`), puts each entry in one group, and adds the preamble, `## [Unreleased]` and the link reference definitions.

Expand Down
2 changes: 1 addition & 1 deletion .claude/commands/plan-refactor.md
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,7 @@ The plan's last step writes the plan's entries, for every plan:

When the repository has a `version.json` at its root, which Nerdbank.GitVersioning builds each package's version from, and the plan has a `Release:` line, the same last step also sets that file's `version` to the `Release:` version without its leading `v`, such as `"1.4.0"` for `v1.4.0`, changing nothing else, and lists `version.json` on its Files line: a release tag whose commit holds another version publishes no package. When that version starts a new major version and the file's `assemblyVersion` names a `version`, the step also sets `assemblyVersion` to `{ "precision": "major" }`. The state script prints `version-file: match` when the file holds the plan's version, `mismatch <version>` when it holds another, and `-` without the file or a `Release:` line.

When the repository has `.github/workflows/raise-baseline.yml`, that workflow opens the pull request that raises `PackageValidationBaselineVersion` once nuget.org lists a release: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.
When the repository has `.github/workflows/raise-baseline.yml`, that workflow pushes the branch that raises `PackageValidationBaselineVersion` once nuget.org lists a release and opens an issue whose link opens its pull request: a plan never raises the baseline in a step or lists raising it under `## Follow-ups`.

Write the step so the executor copies text: it gives the heading, each entry under its group, and each link line in full. In a pre-release project, it gives each entry to add in full, and each entry to rewrite or delete by its first words and, for a rewrite, its new text in full. Only `<date>` is left to the executor, with the `Get-Date` command. Never reformat a changelog in another format, or an older section of any changelog, unless the request asks for it, as an adopted project's follow-up does; a heading that `changelog-duplicates` names in an older release section stays as it is. A plan that converts a changelog keeps every entry's text. It dates each version's heading with its tag's date (`git log -1 --format=%as <tag>`), puts each entry in one group, and adds the preamble, `## [Unreleased]` and the link reference definitions.

Expand Down
Loading