How are feature branches usually named?

Usually feature branches are named so it is immediately clear what is being done in them and why. The name is a short task description plus context.

---

#The most common format

Examples:

• feature/login
• feature/user-profile
• feature/payment-integration

feature/ is a prefix that immediately signals: "a branch for new functionality".

---

#With a ticket number (very common in teams)

If Jira / YouTrack / GitHub Issues is used:

Advantages:

• easy to link code to a task
• convenient to search in history
• a favorite topic in interviews

---

#Alternative, but also popular, options

#Without the feature/ prefix

Sometimes it is simply:

This works for small teams, but scales worse.

---

#With a task type (an extended variant)

This immediately shows the type of change.

---

#General rules for a good branch name

• short, but clear
• lowercase
• words separated with -, not _
• no spaces
• reflects the essence of the task, not technical details

Bad:

• new
• test123
• fix
• my-branch

---

#What is important to say in an interview

Feature branches are usually named with the feature/ prefix and a short task description, often with a ticket number, so that the branch's purpose and its connection to the task are clear.