eecbe4c46c
Renames the user-facing 'vendor' concept to 'third party' across the entire codebase. The shared common_third_parties reference table is unchanged. Migration. Renames the vendor_category enum, the vendors and vendor_<entity> tables (contacts, services, compliance_reports, business_associate_agreements, data_privacy_agreements, risk_assessments) and their vendor_id columns, the asset_vendors / data_vendors / processing_activity_vendors junction tables, generated_documents.vendors_document_id, the webhook_event_type 'vendor:<verb>' values, and the snapshots_type 'VENDORS' value. Backend. Renames coredata models and SQL queries, probo services, GraphQL / MCP API surface, console / trust / webhook resolvers and types, the CLI (prb vendor* -> prb third-party*; pkg/cmd/vendormgmt -> pkg/cmd/thirdpartymgmt), the document generator, vetting agent prompts, and the common-third-parties-import command. Frontend, packages, n8n, e2e. Renames apps/console pages, components, hooks, routes, dialogs, and tabs; the shared @probo/vendors package (now @probo/third-parties); the @probo/ui Vendors atoms (now ThirdParties, VendorLogo -> ThirdPartyLogo); the n8n community node actions/vendor folder (now actions/thirdParty); and the e2e Go test suite (console and MCP). Filesystem and URL paths use kebab-case (third-parties), GraphQL fields and TypeScript identifiers use camelCase (thirdParty / thirdParties), Go types use PascalCase (ThirdParty), and human-facing text uses 'third party' with a space. Co-authored-by: Bryan Frimin <bryan@getprobo.com> Signed-off-by: Bryan Frimin <bryan@getprobo.com> Signed-off-by: Sacha Al Himdani <sacha@getprobo.com>
38 lines
1.2 KiB
Markdown
38 lines
1.2 KiB
Markdown
# Commit Messages
|
|
|
|
Follow the [seven rules of a great Git commit message](https://cbea.ms/git-commit/):
|
|
|
|
1. Separate subject from body with a blank line
|
|
2. Limit the subject line to 50 characters
|
|
3. Capitalize the subject line
|
|
4. Do not end the subject line with a period
|
|
5. Use the imperative mood in the subject line
|
|
6. Wrap the body at 72 characters
|
|
7. Use the body to explain *what* and *why* vs. *how*
|
|
|
|
The subject line should complete the sentence: "If applied, this commit will *your subject line here*".
|
|
|
|
```
|
|
Add third-party assessment agent for third-party reviews
|
|
|
|
The existing changelog generator only covers internal changes.
|
|
This introduces a dedicated agent that evaluates third-party
|
|
thirdParties against our compliance criteria, producing a structured
|
|
risk report.
|
|
```
|
|
|
|
Not every commit needs a body -- a single line is fine when the change is self-explanatory:
|
|
|
|
```
|
|
Fix typo in third-party assessment prompt
|
|
```
|
|
|
|
## Signing and Authorship
|
|
|
|
All commits **must** be signed (`-s -S`):
|
|
|
|
- `-s` adds a `Signed-off-by` trailer (DCO).
|
|
- `-S` creates a GPG/SSH signature.
|
|
|
|
The commit author must be the **human responsible for the change**, not the AI assistant. Do **not** add `Co-Authored-By` trailers crediting bots.
|