32 Commits (32e94538185b61fe64bd16de2459e763ec46b4da)

Author	SHA1	Message	Date
MarcoFalke	fac5ddfc57	doc: Rework section on ACK	6 years ago
Carl Dong	f4a230b627	docs: Clarify PR guidelines w/re documentation	6 years ago
Jon Atack	0d9d2b385b	Doc: update ACK description in CONTRIBUTING.md ... as per https://github.com/bitcoin/bitcoin/pull/15617#issuecomment-474773043 and https://github.com/bitcoin/bitcoin/pull/15626#discussion_r267286564.	6 years ago
JeremyRand	228e80608d	Enable TLS in link to chris.beams.io	6 years ago
Antti Majakivi	b60ac00d2d	Botbot.me (IRC logs) not available anymore ... Remove botbot.me link and add two other IRC history log sources: logs for #bitcoin-core-dev at http://www.erisian.com.au/bitcoin-core-dev/ and http://gnusha.org/bitcoin-core-dev/	6 years ago
Martin Erlandsson	0e6de3aacb	added details about commit messages	6 years ago
Karl-Johan Alm	db213aa47f	doc: add note to contributor docs about warranted PR's	6 years ago
wodry	42c499614a	Docs: Improve readability of "Squashing commits" ... It was not easy to read the comment lines for me because I was not sure whether the sentence ended with the line or not ("pull set commits"?). Therefore, dots had been invented and I have added them to signal the end of a sentence. Also begin New sentence with a capital letter. I guess, not all 'pick' words should be replaced by 'squash'? At least I found [https://www.digitalocean.com/community/tutorials/how-to-rebase-and-update-a-pull-request](this) rebase/squash documentation helpful, where is written that the first line should not be changed.	7 years ago
fanquake	a508091c59	doc: Mention good first issue list in CONTRIBUTING.md	7 years ago
Jim Posen	30d1a0ae37	Docs: Improve documentation on standard communication channels ... More information about connection on IRC will hopefully help new contributors.	7 years ago
Sjors Provoost	fe27a72362	[docs] links to code style guides	7 years ago
Vivek Ganesan	d0b1fc88d8	Docs: Change formatting for sequence of steps ... A numbered list is used when the sequence of steps matters. A bulleted list is used to denote a set of items where the sequence does not matter. The workflow is a sequence and hence changed to a numbered list.	7 years ago
Christian Gentry	f927ee1aa8	Fixed a couple small grammatical errors. ... 1. "If a pull request is not to be considered for merging (yet), please prefix the ..." 2. If a particular commit references another issue, please add the reference. For example: `refs #1234` or `fixes #4321`.	7 years ago
Jonas Schnelli	91c39e38d9	Update CONTRIBUTRING.md to reduce unnecesarry review workload	7 years ago
MeshCollider	87fe21f814	Add translation note to CONTRIBUTING.md	7 years ago
Evan Klitzke	13b1e9a162	Capitalize bullet points in CONTRIBUTING guide ... English grammar dictates that these bullet points should be capitalized. This also makes the capitalization style consistent with the rest of the document, e.g. the "Decision Making Process" section.	7 years ago
Kalle Alm	3ddd227c2f	[doc] Add blob about finding reviewers.	8 years ago
Kalle Alm	846dc179bc	[doc] Wording fixes in CONTRIBUTING.md.	8 years ago
flack	cc995e26c2	add missing spaces so that markdown recognizes headline	8 years ago
Wladimir J. van der Laan	afae75fd3d	Merge #9675: Fix typo and spelling inconsistency in CONTRIBUTING.md ... 36164fa Fix typo and spelling inconsistency in CONTRIBUTING.md (Koki Takahashi)	8 years ago
CryptAxe	00e623d0b8	[Trivial] Update comments referencing main.cpp	8 years ago
Koki Takahashi	36164faa33	Fix typo and spelling inconsistency in CONTRIBUTING.md ... Fix spellings of GitHub Remove unnecessary changes Fix GitHub spelling on doc/translation_process.md	8 years ago
John Newbery	c70622e942	Docs: Update CONTRIBUTING.md ... Update CONTRIBUTING.md to document the different components. Notably, trivial should only be used for PRs that do not change the code.	8 years ago
Peter Todd	36f60a5d5b	Add copyright/patent issues to possible NACK reasons ... Adding in response to a Slack discussion where someone was unclear on the fact that a NACK may be justified if code can't be accepted due to copyright/patent issues. For example, it would be reasonable and prudent to NACK a contribution of AGPL-licensed consensus code on the basis that the license terms are incompatible with the MIT license used by the rest of the codebase.	8 years ago
Wladimir J. van der Laan	bc9e3ab29f	Merge #8771: CONTRIBUTING: Mention not to open several pulls ... faa91bc CONTRIBUTING: Mention not to open several pulls (MarcoFalke)	8 years ago
MarcoFalke	faa91bc335	CONTRIBUTING: Mention not to open several pulls	8 years ago
Andrew Chow	4b6740204d	Mandatory copyright agreement ... All contributions to the repository will agree to use the MIT license	8 years ago
Will Binns	be1d451225	contributing.md: Fix formatting ... This commit contains two changes to CONTRIBUTING.md that: Fix line line lengths. There were several instances where line lengths were well over 80 characters. This commit adjusts them to make them conform to formatting best practices, to stay under 80 characters when possible. Adhere to consist use of quotes. There are a few instances where smart quotes are used (perhaps because it was pasted from a word processor). This commit replaces them with dumb quotes to keep it consistent with the quotation formatting found in the rest of the document.	9 years ago
fanquake	90963e5370	[doc] Add basic git squash example	9 years ago
Patrick Strateman	e1030dddab	Note that reviewers should mention the commit hash of the commits they reviewed.	9 years ago
paveljanik	05b5831aa0	Add PR title prefix for trivial changes [skip ci]	9 years ago
BtcDrak	06d92d71a2	Add CONTRIBUTING.md	9 years ago