Git is a powerful system that tracks changes to files over time, acting like a super-powered “Save” button that remembers every version of your files forever.

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.

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. That's exactly why Git Winch exists — to give you all of Git's powerful benefits without the complexity. With Git Winch, you get:

• Undo any change: Accidentally deleted something important? Get it back instantly
• Never lose work: Every version of your files is saved permanently
• Work with confidence: Make bold changes knowing you can always go back

You don't need to learn complex Git commands or technical details. Git Winch handles all the complicated parts, so you can focus on your work instead of worrying about technology.

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's toes or losing track of changes?

Git hosting is like having a shared online workspace where your project files live. Everyone on your team can access these files, but here's the clever part: Git Winch prevents conflicts by soft-locking files when someone starts editing them. Other team members are notified and cannot edit that file until the person finishes and sends their changes back.

It's different from cloud storage services like Google Drive or Dropbox in important ways. While those services share files easily, they don't prevent people from accidentally overwriting each other's work. Git hosting ensures everyone works on their own copy first, then safely combines changes together. Plus, it gives you complete control over who can access which files and what they can do with them.

Popular Git hosting services include GitHub, GitLab, and Gitea. Think of these like choosing between different banks to keep your money safe — they all do the same basic job, but with different features and interfaces.

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 * Combining everyone's work together safely, even when multiple people edit the same files

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.

A repository (or “repo” for short) is like a dedicated filing cabinet for one specific project. Just as you might have separate filing cabinets for different clients or departments, you create separate repositories for different projects.

For example, you might have: * One repository for your marketing materials * Another for your quarterly reports * A third for your employee handbook

Each repository contains all the files, documents, images, and other materials related to that specific project. This keeps everything organized and makes it easy to control who has access to what.

Only the people who need to work on a particular project get access to its repository. This keeps your sensitive files secure and prevents confusion about which files belong to which project.

Here's how it works step-by-step:

Getting Started: The team leader creates a repository on a service like GitHub, GitLab, or Gitea — think of this as setting up your shared workspace. They then decide who gets access and what level of permission each person needs.

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

Daily Workflow: Here's what a typical day looks like:

• Team members open Git Winch and download the latest versions of project files
• They make their changes or add new files as needed
• When ready, they send their updates back to the main project through Git Winch
• Everyone else can then get these updates the next time they sync

The Big Advantage: Only the team leader needs an account on GitHub, GitLab, or Gitea. Everyone else just needs Git Winch. This eliminates the hassle of managing multiple accounts and keeps costs down.

Real-World Example: Sarah manages a client proposal. She creates a repository and gives her team access. John downloads the files and starts working on the budget spreadsheet — Git Winch locks this file so no one else can edit it at the same time. Meanwhile, Lisa adds new graphics to the presentation (which isn't locked since John isn't using it). When John finishes and sends his updates back to the repository, the lock is released and others can now work on that spreadsheet. Sarah can see all changes, review them, and everyone gets the updated files. If something goes wrong, they can always go back to yesterday's version.

This makes Git Winch perfect for small offices and teams who want professional file management without needing to become technology experts.

Learn the concepts | Table of Contents