Phil Hawksworth

Phil Hawksworth @philhawksworth • March 26th 2019 replying to this from @BRIAN_____

@BRIAN_____ @Netlify FWIW, we're working on this.

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 26th 2019 replying to this from @raymondcamden

@raymondcamden @remotesynth @Netlify

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 26th 2019

Ha ha ha!
When the stars align! 🌟 https://twitter.com/raymondcamden/status/1110634070554406917

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 26th 2019 replying to this from @remotesynth

@remotesynth @raymondcamden @Netlify Timing too perfect!

https://twitter.com/Netlify/status/1110631462628413440?s=19

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 26th 2019

Woohoo! 🚀
Deploy your @codesandbox project to @Netlify with a single click! https://twitter.com/Netlify/status/1110631462628413440

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 26th 2019 replying to this from @Netlify

@Netlify @codesandbox Excellent!

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 26th 2019 replying to this from @bigandy

@bigandy @mrtutty @eleven_ty @Netlify Oopsie!
I'm happy to take any credit or praise for running that marathon though :)

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 26th 2019 replying to this from @__jcmc__

@__jcmc FTW!

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 26th 2019 replying to this from @cole007

@cole007 @hereinthehive @upfrontconf Ha ha ha! You convinced me that I had just typo-ed that!

...checking one last time...

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 26th 2019 replying to this from @hereinthehive

@hereinthehive @upfrontconf Booking my train...

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 26th 2019 replying to this from @netlifystatus

@netlifystatus ...contact support@netlify.com was probably the end of that truncated sentence. 🥴

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 26th 2019 replying to this from @nicknickmm

@nicknickmm @smashingmag @frontendunited @upfrontconf Thanks Nick!

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 26th 2019 replying to this from @__jcmc__

@__jcmc Excellent question. I'm afraid that at the moment, those were just gifts for the Netlify team. One day though, we might see them for sale. But not just yet.

https://twitter.com/philhawksworth/status/1085939024534093824

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 25th 2019 replying to this from @bhavana1110

@bhavana1110 Hmmm. That's an aquired taste.

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 25th 2019 replying to this from @amber1ey

@amber1ey @patmeenan @HenriHelvetica @csswizardry These are good 'uns!

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 25th 2019 replying to this from @raymondcamden

@raymondcamden https://media2.fdncms.com/metrotimes/imager/u/blog/2485878/treat_yo_self.jpeg?cb=1487095722

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 25th 2019 replying to this from @__jcmc__

@__jcmc Hey hey!

That sound lovely! I'd been keen to fins a way to make that happen some time.

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 25th 2019 replying to this from @philhawksworth

@sbstjn @Netlify I spoke too soon. All is well now, but you were not mistaken. There was a network glitch on one of our CDN nodes. It recovered automatically, but a small number of people may have experienced a momentary issue as you did.

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 25th 2019 replying to this from @sbstjn

@sbstjn @Netlify Hard to say. I'm not part of the infra or support teams who notice if there is any sort of disturbance in _the force_... but I'm not seeing reports of anything. And all seems quiet. So I suspect it was downstream of Netlify if there was an issue

Glad that you're all operational!

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 25th 2019 replying to this from @sbstjn

@sbstjn @Netlify oh?

No incidents reported as far as I can see. And all my deployed sites, active builds, and the @Netlify admin site all seem ok to me.

Problems?

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 25th 2019 replying to this from @creativityhurts

@creativityhurts It's a GOBAG from @wearegobag.
And I could not love it more!

https://www.gobag.co/

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 25th 2019 replying to this from @hidgw

@hidgw @Netlify Aren't git PRs made against a specified branch? And so won't the preview builds show whatever that PR would result in?

I'm not sure that it is safe to assume that a request to merge into one branch would eventually always result in a merge to master.

Maybe I misunderstand? 🥴

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 25th 2019 replying to this from @JAMESSTONEco

@JAMESSTONEco @Farzad_YZ @biilmann @Netlify Oh sure. A good question.

There have been a few people asking this. And we are tracking it in an issue for more consideration.

At present it isn't planned onto the roadmap as far as I can see. But we'll certainly shout about it if this does end up being a new feature some day.

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 25th 2019 replying to this from @farzad_yz

@Farzad_YZ @JAMESSTONEco @biilmann @Netlify It feels like it embraces some popular git workflow patterns, which is a model I tend to like.

https://datasift.github.io/gitflow/IntroducingGitFlow.html

Permalink
Twitter

Phil Hawksworth @philhawksworth • March 25th 2019 replying to this from @farzad_yz

@Farzad_YZ @JAMESSTONEco @biilmann @Netlify Git can help here. Many achieve this by having a release branch (which might be master but can be anything) and only merging tagged releases to that branch.

By setting this to be your production branch in Netlify, only your tagged releases get deployed.

Permalink
Twitter

Newest
Previous
Next
Oldest

The source code of this site is available on GitHub and is hosted and updated by Netlify automatically after each code commit

Other than where specified, the content on this site is published under a Creative Commons Attribution 3.0 licence.

Subscribe to a feed of blog posts on this site.