Request for Reconsideration of Labels/Points Due to Git Branching Mistake

[PraneshJha1038]

Hi @Priyanshu-byte-coder,

I realized there was an issue with how I created my branches locally.

The PR for fix-pr-breakdown-visibility-issue (#142) unintentionally included commits from my other branch (fix-overflow-text-at-Pr-Analytics (#143)) because the second branch was created from the first branch instead of directly from main.

So even though I created two separate branches and two separate PRs, the commit history caused both fixes to appear together in the first PR accidentally.

The fixes were actually for two independent issues:

• PR analytics overflow text fix
• PR breakdown visibility fix

Because of that, the second PR was marked as duplicate even though the implementation work for that issue was completed separately.

At the moment, only the merged PR received the level:beginner label, which reflects the visible scope of that PR alone. However, the duplicated PR corresponded to a separate issue with a higher difficulty level (level:intermediate), and its fix was effectively included inside the first PR due to my Git branching mistake.

So the current point allocation does not fully represent the total completed work across both issues, even though both fixes were implemented.

I completely understand that this situation was caused by my Git workflow mistake, and I’ll be more careful with branch ancestry going forward. I just wanted to clarify the context in case the labels/points can still be reconsidered appropriately.

Thank you.

[PraneshJha1038]

@Priyanshu-byte-coder Reminder

[Priyanshu-byte-coder]

Hey @PraneshJha1038 — thanks for the detailed explanation.

I looked at both PRs:

• PR [Fix]: Overflowing Text at PR-Analytics Grid #145 (Overflowing Text at PR-Analytics Grid) — fixes truncation/overflow in PRMetrics.tsx, 4 lines, single file
• PR Fix pr breakdown visibility issue #262 (Fix pr breakdown visibility issue) — fixes the Recharts tooltip CSS variable resolution in PRBreakdownChart.tsx, and also includes those same overflow lines from [Fix]: Overflowing Text at PR-Analytics Grid #145 due to the branch ancestry issue you described

Both fixes are real and independent — PR #145 was missed on labels because the same changes appeared in #262, making it look like a duplicate from the surface.

That said, difficulty is based on the work done, not the issue label. PR #145 is a 4-line CSS fix in a single component — that is level:beginner (20 pts), not intermediate. The intermediate label on the issue described a broader potential scope, but the actual fix was minimal.

I have labeled PR #145 as level:beginner + gssoc:approved — points are now counted.

Going forward: always branch off main directly. Two independent issues = two fresh branches from main. Avoids exactly this kind of cascading commit problem.

[PraneshJha1038]

thanks a lot 🙂