Your SlideShare is downloading. ×
0
WordCamp Asheville 2014: WordPress and Git
WordCamp Asheville 2014: WordPress and Git
WordCamp Asheville 2014: WordPress and Git
WordCamp Asheville 2014: WordPress and Git
WordCamp Asheville 2014: WordPress and Git
WordCamp Asheville 2014: WordPress and Git
WordCamp Asheville 2014: WordPress and Git
WordCamp Asheville 2014: WordPress and Git
WordCamp Asheville 2014: WordPress and Git
WordCamp Asheville 2014: WordPress and Git
WordCamp Asheville 2014: WordPress and Git
WordCamp Asheville 2014: WordPress and Git
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

WordCamp Asheville 2014: WordPress and Git

290

Published on

WordPress and Git by Evan Volgas. Presented at WordCamp Asheville 2014

WordPress and Git by Evan Volgas. Presented at WordCamp Asheville 2014

Published in: Internet
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
290
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. WordPress and Git Evan Volgas @EvanVolgas || evan.is
  • 2. AKA the Least Tweetable WordCamp Presentation Ever (No, seriously)
  • 3. Random Tweet Suggestions • Making WordPress development less painful with git-whiksey and deadlines-ignore #wcavl • Learning the top ten git commands to make men/women fall in love with you #wcavl • Brain fart to WordPress website in 13 seconds with Git and Miracle.js #wcavl
  • 4. What is Git?
  • 5. Some assumptions that I’ll be making today • Google Exists • You know how to use it • You don’t need to tell me how to do something you can Google • You probably think slides full of code are boring • Really what you need to know is how to use Git (and get your team to use Git) in a way that actually saves you time
  • 6. So…. what the heck are we going to talk about today? • The lazy Git workflow that you won’t find on Google (maybe with good reason…???) • Some other workflows you probably should know abut • Git tools • Ignoring things • Applications for Git that you maybe haven’t considered yet
  • 7. Tools for using Git • For Git Hosting: BitBucket, Beanstalk, Github, Gitorious, others • Git GUIs: Tower, Github for Windows/Mac, git-cola, others • Diff management: Meld, Kaleidoscope, DiffMerge, others • Text Editors: Atom, plugins for Coda/Sublime/Etc • Special mention: Dploy.io, Capistrano, others
  • 8. Key Concepts • git remote and git hooks (or Github Web hooks): This is how you push stuff from your Git repo to your production site • branching • merging • pulling • pushing
  • 9. Hi. Ignore me. • gitignore: Tells Git to ignore certain things • Default gitignore for WordPress: https://github.com/github/gitignore/blob/master/Word Press.gitignore • You might want to add .DS_STORE on Mac • (If you use Windows, you might want to stop using Windows) • (If you use Linux, rock on)
  • 10. A lazy workflow (that you might actually use) # Ignore everything in the root except the "wp-content" directory. /* #Except the stuff I want to keep !.gitignore !/wp-content/ !/wp-content/themes/ !/wp-content/themes/* /wp-content/themes/evanis/screenshot.png /wp-content/themes/evanis/README.txt /wp-content/themes/evanis/images /wp-content/themes/evanis/languages /wp-content/themes/evanis/xml .DS_Store
  • 11. Workflows, applications, and discussion • Centralized: Everyone can push to master (just keep your local current) • Feature-based: Everyone branches off of master and issues pull requests for their branches (again, keep your local current. There are also very specific methods of doing this that focus on development branches, release candidates, etc) • Fork-based: Everyone forks the main and issues pull requests to the official repo

×