Skip to content

Commit a91758c

Browse files
committed
update
1 parent 0ccbf8b commit a91758c

File tree

1 file changed

+0
-22
lines changed

1 file changed

+0
-22
lines changed

.github/skills/prepare-release/SKILL.md

Lines changed: 0 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -64,8 +64,6 @@ The script will automatically:
6464

6565
When the script prompts `Proceed? [y/N]`, confirm by entering `y`.
6666

67-
**Sample PR**: https://github.com/Azure/AppConfiguration-JavaScriptProvider/pull/277
68-
6967
#### Step 2: Merge Main to Release Branch
7068

7169
After the version bump PR is merged, create a PR to merge `test-main` into the stable release branch by running:
@@ -76,17 +74,10 @@ After the version bump PR is merged, create a PR to merge `test-main` into the s
7674

7775
For example: `./scripts/merge-to-release.sh 2.5.0`
7876

79-
The script will automatically:
80-
1. Determine the major version from the version string (e.g., `2` from `2.5.0`).
81-
2. Create a PR from `test-main``test-release/stable/v{major}` (e.g., `test-release/stable/v2`).
82-
3. Title the PR: `Merge test-main to test-release/stable/v{major}`.
83-
8477
When the script prompts `Proceed? [y/N]`, confirm by entering `y`.
8578

8679
> **Important**: Use "Merge commit" (not squash) when merging this PR to preserve commit history.
8780
88-
**Sample PR**: https://github.com/Azure/AppConfiguration-JavaScriptProvider/pull/268
89-
9081
---
9182

9283
### Workflow B: Preview Release
@@ -114,12 +105,6 @@ After the merge-to-preview PR is merged, create a version bump PR targeting `tes
114105

115106
For example: `./scripts/version-bump.sh 2.5.1-preview --preview`
116107

117-
The script will automatically:
118-
1. Read the current version from `src/version.ts` on the `test-preview` branch.
119-
2. Create a new branch from `test-preview` named `<username>/version-<new_version>` (e.g., `linglingye/version-2.5.1-preview`).
120-
3. Update the version in all four files (`src/version.ts`, `package.json`, `package-lock.json` lines 3 and 9).
121-
4. Commit, push, and create a PR to `test-preview` with title: `Version bump <new_version>`.
122-
123108
When the script prompts `Proceed? [y/N]`, confirm by entering `y`.
124109

125110
#### Step 3: Merge Preview to Release Branch
@@ -132,17 +117,10 @@ After the version bump PR is merged, create a PR to merge `test-preview` into th
132117

133118
For example: `./scripts/merge-to-release.sh 2.5.1-preview --preview`
134119

135-
The script will automatically:
136-
1. Determine the major version from the version string (e.g., `2` from `2.5.1-preview`).
137-
2. Create a PR from `test-preview``test-release/v{major}` (e.g., `test-release/v2`).
138-
3. Title the PR: `Merge test-preview to test-release/v{major}`.
139-
140120
When the script prompts `Proceed? [y/N]`, confirm by entering `y`.
141121

142122
> **Important**: Use "Merge commit" (not squash) when merging this PR.
143123
144-
**Sample PR**: https://github.com/Azure/AppConfiguration-JavaScriptProvider/pull/274
145-
146124
---
147125

148126
## Review Checklist

0 commit comments

Comments
 (0)