Built with Jekyll and Bootstrap 4
Note: we used github pages during site construction, that is being discontinued henceforth (since deployment to permanent server) due to issues with baseurl and _config.yml
bundle exec jekyll serve. See jekyll docs for more details.
As of now, we're employing a very rudimentary deployment system, essentially scp-ing the built site into the server.
The basic steps are highlighted hence:
git clone email@example.com:you/MuseScore.git)
git remote add upstream git://github.com/musescore/MuseScore.git) (for forks)
git checkout -b 404-new-feature)
git add . ; git commit -m 'commit message')
git fetch upstream) (for those with master access, fetch origin)
git checkout master; git merge upstream/master)
git checkout 404-new-feature; git rebase master)
git push origin 404-new-feature)
After having made a Pull Request don't pull/merge anymore, it'll mess up the commit history. If you (have to) rebase, use 'push --force' (
git push --force) to send it up to your GitHub repository, this will update the PR too. Be careful not to do this while the core team is working on merging in your PR.
// Reference: http://lea.verou.me/2011/10/easily-keep-gh-pages-in-sync-with-master/ $ git add . $ git status // to see what changes are going to be commited $ git commit -m 'Some descriptive commit message' $ git push origin master $ git checkout gh-pages // go to the gh-pages branch $ git rebase master // bring gh-pages up to date with master $ git push origin gh-pages // commit the changes $ git checkout master // return to the master branch
Main changes are incorporated from branches into master, then into gh-pages. Ideally.