Open Design: Difference between revisions

m
formatting
m (formatting)
m (formatting)
Line 42: Line 42:
#* 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.  
#* 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 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.  
# '''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.


''Tips:''
''Tips:''
* If you need to stop in the middle of Steps 3-9 and start over later, it's a good idea to start over again at Step 3. This helps ensure that you don’t overwrite someone else’s change to the same file.
* If you need to stop in the middle of Steps 2-7 and start over later, it's a good idea to start over again at Step 2. This helps ensure that you don’t overwrite someone else’s change to the same file.
* For now, please don't use Github's fork or pull request functionality. As we’re all learning how to use Github, we want to stick to basic Github commands for now - clone, pull, commit, push.
* For now, please don't use Github's fork or pull request functionality. As we’re all learning how to use Github, we want to stick to basic Github commands for now - clone, pull, commit, push.
* Within the Github Desktop client, please don't use the ''Sync'' button, as well as the ''Publish/Unpublish'' options in the ''Branch'' menu. These do unexpected things that impact the remote repo.
* Within the Github Desktop client, please don't use the ''Sync'' button, as well as the ''Publish/Unpublish'' options in the ''Branch'' menu. These do unexpected things that impact the remote repo.
Confirmed users
195

edits