Taguna da sakamakon aiki suna yin aiki a cikin Git?

Question

Accepted Answer

**Taguna** suna tabbatar da wasu wurare na tarihi masu mahimmanci — gamitin **sakamakon aiki** (nau'ikan kamar v1.0.0). Ba kamar reshen ba, taguna sune masu tsayawa waɗanda ba sa motsi, ana amfani da su don sanya labels da nuna nau'ikan sakamakon aiki. Suna da mahimmanci ga ƙididdiga da gudanarwa na sakamakon aiki.

## Sarrafa taguna

```bash
# annotated tag (recommended for releases — has metadata: tagger, date, message)
git tag -a v1.0.0 -m "Release version 1.0.0"

# lightweight tag (just a pointer, no metadata)
git tag v1.0.0

# tag a specific past commit
git tag -a v1.0.0 <commit> -m "..."
```

**Taguna masu bayanai** (an ba da shawara don sakamakon aiki) suna ajiye bayanai na meta (wanda ya yi tag, data, saƙo); **taguna masu nauyi kaɗan** shine kawai suna da bugi da nuni zuwa ƙudori.

## Aiki tare da taguna

```bash
git tag                        # list tags
git show v1.0.0                # show a tag and its commit
git checkout v1.0.0            # check out the code at a tag (detached HEAD)

# tags are NOT pushed by default — push them explicitly:
git push origin v1.0.0         # push a specific tag
git push origin --tags         # push all tags
```

Mahimmanci: **taguna ba sa tura atomatik** tare da `git push` — kuna tura su da bayyane.

## Taguna da reshen

```text
BRANCH → a MOVABLE pointer that advances as you commit (ongoing development)
TAG    → a FIXED pointer to a specific commit (a permanent label — doesn't move)
→ Use tags to permanently mark releases/milestones; branches for ongoing work.
```

## Semantic versioning da sakamakon aiki

```text
SEMANTIC VERSIONING (SemVer): MAJOR.MINOR.PATCH (e.g. v2.3.1)
  MAJOR → breaking changes | MINOR → new features (compatible) | PATCH → bug fixes
→ Tags label these versions. Platforms (GitHub) build "Releases" from tags
  (with release notes, built artifacts) for distribution.
```

## Dalilin da ya sa haka ya mahimma

Fahimtar taguna da sakamakon aiki yana da ƙima don **ƙididdiga da gudanarwa na sakamakon aiki**, don haka yana da mahimmancin aiki-aiki don aiki tare da sakamakon aiki. **Taguna** suna tabbatar da muhimmin wurare a tarihi — gamitin **sakamakon nau'ikan** (kamar v1.0.0) — suna ba da tsayawa, daimitaccen nuni zuwa ƴan ƙudori na musamman, wanda ya zama mahimmanci don duba da nuna abin da code ke nuni a kowacce sakamakon.

Fahimtar bambanci tsakanin **taguna masu bayanai** (an ba da shawara don sakamakon aiki, ajiye bayanai na meta kamar wanda ya yi tag, data, da saƙo) da taguna masu nauyi kaɗan yana da mahimmancin aiki don yi tajiya ta tag na sakamakon.

Sanin yadda za a sarrafa, jera, da bukatar taguna, da mahimmanci cewa **taguna ba sa tura atomatik** (buƙatar bayyane `git push origin --tags` ko tura taguna musamman — wani rashin fahimta na yau-yau inda jama'a ke sarrafa taguna amma suna manta tura su), ya zama mahimmanci don gyara tsayin gudanarwa na sakamakon.

Fahimtar **taguna da reshen** (tag shine tsayawa bugi zuwa ƴan ƙudori na musamman — daimitaccen label waɗanda ba sa motsi — yayin da reshe shine bugi mai motsi wanda ke ci gaba tare da haɓaka) yana bayyana nau'ukan daban-dabansu: taguna don daurin sakamakon/milestones, reshe don aiki na amsaka.

Fahimtar haɗin gida zuwa **semantic versioning** (dabi'u na MAJOR.MINOR.PATCH don sanar da yanayin canja-woji) da yadda platforms suke gina **Sakamakon** daga taguna (tare da saatin sakamakon da kayan aiki don rarrasa) yana nuna yadda taguna ke shiga tsayin gudanarwa na gaske.

Tunda fitar da kuma ƙididdiga na software shine buƙatuwa na yau-yau da taguna sune tsayin Git don tabbatar da sakamakon nau'ikan (mahimmanci wa gudanarwa na sakamakon da haɗa tare da wuraren ƙarƙashiya), fahimtar taguna da sakamakon — taguna masu bayanai da taguna masu nauyi kaɗan, tura su, taguna da reshen, da nau'ukansu a ƙididdiga/sakamakon — yana da ƙima, ilimin Git mai damici don gudanarwa na sakamakon software, ginin mahimmanci na haɓaka na kasuwa wanda ya haɗa da dabi'un ƙididdiga da tsayin rarrasa.