You must be a ticket holder to proceed
Ticket holders must sign in to LeadDev.com with exactly the same email address as stated on your ticket.
Do you have a LeadDev.com account matching the email address on your ticket?
My email is not recognised or, having signed in, it says I do not have access to the content
Double check your ticket to make sure that you are trying to access with the correct email address (see below for where to find your ticket).
If you're sure that the ticket is correct, get in touch via Slack and we'll investigate for you
The verification email does not arrive
Check your spam and/or junk folders for the email. We know that some corporate email firewalls block our emails, and in this case you'll need to get in touch (see below) for us to move your ticket to an alternative email address.
The verification email link does not work
The links are time limited, so make sure you've tried in the last few minutes. If not, some corporate email firewalls have occasionally corrupted the verification links, and in this case you'll need to get in touch (see below) for us to move your ticket to an alternative email address.
Where can I find my ticket?
Your ticket will have been emailed to you from support@tito.io (Tito is our ticketing provider). If you don't have an email from Tito with your ticket, check with the person who made the booking originally. Otherwise, get in touch and we'll be able to help.
Getting help
The quickest way to get support is via our #help-desk channel on Slack (not a member of LeadDev Slack? join here.)
You can also email hello@leaddev.com although response times will be slower.
We’ve all experienced what we believe to be perfectly crafted PRs getting blocked for seemingly arbitrary reasons.
In this short and fun talk (yes it’ll be fun!) – we’ll lament about the top blockers of PRs, but cheer up – because we’ll also provide insights into how to unblock them. We’ll share better mechanisms for qualifying PRs than just the binary block/allow, and how and why you should codify your development process (and not just rely on oral tradition). You’ll come away with good ideas for how to mix and match rules and inputs to intelligently delegate PRs to the right people and optimize your PRs for the process so they don’t just end up in the dead queue of a failed build.
