1. <em id="lgh8k"><acronym id="lgh8k"><u id="lgh8k"></u></acronym></em>

      2. <span id="lgh8k"></span>
        <span id="lgh8k"></span>
          <em id="lgh8k"><acronym id="lgh8k"><input id="lgh8k"></input></acronym></em>

          Pushing patches back to CoApp website

          Version:1.0



          Requirements:

          You need to make sure that you've forked and checked out the CoApp website, and you've modified the website content.

          Pushing changes to your fork

          So, you've modified the website and you've locally committed these modifications to your fork of the CoApp website source code:

          c:\project\>cd www.ustasia.com
          c:\project\www.ustasia.com\>git commit -m "Updated developers.html with..." src\dynamic\pages\developers.html.md.ejs
          

          It is a good idea to get recent updates from the project upstream:

          c:\project\www.ustasia.com\>git fetch upstream
          c:\project\www.ustasia.com\>git merge upstream/master
          

          Typically, you want to push all the updates to your fork of the CoApp website project at GitHub:

          c:\project\www.ustasia.com\>git push origin master
          

          Now, you have pushed your changes to your fork of the CoApp website repository (upstream).

          Submitting your changes to the upstream

          As you've learned by the way of forking and checking out the CoApp website, collaborative development of the CoApp project is based on the Fork + Pull Model defined by GitHub.

          In order to contribute your modifications to the mainstream, you need to generate and send pull request to the CoApp website team.

          Simply, follow the Send pull requests guide at GitHub.


            湖南红中麻将