Önder Bakırtaş onderbakirtas

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.

	import { writable } from 'svelte/store'

	// returns a store with HTTP access functions for get, post, patch, delete
	// anytime an HTTP request is made, the store is updated and all subscribers are notified.
	export default function(initial) {
	// create the underlying store
	const store = writable(initial)

	// define a request function that will do `fetch` and update store when request finishes
	store.request = async (method, url, params=null) => {

	$black: #22292f;
	$grey-darkest: #3d4852;
	$grey-darker: #606f7b;
	$grey-dark: #8795a1;
	$grey: #b8c2cc;
	$grey-light: #dae1e7;
	$grey-lighter: #f1f5f8;
	$grey-lightest: #f8fafc;
	$white: #fff;
	$red-darkest : #3b0d0c;