Skip to content

Conversation

@oleksii-novikov-onix
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.

@oleksii-novikov-onix oleksii-novikov-onix force-pushed the FINERACT-2081/repayment-schedule-for-cumulative-loans branch from b9b8c0e to 9713763 Compare March 13, 2025 09:38
@oleksii-novikov-onix oleksii-novikov-onix force-pushed the FINERACT-2081/repayment-schedule-for-cumulative-loans branch from 9713763 to f743694 Compare March 14, 2025 08:21
@oleksii-novikov-onix oleksii-novikov-onix marked this pull request as ready for review March 14, 2025 08:22
@adamsaghy adamsaghy merged commit 898a18c into apache:develop Mar 14, 2025
10 checks passed
@adamsaghy adamsaghy deleted the FINERACT-2081/repayment-schedule-for-cumulative-loans branch March 14, 2025 12:57
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.

2 participants