docs: rebrand Certifai → Prüfwerk (user-facing name) (#243)

2026-09-02 08:00:12 +00:00
parent e0c54c4659
commit 710fdcab6f
15 changed files with 59 additions and 59 deletions
@@ -1,6 +1,6 @@
 # Adding Repositories

-Repositories are the core resource in Certifai. Each tracked repository is scanned on a schedule, and its results are available across all features -- findings, SBOM, code graph, AI chat, and issue tracking.
+Repositories are the core resource in Prüfwerk. Each tracked repository is scanned on a schedule, and its results are available across all features -- findings, SBOM, code graph, AI chat, and issue tracking.

 ## Adding a Repository

@@ -20,11 +20,11 @@ The repository appears in the list immediately. It will not be scanned until you

 **Public repositories** can be cloned using an HTTPS URL with no additional setup.

-**Private repositories** require SSH access. When you add a repository with an SSH URL (e.g. `git@github.com:org/repo.git`), Certifai uses an SSH deploy key to authenticate.
+**Private repositories** require SSH access. When you add a repository with an SSH URL (e.g. `git@github.com:org/repo.git`), Prüfwerk uses an SSH deploy key to authenticate.

 ### Getting the SSH Public Key

-To grant Certifai access to a private repository:
+To grant Prüfwerk access to a private repository:

 1. Go to the **Repositories** page
 2. The platform's SSH public key is available for copying
@@ -34,7 +34,7 @@ To grant Certifai access to a private repository:
   - **Gitea**: Repository Settings > Deploy Keys > Add Deploy Key

 ::: tip
-Deploy keys are scoped to a single repository and are read-only by default. This is the recommended approach for granting Certifai access to private code.
+Deploy keys are scoped to a single repository and are read-only by default. This is the recommended approach for granting Prüfwerk access to private code.
 :::

 ## Configuring an Issue Tracker