GitHub Project Flow
A concise guide to move efficiently from Project Issue → Branch → Pull Request → Merge, keeping full traceability between your code and project tasks.
1. From GitHub Project to Branch
- Create or select and Issue in your GitHub Project
- Open your GitHub Project Board -> Backlog column
- Click + Add item -> Create a new issue
- Select the target Repository and Template
- Fill the following fields:
- Title: short, clear
- Description: context and motivation
- Assignee: yourself or a team member (if you are the manager)
- Issue Type (optional): Bug, Feature, Task
- Create a linked branch directly from the Issue
- In the Issue page, locate the Development panel (right sidebar)
- Click Create a branch
- Use a clear and consisten banch name, for example:
- GitHub automatically links the branch to the issue (traceability maintained)
- Checkout the branch locally
- Work, add, and commit your changes
- Follow Conventinal Commits to maintain clarity and consistency
- Push your branch to GitHub
- Open Pull Request (PR) in GitHub
- GitHub usually suggests this automatically
- Make sure the PR title is clear and follows Conventional Commits
- Add a concise description summarizing the changes
- Push additional commits as needed before merging
- Merge Pull Request
- Wait for review and approval
- Merge using your team's policy (Squash, Merge or Rebase)
- Click Delete branch in GitHub after merging
- Clean up locally and prune stale remotes
- Sync your local
mainbranch
2. Bring changes from main into a feature branch
When your feature branch becomes outdated, update it with the latest commits from main:
git switch feat/branch
git fetch origin main
git merge origin/main
# resolve conflicts if any, then commit
Reference Material
Git
Guidelines
GitHub