This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
git [2025/06/18 19:18] – cherin | git [2025/06/19 11:01] (current) – cherin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ======Git and Git Hosting====== | + | ====== Git and Git Hosting ====== |
====== What is Git? ====== | ====== What is Git? ====== | ||
- | Git is a smart tool that helps you keep track of changes to your files over time. Think of it like a special version of " | + | Git is a powerful system |
- | You don’t have to use Git directly — tools like **Git Winch** do the hard work for you behind the scenes. But here’s what Git does: | + | 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 |
- | Let’s say you’re working on a report. You create a file called `report.docx`. Git won’t store it yet — that only happens when you tell it to. Once you do, Git saves that version forever. If you make changes | + | Think of Git as a safety net for your files. It gives you the confidence |
- | So, Git is like a safety net for your files. It helps you work with confidence, knowing | + | The challenge |
- | And best of all, you don’t need to know how Git works to benefit from it. Just use **Git Winch**, | + | * Undo any change: Accidentally deleted something important? Get it back instantly |
+ | * See commit history: View all previous versions with commit IDs and revert to any specific version | ||
+ | * Never lose work: Every version of your files is saved permanently | ||
+ | * Work with confidence: Make bold changes knowing | ||
+ | |||
+ | You don't need to learn complex | ||
====== What is Git Hosting? ====== | ====== What is Git Hosting? ====== | ||
- | Now, imagine | + | Now imagine your team is spread across different |
- | That’s where Git Hosting comes in. It’s | + | Git hosting is like having |
- | Some popular | + | Git hosting |
- | - Share files easily | + | |
- | - See who changed what and when | + | These services |
- | - Combine everyone' | + | * Making it easy to share files with the right people |
+ | * Showing exactly | ||
+ | * 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’s not exactly like Google Drive or Dropbox — it’s smarter. It knows how to handle teamwork and keeps everything organized. | ||
====== What is a Repository? ====== | ====== What is a Repository? ====== | ||
- | A repository | + | A repository |
+ | |||
+ | 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, | ||
+ | |||
+ | 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. | ||
- | When you store files in Git, you’re actually storing them inside a repository. And you can create as many repositories as you need — one for each project, department, or client. | + | ====== How Git Winch Brings It All Together ====== |
- | Only the people who need to work on a particular project get access to its repository. That way, your files stay secure and only visible to those who should see them. | + | Here's how it works step-by-step: |
- | ====== How does it work with Git Winch? ====== | + | **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. |
- | In **Git Winch**, the owner creates a repository on a service like GitHub, GitLab, | + | **Permission Levels:** You can give team members one of two access levels: |
+ | * Pull only: They can download and view files but cannot make changes | ||
+ | * Push and pull: They can download files, make changes, and send their updates back to the repository | ||
- | You can choose whether someone can: | + | **Daily Workflow:** Here's what a typical day looks like: |
- | - Only view files (read-only) | + | * Team members open **Git Winch** |
- | - Edit and update existing | + | * They make their changes or add new files as needed |
- | - Or even add completely | + | * 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 | ||
- | This gives you full control over who does what — so your team can work together safely | + | **The Big Advantage: |
- | Team members use **Git Winch** to: | + | **Real-World Example: |
- | - Download files from the repository | + | 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** |
- | - Make changes | + | |
- | - Send their updates | + | |
- | And the best part? No one else needs a separate account on GitHub, GitLab, or Gitea — only the owner does. | + | This makes **Git Winch** perfect for small offices and teams who want professional file management without needing to become technology experts. |
- | This makes **Git Winch** perfect for small offices and teams who want to work together smoothly, without needing to be tech experts. | + | ----- |
+ | [[/ |