Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fineract 2081: Enhance technical documentation #4077

Conversation

Napho
Copy link
Contributor

@Napho Napho commented Sep 26, 2024

Description

Describe the changes made and why they were made.

Descriptions have been added to property file value documentation in fineract-doc module

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.

@Napho Napho force-pushed the FINERACT-2081/enhance_technical_documentation branch from 9984684 to 4996607 Compare September 28, 2024 07:13
Copy link
Contributor

@kjozsa kjozsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kjozsa
Copy link
Contributor

kjozsa commented Sep 30, 2024

@Napho please also filll the ticket description as expected. Thank you

@adamsaghy
Copy link
Contributor

@Napho Please amend the commit message to fit for the required format:
"FINERACT-2981: Enhance technical documentation"

After the Fineract jira ticket there should be a colon and after the short description.

The actual description is misleading: "FINERACT-2081 add descriptions to property file values"

@Napho Napho force-pushed the FINERACT-2081/enhance_technical_documentation branch from 4996607 to 533cfce Compare September 30, 2024 11:40
@Napho Napho force-pushed the FINERACT-2081/enhance_technical_documentation branch from 533cfce to 85acd3f Compare September 30, 2024 11:43
@Napho
Copy link
Contributor Author

Napho commented Sep 30, 2024

@Napho Please amend the commit message to fit for the required format: "FINERACT-2981: Enhance technical documentation"

After the Fineract jira ticket there should be a colon and after the short description.

The actual description is misleading: "FINERACT-2081 add descriptions to property file values"

@adamsaghy thanks for that, ive updated it accordingly

@kjozsa
Copy link
Contributor

kjozsa commented Sep 30, 2024

@Napho Please amend the commit message to fit for the required format: "FINERACT-2981: Enhance technical documentation"
After the Fineract jira ticket there should be a colon and after the short description.
The actual description is misleading: "FINERACT-2081 add descriptions to property file values"

@adamsaghy thanks for that, ive updated it accordingly

sorry @Napho, but the correct commit message format is FINERACT-xxx: <description>. Please be exact, even with upper/lowercase letters!

@adamsaghy adamsaghy changed the title Fineract 2081: enhance technical documentation Fineract 2081: Enhance technical documentation Sep 30, 2024
@kjozsa kjozsa merged commit a29aaf0 into apache:develop Sep 30, 2024
9 checks passed
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