Open Design: Difference between revisions

Jump to navigation Jump to search
19 bytes removed ,  16 October 2015
m
formatting
m (formatting)
m (formatting)
Line 38: Line 38:
#* If it doesn't say that, move (or copy) your changed files into your local repo.
#* If it doesn't say that, move (or copy) your changed files into your local repo.
# '''Describe your changes.'''
# '''Describe your changes.'''
# '''If it's not already highlighted, click the ''"XX uncommitted changes"'' tab.'''
#* If it's not already highlighted, click the ''"XX uncommitted changes"'' tab.
#* Type a descriptive summary of your changes in the Summary input field.  
#* Type a descriptive summary of your changes in the Summary input field.  
#* Add a description of the changes in the Description field. Describe the difference between your changes and the current versions on the remote Github repo. For example, you could copy your Change Log details into the Description field.  
#* Add a description in the Description field. Describe the difference between your changes and the current versions on the remote Github repo. For example, you could copy your Change Log details into the Description field.  
#* Note that the Summary and Description text are displayed in Github History, so other people can see what you’ve changed.
#* Note that the Summary and Description text are displayed in Github History, so other people can see what you’ve changed.
# '''Commit (save) your local repo.'''When you're satisfied that you've got all the changes you want included in the commit, and you’re satisfied with the Summary and Description, click "Commit to master." Your changes are now saved as a package in your local repo.  
# '''Commit (save) your local repo.'''When you're satisfied that you've got all the changes you want included in this commit, and you’re satisfied with the Summary and Description, click "Commit to master." Your changes are now saved as a package in your local repo.  
# Now go to ''Repository>Push.'' This immediately sends the package of changes to the remote Github repo and creates a new version for each changed file.
# Now go to ''Repository>Push.'' This immediately sends the package of changes to the remote Github repo and creates a new version for each changed file.
# You can confirm that your changes appear in the remote Github repo by visiting the remote repo on the web and browsing the folders where you expect to see the changed files.
# You can confirm that your changes appear in the remote Github repo by visiting the remote repo on the web and browsing the folders where you expect to see the changed files.
Confirmed users
195

edits

Navigation menu