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
Related ClickUp, GitHub or Jira tickets : ALEPH-XXX
4
+
5
+
## Self proofreading checklist
6
+
7
+
-[ ] The new code clear, easy to read and well commented.
8
+
-[ ] New code does not duplicate the functions of builtin or popular libraries.
9
+
-[ ] An LLM was used to review the new code and look for simplifications.
10
+
-[ ] New classes and functions contain docstrings explaining what they provide.
11
+
-[ ] All new code is covered by relevant tests.
12
+
-[ ] Documentation has been updated regarding these changes.
13
+
-[ ] Dependencies update in the project.toml have been mirrored in the Debian package build script `packaging/Makefile`
14
+
15
+
## Changes
16
+
17
+
Explain the changes that were made. The idea is not to list exhaustively all the changes made (GitHub already provides a full diff), but to help the reviewers better understand:
18
+
- which specific file changes go together, e.g: when creating a table in the front-end, there usually is a config file that goes with it
19
+
- the reasoning behind some changes, e.g: deleted files because they are now redundant
20
+
- the behaviour to expect, e.g: tooltip has purple background color because the client likes it so, changed a key in the API response to be consistent with other endpoints
21
+
22
+
## How to test
23
+
24
+
Explain how to test your PR.
25
+
If a specific config is required explain it here (account, data entry, ...)
26
+
27
+
## Print screen / video
28
+
29
+
Upload here screenshots or videos showing the changes if relevant.
30
+
31
+
## Notes
32
+
33
+
Things that the reviewers should know: known bugs that are out of the scope of the PR, other trade-offs that were made.
34
+
If the PR depends on a PR in another repo, or merges into another PR (i.o. main), it should also be mentioned here
0 commit comments