Madalin Popa madalinpopa

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
  -m"<optional body>" \
  -m"<optional footer>"

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.

Installing Python 3.7.3 on MX-linux 18.1

I was following this blog to install python 3.7.3 on my MX-linux 18.1 machine. Step by step procedure is as follows

Install the pre-requisites

sudo apt-get install build-essential checkinstall
sudo apt-get install libreadline-gplv2-dev libncursesw5-dev libssl-dev \
 libsqlite3-dev tk-dev libgdbm-dev libc6-dev libbz2-dev libffi-dev

Emoji	Name	Text example
🚀	Rocket	You're up
📦	Package	Installing additional dependencies...
⚓	Hook	Running completion hooks...
📄	Document	Generating README.md...
🎉	Party	Successfully created project hello-vue.
👉	Next	Get started with the following commands:
✔	Tick	Task completed
✨	Magic	Assembling project...


	# This is a very crud example of using the Repository Pattern with SQLAlchemy. It allows me to completely ignore interactions with
	# the database. This is only pulled in whenever I require to persist or retrieve an object from the database. The domain/business
	# logic is entirely separated from persistence and I can have true unit tests for those.

	# The tests for persistence are then limited to very specific cases of persistence and retrieving instances, and I can do those
	# independent of the business logic. They also tend to be less tests since I only need to test them once.

	@media (min-width:320px) { /* smartphones, portrait iPhone, portrait 480x320 phones (Android) */ }
	@media (min-width:480px) { /* smartphones, Android phones, landscape iPhone */ }
	@media (min-width:600px) { /* portrait tablets, portrait iPad, e-readers (Nook/Kindle), landscape 800x480 phones (Android) */ }
	@media (min-width:801px) { /* tablet, landscape iPad, lo-res laptops ands desktops */ }
	@media (min-width:1025px) { /* big landscape tablets, laptops, and desktops */ }
	@media (min-width:1281px) { /* hi-res laptops and desktops */ }

	<style type="text/css">
	@font-face {
	font-family: 'Open Sans';
	font-style: normal;
	font-weight: 300;
	src: local('Open Sans Light'), local('OpenSans-Light'), url(http://fonts.gstatic.com/s/opensans/v13/DXI1ORHCpsQm3Vp6mXoaTa-j2U0lmluP9RWlSytm3ho.woff2) format('woff2');
	unicode-range: U+0460-052F, U+20B4, U+2DE0-2DFF, U+A640-A69F;
	}
	.body {
	width: 90%;

	set ignorecase
	set smartcase
	set scrolloff=3 " 3 lines above/below cursor when scrolling

	" Emulated Plugins
	set surround
	" set easymotion
	set NERDTree

	" Copy to system clipboard as well

	from django.contrib import admin
	from .models import User

	admin.site.register([User])