VenkataKrishna Reddy Avula 452a2de7d0 Merged in bugfix/NTE_num_rows (pull request #570)
Bugfix/NTE num rows to Main

* updated REIMB_TERM_BREAKOUTprompt

* Merged main into bugfix/NTE_num_rows

* updated NTE prompt

* updated reimb_pct_rate prompt

* updated reimb_method prompt

* added cost prompt in reimb method

* Merged main into bugfix/NTE_num_rows

* conflict fixes

* Merged main into bugfix/NTE_num_rows

* updated prompts


Approved-by: Alex Galarce
2025-06-12 14:00:14 +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%