Skip to content
bparlaker edited this page Oct 13, 2026 · 4 revisions

Welcome to the cmpe-git-practice Wiki 👋

This wiki collects my notes on Git version management and on how this repository organises its work with issues and labels.

About me

I'm Berker Parlaker - see the README for a short introduction. What I like most about Git: every change is recorded, attributed, explained and reversible.

🎨 Term project: Local Art Archive

A website for sharing and discovering local and traditional art (kilim, ebru, çini, miniature, local artists...). Every craft entry is saved as structured data through the fields of its craft type.

  1. Project Overview: the idea, users, a sample scenario, scope
  2. Requirements: functional and non-functional requirements (MoSCoW) and requirement validation
  3. Domain Model: category tree, craft types, attributes with units, the Kilim example
  4. Use Cases: use case diagram, UC-04 flow, 10 use cases and user stories
  5. Mockups: 3 screens (add an entry, entry detail, define a craft type)
  6. Resources and Plan: people, time, tools, milestones, risks

Git notes

  1. Git Internals: what a commit really is (blobs, trees, SHA-1 hashes and the commit graph)
  2. Branching and Merging: branches as cheap pointers, fast-forward vs. merge commits, resolving conflicts
  3. Undoing Changes: restore, reset, revert, reflog and when to use which
  4. Rebase and Clean History: rebase, interactive rebase, cherry-pick, bisect
  5. Issue Labels: the label groups used here and the research behind them
  6. Writing Good Issues: template and checklist for well-formed issues

Quick start

git clone https://github.com/bparlaker/cmpe-git-practice.git
cd cmpe-git-practice
git log --oneline --graph --all

The wiki itself is a Git repository! Clone it with git clone https://github.com/bparlaker/cmpe-git-practice.wiki.git

Clone this wiki locally