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.