[PR #134] [MERGED] docs: add warning to save private key in SSH setup step #359

New issue

Closed

opened 2026-03-03 11:29:33 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 11:29:33 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/dflow-sh/dflow/pull/134
Author: @Maryam593
Created: 4/29/2025
Status: ✅ Merged
Merged: 4/29/2025
Merged by: @malla-lokesh

Base: main ← Head: docs/update-private-key-warning

📝 Commits (1)

a42f203 docs: add warning to save private key in SSH setup step

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 src/docs/onboarding/onboarding.md (+4 -0)

📄 Description

📝 What I Did

Updated onboarding.md documentation file.
Added a warning for users to securely save their private key during SSH key setup.

🧠 Why I Did It

Currently, the onboarding doc doesn't inform users that losing the private key will block access to the server.
This addition makes the onboarding process more robust and user-aware.

🗂️ File Changed

src/docs/onboarding/onboarding.md

📌 Note

No functional or code changes made — only documentation.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/dflow-sh/dflow/pull/134 **Author:** [@Maryam593](https://github.com/Maryam593) **Created:** 4/29/2025 **Status:** ✅ Merged **Merged:** 4/29/2025 **Merged by:** [@malla-lokesh](https://github.com/malla-lokesh) **Base:** `main` ← **Head:** `docs/update-private-key-warning` --- ### 📝 Commits (1) - [`a42f203`](https://github.com/dflow-sh/dflow/commit/a42f203735d3b2147b2f89cf99212f44c95e7297) docs: add warning to save private key in SSH setup step ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/docs/onboarding/onboarding.md` (+4 -0) </details> ### 📄 Description ## 📝 What I Did - Updated `onboarding.md` documentation file. - Added a warning for users to **securely save their private key** during SSH key setup. ## 🧠 Why I Did It - Currently, the onboarding doc doesn't inform users that losing the private key will block access to the server. - This addition makes the onboarding process more robust and user-aware. ## 🗂️ File Changed - `src/docs/onboarding/onboarding.md` ## 📌 Note - No functional or code changes made — only documentation. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>