-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add verified commits docs page (#283)
* add verified commits docs page * Update cloud/features/verified-commits.mdx Co-authored-by: Mark Phelps <[email protected]> * chore: titlecase Signed-off-by: Mark Phelps <[email protected]> * chore: finalize docs Signed-off-by: Mark Phelps <[email protected]> --------- Signed-off-by: Mark Phelps <[email protected]> Co-authored-by: Mark Phelps <[email protected]>
- Loading branch information
1 parent
807f4ab
commit 27f5e91
Showing
5 changed files
with
57 additions
and
29 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
--- | ||
title: Verified Commits | ||
description: Learn about verifying Git commits with Flipt Cloud | ||
mode: "wide" | ||
--- | ||
|
||
Verify Flipt's commits to your GitHub repository with SSH signing keys. This ensures that commits are authentic and have not been tampered with. You can be confident that the commits you see in your repository are indeed from Flipt. | ||
|
||
You can learn more about GitHub's commit verification in the [GitHub documentation](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification). | ||
|
||
![Signed Commits](/images/cloud/features/verified-commits/commits.png) | ||
|
||
<Info> | ||
Verified Commits are only available on our Team plan and above. See our | ||
[pricing page](https://www.flipt.io/pricing) for more information. | ||
</Info> | ||
|
||
## Creating a Signing Key | ||
|
||
![Signed Commits](/images/cloud/features/verified-commits/generate-key.png) | ||
|
||
To verify commits with Flipt Cloud, we'll need to create a | ||
signing key, as Flipt needs to be able to sign the commits it | ||
creates itself. | ||
|
||
To do this, head to your user settings in Flipt Cloud, and click 'Generate Key'. | ||
|
||
![Signed Commits](/images/cloud/features/verified-commits/signing-key.png) | ||
|
||
## Adding Your Key to GitHub | ||
|
||
Head to your [key settings](https://github.com/settings/keys) in GitHub, and add it | ||
as an SSH **Signing Key**. | ||
|
||
It's important that it should be a signing key, rather than an authentication | ||
key, as we don't want this key to be able to push to your repositories, just to | ||
verify commits. | ||
|
||
## How We Store Your Key | ||
|
||
Flipt uses [AWS Key Management Service (KMS)](https://aws.amazon.com/kms/) to generate and store your signing key. This means we don't | ||
ever have access to the private key, and instead ask the KMS API to sign commits using your key. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters