Editing Talk:02 Code Review and Approval Procedure (section)

== 3. Code Review and Approval Process Overview ==

=== 3.1 Goal ===
Ensure code changes are reviewed thoroughly via Git, with tests run and comments addressed before approval.

=== 3.2 Core Steps ===

* Use Git for all version control. 
* Apply branching strategy for code changes. 
* Make code changes and run test cases. 
* Create Pull Request in Git. 
* Assign reviewer(s). 
* Reviewer reviews and add comments. 
* Comments are acted upon by the developer. 
* Review and repeat until PR approval. 
* Merge approved PR. 

=== 3.3 SDLC Fit ===
Integrate with Agile sprints (review PRs daily) or Waterfall phases; track in Jira.

=== 3.4 Change Tracking ===
Use Git commits linked to Jira (e.g., “Fix JIRA-123”).

=== 3.5 Process Flow ===

* Step 1: Developer branches in Git and makes changes. 
* Step 2: Run tests locally or in CI. 
* Step 3: Create PR, assign reviewer. 
* Step 4: Reviewer adds comments; developer acts on them. 
* Step 5: Repeat reviews until approval; merge PR. 

=== 3.6 Exceptions ===
Emergency changes allow quick approval with Team Lead sign-off; log in Jira.

=== 3.7 Version Control ===

* Require Git branches like feature/JIRA-123; protect main. 

* '''Automation''': Use GitHub Actions for auto-tests on PR creation.