Use a text editor to add the following three lines: If you aren't sure which one to go with, keep Git as your option.Ĭlick Create repository. Bitbucket creates your repository and displays its Source page.ĭouble-click the bitbucketstationsupplies repository in Sourcetree and notice that there is nothing to commit from your local repository to the remote repository. Include a README? -If you recently created your account, this defaults to a tutorial README. For the purposes of this tutorial, pick either of the Yes options, that way you'll start out with a file.įrom Version control system, you can choose either Git or Mercurial. If this box is unchecked, anyone can see your repository. Keep the rest of the options as is unless you want to change them:Īccess level -Leave the This is a private repository box checked. A private repository is only visible to you and those with access. For example, if the user the_best has a repository called awesome_repo, the URL for that repository would be. Bitbucket uses this Name in the URL of the repository. With the exception of the Repository type, everything you enter on this page you can later change.Įnter BitbucketStationSupplies for the Name field. Take some time to review the dialog's contents. Bitbucket displays the Create a new repository page.
It doesn't have to be something you created yourself. You can also use that you contributed to another open source project. You can use an app, you can use code, you can use an open source project. So, it's all about what will you use to back up your arguments.
Our friend Sean Allen, for example, he has this amazing course right now about the Take Home Project, and just following a course like Sean's, or like someone else's, or like some of your many courses as well, and putting the result on GitHub just to show, “here, I learned this, here's my outcome, I tweaked it a little bit,” or something. "So there are so many different venues to take, which I think is one of the most beautiful things about our industry, is that there is rarely one specific path that you have to take going from beginner, to mid-level, to senior."Īgain, it comes back to: are you able to back up your argument that you are the right person for the job? And if you can do that using a really nice app that you built, if you can do that using some cool code that you've put on GitHub, or just you followed some tutorial, like you mentioned earlier, you put those skills into practice. I can't say to you, "just make an app and put it on the App Store, you're going to get a job." Or, "just make an open-source project, you're going to get a job." Or, "if you don't have either of those two things, you cannot get a job." Neither of those things are true. Someone here in the chat is saying that, "you can take a shot every time John says silver bullets or static site generator." I think you could add, "it depends," to that list as well, because I tend to say, "it depends," a lot. Like, "do I need to do open source to get a job?" Or, "do I need to have an app on the App Store to get a job?" And the boring answer is always, "it depends." John Sundell: So, this is something people ask a lot.
#IOS APP SOURCE CODE GITHUB FULL#
Recorded March 28th 2020 – watch the full episode on YouTube.ĭo you think it's more important to be able to say, "yes, I have shipped apps on the App Store," or "here is my code on GitHub" in order to get a job? Building a portfolio: should you ship an app or put code on GitHub?