@@ -5,19 +5,21 @@ Unless your change is trivial, please create an issue to discuss the change befo
55
66### Describe your changes:
77
8- Fixes <issue-number >
8+ Fixes #<issue-number >
9+ <!--
10+ Linking an issue is REQUIRED. Replace <issue-number> with the GitHub issue number this PR addresses
11+ (e.g., `Fixes #12345`). GitHub will auto-link it. If no issue exists, please open one first so the
12+ problem and design can be discussed before review.
13+ -->
914
1015<!--
1116Short blurb explaining:
1217- What changes did you make?
1318- Why did you make them?
14- - How did you test your changes?
1519-->
1620
1721I worked on ... because ...
1822
19- <!-- For frontend related change, please add screenshots and/or videos of your changes preview! -->
20-
2123#
2224### Type of change:
2325<!-- You should choose 1 option and delete options that aren't relevant -->
@@ -27,13 +29,90 @@ I worked on ... because ...
2729- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
2830- [ ] Documentation
2931
32+ #
33+ ### High-level design:
34+ <!--
35+ REQUIRED for large PRs (new features, refactors, breaking changes, or anything touching >5 files).
36+ Skip for small bug fixes and trivial changes.
37+
38+ Cover:
39+ - Architecture / approach you took and why
40+ - Key components or files added/changed and how they interact
41+ - Alternatives considered and why you rejected them
42+ - Any migration, backward-compatibility, or rollout concerns
43+ - Diagrams or links to design docs / RFCs if available
44+ -->
45+
46+ N/A — small change. <!-- Or fill in the design above -->
47+
48+ #
49+ ### Tests:
50+
51+ #### Use cases covered
52+ <!--
53+ List the user-visible scenarios this PR exercises. Example:
54+ - User with Admin role can create a Glossary Term with a parent term
55+ - Ingestion run for Snowflake correctly extracts row counts for partitioned tables
56+ -->
57+
58+ #### Unit tests
59+ <!--
60+ - [ ] I added unit tests for the new/changed logic.
61+ - Files added/updated:
62+ - Coverage on changed classes (run `mvn jacoco:report` for backend, `yarn test:coverage` for UI,
63+ `make unit_ingestion` for ingestion). Target is 90% line coverage on changed classes.
64+ - Coverage %: <e.g., 92% on EntityRepository.java>
65+ -->
66+
67+ #### Backend integration tests
68+ <!--
69+ - [ ] I added integration tests in `openmetadata-integration-tests/` for new/changed API endpoints.
70+ - [ ] Not applicable (no backend API changes).
71+ - Files added/updated:
72+ -->
73+
74+ #### Ingestion integration tests
75+ <!--
76+ - [ ] I added/updated ingestion integration tests for connector changes.
77+ - [ ] Not applicable (no ingestion changes).
78+ - Files added/updated:
79+ -->
80+
81+ #### Playwright (UI) tests
82+ <!--
83+ - [ ] I added Playwright E2E tests under `openmetadata-ui/.../ui/playwright/` for UI changes.
84+ - [ ] Not applicable (no UI changes).
85+ - Files added/updated:
86+ -->
87+
88+ #### Manual testing performed
89+ <!--
90+ List the manual test steps you performed before requesting review. Example:
91+ 1. Started local stack via `./docker/run_local_docker.sh -m ui -d mysql`
92+ 2. Logged in as admin, created entity X, verified Y appears in the UI
93+ 3. Triggered ingestion for Snowflake source, confirmed lineage edges in the explore page
94+ -->
95+
96+ #
97+ ### UI screen recording / screenshots:
98+ <!--
99+ REQUIRED for any PR that changes the UI. Drag-and-drop a short screen recording (.mov / .mp4 / .gif)
100+ demonstrating the change end-to-end, plus before/after screenshots where relevant.
101+ Mark "Not applicable" if there are no UI changes.
102+ -->
103+
104+ Not applicable. <!-- Or attach recording/screenshots above -->
105+
30106#
31107### Checklist:
32108<!-- add an x in [] if done, don't mark items that you didn't do !-->
33109- [x] I have read the [ ** CONTRIBUTING** ] ( https://docs.open-metadata.org/developers/contribute ) document.
34110- [ ] My PR title is ` Fixes <issue-number>: <short explanation> `
35- - [ ] I have commented on my code, particularly in hard-to-understand areas.
111+ - [ ] My PR is linked to a GitHub issue via ` Fixes #<issue-number> ` above.
112+ - [ ] I have commented on my code, particularly in hard-to-understand areas.
36113- [ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.
114+ - [ ] For UI changes: I attached a screen recording and/or screenshots above.
115+ - [ ] I have added tests (unit / integration / Playwright as applicable) and listed them above.
37116
38117<!-- Based on the type(s) of your change, uncomment the required checklist 👇 -->
39118
0 commit comments