Skip to content

[JEWEL-1289] Add Jewel Bugbot review rules#3459

Open
rock3r wants to merge 1 commit intoJetBrains:masterfrom
rock3r:sebp/JEWEL-1289_add_bugbot_rules
Open

[JEWEL-1289] Add Jewel Bugbot review rules#3459
rock3r wants to merge 1 commit intoJetBrains:masterfrom
rock3r:sebp/JEWEL-1289_add_bugbot_rules

Conversation

@rock3r
Copy link
Copy Markdown
Collaborator

@rock3r rock3r commented Mar 16, 2026

Add platform/jewel/.cursor/BUGBOT.md with Jewel-specific Bugbot review guidance that covers API compatibility, layout/styling checks, common-code boundaries, documentation, testing, and release-notes expectations.

@rock3r rock3r force-pushed the sebp/JEWEL-1289_add_bugbot_rules branch from eaba096 to 6b6c632 Compare March 16, 2026 17:07
@rock3r rock3r self-assigned this Mar 16, 2026
@rock3r rock3r added the Jewel label Mar 16, 2026
@rock3r
Copy link
Copy Markdown
Collaborator Author

rock3r commented Mar 16, 2026

Metalava failure is some random GitHub API rate limiting issue, we can ignore it since we only add a markdown file here...

* See `platform/jewel/docs/pr-guide.md` for the template.
* Does the release notes section include internal implementation details? They should focus on the user value of a change/fix.
* API and behavior changes, new functionality, and new features must be covered.
* Look at `platform/jewel/RELEASE NOTES.md` for a style reference and `platform/jewel/scripts/extract-release-notes.main.kts` for the extraction process.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Always good to make sure we point out any behavioral breaking changes in the PR description as well 😎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants