Discover how the Interface Segregation Principle (ISP) keeps your code lean, modular, and maintainable using real-world analogies and practical examples.
<selectedcontent>
element improves dropdowns
is an experimental HTML element that gives developers control over how a selected option is displayed, using just HTML and CSS.
Learn how to implement an advanced caching layer in a Node.js app using Valkey, a high-performance, Redis-compatible in-memory datastore.
Learn how to properly handle rejected promises in TypeScript using Angular, with tips for retry logic, typed results, and avoiding unhandled exceptions.
3 Replies to "Using stacked pull requests in GitHub"
In your example to break up a large PR, you suggest:
$ git checkout migrate-to-firebase
$ git reset –soft develop
$ git restore –staged .
Is that not the same thing as:
$ git checkout migrate-to-firebase
$ git reset develop
Thanks.
You’re right, David. And you might require a `git rebase develop` before all that if `develop` has newer changes.
As of today, the Github feature no longer works for me. I had this stack of PRs: https://github.com/pypa/setuptools/pull/4103, https://github.com/pypa/setuptools/pull/4069. After merging 4103, 4069 reported that the target branch had been deleted and closed itself without the ability to re-open. Perhaps the “delete branch on merge” feature happens too soon and prevents the “Base automatically change” from taking effect?