bigchaindb
/
bigchaindb
mirror of https://github.com/bigchaindb/bigchaindb.git
1
0
Fork 0
Code Releases Activity
4,324 Commits 25 Branches 54 Tags 18 MiB
Commit Graph

9 Commits

Author SHA1 Message Date
Troy McConaghy abdd23f5a6 Problem: Source files contain no license info (#2455) 
* Problem: Source files contain no license info

Solution: Add comments with SPDX license info to source files

* Python 3 files don't need # -*- coding: utf-8 -*-
 2018-08-16 12:31:32 +02:00
Troy McConaghy 66fd001311
Problem: Doc re/ handling external PRs has moved (#2444) 
Solution: Modify the file `HOW_TO_HANDLE_PULL_REQUESTS.md` to point its readers to the new document about how to handle external pull requests: [BEP-16](https://github.com/bigchaindb/BEPs/tree/master/16).
 2018-08-08 13:27:48 +02:00
Troy McConaghy 51fa3155f6
Problem: what if someone agrees to CLA but no PR? (#2313) 
Solution: ask them if they meant to agree to the CLA, and if so, where is their PR?
 2018-06-01 14:54:51 +02:00
Troy McConaghy f3f1ecdaec Added to HOW_TO_HANDLE_PULL_REQUESTS.md 
Added new subsection: How to Handle CLA Agreement Emails with No Associated Pull Request
 2017-04-02 16:46:41 +02:00
Trent McConaghy af39e204c9 "ascribe" -> "BigchainDB" 2017-01-07 11:31:51 +01:00
troymc 59f11484e5 Merge two paras in comment on CLA as suggested by Greg 2016-10-19 17:52:48 +02:00
Troy McConaghy fba3762dcb Add Greg's explanation to our standard CLA comment 
When someone outside of BigchainDB GmbH submits a pull request, we have a standard comment that we post, asking them to agree to our CLA. @gmcmullen recently wrote [a comment to explain why](https://github.com/bigchaindb/bigchaindb/pull/695#issuecomment-254747113), and I thought it would be a good idea to include that every time we ask.
 2016-10-19 17:17:08 +02:00
troymc 0ecdbd82ea Minor edit in HOW_TO_HANDLE_PULL_REQUESTS.md 2016-04-04 11:44:54 +02:00
troymc ebb8e901da Added HOW_TO_HANDLE_PULL_REQUESTS.md 2016-04-04 11:39:25 +02:00