Glimpse the future with Deploy Previews

Phil Hawksworth - Dec 15 '21 - - Dev Community

Throughout December we'll be highlighting a different Netlify feature each day. It might just be the thing you need to unlock those creative juices, and dust off that domain you registered but never deployed! Keep an eye on the blog and on Twitter for each feature!

Deploy previews are another part of the Netlify time machine! Great Scott!!

While rollbacks give you an opportunity to instantly step back in time to any previous state of your project, Deploy Previews give you the chance to explore the future state of your project.

And knowing the future is a powerful thing!

Netlify's workflow is built on top of Git workflow conventions. Git's Pull Request model lets you propose changes in a way that they can be clearly reviewed and revised, and Netlify uses this to create previews of how these proposed changes will impact your project

How it works

Whenever a Pull Request is submitted to your code repo, Netlify will generate a Deploy Preview. You get a URL to visit and share which shows you how your project will look if you decide to merge that Pull Request. It really is like being able to see the future.

The confirmation of a Deploy Preview being available in the Deploys page on Netlify

The changes look good? Great! Merge the Pull Request into your production branch and they'll get built and deployed just as you'd approved them.

But there's more!

These Deploy Previews proved to be so valuable for collaborators and teams, that Netlify introduced Collaborative Deploy Previews which adds a suite of tools on top of these previews. You can use them to review and manage feedback on your project's development. With integrations with many leading workflow and management tools, you'll be able to surface your feedback where your team is already working.

More information

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .