[Track 0/9] GitHub setup

[taki-tiler-server]

Taqtile - Onboard

Welcome to the Taqtile onboard. It will help you to get used to our technology stack, patterns and best practices.

Thoughout the onboard, you will develop a server able to:

1. Store some data in a database (db)
2. CRUD that data stored in db

Step 1/3 - Warming up - Mastering the Basics

Ok! Your first tasks will be given on next steps. But before moving on, let's be sure you know all the basics we use daily here.

We use git... a lot. If you don't feel confident in your skills using git, here are some recommendations:

• https://try.github.io/
• https://www.atlassian.com/git/tutorials
• https://learngitbranching.js.org/

If you don't have it already, we recommend you to install a VSCode extension called GitLens. It's going to help you a lot with git by adding some functionalities to VSCode, including an extra view on activity bar (the icons on the left side).

With Gitlens you'll be able (among other things...) to check who modifies the file and the prevision versions (previous changes) of that file, right in VSCode.

Even though this extension has some tools to perform git commands, we highly encourage you to use the terminal, and use the extension as a visual guide to your changes.

--

At the end of every task of this onboard, comment the word Finish on the issue to receive your next task (you can try reloading the page if it's taking too long).
You can also comment the word next, in case you had to skip the current task.

In case of any issue, you can ask your tutor for help. Go to next step!

[GuiCastelo]

Finish

[taki-tiler-server]

Step 2/3 - Clone this repository

You can follow these steps in order to clone this repository:

• Login to GitHub (if you don't have an account, create one here)
• Go to this repository root page
• Click on clone or download green button
• Copy the URL and type the following command in Terminal:

$ git clone repository_link

When you're done, the git will download (clone) the entire project into the folder you're running the terminal.

[GuiCastelo]

Finish

[taki-tiler-server]

Step 3/3 - Git Flow

Before continuing, it's important to be familiar with our branch model and a few more git tricks.

Branch model

When working in teams, it's crucial to coordinate the parallel work of all team members.

In order to improve our workflow, a few years ago, we've adopted Vincent Driessen's branch model described here and we are going to use this same branch model during our onboard.

Git Flow

git-flow is a tool that helps to follow Vincent Driessen's branch model. You can use it though it's not necessary.

Our conventions

There are a few conventions we use here and it's important for you to be aware of these:

1. Feature branches are:

   • prepended with feature/ i.e. feature/new-user
   • should have meaningful names - they should give good hints about what modifications to the system they have
   • should not have your name on it

2. Bugfix branches are:

   • prepended with bugfix/ i.e. bugfix/user-list

[GuiCastelo]

Finish

[taki-tiler-server]

Click here for your next track