fineract-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vorbur...@apache.org
Subject [fineract] branch develop updated: Refactoring guideline added to README.md
Date Sun, 26 Apr 2020 09:11:37 GMT
This is an automated email from the ASF dual-hosted git repository.

vorburger pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/fineract.git


The following commit(s) were added to refs/heads/develop by this push:
     new d9d4438  Refactoring guideline added to README.md
d9d4438 is described below

commit d9d44383c082501fb77341843c494bbcca85677a
Author: Nikhil Pawar <16708052+nikpawar89@users.noreply.github.com>
AuthorDate: Sat Apr 25 18:45:39 2020 -0400

    Refactoring guideline added to README.md
---
 README.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/README.md b/README.md
index 914ebf2..272330a 100644
--- a/README.md
+++ b/README.md
@@ -244,6 +244,9 @@ documents that we cannot accept huge "code dump" Pull Requests, with some
relate
 
 [How to Release Apache Fineract](https://cwiki.apache.org/confluence/x/DRwIB) documents the
process how we make the source code that is available here in this git repository into a binary
release ZIP available on http://fineract.apache.org.
 
+Guideline for new Feature commits involving Refactoring: If you are submitting PR for a new
Feature, 
+and it involves refactoring, try to differentiate "new Feature code" with "Refactored" by
placing
+them in different commits. This helps review to review your code faster.
 
 More Information
 ============


Mime
View raw message