Who's hiring? I've been effected by the latest round of redundancies at Netlify. So I'm on the hunt for Senior/Staff-level Software Engineering positions right now!
@matthewmercer I know you're not likely to even spot this given how many folks likely message you every day. But on the off chance you do I'd love your thoughts on where a race of Plasmoid Nudibranchs could thrive on the Menagerie Coast https://t.co/W5M0YPuDVh
@bigbearcatdev I'm trying to add cantrips to a Ranger who has the Druid Warrior fighting style via the Prepare view, but can't adjust the filters to show them. Is there a way around this?
I’m excited to announce that the new navigation has graduated from Labs and is now available by default to all @Netlify users!
We’ve also included a ✨bonus✨ update in this release – our breadcrumb nav now includes a new dropdown to quickly switch between your sites.
@Ms5000Watts I saw a vid that suggests using just waiting for the red lock-on marker to appear rather than the full charge in PvP, and then following up with tap firing if needed
@manlikeslatt@mrdillon66@BungieHelp If you get to this screen you are good to go. If you are stuck on "Connecting" and the sound crashes, you have the bug
@mrdillon66@BungieHelp I'm guessing that if they are in our collections we should be ok. But will have to wait until later to check. I hope in the long run they will fix this bug for everyone
@BungieHelp I also had to delete all the other add-ons (pre-order ones I think) that mentioned Forsaken, and the original pre-order bonuses (such as Coldheart pack) to get past the "Connecting" bug
@BungieHelp I also had to delete all the other add-ons (pre-order ones I think) that mentioned Forsaken, and the original pre-order bonuses (such as Coldheart pack) to get past the "Connecting" bug
@BungieHelp I also had to delete all the other add-ons (pre-order ones I think) that mentioned Forsaken, and the original pre-order bonuses (such as Coldheart pack) to get past the "Connecting" bug
@LeaVerou@Netlify This approach might fall foul of our automatic deploy deletion functionality though (https://t.co/JGlktMVIzr). Previously I've personally used branches to achieve this, and added branch protection in GitHub to make sure they are less likely to get deleted
@LeaVerou@Netlify Can't test right now as I'm away from my desk, but a possible solution could be to add the subdomain as a domain alias under Site Settings. Then set up a domain level redirect (https://t.co/w4NMEgjIej) to point to the permalink of the specific commit (https://t.co/7nGPJEsSui)