GItHub IB Guide

[slowdive]

Steps for how to best use GitHub features for collaborative work:

(I'll add images and more detail later)
1) clone repo to your PC (unless you already have it on your PC)
2) create a branch in VS

IB12.png (24.43 KiB) Viewed 44218 times

IB13.PNG (4.22 KiB) Viewed 44218 times

IB14.PNG (4.1 KiB) Viewed 44218 times

3) make your code changes to your branch (not the to master) and test them out
4) push periodically to your branch (not to the master) on GitHub (make sure only to push code, not .exe, .config, or modules, etc)
5) once you are ready to finalize your code for your branch, create a pull request from within VS (VS will redirect you to the GItHub web page for the actual making of the pull request)

IB26.PNG (15.73 KiB) Viewed 44074 times

IB23.png (33.79 KiB) Viewed 44167 times

6) wait for Karl or Slowdive to merge the pull request into the master

IB24.png (48.93 KiB) Viewed 44167 times

IB25.png (41.64 KiB) Viewed 44167 times

7) once it has been merged, switch back to the master branch in VS and pull the latest changes to your PC version of the master branch
8) start another branch to make more changes (go to step 2)

[youngneil1]

Thank you, Jer - once I restart my coding endeavours (soon, I hope) this will be extremely helpful.

[slowdive]

Thank you, Jer - once I restart my coding endeavours (soon, I hope) this will be extremely helpful.

I figure it will be useful for us both since I often can't remember how I did things after a few days

I have similar type step by step instructions for how to build release versions and post to Google Play and Apple App Store (because I always forget).

[slowdive]

So now that most of the features from IBbasic are added to IB, I will start creating smaller branches. I'll make a branch for each bug that I am trying to fix and then make a pull request once the bug is fixed.