Alex Galarce ae4eda6f25 Merged in feature/one-to-n-docs (pull request #715)
Feature/one to n docs

* Refactor function signatures and improve imports in one_to_n_funcs.py

* Enhance type hints and documentation for carveout_check and methodology_breakout functions

* Add docstring to methodology_breakout_secondary function for clarity on parameters and return values

* Add docstring to special_case_breakout function for clarity on parameters and return values

* Enhance docstring for deduplicate_with_accumulator function to clarify behavior and parameters

* Enhance docstring for filter_services_without_reimbursements function to clarify validation process and answer structure

* Enhance docstring for filter_services_without_reimbursements function to clarify filtering criteria and validation process

* Enhance docstring for split_compound_reimbursements function to clarify the splitting process and provide an example

* Enhance docstring for split_reimb_dates function to clarify date processing, parameters, return values, and provide an example

* Remove unused regex import from one_to_n_funcs.py

* Remove unused Delimiter import from one_to_n_funcs.py


Approved-by: Katon Minhas
2025-09-30 14:04:47 +00:00
2024-07-01 15:51:23 -05:00
2024-07-01 10:47:54 -05:00
2024-09-30 12:21:29 +01:00
2024-09-25 12:23:27 +01:00
2024-09-30 12:21:29 +01:00
2024-09-30 12:21:29 +01:00

Branching and Release Management Guide

Overview

This guide outlines the naming conventions, branching strategy, and merging process for our Git repository.

Branch Naming Conventions

  • Feature Branch: feature/<name>
    • Example: feature/add_build_stage
  • Bugfix Branch: bugfix/<name>
    • Example: bugfix/pages_duplication
  • Hotfix Branch: hotfix/<name>
    • Example: hotfix/deployment_failure

....

Branching Strategy

Creating Branches

  1. Create a feature branch from main using the appropriate naming convention.
  2. Create a small and complete change. main must always have deployable code.
  3. Create a Pull Request back to main.
  4. Ensure all checks have passed.
  5. Merge new code.
  6. Ensure the functionality is verified in the dev environment.

Refer to the branching guide in Confluence for more info on this


This guide ensures that all team members follow the best practices for branch management and releases.

S
Description
AARETE DoczyAI pipelines mirror.
Readme 642 MiB
Languages
Python 80.5%
Jupyter Notebook 13%
HCL 3.1%
HTML 1.6%
PLpgSQL 1.5%
Other 0.2%