Closed cpendery closed 2 years ago
Thanks for pointing this out. It looks like it's just misconfigured. It should be configured to not create a merge or squash commits, just to rebase.
@rgreinho can you help take a look at this? Thanks.
Sure thing!
for 1, I think we should put the burden on the committer to squash their commits. We don't know how they want to fix them up.
I can change it in the configure for sure, but I believe that's too big of a task for the committers in general and it will end up being skipped...
Personally I just do git commit --amend
on any PR I'm working on or rebase -i
if I end up wanting to create commits I'm not sure I wanna keep. I just think we can require one single commit. and just block until they've fixed it. I don't want us to make a fix though that ends up causing a bigger annoyance than the squash.
I totally agree with you! But sadly, not some many contributors do that 😢
@rgreinho For reference, my pr just merged with CLA issues. It doesn't cause DCO issues https://github.com/guacsec/guac/pull/150
@lumjjb I think this issue should be opened back up. The fix merged makes the auto-merge functionality (for merging once the pr is complete) into a rebase rather than a squash. The issue is when the Kodiak bot merges changes into an open PR. It happened a few hours ago as seen above ^
i've been looking at this right now, as you may see my commits :p... i think this will fix it : https://github.com/guacsec/guac/pull/187
we'll keep it squash for now and this should fix issues with the CLA for now... we will talk more about rebase later on, since its more of an opinion rather than functional.
Sounds good, it definitely fixed the issue since after merging Kodiak didn't add it to my pr again. Thank you!
Can we please disable the Kodiak Bot merge feature for the following reasons?