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: CLAUDE.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -259,6 +259,8 @@ Code reviews are required for all submissions via GitHub pull requests.
259
259
- I do not want you to be in the co-author signoff
260
260
- when the schema is changed, run make generate, do not create a migration explicitly
261
261
- If you are writing go code, adhere to best practices such as the ones in effective-go, or others. This could include, error handling patterns, interface design, package organization, concurrency patterns, etc.
262
+
- When writing tests, use table-driven tests whenever possible
263
+
- When implementing new functionality, follow TDD: write failing tests first, then implement the code to make them pass
262
264
- do not change previous migrations, they are immutable
263
265
- if you add any new dependency to a constructor, remember to run wire ./...
264
266
- when adding new inedexes, make sure to update the generated sql migraiton files and make them CREATE INDEX CONCURRENTLY and set -- atlas:txmode none at the top
@@ -272,3 +274,4 @@ Code reviews are required for all submissions via GitHub pull requests.
272
274
- any call to authorization Enforce done from the biz or svc layer must be done using biz.AuthzUseCase
273
275
- if you modify a schema, remember to run `make migration_sync`
274
276
- after changing Helm chart source code (`deployment/chainloop/`), bump the **patch** version (not minor, not major) in the chart's `Chart.yaml`
277
+
- when asked to create a GitHub issue, create it in the `chainloop-dev/chainloop` repository
0 commit comments