Stream: general

Topic: Any PR `force-push` guidance for `bytecodealliance` crates?


view this post on Zulip Frank Rehwinkel (May 13 2024 at 14:23):

I see very many PRs belonging to the bytecodealliance being updated with forced pushes.

I've seen at least one request on a particular PR to use the simpler push and then let the maintainer squash merge when they are ready and that made a lot of sense to me. I too find it hard to follow progress of PRs when an entire bank of diffs has to be looked through again.

But it happens so often, I wonder if I'm in the minority and just not knowing about some way to use GH from the browser to see what's changed?

view this post on Zulip Frank Rehwinkel (May 13 2024 at 14:25):

I see GH provides a compare button. I guess that solves my immediate concern. Still I wonder why forced pushes are so common here.

view this post on Zulip Lann Martin (May 13 2024 at 14:30):

One reason I force push PR branches (in general) is that I prefer to rebase rather than merge when pulling upstream changes into the branch


Last updated: Dec 23 2024 at 12:05 UTC