indigotech / onboard-lucas-tamai

0 stars 0 forks source link

[Track 0/9] GitHub setup #1

Open taki-tiler[bot] opened 4 years ago

taki-tiler[bot] commented 4 years ago

Taqtile - Onboard

Welcome to the Taqtile onboard. The main goals of this onboard are:

  1. Learn the basics about some concepts building your own application/website
  2. Get you ready for a real project by presenting some of our stack of technology and best practices

Step 1/3 - Warming up - Mastering the Basics

Ok! Your very first tasks are to clone this repository into your own account and update the README.md file.

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:

BTW, we highly encourage training using the terminal.

On 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. Any problem with me, you can ask your tutor for help.

LucasTamai commented 4 years ago

Finish

taki-tiler[bot] commented 4 years ago

Step 2/3 - Clone this repository

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

$ git clone repository_link

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

LucasTamai commented 4 years ago

Finish

taki-tiler[bot] commented 4 years ago

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-screen
    • 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
LucasTamai commented 4 years ago

Finish

taki-tiler[bot] commented 4 years ago

Click here for your next track