Kabaforce/guide
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

kılavuz: dil dizinleri (en/tr/de/fr/ru) + dil değiştirici ve bölüm gezinmesi

Browse Source 
- iki dilli tek dosyalar en/ ve tr/ altına ayrıldı
- Almanca, Fransızca, Rusça çeviriler eklendi (10 bölüm)
- kök README dil seçici oldu; her dilde kendi içindekiler sayfası
- her bölüme dil değiştirici satırı + önceki/sonraki gezinme eklendi
This commit is contained in:
semih
2026-07-24 10:21:13 +03:00
parent dfebe8a742
commit 01e9b4d15f
59 changed files with 2697 additions and 705 deletions
Download Patch File Download Diff File Expand all files Collapse all files
en/01-getting-started/readme.md
+43
View File
@@ -0,0 +1,43 @@
# 01 — Getting started
🌍 **English** · [Türkçe](../../tr/01-getting-started/readme.md) · [Deutsch](../../de/01-getting-started/readme.md) · [Français](../../fr/01-getting-started/readme.md) · [Русский](../../ru/01-getting-started/readme.md)
KabaForge is the place where your code, documents and project history live. This chapter gets you signed in and shows you around.
## Signing in
1. Open [forge.kabaforce.com](https://forge.kabaforce.com).
2. Press **Sign in with KabaForce ID**.
3. Enter your KabaForce account details on `id.kabaforce.com`.
4. You are returned to KabaForge, signed in.
There is no separate password for KabaForge — your KabaForce ID is the only account you need. If you do not have one yet, use the **Sign up** link on the same page.
## What you see after signing in
| Area | What it is for |
|------|----------------|
| **Dashboard** (home) | Recent activity across your repositories |
| **Explore** | Public repositories on this server |
| **+** (top right) | Create a new repository or organisation |
| **Avatar** (top right) | Your profile, settings and sign out |
## Vocabulary you will meet
- **Repository (repo)** — one project: its files plus their entire history.
- **Commit** — one saved change, with a message describing it.
- **Branch** — a parallel line of work; the default one is usually `main`.
- **Pull request** — a proposal to merge one branch into another.
## Your first five minutes
1. Press **+ → New Repository**.
2. Name it `deneme` (or anything else), tick *Initialize repository*, press **Create**.
3. Open it and press **Add File → New File**.
4. Type `readme.md` as the name, write a couple of lines, press **Commit Changes**.
You now have a repository with a front page. The next chapters explain each of those steps in detail.
---
📚 [Contents](../README.md) · [Next: 02 — Creating a repository](../02-create-repository/readme.md) ➡
en/02-create-repository/readme.md
+41
View File
@@ -0,0 +1,41 @@
# 02 — Creating a repository
🌍 **English** · [Türkçe](../../tr/02-create-repository/readme.md) · [Deutsch](../../de/02-create-repository/readme.md) · [Français](../../fr/02-create-repository/readme.md) · [Русский](../../ru/02-create-repository/readme.md)
A repository is one project. Create one per project, not one per file.
## Steps
1. Press **+** at the top right → **New Repository**.
2. **Owner** — yourself, or an organisation you belong to.
3. **Repository name** — lowercase, no spaces: `network-lab`, `web-site`, `guide`.
4. **Description** — one line explaining what it is. It appears in search results.
5. **Visibility**
- *Public* — anyone who can reach the server can read it.
- *Private* — only you and the people you invite.
6. **Initialize repository** — tick it. This creates the first commit with a `README.md`, so the repository is usable straight away.
7. Press **Create Repository**.
## Good names
| Instead of | Prefer |
|-----------|--------|
| `Yeni Proje (son)` | `yeni-proje` |
| `Ağ Ödevi 1` | `network-lab-01` |
| `test test 2` | `packet-tracer-tests` |
Spaces and brackets in names make links harder to share and can confuse relative paths inside documents. Lowercase letters, digits and hyphens are always safe.
## After creation
- **Settings → Collaborators** — give other people read or write access.
- **Settings → Branches** — protect `main` so nobody commits to it directly.
- **Add File** — start filling the repository (chapter 03).
## Deleting a repository
**Settings → Danger Zone → Delete this repository.** You must type the repository name to confirm. This cannot be undone — the history goes with it.
---
⬅ [Previous: 01 — Getting started](../01-getting-started/readme.md) · 📚 [Contents](../README.md) · [Next: 03 — Adding and editing files](../03-add-and-edit-files/readme.md) ➡
en/03-add-and-edit-files/readme.md
+52
View File
@@ -0,0 +1,52 @@
# 03 — Adding and editing files
🌍 **English** · [Türkçe](../../tr/03-add-and-edit-files/readme.md) · [Deutsch](../../de/03-add-and-edit-files/readme.md) · [Français](../../fr/03-add-and-edit-files/readme.md) · [Русский](../../ru/03-add-and-edit-files/readme.md)
Everything in this chapter happens in the browser. No tools to install.
## Add File menu
Open a repository (or any folder inside it) and press **Add File**:
| Item | Use it for |
|------|-----------|
| **New File** | Writing a file by hand — notes, code, `readme.md` |
| **New Directory** | Creating an empty folder (chapter 04) |
| **Upload File** | Bringing files from your computer — images, PDFs, archives |
| **Patch** | Applying a ready-made diff |
## Writing a new file
1. **Add File → New File**.
2. Type the file name at the top, for example `notes.md`.
Typing `docs/notes.md` creates the `docs` folder at the same time.
3. Write the content in the editor.
4. Fill in the commit box at the bottom:
- **Summary** — short, in the imperative: *add setup notes*.
- **Description** — optional detail.
5. Choose **Commit directly to `main`**, or *create a new branch* if you want a review first (chapter 09).
6. Press **Commit Changes**.
## Uploading files
1. **Add File → Upload File**.
2. Drag files in, or press the box to pick them.
3. To place them in a subfolder, type the folder name in the path field at the top.
4. Press **Commit Changes**.
Very large files (video, disk images) belong in file storage, not in a repository — the history keeps every version forever.
## Editing an existing file
1. Open the file.
2. Press the pencil ✏️ icon at the top right.
3. Change the text; the **Preview changes** tab shows what you altered.
4. Commit as above.
## Renaming and moving
Editing a file lets you change its path: put the cursor in the name field and type a new path, e.g. `docs/notes.md`. On commit, the file is moved — history is preserved.
---
⬅ [Previous: 02 — Creating a repository](../02-create-repository/readme.md) · 📚 [Contents](../README.md) · [Next: 04 — Creating directories](../04-create-directory/readme.md) ➡
en/04-create-directory/readme.md
+50
View File
@@ -0,0 +1,50 @@
# 04 — Creating directories
🌍 **English** · [Türkçe](../../tr/04-create-directory/readme.md) · [Deutsch](../../de/04-create-directory/readme.md) · [Français](../../fr/04-create-directory/readme.md) · [Русский](../../ru/04-create-directory/readme.md)
## The quick way
1. Open the repository, or the folder you want the new folder inside.
2. **Add File → New Directory**.
3. Type the folder name, e.g. `docs`.
4. Press **Commit Changes**.
The panel shows where the folder will be created (`current/path/`) above the name box, so you always know where you are.
## Nested folders in one go
Type a path instead of a single name:
```
docs/images
```
That creates `docs`, and `images` inside it, in a single commit.
## Why a `.gitkeep` file appears
Version control tracks *files*, not empty folders. To keep a folder that has nothing in it yet, KabaForge puts an empty file named `.gitkeep` inside. It has no effect on your project — delete it once the folder has real content, or simply leave it.
## The other way: create a folder while creating a file
**Add File → New File** and type a path in the name box:
```
reports/2026/january.md
```
Both folders and the file are created together. Use this when you already know the first file.
## Naming rules that save you pain
| Avoid | Use |
|-------|-----|
| `Ağ Ödevi (1)` | `network-lab-01` |
| `My Notes` | `my-notes` or `notes` |
| `resimler ve ekler` | `assets` |
Folder names with **spaces** or brackets make links harder to share, and relative image paths inside Markdown are more fragile. Lowercase letters, digits and hyphens are always safe.
---
⬅ [Previous: 03 — Adding and editing files](../03-add-and-edit-files/readme.md) · 📚 [Contents](../README.md) · [Next: 05 — Deleting files and directories](../05-delete-files/readme.md) ➡
en/05-delete-files/readme.md
+49
View File
@@ -0,0 +1,49 @@
# 05 — Deleting files and directories
🌍 **English** · [Türkçe](../../tr/05-delete-files/readme.md) · [Deutsch](../../de/05-delete-files/readme.md) · [Français](../../fr/05-delete-files/readme.md) · [Русский](../../ru/05-delete-files/readme.md)
Nothing is ever truly lost: a deletion is just another commit, and the old content stays in the history.
## Deleting one file
1. Open the file.
2. Press the **…** menu at the top right of the file view.
3. Choose **Delete this file** (or use the 🗑️ icon next to the edit pencil).
4. Write a commit message and press **Commit Changes**.
## Deleting a folder
1. Open the folder.
2. Press the **…** menu next to *Add File*.
3. Choose **Delete this directory**.
4. Commit.
Everything inside the folder is removed in that single commit.
## Deleting several files at once
The browser deletes one path at a time. For a large clean-up, work from your computer (chapter 10):
```bash
git rm -r old-folder
git commit -m "remove old folder"
git push
```
## Getting a deleted file back
1. Open **History** on the folder that used to contain it, or the repository history.
2. Find the commit *before* the deletion.
3. Open the file at that commit and copy the content, or press **Browse source at this point** and recreate it.
Anything that was ever committed can be recovered. Something you typed in the editor but never committed cannot.
## Careful with
- **Deleting the folder instead of the file** — check the menu title says *file* when you mean one file.
- **Protected branches** — if `main` is protected, deletion goes through a pull request instead (chapter 09).
- **Secrets** — deleting a password from a file does *not* remove it from the history. Change the password itself.
---
⬅ [Previous: 04 — Creating directories](../04-create-directory/readme.md) · 📚 [Contents](../README.md) · [Next: 06 — Markdown basics](../06-markdown-basics/readme.md) ➡
en/06-markdown-basics/readme.md
+83
View File
@@ -0,0 +1,83 @@
# 06 — Markdown basics
🌍 **English** · [Türkçe](../../tr/06-markdown-basics/readme.md) · [Deutsch](../../de/06-markdown-basics/readme.md) · [Français](../../fr/06-markdown-basics/readme.md) · [Русский](../../ru/06-markdown-basics/readme.md)
Markdown is plain text with a few punctuation rules. Files ending in `.md` are rendered automatically, and a file named `readme.md` is shown on its folder page.
## Headings
```markdown
# Title
## Section
### Subsection
```
Leave a blank line before and after a heading.
## Text
```markdown
**bold** *italic* ~~struck through~~ `code`
```
A single line break is ignored. To start a new paragraph, leave a blank line.
## Lists
```markdown
- first
- second
- nested (two spaces)
1. step one
2. step two
```
## Links
```markdown
[KabaForge](https://forge.kabaforce.com)
[chapter 04](../04-create-directory/readme.md)
```
Links to files in the same repository are best written as relative paths — they keep working on every branch.
## Code
Fenced blocks keep spacing and add colours. Write the language after the opening fence:
~~~markdown
```bash
git status
```
~~~
## Tables
```markdown
| Column | Meaning |
|--------|---------|
| `main` | default branch |
| `.md` | Markdown file |
```
## Quotes, rules, tasks
```markdown
> A quoted note.
---
- [x] done
- [ ] not done yet
```
## Practical tips
- Preview before committing: the **Preview** tab in the editor renders exactly what others will see.
- Keep one sentence per line in long documents — differences between versions stay readable.
- Emoji work directly: 📌 ✅ ⚠️
---
⬅ [Previous: 05 — Deleting files and directories](../05-delete-files/readme.md) · 📚 [Contents](../README.md) · [Next: 07 — Images and attachments](../07-images-and-media/readme.md) ➡
en/07-images-and-media/readme.md
+71
View File
@@ -0,0 +1,71 @@
# 07 — Images and attachments
🌍 **English** · [Türkçe](../../tr/07-images-and-media/readme.md) · [Deutsch](../../de/07-images-and-media/readme.md) · [Français](../../fr/07-images-and-media/readme.md) · [Русский](../../ru/07-images-and-media/readme.md)
## Putting an image in a document
1. Upload the image next to the document: open the folder, **Add File → Upload File**.
2. Reference it from the Markdown file:
```markdown
![Network topology](topology.png)
```
The text in brackets is the description shown if the image cannot load, and read aloud by screen readers. Write a real description, not "image".
## Where to keep images
A predictable layout that always works:
```
project/
readme.md
assets/
topology.png
rack.jpg
```
and in `readme.md`:
```markdown
![Network topology](assets/topology.png)
```
## Naming — the one rule to remember
Use lowercase names without spaces for **folders** and image files:
| Fragile | Safe |
|---------|------|
| `Ekran Alıntısı.PNG` | `ekran-alintisi.png` |
| `1-) Inter-VLAN Notes/` | `01-inter-vlan/` |
If a name does contain spaces, write them as `%20` in the link:
```markdown
![Topology](Ekran%20Alintisi.PNG)
```
## Controlling the size
Markdown has no size option, so use a plain HTML tag when you need one:
```markdown
<img src="assets/topology.png" alt="Network topology" width="600">
```
## Linking a file instead of showing it
Drop the exclamation mark and you get a download link:
```markdown
[Packet Tracer file](main.pkt)
```
## Attachments in issues
While writing an issue or a comment, drag a file into the text box. It is uploaded and the link is inserted for you. Use this for screenshots and logs that do not belong in the repository itself.
---
⬅ [Previous: 06 — Markdown basics](../06-markdown-basics/readme.md) · 📚 [Contents](../README.md) · [Next: 08 — Commits and history](../08-commits-and-history/readme.md) ➡
en/08-commits-and-history/readme.md
+46
View File
@@ -0,0 +1,46 @@
# 08 — Commits and history
🌍 **English** · [Türkçe](../../tr/08-commits-and-history/readme.md) · [Deutsch](../../de/08-commits-and-history/readme.md) · [Français](../../fr/08-commits-and-history/readme.md) · [Русский](../../ru/08-commits-and-history/readme.md)
A commit is one saved step: what changed, who changed it, when, and why.
## Writing a good message
```
add VLAN configuration notes
fix wrong gateway address in readme
remove unused packet capture
```
- One line, present tense, no full stop.
- Say *what* the change does, not "update" or "fix stuff".
- Longer explanation? Put it in the description box below the summary.
## Committing well
- **One idea per commit.** Two unrelated changes are two commits.
- **Commit often.** Small steps are easy to review and easy to undo.
- **Never commit passwords, keys or tokens.** Removing them later does not remove them from history — you have to change the secret itself.
## Reading history
| Where | What you get |
|-------|--------------|
| **History** button on a folder or file | Every commit that touched it |
| A commit's page | The full diff: red removed, green added |
| **Blame** on a file | Which commit last changed each line |
| **Activity** tab | Contribution graph over time |
## Undoing
- **One commit was wrong** → open the commit, press **Revert**. This creates a new commit that undoes it; nothing is erased.
- **A file was wrong** → open its history, view the good version, copy the content back and commit.
- **A commit is not pushed yet** (working from your computer) → `git commit --amend` to fix the last one before sharing it.
## Comparing
Add `/compare/main...my-branch` to a repository URL, or use the **Compare** button, to see every difference between two branches or tags.
---
⬅ [Previous: 07 — Images and attachments](../07-images-and-media/readme.md) · 📚 [Contents](../README.md) · [Next: 09 — Branches and pull requests](../09-branches-and-pull-requests/readme.md) ➡
en/09-branches-and-pull-requests/readme.md
+58
View File
@@ -0,0 +1,58 @@
# 09 — Branches and pull requests
🌍 **English** · [Türkçe](../../tr/09-branches-and-pull-requests/readme.md) · [Deutsch](../../de/09-branches-and-pull-requests/readme.md) · [Français](../../fr/09-branches-and-pull-requests/readme.md) · [Русский](../../ru/09-branches-and-pull-requests/readme.md)
A branch is a safe copy of the project where you can work without disturbing `main`. A pull request is the request to bring that work back.
## When you need a branch
- The change is big enough that half-finished work would break things.
- Somebody should look at it before it goes live.
- You want to try an idea and be able to throw it away.
For a typo in a document, committing straight to `main` is fine.
## Creating a branch in the browser
While committing (chapter 03), choose **Create a new branch for this commit and start a pull request**, name the branch, and commit. Good names describe the work:
```
docs/vlan-notes
fix/wrong-gateway
feature/report-export
```
## Opening a pull request
1. Go to **Pull Requests → New Pull Request**.
2. Pick the source branch (yours) and the target (`main`).
3. Title = what the change does. Description = why, plus anything reviewers should check.
4. Press **Create Pull Request**.
## Review
- Reviewers comment on individual lines from the **Files Changed** tab.
- Push more commits to the same branch — the pull request updates itself.
- When it is approved, press **Merge Pull Request**, then delete the branch.
## Merge conflicts
If `main` changed the same lines you did, KabaForge asks you to resolve it. From your computer:
```bash
git switch my-branch
git fetch origin
git merge origin/main
# open the marked files, keep the correct lines
git add .
git commit
git push
```
## Protecting `main`
**Settings → Branches → Add rule**: require pull requests and approvals before anything reaches `main`. Recommended as soon as more than one person works in the repository.
---
⬅ [Previous: 08 — Commits and history](../08-commits-and-history/readme.md) · 📚 [Contents](../README.md) · [Next: 10 — Working from your computer](../10-clone-and-tokens/readme.md) ➡
en/10-clone-and-tokens/readme.md
+75
View File
@@ -0,0 +1,75 @@
# 10 — Working from your computer
🌍 **English** · [Türkçe](../../tr/10-clone-and-tokens/readme.md) · [Deutsch](../../de/10-clone-and-tokens/readme.md) · [Français](../../fr/10-clone-and-tokens/readme.md) · [Русский](../../ru/10-clone-and-tokens/readme.md)
The browser is enough for documents. For real work — many files at once, or running the code — copy the repository to your machine.
## Getting a copy
Press the **Clone** button on the repository page and copy the address.
```bash
git clone https://forge.kabaforce.com/owner/project.git
cd project
```
## The daily loop
```bash
git pull # get what others changed
# ... edit files ...
git status # what did I change?
git add . # stage the changes
git commit -m "add setup notes"
git push # send them to KabaForge
```
If `git push` is rejected, somebody else pushed first: run `git pull`, resolve anything it reports, then push again.
## Signing in from the command line
Your KabaForce ID password does not work over HTTPS. Create a token instead:
1. **Avatar → Settings → Applications → Generate New Token**.
2. Give it a name and only the permissions you need (`repo` is usually enough).
3. Copy it once — it is never shown again.
4. When git asks for a password, paste the token.
Store it so you are asked only once:
```bash
git config --global credential.helper store
```
## SSH instead of tokens
1. Create a key if you do not have one: `ssh-keygen -t ed25519`
2. Copy `~/.ssh/id_ed25519.pub`.
3. **Avatar → Settings → SSH Keys → Add Key**, paste it.
4. Clone with the SSH address shown under **Clone**.
No password prompts after that.
## Useful extras
| Need | Command |
|------|---------|
| See the history | `git log --oneline --graph` |
| Discard local changes to a file | `git restore file.md` |
| Switch branch | `git switch branch-name` |
| Create a branch | `git switch -c new-branch` |
## Automation
Repositories can also be read and written through the KabaForge API using the same token:
```bash
curl -H "Authorization: token YOUR_TOKEN" \
https://forge.kabaforce.com/api/v1/repos/owner/project/contents
```
Treat tokens like passwords: never put one in a file you commit.
---
⬅ [Previous: 09 — Branches and pull requests](../09-branches-and-pull-requests/readme.md) · 📚 [Contents](../README.md)
en/README.md
+38
View File
@@ -0,0 +1,38 @@
# 📘 KabaForge Guide — English
Short, practical recipes for using KabaForge — no prior experience required.
🌍 **English** · [Türkçe](../tr/README.md) · [Deutsch](../de/README.md) · [Français](../fr/README.md) · [Русский](../ru/README.md)
---
## 📚 Chapters
| # | Chapter |
|---|---------|
| 01 | [Getting started](01-getting-started/readme.md) |
| 02 | [Creating a repository](02-create-repository/readme.md) |
| 03 | [Adding and editing files](03-add-and-edit-files/readme.md) |
| 04 | [Creating directories](04-create-directory/readme.md) |
| 05 | [Deleting files and directories](05-delete-files/readme.md) |
| 06 | [Markdown basics](06-markdown-basics/readme.md) |
| 07 | [Images and attachments](07-images-and-media/readme.md) |
| 08 | [Commits and history](08-commits-and-history/readme.md) |
| 09 | [Branches and pull requests](09-branches-and-pull-requests/readme.md) |
| 10 | [Working from your computer](10-clone-and-tokens/readme.md) |
---
## 🚀 The 60-second version
1. Sign in at [forge.kabaforce.com](https://forge.kabaforce.com) with your KabaForce ID.
2. Press **+ → New Repository**, give it a name, tick *Initialize repository*.
3. Open the repository, press **Add File → New File**, write something, press **Commit Changes**.
4. Name a file `readme.md` and it is shown automatically on the folder page.
---
## 💡 How to read this guide
Chapters are independent. Jump to the one you need; each is a single page you can
finish in a few minutes.