11 — Issues, projects and wiki

Everything that is not code — to-dos, bugs, decisions and notes — lives inside the repository too.

Opening an issue

In the repository, Issues → New Issue.
Title — the problem or request in one sentence: login page shifts on mobile.
Description — what you expected, what happened, how to reproduce it. Markdown works (chapter 06).
Drag files into the text box to attach screenshots and logs.

Organising tools

Field	What it is for
Labels	Classify the issue: `bug`, `feature`, `docs`, `priority`
Milestone	Tie issues to a release or a date
Assignee	Who owns the work
Dependencies	This issue cannot start before that one is done

Define labels once under Issues → Labels; after that everybody uses the same vocabulary.

Closing an issue from a commit

Put the issue number in the commit message and the issue closes by itself when the change reaches main:

fix login page alignment on mobile

Fixes #12

Fixes, Closes and Resolves all work. To reference without closing, write just #12.

Search and filters

The filters above the issue list narrow by label, milestone, assignee and state. The resulting query in the address bar is shareable — hand your team the "open bugs" link.

Projects (boards)

Projects → New Project opens a kanban board: drag issues between To do / In progress / Done. Closing an issue closes its card. A board does not replace issues; it arranges them.

Wiki

The Wiki tab is a document space attached to the repository but separate from it: setup notes, architecture decisions, meeting outcomes. Pages are Markdown and keep their own history.

Rule of thumb: how the code works belongs in the repository (readme.md), the knowledge around it belongs in the wiki.

Activity

The Activity tab shows who did what over a period you choose: commits, issues opened and closed, pull requests merged. A ready-made summary for a weekly status meeting.