The Complete HOW TO USE GITHUB WITH ANDROID STUDIO Book
Includes a 123-page PDF guide and step-by-step video demonstrations to show you how to:
Our work has been featured in:
GET THE BOOK
£2 ($2.50 USD)
(95% OFF NORMAL PRICE £39.99)
The Book - a 123-page illustrated guide (PDF)
Access to the closed community
Full video demonstrations
Bonus videos: Android Studio set-up for Windows & MAC OS X
Lesson 1: How to Push Your Project to GitHub
Step 1 - Create an Android Studio Project
Step 2 - Test the Project
Step 3 - Push Your Project to GitHub
Lesson 2: How to Clone a GitHub Project
Step 1 - Clone the Project
Step 2 - Making Changes
Step 3 - Commit Changes and Push to GitHub
Step 4 - View Changes on GitHub
Lesson 3: What Are Branches and How to Use Them
Step 1 - Creating a Branch
Step 2 - Switch between Branches
Step 3 - Rebasing a Branch Merge and Rebase
Step 4 - Pushing a Branch to GitHub
Step 5 - Merging Changes
Lesson 4: Pulling Changes and Handling Conflicts
Step 1 - Make Change on GitHub
Step 2 - Update Android Studio Project
Step 3 - Create Conflicting Change
Step 4 - Update Project with Conflicting Change
Step 5 - Commit and Push to GitHub
Step 6 - View Changes in GitHub
Lesson 5: Forking Projects and Making Pull Requests
Step 1 - Fork the Project on GitHub
Step 2 - Clone the Project to Your Local Drive
Step 3 - Push Change to GitHub
Step 4 - Create Pull Request
Step 5 - Accept Pull Request
Lesson 6: Troubleshooting Common Problems
Issue 1 - Push Rejected
Issue 2 - Using GitHub Two Factor Authentication
Issue 3 - No Git controls at bottom of screen
Issue 4 - Missing options under VCS
Learning how to use GitHub is not just about the technology
The single-most important thing I’ve done to advance my programming career is really quite simple: publish my code.
I went from an IT support role to a senior full-stack developer in 3 years, and now charge $600 USD a day for my time.
I put in a lot of hard work to get here, but one of the biggest factors for my success was learning how to use GitHub.
GitHub is just a tool. The skills you develop from learning how to use it, however, is truly what makes you stand out as a great developer.
If you’re a professional developer, or your goal is to become one, I guarantee you that most of your time will be spent working in teams. This was something I didn’t realize when I was a student but it became blatantly obvious to me when I joined the workforce.
The myth of the lone developer sitting in his room building the next Facebook is just that…a myth. Your success as a developer, however you want to measure it, will depend entirely on how well you work with other developers. GitHub is the world’s largest repository for open-source projects and the largest network of developers from around the globe. Learning how to use it is an opportunity to network, collaborate and build world-class projects with like-minded people.
Publishing your code for the world to see forces you out of your comfort zone – and that’s when you truly grow as a developer. By making your code public, you are putting yourself, your skills and experience out there for the world to see. The sheer act of exposing your code, of facing your fears as a developer (whatever they may be) builds character and confidence. Every time you share your code, your confidence as a developer grows.
Publishing your code to GitHub showcases your skills and experience and establishes your authority as a great developer. You don’t have to create an app with a million downloads, or build the next Facebook to do this.
When I was first starting out in my career, I had trouble getting the roles I wanted. Despite my work ethic and positive attitude, hiring managers couldn’t see past my lack of formal experience. So I started creating little projects in my spare time. I built a phone-to-desktop clipboard app and an app for my friend’s wedding, both in Android. I published all my code to GitHub and slowly started to build a reputation in the community. The fact that I had a portfolio of code and a reputation – no matter how basic – was enough to get employers to take notice of me.
Follow a Proven Method
I made this book to solve one simple problem: To help developers showcase their skills and experience so they can get the jobs they deserve.
That’s my core goal.
But to get to the finish line – to get the job you truly deserve – you need to learn how to use this technology.
The value in this book is that it explains how to use these technologies in-depth and according to BEST PRACTICE.
Best practice is what separates good developers from great ones. It’s what makes your code cleaner and easier for other developers to work with. It’s scalable and less likely to break. And it means never having to go back and start from scratch. Everything designed in the book is built according to best practice so you can learn how to use this technology properly the first time around.
Each chapter shows you step-by-step – with straight-forward instructions, screenshots and code snippets – how to complete the five most important functions you’ll need in order to showcase your skills and collaborate with other developers.
By taking away the guesswork we can get you up and running in record time with a solid understanding of the technology. That means more time and energy for you to focus on getting your projects published and getting the recognition you deserve.
Why should I buy this book when I can find tutorials online for free?
Because rather than having to scour the blogs and forums trying to find it, it’s all right here, in true best practice form. All you have to do is follow the book step-by-step.
Plus – if I don’t charge you for it, you won’t value this information or put it to use. We value what we invest in. Everything else we archive.
If you’re the type of developer who just wants to knock out code as quickly as possible so you can move onto the next thing and get “more” done, then I wouldn’t buy this book. You can find free alternatives online. Just do some digging to find fast hacks. Bing, bang, boom. Job done.
But if you’re like me and you:
1. Are committed to producing quality code
2. Want to learn the best practice way of doing things
3. Need clear direction on how to master this technology to take your career to the next level
…then maybe the How to Use GitHub with Android Studio book is right for you.
If you are serious in learning how to properly use this technology and see it as a critical building block to your career, then consider this book.
What if I don’t like it?
Customer satisfaction is my number one priority. I want you to be happy with the book. My goal for creating it is to help people with their careers. If it doesn’t bring any value to you, then I don’t want your money. Just get in contact with me within 30 days of your purchase and I’ll issue you a full refund. I may ask for feedback just so I can learn what worked and what didn’t for you, but you won’t be obligated to give it.
Where can I learn more about you?
Everything I write about is on londonappdeveloper.com. If you want to receive my latest free tutorials, sign up to my newsletter. (It goes out to 5,000+ developers a week). I’m also on Twitter, Facebook and GitHub.
Do I have to have programming experience to use this book?
This book is designed for you to use step-by-step to arrive at a very specific outcome. No prior programming experience is required, but as with everything, it helps. If you have a basic understanding of Android, even better.
Any other questions? Just drop me a line at firstname.lastname@example.org
Hey I’m Mark. I’m the founder of London App Developer – a software consultancy firm and an educational blog for developers. My projects have been featured in the Daily Mail, Mashable, TechCrunch, the Huffington Post, the Mirror and Gizmodo, and over 30,000 developers read my programming tutorials every month.
My goal with this book, and the blog, is to help developers make a better living through their code.
I live in London, England with my wife and business partner, Brooke. (Who also worked on this book!)
MARK WINTERBOTTOM & BROOKE RUTHERFORD
About the Authors
“What if my code sucks?”
I guarantee you that your code does not suck. The fact that you’re saying this means you’ve set yourself high standards, and you feel like you’re not living up to them. You’re called an insecure-overachiever, and you’re the best kind of developer because you have the desire to improve and the willingness to learn. All that’s needed is accountability.
Accountability is what separates people who achieve their goals from those who don’t. It’s what holds us to our word when we’re not putting in the time or effort to make things happen.
By making your code public, you are making yourself accountable for your work. You are putting your name to your code. Trust me when I say the fear of pushing code to GitHub, where millions of other developers can see it, is enough leverage for me to focus on improving it. I have a feeling the same will be the case for you.
It also gives other developers the opportunity to help you. How do you expect to improve without the guidance and advice of others? They can’t give you tips or suggestions on your code when it’s sitting at home on your hard drive. You have to get it out there in the public domain for it to have any impact. Do you want your code to have impact?