# Good PR and Commits Start your PR title with a good tag: `feat: fix: refacto: doc:`.... See [[Git Commit Type]] Put in the general commit message the "what" and "why": - `What`: what does this PR does at a high level: modification of code, modification of behavior, what you implemented - `Why`: why you do this PR, why it's necessary, what does it solves ? Example: ``` ### Feat: Query ID at the query time and feedback comments - Why: Currently giving feedback requiere to list queries to get their ID. Now we can use the ID provided by Bedrock directly at query time to send feedback - What: Adding query_uuid to store bedrock ID and allowing to enter string ID to feedback endpoint. It requiered a DB migration. Also keep support for legacy query_id (int). Allow feedback comments ```