Moved files around

Author: Sidney Andrews

.gitignore

@@ -0,0 +1,63 @@
+### Jekyll ###
+_site/
+.sass-cache/
+.jekyll-cache/
+.jekyll-metadata
+
+### Ruby ###
+*.gem
+*.rbc
+/.config
+/coverage/
+/InstalledFiles
+/pkg/
+/spec/reports/
+/spec/examples.txt
+/test/tmp/
+/test/version_tmp/
+/tmp/
+
+# Used by dotenv library to load environment variables.
+# .env
+
+# Ignore Byebug command history file.
+.byebug_history
+
+## Specific to RubyMotion:
+.dat*
+.repl_history
+build/
+*.bridgesupport
+build-iPhoneOS/
+build-iPhoneSimulator/
+
+## Specific to RubyMotion (use of CocoaPods):
+#
+# We recommend against adding the Pods directory to your .gitignore. However
+# you should judge for yourself, the pros and cons are mentioned at:
+# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
+# vendor/Pods/
+
+## Documentation cache and generated files:
+/.yardoc/
+/_yardoc/
+/doc/
+/rdoc/
+
+## Environment normalization:
+/.bundle/
+/vendor/bundle
+/lib/bundler/man/
+
+# for a library or gem, you might want to ignore these files since the code is
+# intended to run in multiple environments; otherwise, check them in:
+# Gemfile.lock
+# .ruby-version
+# .ruby-gemset
+
+# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
+.rvmrc
+
+# ignore Gemfile
+Gemfile
+Gemfile.lock

collaboration.md

@@ -0,0 +1,13 @@
+# Receiving update notifications, suggesting changes, and collaborating on projects
+
+You can configure your GitHub experience so that you receive notifications when updates occur to a GitHub repo. There are several ways in which you can sign up for notifications, and many of them relate to the many ways that you can collaborate on a project. To receive notifications, you can:
+
+| Action | Description |
+| --- | --- |
+| [Watch repositories](watching/) | When you watch a repository, GitHub subscribes you automatically to notifications for any new pull requests or issues that are created for that specific repository. You automatically watch any repository that you create or for which you are a collaborator. |
+| [Pull request](pullrequest/) | When you create a pull request, and propose that the owners of a repo accept a change that you make, you automatically subscribe to receive notifications for the related discussion about the pull request. In order to create a Pull request you must first create a branch. |
+| [Comments](comment/) | When you make comments about another person’s pull request, GitHub subscribes you automatically to the forum that pertains to that comment, or you can subscribe to the forum manually. |
+| [Issues](issue/) | An issue is a suggestion, question, or request that pertains to a repository. Each issue has its own discussion, and you can subscribe to issues, or GitHub subscribes you automatically to issues that you create. |
+| [Mentions](mention/) | When another user mentions you in a conversation, using your GitHub user name (@username), GitHub subscribes you automatically to the discussion. |
+
+> **Note**: You can modify how and when you receive notifications, and you also can unsubscribe to any or all discussions.

comment.md renamed to collaboration/comment/index.md

@@ -16,8 +16,8 @@ GitHub should not be used to discuss technical content in the course, or how to
 
 ## Sections
 
-- [GitHub Terminology](terminology.md)
+- [GitHub Terminology](terminology/)
 
-- [Microsoft Learning's GitHub solution for course labs](solution.md)
+- [Microsoft Learning's GitHub solution for course labs](solution/)
 
-- [Receiving update notifications, suggesting changes, and collaborating on projects](collaboration.md)
+- [Receiving update notifications, suggesting changes, and collaborating on projects](collaboration/)