Aman-Mittal opened a new pull request, #185:
URL: https://github.com/apache/fineract-consumer-facing/pull/185

   Closes #184.
   
   ## Issue forms (`.github/ISSUE_TEMPLATE/`)
   
   The forms follow the shape apache/fineract-backoffice-ui uses, adapted to 
this repository.
   
   **`bug_report.yml`** (labels `bug`, `Triage`) asks for:
   - the area (Angular app, BFF, both, or build/CI/docs);
   - steps to reproduce;
   - the BFF error `code`, the `X-Correlation-ID` and log lines, with a 
reminder to strip personal data, tokens and OTPs;
   - how the stack was run (e2e compose, JVM, native, or dev servers);
   - the Fineract image tag, the commit and the browser.
   
   **`feature_request.yml`** (labels `enhancement`, `Triage`):
   - It sends new features to [email protected] and Matrix first. A 
consumer-facing feature usually needs agreement on what a consumer may see or 
change before code is written.
   - It asks for the Fineract API the feature relies on and a link to the 
discussion.
   
   **`config.yml`** contact links:
   - Security reports go to `SECURITY.md` and [email protected], not public 
issues.
   - Fineract Core bugs go to the ASF Jira.
   - Discussion goes to the dev list and Matrix.
   
   ## PR template
   
   - **Added a comment block** with the dev-list and Matrix guidance (as in the 
back-office template) and a security pointer.
   - **Added checklist items:**
     - backend code follows the CQRS and module layout in `AGENTS.md`, and 
frontend code goes through `core/adapters`;
     - no entries were added to a lint or architecture baseline to get the 
build passing;
     - features or changes to what a consumer can see or do were raised on the 
dev list first.
   
   ## Verification
   
   - The YAML parses.
   - The labels used (`bug`, `enhancement`, `Triage`) exist.
   - New files carry the ASF header.
   - The `AGENTS.md` anchor (`#backend-conventions-consumer`) matches its 
heading.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to