Talk:02 Code Review and Approval Procedure - Revision history

Artha.kadamb@heinfricke.team: /* 1. Introduction */

2025-12-22T11:14:48Z

1. Introduction

← Older revision		Revision as of 11:14, 22 December 2025
Line 2:		Line 2:

	=== 1.1 Purpose ===		=== 1.1 Purpose ===
	* Establish a standardized process for reviewing and approving code changes to maintain quality, catch issues early, and ensure audit traceability using tools like Git.		Establish a standardized process for reviewing and approving code changes to maintain quality, catch issues early, and ensure audit traceability using tools like Git.

	=== 1.2 Scope ===		=== 1.2 Scope ===
	* Covers all code changes in software projects across development teams, focusing on Git-based repositories.		Covers all code changes in software projects across development teams, focusing on Git-based repositories.

	=== 1.3 Objectives ===		=== 1.3 Objectives ===
	* Enforce coding standards, reduce bugs, promote collaboration, and keep detailed records for internal audits.		Enforce coding standards, reduce bugs, promote collaboration, and keep detailed records for internal audits.

	=== 1.4 Key Terms ===		=== 1.4 Key Terms ===
Line 17:		Line 17:

	=== 1.5 Standards ===		=== 1.5 Standards ===
	* Align with company coding guidelines and audit requirements for traceability.		Align with company coding guidelines and audit requirements for traceability.

	=== 1.6 Audience ===		=== 1.6 Audience ===
	* Developers, reviewers, team leads, and auditors.		Developers, reviewers, team leads, and auditors.

	=== 1.7 How to Use ===		=== 1.7 How to Use ===
	* Follow this for all code changes; store in Confluence for access.		Follow this for all code changes; store in Confluence for access.

	== 2. Roles and Responsibilities ==		== 2. Roles and Responsibilities ==
Line 48:		Line 48:

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

	=== 3.2 Core Steps ===		=== 3.2 Core Steps ===
Line 64:		Line 63:

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

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

	=== 3.5 Process Flow ===		=== 3.5 Process Flow ===
Line 80:		Line 77:

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

	=== 3.7 Version Control ===		=== 3.7 Version Control ===

Artha.kadamb@heinfricke.team: /* Goal: */

2025-12-22T11:13:29Z

Goal:

Show changes

Artha.kadamb@heinfricke.team: /* 2. Roles and Responsibilities */

2025-12-22T10:43:23Z

2. Roles and Responsibilities

Show changes

172.19.0.4: /* 1. Introduction */

2025-12-22T07:06:10Z

1. Introduction

← Older revision		Revision as of 07:06, 22 December 2025
Line 1:		Line 1:
	== 1. Introduction ==		== 1. Introduction ==

	* '''Purpose''': Establish a standardized process for reviewing and approving code changes to maintain quality, catch issues early, and ensure audit traceability using tools like Git.		=== '''Purpose''': ===
			* Establish a standardized process for reviewing and approving code changes to maintain quality, catch issues early, and ensure audit traceability using tools like Git.

	* '''Scope''': Covers all code changes in software projects across development teams, focusing on Git-based repositories.		=== '''Scope''': ===
			* Covers all code changes in software projects across development teams, focusing on Git-based repositories.

	* '''Objectives''': Enforce coding standards, reduce bugs, promote collaboration, and keep detailed records for internal audits.		=== '''Objectives''': ===
			* Enforce coding standards, reduce bugs, promote collaboration, and keep detailed records for internal audits.

	* '''Key Terms''':		=== '''Key Terms''': ===
	** Git: Version control system for tracking code changes.		* Git: Version control system for tracking code changes.
	** Branching: Creating separate code lines (e.g., feature branches) in Git.		* Branching: Creating separate code lines (e.g., feature branches) in Git.
	** Pull Request (PR): Git mechanism for proposing and reviewing code changes.		* Pull Request (PR): Git mechanism for proposing and reviewing code changes.
	** Reviewer: Assigned team member who evaluates the PR.		* Reviewer: Assigned team member who evaluates the PR.

	* '''Standards''': Align with company coding guidelines and audit requirements for traceability.		=== '''Standards''': ===
			* Align with company coding guidelines and audit requirements for traceability.

	* '''Audience''': Developers, reviewers, team leads, and auditors.		=== '''Audience''': ===
			* Developers, reviewers, team leads, and auditors.

	* '''How to Use''': Follow this for all code changes; store in Confluence for access.		=== '''How to Use''': ===
			* Follow this for all code changes; store in Confluence for access.

	== '''2. Roles and Responsibilities''' ==		== '''2. Roles and Responsibilities''' ==

172.19.0.4 at 07:04, 22 December 2025

2025-12-22T07:04:13Z

Show changes

172.19.0.4 at 06:44, 22 December 2025

2025-12-22T06:44:09Z

@@ Line 23: / Line 23: @@
 * '''Key Roles''':
-* Developer: Makes code changes, runs tests, creates PRs.
+* '''Developer Tasks''':
-* Reviewer: Reviews PRs, adds comments, approves or requests changes.
+* '''Reviewer Tasks''':
-* Team Lead: Assigns reviewers, resolves issues, ensures process adherence.
+* '''Team Collaboration''':
+** Use Slack #code-reviews for notifications.
-* '''Developer Tasks''':
+** Link PRs to Jira tickets for tracking.

Artha.kadamb@heinfricke.team: Created page with "== Introduction == * '''Purpose''': Establish a standardized process for reviewing and approving code changes to maintain quality, catch issues early, and ensure audit traceability using tools like Git. * '''Scope''': Covers all code changes in software projects across development teams, focusing on Git-based repositories. * '''Objectives''': Enforce coding standards, reduce bugs, promote collaboration, and keep detailed records for internal audits. * '''Key Terms..."

2025-12-19T11:27:34Z

Created page with "== Introduction == * '''Purpose''': Establish a standardized process for reviewing and approving code changes to maintain quality, catch issues early, and ensure audit traceability using tools like Git. * '''Scope''': Covers all code changes in software projects across development teams, focusing on Git-based repositories. * '''Objectives''': Enforce coding standards, reduce bugs, promote collaboration, and keep detailed records for internal audits. * '''Key Terms..."

New page

== Introduction ==

* '''Purpose''': Establish a standardized process for reviewing and approving code changes to maintain quality, catch issues early, and ensure audit traceability using tools like Git.

* '''Scope''': Covers all code changes in software projects across development teams, focusing on Git-based repositories.

* '''Objectives''': Enforce coding standards, reduce bugs, promote collaboration, and keep detailed records for internal audits.

* '''Key Terms''':
** Git: Version control system for tracking code changes.
** Branching: Creating separate code lines (e.g., feature branches) in Git.
** Pull Request (PR): Git mechanism for proposing and reviewing code changes.
** Reviewer: Assigned team member who evaluates the PR.

* '''Standards''': Align with company coding guidelines and audit requirements for traceability.

* '''Audience''': Developers, reviewers, team leads, and auditors.

* '''How to Use''': Follow this for all code changes; store in Confluence for access.

'''2. Roles and Responsibilities'''

* '''Key Roles''':

* Developer: Makes code changes, runs tests, creates PRs.

* Reviewer: Reviews PRs, adds comments, approves or requests changes.

* Team Lead: Assigns reviewers, resolves issues, ensures process adherence.

* '''Developer Tasks''':

* Use Git for branching and code changes.

* Run test cases before creating PRs.

* Act on reviewer comments and update PRs.

* '''Reviewer Tasks''':

* Review code, add comments on issues.

* Re-review updates until PR is approved.

* '''Team Collaboration''':

* Use Slack #code-reviews for notifications.

* Link PRs to Jira tickets for tracking.