GitHub user dmiele-bonial added a comment to the discussion: PR Coding time affected by (squash) merge strategy
Hi @klesh , thank you for the reply. Attaching some screenshot to show in details the challenge we are facing. PR opened on **2025-04-01**, updated two times and finally merged two days later on **2025-04-03**. <img width="793" alt="Screenshot 2025-05-21 at 11 26 52" src="https://github.com/user-attachments/assets/63d8f8e5-17e6-41cf-a8ae-46024e4f25fc"; /> Upon merge the commits were squashed and resulted in only one commit with a timestamp equal to merge date: **2025-04-03** <img width="2250" alt="Screenshot 2025-05-21 at 11 27 09" src="https://github.com/user-attachments/assets/dd3227da-9fae-421c-88f8-2d8ffd17e753"; /> Eventually this PR has **0 hours** for coding, pickup and review time. The **change_lead_time** though seems calculated correctly (2.30 days). <img width="2229" alt="Screenshot 2025-05-21 at 11 25 46" src="https://github.com/user-attachments/assets/14b0f1e1-b2b8-4672-8397-4574e1ecb183"; /> _Are you rebasing and force-pushing the PR before merging?_ No, we are don't. We simply (in this case renovate) merge using a default bit bucket merge strategy, no force push. <img width="606" alt="Screenshot 2025-05-21 at 11 48 35" src="https://github.com/user-attachments/assets/797f5e9c-0c55-4d86-bb55-4b3bc94f5e4b"; /> GitHub link: https://github.com/apache/incubator-devlake/discussions/8440#discussioncomment-13218234 ---- This is an automatically sent email for dev@devlake.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@devlake.apache.org
