This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
git [2025/06/18 20:40] – cherin | git [2025/06/26 22:06] (current) – admin | ||
---|---|---|---|
Line 3: | Line 3: | ||
====== What is Git? ====== | ====== What is Git? ====== | ||
- | Git is a powerful system | + | Git is a powerful |
Here's how it works: Let's say you're working on a report called quarterly-report.docx. When you first save it with Git, it stores that version permanently. Make changes next week? Git saves that new version too, while still keeping the old one. Need to go back to how things were two weeks ago? Git makes that simple. | Here's how it works: Let's say you're working on a report called quarterly-report.docx. When you first save it with Git, it stores that version permanently. Make changes next week? Git saves that new version too, while still keeping the old one. Need to go back to how things were two weeks ago? Git makes that simple. | ||
Line 9: | Line 9: | ||
Think of Git as a safety net for your files. It gives you the confidence to make changes, knowing you can always get back to any earlier version if something goes wrong. | Think of Git as a safety net for your files. It gives you the confidence to make changes, knowing you can always get back to any earlier version if something goes wrong. | ||
- | The challenge is that Git can be complex to use directly. | + | //Git// can be complex to use directly. |
- | * Undo any change: Accidentally deleted something important? Get it back instantly | + | |
- | * See exactly what changed: Compare today' | + | * See commit history: View all previous versions |
- | * Never lose work: Every version of your files is saved permanently | + | * Never lose work: Every version of your files is saved permanently |
- | * Work with confidence: Make bold changes knowing you can always go back | + | * Work with confidence: Make bold changes knowing you can always go back |
- | You don't need to learn Git commands | + | The entire list of [[/ |
+ | |||
+ | You don't need to learn complex | ||
====== What is Git Hosting? ====== | ====== What is Git Hosting? ====== | ||
Line 22: | Line 24: | ||
Now imagine your team is spread across different offices, or some people work from home. How do you all work on the same files without stepping on each other' | Now imagine your team is spread across different offices, or some people work from home. How do you all work on the same files without stepping on each other' | ||
- | Git hosting is like having a shared online workspace where your project files live. Everyone | + | Git hosting is like having a shared online workspace where your project files live. It's a service that stores your Git repositories |
- | It' | + | Git hosting is different from cloud storage services like Google Drive or Dropbox in important ways. While cloud storage |
- | + | ||
- | Popular Git hosting services include GitHub, GitLab, and Gitea. Think of these like choosing between | + | |
These services help teams by: | These services help teams by: | ||
- | * Making it easy to share files with the right people | + | |
- | * Showing exactly who changed what and when they changed it | + | * Showing exactly who changed what and when they changed it |
- | * Combining everyone' | + | * Keeping a complete history of all changes made to files |
+ | * Providing secure access controls for different team members | ||
+ | |||
+ | However, setting up and managing Git hosting can be technical and overwhelming for many teams. You need to understand Git commands, repository management, and often deal with complex workflows involving branches, merges, and conflict resolution. | ||
+ | |||
+ | This is where **Git Winch** shines - it connects seamlessly to any of these hosting services while hiding all the technical complexity. **Git Winch** prevents conflicts by soft-locking files when someone starts editing them. Other team members are notified and cannot | ||
- | However, setting up and managing Git hosting can be technical and overwhelming for many teams. This is where **Git Winch** shines — it connects seamlessly to any of these hosting services while hiding all the technical complexity. Your team gets all the benefits of professional Git hosting without anyone needing to become a Git expert. | ||
====== What is a Repository? ====== | ====== What is a Repository? ====== | ||
Line 55: | Line 59: | ||
**Permission Levels:** You can give team members one of two access levels: | **Permission Levels:** You can give team members one of two access levels: | ||
- | * Pull only: They can download and view files but cannot make changes or send updates back | + | |
- | * Push and pull: They can download files, make changes, and send their updates back to the repository | + | * Push and pull: They can download files, make changes, and send their updates back to the repository |
**Daily Workflow:** Here's what a typical day looks like: | **Daily Workflow:** Here's what a typical day looks like: | ||
- | 1. Team members open **Git Winch** and download the latest versions of project files | + | * Team members open **Git Winch** and download the latest versions of project files |
- | 2. They make their changes or add new files as needed | + | |
- | 3. When ready, they send their updates back to the main project through Git Winch | + | |
- | 4. Everyone else can then get these updates the next time they sync | + | |
**The Big Advantage: | **The Big Advantage: |