Suggestion: We should avoid merge commits. #321
Replies: 3 comments 6 replies
-
Hello Shailesh,
I also suggested to do "Squash and merge" for every PR.
Also the commit messages must contain what this particular commit does - a brief and meaningful message.
Best Regards,
Huang HUa
…________________________________
From: Shailesh Vadiya <[email protected]>
Sent: Sunday, September 20, 2020 9:27 PM
To: Seagate/cortx <[email protected]>
Cc: Subscribed <[email protected]>
Subject: [Seagate/cortx] Suggestion: We should avoid merge commits. (#321)
Just a suggestion
|
Beta Was this translation helpful? Give feedback.
-
Currently we have 76 branches in https://github.com/Seagate/cortx 😟
Seems we are not deleting branches after merge. Ideally we should move to |
Beta Was this translation helpful? Give feedback.
-
@shailesh-vaidya, We had enabled auto delete branches from cortx repo once they are merged as well as will initiate to delete the stale branches as well |
Beta Was this translation helpful? Give feedback.
-
Just a suggestion☺️
https://github.com/Seagate/cortx shows merge commits in history and its bit difficult to associate commit with task/ticket. We can merge PR using
Squash and merge
option with proper description. So that we can identify changes done for particular ticket/task.Current git history graph looks like this,
Beta Was this translation helpful? Give feedback.
All reactions