├── .gitignore ├── README.md ├── TryChanges ├── exercises ├── 1_helloworld.md ├── 2_branches.md ├── 3_forking.md └── 4_pages.md ├── playground ├── 7-principles-cdt.md ├── agile-manifesto.md ├── historyQuip.md ├── jabberwocky.md ├── jptest.md └── playground_changes.md └── references ├── README.md ├── git_cheat_sheet.pdf ├── github-git-cheat-sheet.pdf └── github-page-examples.md /.gitignore: -------------------------------------------------------------------------------- 1 | *.xml 2 | *.lock 3 | *.swp 4 | .DS_Store 5 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Contributing to GitHub is For You 2 | 3 | Contributing to GitHub is for You Workshop 4 | by [Chris Kenst](http://www.kenst.com/about) 5 | 6 | Presented to the [DAQAA](https://www.daqaa.com/) meet-up on April 11th, 2018. 7 | 8 | ## Pre-requisites: 9 | 10 | 1. Have your own laptop 11 | 2. Sign up for your own GitHub account: https://github.com/ 12 | 3. Star this repo! 13 | 4. Configure / install Git version control: https://git-scm.com/downloads 14 | - For macOS install Xcode from the App Store and enable Git / Command line tools 15 | - We won't use GitHub desktop, but feel free to install and play around 16 | 5. Have a good text editor 17 | - I use and recommend [Atom](https://atom.io/) 18 | - I also tend to like [Sublime Text](https://www.sublimetext.com/) 19 | 20 | 21 | ## Slides 22 | 23 | - [Presentation](https://docs.google.com/presentation/d/19TeJeCsANL2O0nGZw-hiqy6mAZYq7eKw0UEIZhezKl4/edit?usp=sharing) 24 | - My contact information is in the slides and also available at the bottom of [this](http://www.kenst.com/about) page. 25 | -------------------------------------------------------------------------------- /TryChanges: -------------------------------------------------------------------------------- 1 | Write some content inside 2 | -------------------------------------------------------------------------------- /exercises/1_helloworld.md: -------------------------------------------------------------------------------- 1 | # Exercise 1, Hello World 2 | 3 | > Hello world is often the first program you build when learning to program. You simply program the computer to output a line of text called "Hell World" 4 | 5 | This first exercise is the simplest in the git workflow: change, commit, deploy. You have a repository on GitHub that you'd like to work on locally. Make a few updates and then push those changes back to GitHub. 6 | 7 | Objectives: 8 | 1. Create a repository on GitHub 9 | 2. Clone directory to your local environment 10 | 3. Make some changes and then publish those changes back to GitHub on the master branch 11 | -------------------------------------------------------------------------------- /exercises/2_branches.md: -------------------------------------------------------------------------------- 1 | # Exercise 2, Branches Galore 2 | 3 | This second exercise is the foundation of the GitHub workflow: branch, commit, pull request, merge, deploy. You can do all of this in your existing repository. 4 | 5 | Objectives: 6 | 1. Create a new branch (in your local repository) e.g. `readme-edits` 7 | 2. Make some changes, commit and push those changes 8 | 3. Open a Pull Request 9 | 4. Merge the Pull Request back into the master branch 10 | -------------------------------------------------------------------------------- /exercises/3_forking.md: -------------------------------------------------------------------------------- 1 | # Exercise 3, Use Your Fork Please 2 | 3 | In this third exercise we're going to fork an existing repository, go through the GitHub workflow and open a pull in a repository we don't control. 4 | 5 | Objectives: 6 | 1. Fork /this/ repository 7 | 2. Make a branch, make a change to the playground directory and commit it 8 | 3. Open a Pull Request 9 | 4. Wait... Your Pull Request is being reviewed 10 | -------------------------------------------------------------------------------- /exercises/4_pages.md: -------------------------------------------------------------------------------- 1 | # Exercise 4, Capstone 2 | 3 | In this fourth and final exercise we're going to combine everything we've learned so far by creating a website using GitHub Pages. 4 | 5 | Objectives: 6 | 1. Create a website using GitHub Pages. 7 | 2. Create a branch and start adding details to your website. 8 | 3. Using the existing GitHub workflow, make changes, push commits, and when you are ready to deploy your changes to production, open a Pull Request and merge it in. 9 | -------------------------------------------------------------------------------- /playground/7-principles-cdt.md: -------------------------------------------------------------------------------- 1 | # The Seven Basic Principles of the Context-Driven School 2 | 3 | *Principles* 4 | 5 | 1. The value of any practice depends on its context. 6 | 2. There are good practices in context, but there are no best practices. 7 | 3. People, working together, are the most important part of any project’s context. 8 | 4. Projects unfold over time in ways that are often not predictable. 9 | 5. The product is a solution. If the problem isn’t solved, the product doesn’t work. 10 | 6. Good software testing is a challenging intellectual process. 11 | 7. Only through judgment and skill, exercised cooperatively throughout the entire project, are we able to do the right things at the right times to effectively test our products. 12 | 13 | [link](http://context-driven-testing.com) 14 | 15 | ## Maha 16 | These are seven great principles *** 17 | 18 | -------------------------------------------------------------------------------- /playground/agile-manifesto.md: -------------------------------------------------------------------------------- 1 | # Manifesto for Agile Software Development 2 | 3 | We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: 4 | 5 | - Individuals and interactions over processes and tools 6 | - Working software over comprehensive documentation 7 | - Having PB&J bar on Thursdays 8 | - Customer collaboration over contract negotiation 9 | - Responding to change over following a plan 10 | 11 | That is, while there is value in the items on the right, we value the items on the left more. 12 | 13 | [link](http://agilemanifesto.org) 14 | 15 | 16 | I am signing this... Jeremy Sims. -------------------------------------------------------------------------------- /playground/historyQuip.md: -------------------------------------------------------------------------------- 1 | "History may not repeat itself, but it often rhymes" -------------------------------------------------------------------------------- /playground/jabberwocky.md: -------------------------------------------------------------------------------- 1 | [Jabberwocky](https://www.poetryfoundation.org/poems/42916/jabberwocky) 2 | BY LEWIS CARROLL 3 | 4 | ’Twas brillig, and the slithy toves 5 | Did gyre and gimble in the wabe: 6 | All mimsy were the borogoves, 7 | And the mome raths outgrabe. 8 | 9 | “Beware the Jabberwock, my son! 10 | The jaws that bite, the claws that catch! 11 | Beware the Jubjub bird, and shun 12 | The frumious Bandersnatch!” 13 | 14 | He took his vorpal sword in hand; 15 | Long time the manxome foe he sought— 16 | So rested he by the Tumtum tree 17 | And stood awhile in thought. 18 | 19 | And, as in uffish thought he stood, 20 | The Jabberwock, with eyes of flame, 21 | Came whiffling through the tulgey wood, 22 | And burbled as it came! 23 | 24 | One, two! One, two! And through and through 25 | The vorpal blade went SNICKER-SNACK! 26 | He left it dead, and with its head 27 | He went galumphing back. 28 | 29 | “And hast thou slain the Jabberwock? 30 | Come to my arms, my beamish boy! 31 | O frabjous day! Callooh! Callay!” 32 | He chortled in his joy. 33 | 34 | ’Twas brillig, and the slithy toves 35 | Did gyre and gimble in the wabe: 36 | All mimsy were the borogoves, 37 | And the mome raths outgrabe. 38 | 39 | 40 | Lewis Carol knew there was some scary stuff out there that no one understands but it's still harmful. He was woke son!! 41 | 42 | TESTING 43 | 44 | Twas a dark and stormy night 45 | 46 | "I NEED A PIG!" 47 | "wee baby jabberwocky" -------------------------------------------------------------------------------- /playground/jptest.md: -------------------------------------------------------------------------------- 1 | JP New Test -------------------------------------------------------------------------------- /playground/playground_changes.md: -------------------------------------------------------------------------------- 1 | playground changes! -------------------------------------------------------------------------------- /references/README.md: -------------------------------------------------------------------------------- 1 | # References: 2 | 3 | A few references you might find useful: 4 | 5 | 1. [Shortcuts for navigating the command line](https://clementc.github.io/blog/2018/01/25/moving_cli/) 6 | 2. [GitHub Desktop for visualizing changes](https://desktop.github.com/) 7 | 3. [Git Book]( https://git-scm.com/book/en/v2/) 8 | 4. [tryGit: Git Challenges from GitHub + CodeSchool (aka an interactive training program)](https://try.github.io/levels/1/challenges/1) 9 | 5. [Git Handbook](https://guides.github.com/introduction/git-handbook/) 10 | 6. [9 GitHub Lists for Testing](http://www.kenst.com/2017/05/9-github-lists-for-testing/) 11 | 7. [18 GitHub Projects for Testing](http://www.kenst.com/2017/05/18-github-projects-for-testing/) 12 | 8. [Practice Using Selenium Now](https://www.kenst.com/2017/01/practice-using-selenium-now/) 13 | 14 | 15 | Also see [GitHub Page Examples](github-page-examples.md) 16 | 17 | ## GitHub Projects to contribute to: 18 | 19 | > Many of these projects have labels for first time submitters. Using these labels will get you better responses from the project’s members 20 | 21 | - [TestingConferences.org](http://testingconferences.org/) - A simple list of software testing conferences and workshops published collaboratively with the testing community. 22 | - [Tech Community Slacks](https://github.com/ladyleet/tech-community-slacks) - This is a list of tech community Slack teams, organized by region. If your group has a Slack team, you can add it here. 23 | - [Wordpress.com Desktop App](https://github.com/Automattic/wp-calypso) 24 | - Babel, Node / NPM, Rails 25 | -------------------------------------------------------------------------------- /references/git_cheat_sheet.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ckenst/githubforyou-workshop/0631113f7c7015282c4ea06e30eda1657474fccd/references/git_cheat_sheet.pdf -------------------------------------------------------------------------------- /references/github-git-cheat-sheet.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/ckenst/githubforyou-workshop/0631113f7c7015282c4ea06e30eda1657474fccd/references/github-git-cheat-sheet.pdf -------------------------------------------------------------------------------- /references/github-page-examples.md: -------------------------------------------------------------------------------- 1 | # GitHub Page templates and examples 2 | 3 | 4 | ## Websites: 5 | 6 | - https://github.com/diemol/diemol.github.io 7 | - Original template: https://github.com/mmistakes/so-simple-theme 8 | 9 | - https://github.com/connor/connor.github.io 10 | - My own version: http://www.cken.st/ 11 | 12 | - https://github.com/TestingConferences/testingconferences.github.io 13 | 14 | - https://github.com/dsmwebcollective/dsmwebcollective.github.io 15 | 16 | - http://h313.info/ 17 | - https://github.com/h313/h313.github.io 18 | 19 | - http://olivierlacan.com/ 20 | - http://jonallured.com/ 21 | 22 | ## Blogs: 23 | 24 | - https://github.com/benbalter/benbalter.github.com 25 | 26 | - http://tom.preston-werner.com/ 27 | - https://github.com/mojombo 28 | 29 | - https://www.richgrundy.com/ 30 | - https://github.com/RichGuk/richguk.github.io 31 | 32 | - https://github.com/FriendlyTester/friendlytester.github.io 33 | - https://github.com/barryclark/jekyll-now 34 | 35 | 36 | ## More examples: 37 | - https://github.com/jekyll/jekyll/wiki/Sites 38 | --------------------------------------------------------------------------------