├── pet-pics ├── Jasper.jpg ├── Pepper.png ├── agbar_kamar_photo_1.jpg └── photo-1548199973-03cce0bbc87b.jpeg ├── help-pages ├── assets │ └── styles │ │ └── layout.css ├── twitter-handles.html ├── index.html └── pull-requests.html ├── pet-pics.md ├── .gitignore └── README.md /pet-pics/Jasper.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kapunahelewong/git-playground/HEAD/pet-pics/Jasper.jpg -------------------------------------------------------------------------------- /pet-pics/Pepper.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kapunahelewong/git-playground/HEAD/pet-pics/Pepper.png -------------------------------------------------------------------------------- /pet-pics/agbar_kamar_photo_1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kapunahelewong/git-playground/HEAD/pet-pics/agbar_kamar_photo_1.jpg -------------------------------------------------------------------------------- /pet-pics/photo-1548199973-03cce0bbc87b.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/kapunahelewong/git-playground/HEAD/pet-pics/photo-1548199973-03cce0bbc87b.jpeg -------------------------------------------------------------------------------- /help-pages/assets/styles/layout.css: -------------------------------------------------------------------------------- 1 | hr { 2 | width: 80%; 3 | } 4 | 5 | nav { 6 | margin-bottom: 1em; 7 | } 8 | 9 | #page-content { 10 | padding: 1em 5%; 11 | } 12 | 13 | #navbarSupportedContent { 14 | justify-content: flex-end; 15 | } 16 | 17 | #navbarSupportedContent .navbar-nav { 18 | margin-right: 1em; 19 | } 20 | -------------------------------------------------------------------------------- /pet-pics.md: -------------------------------------------------------------------------------- 1 | # Share your pet pictures here 2 | 3 | This is my little old schnauzer, Pepper: 4 | ![Pepper](pet-pics/Pepper.png) 5 | 6 | --- 7 | 8 | [@danieljustus32](https://github.com/danieljustus32)'s partner in crime and eating, Jasper: 9 | ![Jasper](pet-pics/Jasper.jpg) 10 | This is my dog... 11 | ![Cachupin](pet-pics/agbar_kamar_photo_1.jpg) 12 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_STORE 2 | 3 | /dist/ 4 | /bazel-out 5 | /integration/bazel/bazel-* 6 | e2e_test.* 7 | node_modules 8 | tools/gulp-tasks/cldr/cldr-data/ 9 | 10 | # Include when developing application packages. 11 | pubspec.lock 12 | .c9 13 | .idea/ 14 | .devcontainer/* 15 | !.devcontainer/recommended-devcontainer.json 16 | !.devcontainer/recommended-Dockerfile 17 | .settings/ 18 | .vscode/launch.json 19 | .vscode/settings.json 20 | *.swo 21 | modules/.settings 22 | modules/.vscode 23 | .vimrc 24 | .nvimrc 25 | 26 | # Don't check in secret files 27 | *secret.js 28 | 29 | # Ignore npm/yarn debug log 30 | npm-debug.log 31 | yarn-error.log 32 | 33 | # build-analytics 34 | .build-analytics 35 | 36 | # rollup-test output 37 | /modules/rollup-test/dist/ 38 | 39 | # User specific bazel settings 40 | .bazelrc.user -------------------------------------------------------------------------------- /help-pages/twitter-handles.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | Twitter Handles 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 39 |
40 |

Add your twitter handle here

41 |
    42 |
  1. Mohammed Asker @mohdaasker
    2. 43 |
44 |
45 | 46 | -------------------------------------------------------------------------------- /help-pages/index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | Your last Pull Request 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 39 |
40 |

My first pull request (and not the last one)

41 | 42 |
43 | 44 |

This is me thinking about life after wasting 2 hours searching why git is not working and forgot to init git

45 |
46 | 47 |

Mohammed Asker, Oct 08 2019

48 |
49 | 61 | 62 | -------------------------------------------------------------------------------- /help-pages/pull-requests.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | Your first Pull Request 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 39 |
40 |

This is your first pull request

41 |
    42 |
  1. Fork this repo
    2. 43 |
  2. Clone this repo on your local
    3. 44 |
  3. Create a new branch
    4. 45 |
  4. In the new local branch make your changes
    5. 46 |
  5. Push your local changes to your forked repo
    6. 47 |
  6. Go to your github forked repo
    7. 48 |
  7. A Pull Request prompt will appear on your forked repo use it
    8. 49 |
50 | 51 | 54 |

Below this p tag there is another p tag with the name and date of the last author. Change it for your own.

55 |

Sam, July 29 2019

56 |
57 | 58 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Git and Github Playground 2 | 3 | This is a repo intended as a safe place to practice your git skills. You can do all kinds of things, such as: 4 | 5 | * Open an issue. 6 | * Respond to someone else's issue. 7 | * Open an issue just to close it. 8 | * Clone this repo. 9 | * Open a PR. 10 | * Leave comments on issues and PRs. 11 | * Make a number of commits on your computer, push them up to see them listed in your PR (assuming you've submitted one), try squashing them, rebasing, etc., and push up to see the results. 12 | * Open a PR just to close it. 13 | * Tag me for a review. 14 | * Submit a PR with a code of conduct, a story (keep it public domain, please), a picture (same thing about public domain), etc. 15 | * Maintain a fork and rebase it every once in a while. 16 | * Collaborate with someone. 17 | * Checkout the [issues](https://github.com/kapunahelewong/git-playground/issues) for more ideas on types of PRs to submit. 18 | * Open an issue with an idea! 19 | 20 | You don't have to submit code or anything technical. 21 | It can be just a note saying hi, or something as simple as a typo fix. Or hey, how about a typo for someone else to fix?! 😊 22 | 23 | ## Git Playground Spotlight 24 | 25 | When your PR is merged, you'll automatically appear in the [Git Playground Spotlight](https://cutiko.github.io/git-playground-spotlight/), as built by the most excellent @cutiko!🎉 26 | 27 | 28 | ## New 29 | 30 | Just added: Pet Pics! Add a photo of your favorite pet to the `pet-pics` folder and add it to the `pet-pics.md` file, following my example. I've started with my little dog, Pepper. Here's a preview! 31 | 32 | ![Pepper](pet-pics/Pepper.png) 33 | 34 | Look at her^^. She's serious about play, perfect for our Git Playground!! 35 | 36 | ## Code of conduct 37 | 38 | I'll start: 39 | 40 | * Be kind. <-seriously 41 | * Material must be your original work or public domain. 42 | * Anything that gets merged here falls under the GNU General Public License. 43 | 44 | We'll need more than this, but it's a start. 45 | 46 | Finally, **please keep PRs small and simple** — it's just me over here! 47 | 48 | **** 49 | 50 | ### Check out the first PR that was merged below! Woohoo! Thanks, @cutiko!!! 51 | 52 | ## Your first Pull Request 53 | Making your first Pull Request (PR) is exciting! Pull Requests are the way we all can collaborate to make a better open source ecosystem. For guidance on how to make your first PR: 54 | 55 | 1. Go to `pullrequests/` folder 56 | 2. Open the index.html file 57 | 3. Follow the instructions 58 | 59 | You are very close to making your name shine on the spotlight. You can do it! 60 | 61 | ## Adding Help Pages 62 | 63 | If you'd like to add a page with instructions for how to use a certain GitHub feature, à la `help-pages/pull-requests.html`, 64 | follow these steps: 65 | 66 | 1. Create a new `.html` file in the `help-pages` directory 67 | 2. Copy and paste the entire `` section into your new file 68 | 3. Copy and paste the `