copilot instructions: Update "No prerelease docs" instruction (#6795)
This commit is contained in:
@@ -34,7 +34,8 @@
|
|||||||
- Async/await misuse or blocking operations in async contexts
|
- Async/await misuse or blocking operations in async contexts
|
||||||
- Improper trait implementations
|
- Improper trait implementations
|
||||||
|
|
||||||
|
### No Prerelease Docs
|
||||||
|
- If the PR contains both code changes to features/functionality AND updates in `/documentation`: Documentation updates must be separated to keep public docs in sync with released versions. Either mark new topics with `unlisted: true` or remove/hide the documentation.
|
||||||
|
|
||||||
## Project-Specific Context
|
## Project-Specific Context
|
||||||
|
|
||||||
@@ -45,7 +46,6 @@
|
|||||||
- See HOWTOAI.md for AI-assisted code standards
|
- See HOWTOAI.md for AI-assisted code standards
|
||||||
- MCP protocol implementations require extra scrutiny
|
- MCP protocol implementations require extra scrutiny
|
||||||
- Naming convention: In `documentation/docs` and `documentation/blog`, always refer to the project as "goose" (lowercase), never "Goose" (even at the start of sentences)
|
- Naming convention: In `documentation/docs` and `documentation/blog`, always refer to the project as "goose" (lowercase), never "Goose" (even at the start of sentences)
|
||||||
- No prerelease docs: PRs should not contain updates in `/documentation` that correspond to code changes in the PR so that the public docs stay in sync with the latest released version. New topics should be marked with `unlisted: true`; other content should be removed or hidden from public view.
|
|
||||||
|
|
||||||
## CI Pipeline Context
|
## CI Pipeline Context
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user