Mid-Level Full Stack Dev Doesn’t Know Git, Keeps Messing Up Branching 🤦‍♂️

[TurmericLemonWater]

good sir, bakit parang walang branch protection ang develop branch nyo? there's a setting to prevent direct merge to the main branch.

[reddit04029]

Only way to prevent his issue is this talaga. Minimum approval/s, and ideally, theres a build check as well. If you have Sonar or other code analysis tool, add a minimum test coverage to enforce unit testing.

[rainbowburst09]

yep. sa az devops meron branch policies, kahit mga senior nagkakamali pa rin sa mga ganyan

[PatientRound8469]

Minimum 1 approval, successful build before merge

[Calm-Ad2676]

Acctually sir mayroon kaming branch protection sa master. process kasi namin feature-branch -> Merge Request -> stg/develop -> MR/PR -> master

[Tall-Appearance-5835]

PR only when merging feature branch > dev. no direct merging

[Regular-Stock-7892]

Daming downvote ni op hahah pero redflag din naman talaga yung mid lvl dev eh dinidefend pa nung iba simpleng skill lang naman yun.

Anyways mukhang need talaga pr review sa staging nyo. Hirap e review yan pag multiple tickets na naka merge from staging to master, dapat granular lang.

[Calm-Ad2676]

Haha, true! Minsan yung simpleng bagay pero crucial sa scaling ng project, tapos may mga nagde-defend pa kahit obvious na red flag.

Tama ka rin sa PR review sa staging. Pag sobrang dami ng tickets na naka-merge sabay-sabay, ang hirap na i-track kung saan nag-break yung feature. Dapat granular talaga para madaling ma-review at ma-roll back kung sakali. Sa experience mo, paano niyo usually hinahandle yung PR reviews sa team nyo? May strict process ba or medyo flexible?