delta/python-packages/gitpython.git - github.com: gitpython-developers/GitPython.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	overhaul CONTIRIBUTING.md	Sebastian Thiel	2021-08-18	1	-8/+7
\| \| \| \|	Thanks to #1322
*	add initial types to remote.py	yobmod	2021-05-03	1	-1/+2
\|
*	update contribution guidelines to be a little less concise and more polite	Sebastian Thiel	2020-09-03	1	-4/+7
\|
*	Correcting a file name	Arthur Milchior	2019-08-12	1	-1/+1
\|
*	github -> GitHub	Hugo	2018-03-18	1	-1/+1
\|
*	Make it more obvious how tests can be run locally	Sebastian Thiel	2017-12-11	1	-0/+1
\| \| \| \| \| \|	See #674 for reference. [skip CI]
*	doc(README): add basic contribution guidelines	Sebastian Thiel	2016-06-13	1	-0/+6
	The main point is that from now on, tests are required to add new features. If the fix is minor enough, not having a test is probably alright. That distinction is not represented in the contribution guide as more tests are better - people should prefer to have a test whenever they contribute anything. My motivation to finally do this is the sad realization that I grow too unconfident about the quality of some contributions without having tests that proof they are valid. It's not enough to not break anything that exists, as the current test-suite is certainly not perfect either.