Skip to content

Conversation

@Friedrich482
Copy link
Owner

No description provided.

refactor: logger, chore: extension bump, chore: extension bump, feat: react-day-picker, chore: migration, fix: calendar, fix: ProjectTimeOnPeriod , chore: checkbox, chore: zod,chore: web and feat: auth
fix: bar, line and area charts, chore: logging  and fix: DayLanguagesChart
- added a `build-and-deploy.yaml`for ci/cd, especially for the api
- added the monorepo eslint rules in the `@repo/common` and `@repo/trpc` packages
- replaced the usage of `z.prettifyError` in the `errorFormatter` filter of the api by the `formatZodError` utility function of the `@repo/common` package
- testing the dokploy webhook for auto-redeploy
- added husky for pre-commit hook
- changed the `npm run prepare` command to make the ci/cd pipeline pass (husky is a dev dependency so it is not installed during the `RUN npm ci --omit=dev` command of the `Dockerfile` of the api. But the ci command also runs the `npm run prepare` script  that needs husky. We now use `husky || true` to make it pass during that build)
@coderabbitai
Copy link

coderabbitai bot commented Nov 16, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch main

Tip

📝 Customizable high-level summaries are now available!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide custom instructions to shape the summary (bullet lists, tables, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example:

"Create a concise high-level summary as a bullet-point list. Then include a Markdown table showing lines added and removed by each contributing author."


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@Friedrich482 Friedrich482 merged commit 6c65c04 into features Nov 16, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants