Git & GitHub Workflow + Auth Service Folder Setup

What I Learned

1. Git Branching Strategy
We used GitHub Flow, which is simpler than GitFlow and ideal for small teams and projects.

Branch Types:

• main or master → production-ready code

• dev → integration branch

• feature/<name> → new features

• fix/<name> → bug fixes

• docs/<name> → documentation changes

Workflow:

1. Create a feature branch

2. Make changes

3. Commit frequently

4. Push branch

5. Create Pull Request (PR)

6. Merge to dev

7. Merge dev → main during deployment

2. Writing Good Commit Messages

Good commit messages communicate the why behind a change, not just what changed.

Format:

<type>: <short description>

[optional body]

Types:

• feat: new feature

• fix: bug fix

• docs: documentation

• chore: small task

• refactor: code restructure

Example:

feat(auth): add user model with bcrypt hashing

3. Pull Requests (PRs)

A pull request is a proposal to merge changes from one branch to another.

PR Must Include:

• What you built

• Files changed summary

• Testing instructions

• Screenshots (if UI)

Notes:

• Avoid force-pushing to a PR

• Use topic branches for PRs

• Draft PRs cannot be merged

• Mark PR ready for review when complete

4. GitHub Issues

Every task becomes an issue, which acts like a to-do list inside GitHub.

Labels to Use:

• feature

• bug

• backend

• frontend

• priority-high

• documentation

Why Issues Matter:

• Track progress

• Assign labels

• Link issues to pull requests

• Maintain a professional workflow

What I Built Today

1. GitHub Repository

• finflow-microservices created

• Branches: main, dev, and feature branches

2. Issues Created

• Setup Auth Folder Structure → backend, feature

• Setup Frontend Skeleton → frontend, feature

• Add README Structure → docs

• Setup Environment Variables → backend, feature

3. Auth Service Folder Structure Implemented

backend/auth/src/
  config/
    db.js
  controllers/
    auth.controller.js
  models/
    user.model.js
  routes/
    auth.routes.js
  utils/
    response.js
  index.js

4. Basic Auth Service Setup

• Express server configured

• MongoDB connection in config/db.js

• Health check route implemented

5. Git Workflow Applied

• Feature branch feature/auth-structure created

• Changes committed with proper commit messages

• Pull Request created → merged into dev

Tech Used

• Git

• GitHub

• Node.js

• Express

• MongoDB

GitHub PR Link

Summary
Day 2 focused on setting up professional Git workflow, organizing the backend Auth service, and applying best practices for commit messages, PRs, and issues. This workflow sets the foundation for a maintainable and scalable FinFlow system.