Draft Pull Requests and WIP Workflows
What you'll learn: How to use draft pull requests to gather early feedback and collaborate on work that's not yet ready for formal review.
The Problem with Waiting Until Perfect
Imagine writing an entire data analysis notebook, refactoring a complex pipeline, or building a new feature—only to discover during review that your approach doesn't align with team expectations. Waiting until work is "done" to share it can waste time and effort.
What Are Draft Pull Requests?
Draft pull requests are a special PR state that signals "this is work-in-progress—feedback welcome, but don't merge yet." They let you share code early without the pressure of a formal review. Think of it like showing a rough sketch to a colleague before painting the final canvas.
On platforms like GitHub, you mark a PR as "draft" when creating it. Drafts can't be merged accidentally, clearly communicate status, and invite discussion without blocking the review queue.
When to Use Draft PRs
- Early feedback on approach: "Before I process these 50 datasets, does this transformation logic look right?"
- Architectural discussion: Sharing skeleton code to validate design decisions
- Incremental collaboration: Breaking large features into reviewable chunks while still working
- Transparency: Showing progress to stakeholders without claiming completion
The WIP Workflow
- Create a feature branch as usual
- Make initial commits with your approach
- Open a draft PR with a clear description of what's complete vs. in-progress
- Tag relevant teammates for specific feedback
- Continue committing and pushing as you iterate
- When ready, mark as "ready for review" to trigger formal review
This approach reduces surprises, catches misalignment early, and makes collaboration feel less like judgment and more like partnership.
Key Takeaway: Draft pull requests transform PRs from gatekeeping checkpoints into collaborative workspaces, enabling early feedback loops that save time and improve outcomes in data science projects.