Handling multiple distribution methods with a git repo -



Handling multiple distribution methods with a git repo -

i've been co-working on browser puzzle based game using html, js , css, , uses git source control. can run game using index.html of coarse , hosted on server soon.

lately i've been thinking creating chrome app version/package of project can distribute on chrome web store too. , consider other markets soon. require additional files added git repo, specific chrome-app version of repo. along minor code changes allow total integration within chrome.

would improve create fork of original repo , handle chrome-app files there. original/plain game separate chrome-app port? or considering minor code changes required, totally separate git repo improve , manually re-create updates between repos?

i think there few ways go managing product lines, depending on comfort level managing repos, branches, tags etc.

one way create new chrome-app repo, , introduce original (maybe phone call baseline) repo submodule in chrome-app repo. if using github, can like:

git submodule add together https://github.com/<username>/<baseline>.git

if decided utilize submodules, should familiarize commands git submodule init , git submodule update. can utilize git merge , git fetch merge in new changes upstream baseline repo, , git force --recurse-submodules publish changes baseline.

alternately, if felt overkill, can fork original repo, create chrome-app repo. since owners of these repos, should easy sync them using git push , git pull.

and if much, (for little projects) can branch off master of original repo, , maintain in 1 repo.

git

Comments

Popular posts from this blog

formatting - SAS SQL Datepart function returning odd values -

c++ - Apple Mach-O Linker Error(Duplicate Symbols For Architecture armv7) -

php - Yii 2: Unable to find a class into the extension 'yii2-admin' -