Branching

Quick Legend

Description, Instructions, Notes

Instance	Branch

elifnurkarakoc / ultimate-ut-cheat-sheet.md

Created January 6, 2022 13:02 — forked from yoavniran/ultimate-ut-cheat-sheet.md

The Ultimate Unit Testing Cheat-sheet For Mocha, Chai, Sinon, and Jest

The Ultimate Unit Testing Cheat-sheet

Sinon Chai
Chai
Sinon

elifnurkarakoc / clean_code.md

Created January 6, 2022 11:39 — forked from wojteklu/clean_code.md

Summary of 'Clean code' by Robert C. Martin

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules

elifnurkarakoc / conventional-commits.md

Created December 22, 2021 18:36 — forked from Zekfad/conventional-commits.md

Conventional Commits Cheatsheet

Quick examples

feat: new feature
fix(scope): bug in scope
feat!: breaking change in API
chore(deps): update dependencies

Commit types

build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
ci: Changes to CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
chore: Changes wich doesn't change source code or tests e.g. chnages to the build process, auxiliary tools, libraries