Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial![](https://ecs-static.teamtreehouse.com/assets/views/marketing/shared/community-banner-white-47072046c51352fe6a69f5e691ff5700b28bb11d45197d7bdf066d9ea3f72d0c.webp)
![Jerome vanGaalen](https://uploads.teamtreehouse.com/production/profile-photos/7993882/micro_IMG_2266__2_.jpg)
Jerome vanGaalen
18,941 PointsCan we do all of this directly from the github site?
Is it best practice to do this from your text editor? Can't we do all this directly from the github site?
1 Answer
![John Stratton](https://uploads.teamtreehouse.com/production/profile-photos/6766162/micro_76155999-5292-4BBA-AA6E-91BD156AD233.jpg)
John Stratton
18,726 PointsYou can do this directly from the GitHub website, but in production you will most likely need to use a text editor (and most have features and tools which aren't available through GitHub's online text editor), so it would be best practice to use your own text editor.
There are also gui's for using Git, but the command line is sometimes the only way you may be able to interface with Git in many situations.
Jerome vanGaalen
18,941 PointsJerome vanGaalen
18,941 PointsThanks John. I also figured this out after watching the conflict video a little later on.
John Stratton
18,726 PointsJohn Stratton
18,726 PointsYou're welcome!