#Git commands for creating a new article or updating an existing article Follow the steps in this article to create a local working branch on your computer so that you can create a new article for the technical documentation section of azure.microsoft.com or update an existing article.
- Start Git Bash (or the command-line tool you use for Git).
[AZURE.TIP] If you are working in the public repository, change azure-content-pr to azure-content in all the commands.
-
Change to azure-content-pr:
cd azure-content-pr
-
Check out the master branch:
git checkout master
-
Create a fresh local working branch derived from the master branch:
git pull upstream master:<working branch>
-
Move into the new working branch:
git checkout <working branch>
-
Let your fork know you created the local working branch:
git push origin <working branch>
-
Create your new article or make changes to an existing article.
-
Add and commit the changes you made:
git add . git commit –m "<comment>"
Or, to add only the specific files you modified:
git add <file path> git commit –m "<comment>"
-
Periodically, update your local working branch with changes from upstream:
git pull upstream master
-
Daily at least, push the changes to your fork on GitHub for safe keeping:
git push origin <working branch>
-
Stage the article if you wish; see GitHub commands for staging an article. (Internal contributors only)
-
When you are ready to publish the article live, create a pull request that moves your changes from the working branch in your fork to the master branch of the upstream repository.
-
The pull request acceptor reviews and accepts your pull request.
-
Review your content at
http://azure.microsoft.com/documentation/articles/*name-of-your-article-without-the-MD-extension*
At this time, technical articles are published once daily around 10 AM Pacific Standard Time (PST), Monday-Friday. Remember, your pull request has to be accepted before changes are included in the next scheduled publishing run.