├── CONTRIBUTING.md ├── LICENSE └── README.md /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Contributing to This Project (and Others) 4 | 5 | New to GitHub? No problem! You're in the right place! 6 | 7 | Fork this repo by clicking on the `Fork` button on the top right of this page. 8 | 9 | ![image](https://user-images.githubusercontent.com/36825567/131013036-a7874694-3256-4e0e-87e8-13dc1d402b31.png) 10 | 11 | After that, you'll be working off of your Fork of this repository, which is effectively a snapshop in time. Here, you will have a copy of this repo and you can modify it to your heart's content. Once done, you can do a Pull Request to propose changes to this main repo so everyone else can benefit from your contributions. With this repo, it's purely for practice, so don't worry about solving the world's problems on this repo. 12 | 13 | ![image](https://user-images.githubusercontent.com/36825567/131013270-7c991c8d-d1b9-4f84-8c3d-9ef20a8d86e4.png) 14 | 15 | As time goes on, this repository will evolve and your Fork will be left behind if you don't keep it updated. Remember, it is a snapshot in time. Be sure to Fetch Upstream prior contributing more so you have the most up to date copy of the repository before you starting adding to it! 16 | 17 | ![GitHubFetchandMergeandContributeExample](https://user-images.githubusercontent.com/36825567/131013496-8b547597-8e97-443e-88bb-ce75501f07c9.gif) 18 | 19 | Above is an example of Fetch Upstream combined with doing a Pull Request, which is what you should do when you have something new to the repo you'd like to add to the main repo. Ideally, Fetch Upstream -> make your changes -> do a PR to the main repo. Then, you wait for the Owner/Collaborator to approve/deny/request changes to your PR. 20 | 21 | ### New to Markdown? No problem! 22 | 23 | * Use [StackEdit](https://stackedit.io/app#) to write in Markdown with live preview. 24 | * Additionally, GitHub has a useful guide for Markdown syntax [here](https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). 25 | * Need help with making/using tables in Markdown? Check out this [site](https://www.tablesgenerator.com/markdown_tables)! 26 | 27 | 28 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2021 Digital Forensics Discord Server 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # GitHubLearningPlayground 2 | 3 | Fork this repo! Do a Pull Request! As many times as you want! Learn the ins and outs of how to contribute to GitHub! Make your mistakes here before you make them elsewhere more public! 4 | 5 | Please check out [CONTRIBUTING.md](https://github.com/Digital-Forensics-Discord-Server/GitHubLearningPlayground/blob/main/CONTRIBUTING.md) for guidance on how to contribute to this repo. `.md` is simply a Markdown file, meaning the syntax used is Markdown! 6 | 7 | 8 | # Test 9 | 10 | 11 | Toy around with Markdown [here](https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)! 12 | 13 | asdfasdfasdf 14 | 15 | # spelling errors go here 16 | 17 | Hey there, how are you doing? Bababooey. 18 | 19 | Why can't I spell? 20 | 21 | hey there how are you doing? 22 | i'm doing pretty good how are you! 23 | 24 | eye am dooing well, than kyou 25 | I'm doing well thanks! 26 | 27 | one more test addition 28 | 29 | (please correct these spelling errors and PR the corrections, for practice! be sure to leave new spelling errors for the next person!) 30 | 31 | # next section 32 | 33 | test 34 | correct only one of the below, then do a PR! rinse and repeat 35 | 36 | please fix this spelling error 37 | 38 | please fix this spelling error - this one has been corrected 2/3/2022 39 | 40 | plz fixx this spelling error 41 | 42 | please fix thhis spelling error 43 | 44 | please fix this spelling errororor 45 | 46 | I don't want to fix this. 47 | 48 | # let's practice bullet lists 49 | 50 | * text goes here that you want bulleted 51 | * go to the end of this line and hit the enter button. then, start typing text you want bulleted! 52 | * bullet1 53 | * bullet2 54 | * bullet3 55 | 56 | ## test 57 | 58 | * bullet list 59 | * bullet list 60 | * blah 61 | * test 62 | * hello 63 | 64 | # let's practice numbered lists 65 | 66 | 1. same deal as above, kids 67 | 2. rinse and repeat 68 | 3. I don't care 69 | 4. I don't know 70 | 71 | ### test header 72 | 73 | ## First? 74 | 75 | Adding more text here so your fork falls behind. Be sure to Fetch Upstream! - This is one commit 76 | 77 | More text being added here. - This is a separate commit from the one above. 78 | 79 | You can do as much or as little as you want within a commit. Organize it how you want. Whether it's a simple spelling error or 1000 lines of code or markdown or whatever, it doesn't matter. Commit as much as you want and then do a PR when you're ready to merge into this repo! 80 | 81 | ### Second 82 | Think I got the hang of it :) 83 | 84 | ### Fifteenth 85 | 86 | ## Third 87 | 88 | Increment the following number by one, for each commit: 0001 89 | 90 | --------------------------------------------------------------------------------