
@sarah_edo Turn this battle into an HBO series that we can all enjoy watching from the comfort of our living rooms?

@kdembler_ @Netlify @NetlifySupport This is helpful feedback.
Also makes me wonder if socialising the permalink to the specific deploy in the PR in additional to the main deploy preview URL might be useful in general.
I'll pass it all along.
Also makes me wonder if socialising the permalink to the specific deploy in the PR in additional to the main deploy preview URL might be useful in general.
I'll pass it all along.

@martinbean @Netlify Ooh sorry if you received many emails. This will be related to the new collaborative deploy previews feature.
Info on the feature:
https://www.netlify.com/products/deploy-previews/
More info here on those permissions:
https://answers.netlify.com/t/netlify-github-app-permission-updates-with-collaborative-deploy-previews/37872
Info on the feature:
https://www.netlify.com/products/deploy-previews/
More info here on those permissions:
https://answers.netlify.com/t/netlify-github-app-permission-updates-with-collaborative-deploy-previews/37872

@kdembler_ @Netlify @NetlifySupport This is not currently configurable (although I'll pass along the feedback, so thanks!).
However this is only added to the preview deploys so you can always see every deploy without it by visiting the permalink for any deploy (or any branch deploy URL)
However this is only added to the preview deploys so you can always see every deploy without it by visiting the permalink for any deploy (or any branch deploy URL)

@Bradamante @Netlify @NetlifySupport Oh!
That is very unexpected and suggests some other issue. I think that the support team will want to help out. They might ask for details.
That is very unexpected and suggests some other issue. I think that the support team will want to help out. They might ask for details.

@Bradamante @Netlify @NetlifySupport Extra builds?
This should not have resulted in any extra builds. It should add the UI for commenting only to the preview deploys which you create as a result of making a pull request on you site's repo.
Are you seeing something different?
This should not have resulted in any extra builds. It should add the UI for commenting only to the preview deploys which you create as a result of making a pull request on you site's repo.
Are you seeing something different?

@johnson_brad @featurepeek @Netlify SHOUT IT FROM THE ROOFTOPS!
So thrilled to be working with you, Brad!
So thrilled to be working with you, Brad!

@_developit @biilmann That's an interesting idea.
I expect that this would play into the discussions around making this as discoverable as we can with the least friction possible. But I'll happily feed the suggestion back to the team.
I expect that this would play into the discussions around making this as discoverable as we can with the least friction possible. But I'll happily feed the suggestion back to the team.

@_developit @biilmann Branch deploys should have you covered for that. You can watch and build unlimited branches which don't get this feature and the branch deploy URL always track the head of that branch.


Phil Hawksworth
@philhawksworth •
I was already excited before I even saw this shocking pun and the bonus photo of @jlengstorf.
Why would you NOT join?
http://ntl.fyi/product-reveal https://twitter.com/Netlify/status/1394968854997213186
Why would you NOT join?
http://ntl.fyi/product-reveal https://twitter.com/Netlify/status/1394968854997213186

@DavidDarnes @futuregerald It starts getting awkward at around the 3 minute mark.

@zachleat White Screen of Death.

@bdougieYO Class

@Robb0wen I see you taking my picture.
Don't you dare put that shit on twi...
Don't you dare put that shit on twi...

@ianand Oh good. I'm glad that came across. The tricky line to walk is in making this potential advancement both compelling yet faithful, while also keeping it suitable for wider adoption and avoiding a tight coupling to either vendor or framework.

@webstandards 🙂
That's the right form. With more info on our pro account support for open source projects here:
https://www.netlify.com/legal/open-source-policy/
That's the right form. With more info on our pro account support for open source projects here:
https://www.netlify.com/legal/open-source-policy/

@ianand This is also the intent behind the DPR RFC.
By describing in detail the model/flow it would enable, the hope is that any vendor/ssg could strive to support it. The more the merrier. And it optionally expands, rather than undermines the core attributes of Jamstack
By describing in detail the model/flow it would enable, the hope is that any vendor/ssg could strive to support it. The more the merrier. And it optionally expands, rather than undermines the core attributes of Jamstack

@ianand A valuable point. I think as the category matures, capabilities will/should get added if they are in keeping. Ideally in a non-proprietary way.
Edge-based redirects is an example. Many vendors support this feature which extends the original core simplicity of Jamstack
Edge-based redirects is an example. Many vendors support this feature which extends the original core simplicity of Jamstack

@DavidDarnes @zachleat (chairman of the)

@zachleat I think the Queen keeps an eye on Twitter for the #NeedsAKnighthood hashtag