From 0e370118d406341f0dbac4b75ba71965325bbeac Mon Sep 17 00:00:00 2001 From: kapmaurya Date: Thu, 31 Oct 2024 03:01:16 +0530 Subject: [PATCH] update readme file with committing your changes --- README.md | 33 +-------------------------------- 1 file changed, 1 insertion(+), 32 deletions(-) diff --git a/README.md b/README.md index c961c2cb7..65c2b6da7 100644 --- a/README.md +++ b/README.md @@ -31,39 +31,8 @@ Mifos boasts an active and vibrant contributor community, Please join us on [sla ### [Development Setup](https://github.com/openMF/mobile-wallet/wiki/Development-Setup) -### **Committing Your Changes** +### [Committing Your Changes](https://github.com/openMF/mobile-wallet/wiki/Committing-Your-Changes) -When you've finished making your changes and have tested them locally, it's time to commit your work: - -1. **Stage Changes** - - Use the following command to stage all changes: - - ```bash - git add . - ``` - - This adds all modified and new files to the staging area, preparing them for the commit. - -2. **Commit Changes** - - Commit your changes with a meaningful commit message that describes the purpose of your changes: - - ```bash - git commit -m "Your commit message goes here" - ``` - - A good commit message is concise and provides enough context about the changes made. Mifos follows its own commit style guidelines that you must follow. Learn more about it [here](https://github.com/openMF/mifos-mobile-cn/blob/master/COMMIT_STYLE.md). - -3. **Push Changes** - - Push your changes to your forked repository on GitHub: - - ```bash - git push origin new-branch-name - ``` - - Replace **`new-branch-name`** with the name of the branch you created earlier. ### **Making a Pull Request**