kpi-web-guild / django-girls-blog-serhii73

django-girls-blog-serhii73 created by GitHub Classroom
MIT License
0 stars 1 forks source link

Proceed with the Django Girls tutorial #8

Closed webknjaz closed 6 years ago

webknjaz commented 6 years ago

Do a PR per each tutorial page. For simplicity of tracking progress, you may add markdown checkboxed list here.

serhii73 commented 6 years ago

@webknjaz https://github.com/kpi-web-guild/django-girls-blog-serhii73/pull/21 - I passed the first page. Did I understand correctly that I need a new branch for each page? From what branch I need new branch? From master? Right? I need to merge into master, and only then create a new branch? Am I not able to create a parallel branch? Before I merge into master?

webknjaz commented 6 years ago

Sometimes you can do stuff in parallel. According to GitHub Flow (which you should check out), you have to create new feature branches from master and then sync your branches with mater using merge or rebase (but I strongly don't recommend you mixing these two techniques). So you don't have to wait till merging some feature into master unless it depends on that code. It this case you could create new branch from dependent one, but after it's merged to master sync your code in newer branch with rebase or merge.

webknjaz commented 6 years ago

Now most of the tasks are designed to be done sequentially.

webknjaz commented 6 years ago

Again, it would be easier if you create a list of subtasks here to track your progress. For now, you can do a branch per page.

serhii73 commented 6 years ago
serhii73 commented 6 years ago

@webknjaz I finished the tutorial. http://serhii73.pythonanywhere.com/ https://github.com/kpi-web-guild/django-girls-blog-serhii73/pull/31

webknjaz commented 6 years ago

Finishing tutorial was never the point. The main goal is to show you how to work with code/github