You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merging all changes in main branch of the last weeks into dev branch (#2444)
* fixed identities tab
* fix: Loan Product capitalized income form validation
* Loan account with Capitalized Income transaction
* fix: Use first API url from url list
* Loan Product with Capitalized Income GL accounting mappings
* fix: Loan Product capitalized income with Income Type
* Loan account details - income capitalization type
* fix: Loan Product Cash accounting view
* fix: Loan Id updated in Loan views after url changed
* fix: Charge management minimum and maximum cap values validation
* build(deps-dev): bump http-proxy-middleware from 2.0.7 to 2.0.9 (#2421)
Bumps [http-proxy-middleware](https://github.com/chimurai/http-proxy-middleware) from 2.0.7 to 2.0.9.
- [Release notes](https://github.com/chimurai/http-proxy-middleware/releases)
- [Changelog](https://github.com/chimurai/http-proxy-middleware/blob/v2.0.9/CHANGELOG.md)
- [Commits](chimurai/http-proxy-middleware@v2.0.7...v2.0.9)
---
updated-dependencies:
- dependency-name: http-proxy-middleware
dependency-version: 2.0.9
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* docs: Improve contributing guidelines (#2440)
The CONTRIBUTING.md file has been updated to clarify that
we use the dev branch for development. In addition to
that, I have slightly shortened and restructured the text.
FIXES: WEB-165
---------
Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: Craig-Rosario <[email protected]>
Co-authored-by: Jose Alberto Hernandez <[email protected]>
Co-authored-by: Jose Alberto Hernandez <[email protected]>
Co-authored-by: adam.magyari <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Follow our [code of conduct](https://mifos.org/resources/community/code-of-conduct/).
9
-
-[Find a Jira ticket to work on](https://mifosforge.jira.com/browse/WEB) and start smashing!
10
-
-[Ask a question on Slack](https://app.slack.com/client/T0F5GHE8Y/CJJGJLN10).
4
+
- Sign the [Contribution License Agreement](http://mifos.org/about-us/financial-legal/mifos-contributor-agreement/).
5
+
- Always follow the [code of conduct](https://mifos.org/resources/community/code-of-conduct/) - this is important to us. We are proud to be open, tolerant and providing a positive environment.
6
+
- Introduce yourself or ask a question on the [#webapp channel on Slack](https://app.slack.com/client/T0F5GHE8Y/CJJGJLN10).
7
+
- Find a [Jira](https://mifosforge.jira.com/browse/WEB) ticket to work on and start smashing!
8
+
- Sign up to the [mailing list](https://sourceforge.net/projects/mifos/lists/mifos-developer).
11
9
- Learn more at our [getting started guide](https://mifosforge.jira.com/wiki/spaces/RES/pages/464322561/New+Contributor+Getting+Started+Guide).
12
10
- Have a look at our [Wiki](https://github.com/openMF/web-app/wiki).
13
11
14
-
Please outline the change you wish to make via a Jira ticket _before_ you start contributing. And please do not create Jira tickets for general support questions, as we want to keep Jira for bug reports and feature requests. If you have got any questions, the quickest way to get an answer is to join the above Slack channel. You can also write an email on our [mailing list](https://sourceforge.net/projects/mifos/lists/mifos-developer). Mifos has quite a few active repositories, and each has its own Slack channel to direct questions to.
12
+
Tips for working with the web app repository:
15
13
16
-
Mifos is an inclusive community, committed to creating a safe, positive environment. Read the above Code of Conduct, and please follow it in all your interactions with the project.
14
+
- Learn how to [format pull requests](#submitting-a-pull-request).
15
+
- Read how to [rebase/merge upstream branches](#configuring-remotes).
### Best Practices for reporting or requesting for Issues/Enhancements:
20
+
### Reporting or requesting Issues/Enhancements
21
21
22
-
- Before you submit an issue, please search Jira. Maybe an issue for your problem already exists, and the discussion might inform you of workarounds readily available.
23
-
- Include screenshots if any (specially for UI related issues).
22
+
- Before you submit an issue in Jira, please browse existing issues or ask on Slack. Maybe an issue for your problem already exists, or the discussion might inform you of workarounds readily available.
23
+
- Include screenshots if helpful (specially for UI related issues).
24
24
- For UI enhancements include mockups to provide a clear idea to the reader.
25
25
26
-
### Best Practices for getting assigned to work on an Issue/Enhancement:
26
+
### Getting assigned and working on an Issue/Enhancement
27
27
28
-
- If you would like to work on an issue, make sure it is not assigned to someone else.
29
-
- If you don't work on a Jira ticket, please unassign yourself.
30
-
- Please be sure that you are able to reproduce the issue, before working on it. If not, please ask for clarification by commenting or asking the issue creator.
28
+
- Always outline the change you wish to make via a Jira ticket _before_ contributing.
29
+
- Do not create Jira tickets for support questions. Jira is for bug reports and feature requests. (If you have questions, ask in the above Slack channel or write an email on the named mailing list.)
30
+
- If you would like to work on a Jira issue, make sure it is not assigned to someone else. (We do not appreciate pull requests for issues that are assigned to someone else or do not refer to a Jira ticket.)
31
+
- If you want to take over a ticket, ask the assignee in a comment (utilizing the "@" prefix), if you can. Wait 3 days, before you assign the ticket to yourself.
32
+
- If you don't work on a Jira ticket, unassign yourself.
31
33
32
-
**Note:** Please do not work on an issue which is assigned to someone else. We don't encourage creating multiple pull requests for the same issue. Also, please allow the assigned person at least 3 days to work on an issue. If there is no progress after this deadline, comment on the issue asking the contributor whether he/she is still working on it. Only if there is no reply after a couple of days, assign the ticket to you and work on it.
34
+
## Jira
33
35
34
-
###Jira ticket life cycle
36
+
Our Jira tickets follow the following life cycle:
35
37
36
-
- To Do: The issue is not prioritized yet. Make sure it make sense working on it by asking in Slack.
38
+
- To Do: The issue is not prioritized yet. Make sure it makes sense working on it by asking in Slack.
37
39
- On Deck: The issue can be worked on, but work hasn't been started. Often the issue has already someone assigned to it.
38
40
- In Progress: The issue is being worked on.
39
41
- In Review: There is a Pull Request on GitHub or the ticket is on hold, because someone needs to review made changes.
40
42
- Done: The Pull Request got merged on GitHub.
41
43
- Canceled: The ticket is unnecessary and for some reason (probably in the comments) work on it became unnecessary.
42
44
43
-
## Submitting a Pull Request
45
+
Updating the Jira ticket is the responsibility of the person working on it. Make in particular sure the Status field is up-to-date.
44
46
45
-
### Best Practices to send Pull Requests:
47
+
## Git and Github
48
+
49
+
### Best Practices to send Pull Requests
46
50
47
51
- Fork the [project](https://github.com/openMF/web-app) on GitHub
48
52
- Clone the project locally into your system.
@@ -51,10 +55,10 @@ Mifos is an inclusive community, committed to creating a safe, positive environm
-We use the `main` branch for releases, hotfixes and special purposes. All regular work on releases flows into the `dev` branch.
55
59
56
60
```
57
-
git checkout main
61
+
git checkout dev
58
62
```
59
63
60
64
- Create a new branch with a meaningful name before adding and committing your changes.
@@ -63,7 +67,7 @@ git checkout main
63
67
git checkout -b branch-name
64
68
```
65
69
66
-
- Add the files you changed. (avoid using`git add .`)
70
+
- Add the files you changed. (Better don't use`git add .`)
67
71
68
72
```
69
73
git add file-name
@@ -81,7 +85,7 @@ git commit
81
85
git commit --amend
82
86
```
83
87
84
-
- Squash multiple commits to a single commit. (example: squash last two commits done on this branch into one)
88
+
- Squash multiple commits to a single commit. (Example: squash last two commits done on this branch into one.)
85
89
86
90
```
87
91
git rebase --interactive HEAD~2
@@ -90,7 +94,7 @@ git rebase --interactive HEAD~2
90
94
- Push this branch to your remote repository on GitHub.
91
95
92
96
```
93
-
git push origin branch-name
97
+
git push --set-upstream origin branch-name
94
98
```
95
99
96
100
- If any of the squashed commits have already been pushed to your remote repository, you need to do a force push.
@@ -99,13 +103,13 @@ git push origin branch-name
99
103
git push origin remote-branch-name --force
100
104
```
101
105
102
-
- Follow the Pull request template and submit a pull request with a motive for your change and the method you used to achieve it to be merged with the `main` branch.
103
-
- If you can, please submit the pull request with the fix or improvements including tests.
104
-
- During review, if you are requested to make changes, rebase your branch and squash the multiple commits into one again. Once you push these changes, the pull request will edit automatically.
106
+
- Follow the Pull request template and submit a pull request with a motive for your change and the method you used to achieve it to be merged with the `dev` branch.
107
+
- If possible, please submit the pull request along with tests.
108
+
- During review, if you are requested to make changes, rebase your branch and squash commits into one again. Once you push these changes, the pull request will edit automatically.
105
109
106
-
## Configuring remotes
110
+
###Configuring remotes
107
111
108
-
When a repository is cloned, it has a default remote called `origin` that points to your fork on GitHub, not the original repository it was forked from. To keep track of the original repository, you should add another remote called `upstream`.
112
+
When a repository is cloned, it has a default remote called `origin` that points to your fork on GitHub, not the original repository it was forked from. To keep track of the original repository, you can add another remote called `upstream`.
3. To update your local copy with remote changes, run the following: (This will give you an exact copy of the current remote. You should not have any local changes on your main branch, if you do, use rebase instead.)
129
+
3. To update your local copy with remote changes, run the following: (This will give you an exact copy of the current remote. You should not have any local changes on your dev branch, if you do, use rebase instead.)
126
130
127
131
```
128
132
git fetch upstream
129
-
git checkout main
130
-
git merge upstream/main
133
+
git checkout dev
134
+
git merge upstream/dev
131
135
```
132
136
133
-
4. Push these merged changes to the main branch on your fork. Ensure to pull in upstream changes regularly to keep your forked repository up to date.
137
+
4. Push these merged changes to the dev branch on your fork. (Ensure to pull in upstream changes regularly to keep your forked repository up to date. Or you use the "Sync fork" button on top of the Github page of your fork, followed by `git pull`.)
134
138
135
139
```
136
-
git push origin main
140
+
git push origin dev
137
141
```
138
142
139
143
5. Switch to the branch you are using for some piece of work.
@@ -145,7 +149,7 @@ git checkout branch-name
145
149
6. Rebase your branch, which means, take in all latest changes and replay your work in the branch on top of this - this produces cleaner versions/history.
146
150
147
151
```
148
-
git rebase main
152
+
git rebase dev
149
153
```
150
154
151
155
7. Push the final changes when you're ready.
@@ -154,20 +158,20 @@ git rebase main
154
158
git push origin branch-name
155
159
```
156
160
157
-
## After your Pull Request is merged
161
+
###After your Pull Request is merged
158
162
159
-
After your pull request is merged, you can safely delete your branch and pull the changes from the main (upstream) repository.
163
+
After your pull request is merged, you can safely delete your branch and pull the changes from the dev (upstream) repository.
160
164
161
165
1. Delete the remote branch on GitHub.
162
166
163
167
```
164
168
git push origin --delete branch-name
165
169
```
166
170
167
-
2. Checkout the main branch.
171
+
2. Checkout the dev branch.
168
172
169
173
```
170
-
git checkout main
174
+
git checkout dev
171
175
```
172
176
173
177
3. Delete the local branch.
@@ -176,14 +180,14 @@ git checkout main
176
180
git branch -D branch-name
177
181
```
178
182
179
-
4. Update your main branch with the latest upstream version.
183
+
4. Update your dev branch with the latest upstream version.
180
184
181
185
```
182
-
git pull upstream main
186
+
git pull upstream dev
183
187
```
184
188
185
-
## Skipping a Travis CI Build
189
+
###Skipping a Travis CI Build
186
190
187
191
If running a build is not required for a particular commit (in some cases like an update to README.md), add [ci skip] or [skip ci] to the git commit message. Commits that have [ci skip] or [skip ci] anywhere in the commit messages are ignored by Travis CI.
Copy file name to clipboardExpand all lines: src/app/accounting/financial-activity-mappings/edit-financial-activity-mapping/edit-financial-activity-mapping.component.ts
-1
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,6 @@ export class EditFinancialActivityMappingComponent implements OnInit {
Copy file name to clipboardExpand all lines: src/app/deposits/fixed-deposits/fixed-deposit-account-stepper/fixed-deposit-account-terms-step/fixed-deposit-account-terms-step.component.ts
-1
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,6 @@ export class FixedDepositAccountTermsStepComponent implements OnInit, OnChanges
0 commit comments