Upgrade to Pro — share decks privately, control downloads, hide ads and more …

My GIT journey to contributing to Nextcloud

My GIT journey to contributing to Nextcloud

A lightening talk about navigating GIT and contributing to open source using the imagery of the Wizzard of Oz.

Jessica Greene

August 26, 2018
Tweet

More Decks by Jessica Greene

Other Decks in Technology

Transcript

  1. “Pay no attention to that man behind the curtain.” Useful

    GIT for contributing to Open Source Projects
  2. Issues good first issue $ git checkout –b vue-new-fix $

    git push --set-upstream origin experiment $ git merge origin/vue 113 OR Fork it $ git remote add <remote-name> https://github.com/user/repo.git
  3. $ git branch $ git remote -v $ git status

    $ git log “I don't know. But, some people without brains do an awful lot of talking, don't they?”
  4. $ git add <file-name> $ git commit –m ’commit message’

    $ git status $ git push “You people with hearts…have something to guide you, and need never do wrong.”
  5. $ git stash $ git commit --amend pop drop $

    git diff --staged “There's only one thing I want you guys to do. Talk me out of it.”
  6. $ git reset HEAD~ --soft $ git reset HEAD~ --hard

    $ git cherry-pick master $ git reset HEAD@{index} $ git reflog “Lions and tigers and bears, oh my!”
  7. git reset --soft HEAD~3 && git commit --edit -m"$(git log

    --format=%B --reverse HEAD..HEAD@{1})"
  8. Add a meaningful message and use keywords to link your

    PR to the issue it addresses #456 (close / closes / closed / fix / fixes / fixed / resolve / resolves / resolved)
  9. Add Reviewers Add Labels 2. developing 3. To review enhancement

    “I'll get you my pretty, and your little dog too!”
  10. They ask for some changes but overall they like your

    work! (YASS) “Because she wouldn't have believed me. She had to learn it for herself.”
  11. Congratulations you are now officially contributing to Nextcloud, a open

    source software ☺ “You don’t need to be helped any longer.”
  12. Don’t be afraid to ask lots of questions Commit often,

    with relative commit messages Make PRs and get reviews on your code If you make a mistake it can be reset, even if you pushed it, just let other contributors know!