You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/copilot-instructions.md
+8-17Lines changed: 8 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,14 +22,6 @@ The Azure SDK for Java repository contains client libraries for Azure services,
22
22
-**Management Libraries**: Libraries with Maven group `com.azure.resourcemanager`
23
23
-**Spring Libraries**: Libraries with Maven group `com.azure.spring`
24
24
25
-
## SDK Generation Guidelines
26
-
27
-
ACTION: Use azure-sdk-java-mcp sdk tools to generate the SDK.
28
-
ACTION: Do not use pure `mvn` command to compile, build or package SDK, use `build_java_sdk` tool instead, it runs `mvn` command inside.
29
-
ACTION: Use azure-sdk-java-mcp sdk tool `update_client_name` to update client name.
30
-
ACTION: Only update the manual written code or class when you fix compile errors. Manual written class does not have `// Code generated by Microsoft (R) TypeSpec Code Generator.` header. Manual written functions or properties do not have `@Generated` annotation.
31
-
32
-
33
25
## Behavior
34
26
35
27
- Always ensure your solutions prioritize clarity, maintainability, and testability.
@@ -121,11 +113,11 @@ When possible, refer to the Azure SDK for Java Design Guidelines for specific ex
121
113
- Include tests that cover your changes
122
114
- Update CHANGELOG.md with your changes
123
115
- Provide a proper description of the pull request to document the changes in the PR. The description should include:
124
-
- A summary of the changes made.
125
-
- The reason for the changes.
126
-
- Any relevant issue numbers.
127
-
- Instructions on how to verify the changes.
128
-
- Any additional context or information that reviewers should be aware of.
116
+
- A summary of the changes made.
117
+
- The reason for the changes.
118
+
- Any relevant issue numbers.
119
+
- Instructions on how to verify the changes.
120
+
- Any additional context or information that reviewers should be aware of.
129
121
130
122
## Release Process
131
123
@@ -163,12 +155,11 @@ There are two tools to help with SDK releases:
163
155
Run `CheckPackageReleaseReadiness` to verify if the package is ready for release. This tool checks:
164
156
- API review status
165
157
- Change log status
166
-
- Package name approval(If package is new and releasing a preview version)
158
+
- Package name approval(If package is new and releasing a preview version)
167
159
- Release date is set in release tracker
168
160
169
161
### Release SDK
170
-
Run `ReleasePackage` to release the package. This tool requires package name and language as inputs. It will:
171
-
- Check if the package is ready for release
162
+
Run `ReleasePackage` to release the package. This tool requires package name and language as inputs. It will:- Check if the package is ready for release
172
163
- Identify the release pipeline
173
164
- Trigger the release pipeline.
174
-
User needs to approve the release stage in the pipeline after it is triggered.
165
+
User needs to approve the release stage in the pipeline after it is triggered.
0 commit comments