Skip to content

Instantly share code, notes, and snippets.

View hamdinawfel's full-sized avatar

HAMDI Nawfel hamdinawfel

View GitHub Profile

PFE: Dev Matrix

Table of contents

Introduction

Functional requirements

Technical requirements

HTTP response status codes

Successful responses

200 OK The request succeeded. The result meaning of "success"

201 Created The request succeeded, and a new resource was created as a result. This is typically the response sent after POST requests, or some PUT requests.

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example

@hamdinawfel
hamdinawfel / git_branching_cheatsheet.md
Last active June 3, 2025 11:15
Git branching cheat sheet

Git branching cheat sheet

Git branching diagram

Creating a feature branch

story

$ git checkout -b US-10 develop
@hamdinawfel
hamdinawfel / markdown-cheatsheet.md
Last active September 20, 2021 22:58
Markdown Cheatsheet.

Markdown Cheatsheet

Mark Down

Heading

Folder Structure

Please note

While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.

Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.