Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@somasorosdpc
Copy link
Contributor

Description

Describe the changes made and why they were made.

Ignore if these details are present on the associated Apache Fineract JIRA ticket.

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

  • Write the commit message as per https://github.com/apache/fineract/#pull-requests
  • Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
  • Create/update unit or integration tests for verifying the changes made.
  • Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.
  • Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
  • Submission is not a "code dump". (Large changes can be made "in repository" via a branch. Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

@somasorosdpc somasorosdpc force-pushed the FINERACT-2326/DOC-interest-rate-change-for-progressive-loans branch from 4d52af8 to 471ff66 Compare August 11, 2025 13:02
@adamsaghy
Copy link
Contributor

@somasorosdpc Please resolve the conflicts

@somasorosdpc somasorosdpc force-pushed the FINERACT-2326/DOC-interest-rate-change-for-progressive-loans branch from 471ff66 to 5886732 Compare August 12, 2025 13:30
@adamsaghy adamsaghy merged commit 87c0a02 into apache:develop Aug 13, 2025
39 checks passed
@adamsaghy adamsaghy deleted the FINERACT-2326/DOC-interest-rate-change-for-progressive-loans branch August 13, 2025 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants