"Draft Pull Requests" help sync your current work with your team, creating transparency, and it's simpler to ask for help by sharing the status quo of your task even if it's not done. A Pull Request isn't only for a "finished" thing. Software is about collaboration, individuals, and interactions.
I usually don't create the Pull Request with the first commit, but if it takes me more than one day of work, I don't hesitate to create it (yes, even if it's not finished). It also helps me review everything I've done up to that point.
In Agile, responding to change over following a plan, obstacles are opportunities for change and increased overall value rather than things to barrel through for the sake of the original plan.
Here you can see a little demo of the current status of the new library I am developing with #[0]: It's a #PHP library that let you get a lightning address on your own domain.
Maybe #[0] already said this somewhere, but I didn't find it so far; is the new "Blue Sky app" gonna be a new client for #nostr or something similar? 🤔