url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=no | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English (United States)) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 | 2026-01-13T09:29:22 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=he | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | <a class="tN8c4d" href="https://www.ftc.go.kr/selectBi | 2026-01-13T09:29:22 |
https://git-scm.com/book/uk/v2/%d0%93%d0%b0%d0%bb%d1%83%d0%b6%d0%b5%d0%bd%d0%bd%d1%8f-%d0%b2-git-%d0%93%d1%96%d0%bb%d0%ba%d0%b8-%d1%83-%d0%ba%d1%96%d0%bb%d1%8c%d0%ba%d0%be%d1%85-%d1%81%d0%bb%d0%be%d0%b2%d0%b0%d1%85 | Git - Гілки у кількох словах About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Вступ 1.1 Про систему контролю версій 1.2 Коротка історія Git 1.3 Основи Git 1.4 Git, зазвичай, тільки додає дані 1.5 Три стани 1.6 Командний рядок 1.7 Інсталяція Git 1.8 Початкове налаштування Git 1.9 Отримання допомоги 1.10 Підсумок 2. Основи Git 2.1 Створення Git-сховища 2.2 Запис змін до репозиторія 2.3 Перегляд історії комітів 2.4 Скасування речей 2.5 Взаємодія з віддаленими сховищами 2.6 Теґування 2.7 Псевдоніми Git 2.8 Підсумок 3. Галуження в git 3.1 Гілки у кількох словах 3.2 Основи галуження та зливання 3.3 Управління гілками 3.4 Процеси роботи з гілками 3.5 Віддалені гілки 3.6 Перебазовування 3.7 Підсумок 4. Git на сервері 4.1 Протоколи 4.2 Отримання Git на сервері 4.3 Генерація вашого публічного ключа SSH 4.4 Налаштування Серверу 4.5 Демон Git 4.6 Розумний HTTP 4.7 GitWeb 4.8 GitLab 4.9 Варіанти стороннього хостингу 4.10 Підсумок 5. Розподілений Git 5.1 Розподілені процеси роботи 5.2 Внесення змін до проекту 5.3 Супроводжування проекту 5.4 Підсумок 6. GitHub 6.1 Створення та налаштування облікового запису 6.2 Як зробити внесок до проекту 6.3 Супроводжування проєкту 6.4 Керування організацією 6.5 Скриптування GitHub 6.6 Підсумок 7. Інструменти Git 7.1 Вибір ревізій 7.2 Інтерактивне індексування 7.3 Ховання та чищення 7.4 Підписання праці 7.5 Пошук 7.6 Переписування історії 7.7 Усвідомлення скидання (reset) 7.8 Складне злиття 7.9 Rerere 7.10 Зневадження з Git 7.11 Підмодулі 7.12 Пакування 7.13 Заміна 7.14 Збереження посвідчення (credential) 7.15 Підсумок 8. Налаштування Git 8.1 Конфігурація Git 8.2 Атрибути Git 8.3 Гаки (hooks) Git 8.4 Приклад політики користування виконуваної Git-ом 8.5 Підсумок 9. Git and Other Systems 9.1 Git як клієнт 9.2 Міграція на Git 9.3 Підсумок 10. Git зсередини 10.1 Кухонні та парадні команди 10.2 Об’єкти Git 10.3 Посилання Git 10.4 Файли пакунки 10.5 Специфікація посилань (refspec) 10.6 Протоколи передачі 10.7 Супроводження та відновлення даних 10.8 Змінні середовища 10.9 Підсумок A1. Додаток A: Git в інших середовищах A1.1 Графічні інтерфейси A1.2 Git у Visual Studio A1.3 Git в Eclipse A1.4 Git у Bash A1.5 Git у Zsh A1.6 Git у Powershell A1.7 Підсумок A2. Додаток B: Вбудовування Git у ваші застосунки A2.1 Git з командного рядка A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. Додаток C: Команди Git A3.1 Налаштування та конфігурація A3.2 Отримання та створення проектів A3.3 Базове збереження відбитків A3.4 Галуження та зливання A3.5 Поширення й оновлення проектів A3.6 Огляд та порівняння A3.7 Зневаджування A3.8 Латання (patching) A3.9 Електронна пошта A3.10 Зовнішні системи A3.11 Адміністрування A3.12 Кухонні команди 2nd Edition 3.1 Галуження в git - Гілки у кількох словах Майже кожна система контролю версій підтримує гілки (branches) в певній мірі. Галуження - це відмежування від основної лінії розробки для продовження своєї частини роботи та уникнення конфліктів з основною лінією. В багатьох системах контролю версій цей процес "дорогий", часом вимагає створювати копію коду, що може зайняти багато часу для великих проектів. Дехто вважає гілки Git вбивчою особливістю, що вирізняє Git від інших систем. Що ж в них такого особливого? Гілки Git надзвичайно легкі, операції галуження майже миттєві, перехід між гілками зазвичай теж. На відміну від інших систем, Git заохочує схеми, де гілки часто створюються та зливаються, навіть кілька разів на день. Розуміння та вміння працювати з цією "фішкою" дає вам потужний та унікальний інструмент, що може кардинально змінити ваш процес розробки. Гілки у кількох словах Щоб дійсно зрозуміти як Git працює з гілками, нам треба повернутись назад та розібратись, як Git зберігає дані. Як ви можете пам’ятати з Вступ , Git зберігає дані не як послідовність змін, а як послідовність знімків. Коли ви фіксуєте зміни, Git зберігає об’єкт фіксації, що містить вказівник на знімок змісту, який ви додали. Цей об’єкт також містить ім’я та поштову адресу автора, набране вами повідомлення та вказівники на фіксацію або фіксації, що були прямо до цієї фіксації (батько чи батьки): нуль для першої фіксації, одна фіксація для нормальної фіксації, та декілька фіксацій для фіксацій, що вони є результатом злиття двох чи більше гілок. Щоб це уявити, припустимо, що у вас є тека з трьома файлами, які ви додали та зафіксували. Додання файлів обчислює контрольну суму для кожного (SHA-1 хеш про котрий ми згадували в Вступ ), зберігає версію файлу в сховищі Git (Git називає їх блобами), та додає їх контрольні суми до області додавання: $ git add README test.rb LICENSE $ git commit -m 'The initial commit of my project' Коли ви створили фіксацію за допомогою git commit , Git обчислив контрольну суму кожної теки (у цьому випадку, тільки кореневої теки) та зберігає ці об’єкти дерева в сховищі Git. Потім Git створює об’єкт фіксації, що зберігає метадані та вказівник на корінь дерева проекту, щоб він міг відтворити цей знімок, коли потрібно. Ваше Git сховище тепер зберігає п’ять об’єктів: по одному блобу зі змістом на кожен з трьох файлів, одне дерево, що перелічує зміст теки та вказує, які файли зберігаються у яких блобах, та одну фіксацію, що вказує на корінь дерева, та зберігає метадані фіксації. Рисунок 9. Фіксація як дерево Якщо ви зробите якісь зміни та зафіксуєте знову, наступна фіксація буде зберігати вказівник на попередню. Рисунок 10. Фіксації та їх батьки Гілка в Git це просто легкий вказівник, що може пересуватись, на одну з цих фіксацій. Загальноприйнятим ім’ям першої гілки в Git є master . Коли ви почнете робити фіксації, вам надається гілка master , що вказує на останню зроблену фіксацію. Щоразу ви фіксуєте, вона переміщується вперед автоматично. Зауваження Гілка `master'' у Git не має нічого особливого. Вона нічим не відрізняється від інших. Єдина причина, чому майже кожне сховище має таку гілку — команда `git init автоматично її створює, і більшість людей не мають клопоту змінити її. Рисунок 11. Гілка та її історія фіксацій Створення нової гілки Що відбувається, якщо ви створюєте нову гілку? Ну, це створює новий вказівник, щоб ви могли пересуватися. Припустімо, ви створюєте нову гілку під назвою testing. Ви це робите за допомогою команди git branch : $ git branch testing Це створює новий вказівник на фіксацію, в якій ви зараз знаходитесь. Рисунок 12. Дві гілки вказують на одну послідовність фіксацій Звідки Git знає, на якій гілці ви зараз знаходитесь? Він зберігає особливий вказівник під назвою HEAD . Завважте, що це геть інша концепція HEAD , ніж в інших СКВ, з якими ви могли працювати, таких як Subversion чи CVS. У Git це просто вказівник на локальну гілку, на якій ви знаходитесь. В даному випадку, ви досі на гілці master . Команда git branch тільки створює нову гілку — вона не переключає на цю гілку. Рисунок 13. HEAD вказує на гілку Ви легко можете це побачити за допомогою простої опції команди git log , що може показати куди вказують вказівники гілок. Ця опція називається --decorate . $ git log --oneline --decorate f30ab (HEAD -> master, testing) add feature #32 - ability to add new formats to the central interface 34ac2 Fixed bug #1328 - stack overflow under certain conditions 98ca9 The initial commit of my project Як бачите, гілки master'' та testing'' прямо поруч з фіксацією f30ab . Переключення гілок Щоб переключитися на існуючу гілку, треба виконати команду git checkout . Переключімося на нову гілку testing : $ git checkout testing Це пересуває HEAD , щоб він вказував на гілку testing . Рисунок 14. HEAD вказує на поточну гілку Чому це важливо? Ну, давайте зробимо ще одну фіксацію: $ vim test.rb $ git commit -a -m 'Зробив зміни' Рисунок 15. Гілка HEAD пересувається уперед при фіксації Це цікаво, бо тепер ваша гілка testing пересунулась уперед, а ваша гілка master досі вказує на фіксацію, що й у момент виконання git checkout для переключення гілок. Переключімося назад до гілки master : $ git checkout master Рисунок 16. HEAD пересувається, коли ви отримуєте (checkout) Ця команда зробила дві речі. Вона пересунула вказівник HEAD назад на гілку master , та повернула файли у вашій робочій теці до стану знімку, на який вказує master . Це також означає, що якщо ви зараз зробите нові зміни, вони будуть походити від ранішої версії проекту. Вона, суттєво, перемотує працю, що ви зробили у гілці testing , щоб ви могли працювати в іншому напрямку. Зауваження Переключення між гілками змінює файли у вашій робочій теці Важливо зауважити, що коли ви переключаєте гілки в Git, файли у вашій робочій теці змінюються. Якщо ви переключаєтесь до старшої гілки, ваша робоча тека буде повернута до того стаку, який був на момент останнього фіксування у тій гілці. Якщо Git не може зробити це без проблем, він не дасть вам переключитися взагалі. Зробимо декілька змін та знову зафіксуємо: $ vim test.rb $ git commit -a -m 'Зробив інші зміни' Тепер історія вашого проекту розбіглася ( diverged ) (дивіться Історія, що розбіглася ). Ви створили гілку, дещо в ній зробили, переключились на головну гілку та зробили там щось інше. Обидві зміни ізольовані в окремих гілках. Ви можете переключатись між цими гілками та злити їх, коли вони будуть готові. І все це ви зробили за допомогою простих команд branch , checkout та commit . Рисунок 17. Історія, що розбіглася Ви також можете легко це побачити за допомогою команди git log . Якщо ви виконаєте git log --oneline --decorate --graph --all , вона надрукує історію ваших фіксацій, покаже куди вказують ваші гілки та як розбіглася ваша історія. $ git log --oneline --decorate --graph --all * c2b9e (HEAD, master) Зробив інші зміни | * 87ab2 (testing) Зробив зміни |/ * f30ab add feature #32 - ability to add new formats to the * 34ac2 fixed bug #1328 - stack overflow under certain conditions * 98ca9 initial commit of my project Оскільки гілка в Git — це насправді простий файл, що містить 50 символів контрольної суми SHA-1 коміту, на який вказує, гілки дешево створювати та знищувати. Створити гілку так же швидко, як записати 41 байт до файлу (40 символів та символ нового рядка). Це вражаюча відмінність від того, як більшість інших СВК працюють з гілками — зазвичай це потребує копіювання усіх файлів проекту в другу теку. Це може зайняти декілька секунда, або навіть хвилин, в залежності від розміру проекту, у той час як у Git процес завжди миттєвий. Також, оскільки ми записуємо батьків кожної фіксації, пошук відповідної бази для злиття може бути зроблено автоматично та зазвичай дуже просто. Ці можливості допомагають заохотити розробників створювати та використовувати гілки часто. Подивимось, чому і вам варто так робити. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:22 |
https://git-scm.com/book/uk/v2/%d0%92%d1%81%d1%82%d1%83%d0%bf-Git,-%d0%b7%d0%b0%d0%b7%d0%b2%d0%b8%d1%87%d0%b0%d0%b9,-%d1%82%d1%96%d0%bb%d1%8c%d0%ba%d0%b8-%d0%b4%d0%be%d0%b4%d0%b0%d1%94-%d0%b4%d0%b0%d0%bd%d1%96 | Git - Git, зазвичай, тільки додає дані About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Вступ 1.1 Про систему контролю версій 1.2 Коротка історія Git 1.3 Основи Git 1.4 Git, зазвичай, тільки додає дані 1.5 Три стани 1.6 Командний рядок 1.7 Інсталяція Git 1.8 Початкове налаштування Git 1.9 Отримання допомоги 1.10 Підсумок 2. Основи Git 2.1 Створення Git-сховища 2.2 Запис змін до репозиторія 2.3 Перегляд історії комітів 2.4 Скасування речей 2.5 Взаємодія з віддаленими сховищами 2.6 Теґування 2.7 Псевдоніми Git 2.8 Підсумок 3. Галуження в git 3.1 Гілки у кількох словах 3.2 Основи галуження та зливання 3.3 Управління гілками 3.4 Процеси роботи з гілками 3.5 Віддалені гілки 3.6 Перебазовування 3.7 Підсумок 4. Git на сервері 4.1 Протоколи 4.2 Отримання Git на сервері 4.3 Генерація вашого публічного ключа SSH 4.4 Налаштування Серверу 4.5 Демон Git 4.6 Розумний HTTP 4.7 GitWeb 4.8 GitLab 4.9 Варіанти стороннього хостингу 4.10 Підсумок 5. Розподілений Git 5.1 Розподілені процеси роботи 5.2 Внесення змін до проекту 5.3 Супроводжування проекту 5.4 Підсумок 6. GitHub 6.1 Створення та налаштування облікового запису 6.2 Як зробити внесок до проекту 6.3 Супроводжування проєкту 6.4 Керування організацією 6.5 Скриптування GitHub 6.6 Підсумок 7. Інструменти Git 7.1 Вибір ревізій 7.2 Інтерактивне індексування 7.3 Ховання та чищення 7.4 Підписання праці 7.5 Пошук 7.6 Переписування історії 7.7 Усвідомлення скидання (reset) 7.8 Складне злиття 7.9 Rerere 7.10 Зневадження з Git 7.11 Підмодулі 7.12 Пакування 7.13 Заміна 7.14 Збереження посвідчення (credential) 7.15 Підсумок 8. Налаштування Git 8.1 Конфігурація Git 8.2 Атрибути Git 8.3 Гаки (hooks) Git 8.4 Приклад політики користування виконуваної Git-ом 8.5 Підсумок 9. Git and Other Systems 9.1 Git як клієнт 9.2 Міграція на Git 9.3 Підсумок 10. Git зсередини 10.1 Кухонні та парадні команди 10.2 Об’єкти Git 10.3 Посилання Git 10.4 Файли пакунки 10.5 Специфікація посилань (refspec) 10.6 Протоколи передачі 10.7 Супроводження та відновлення даних 10.8 Змінні середовища 10.9 Підсумок A1. Додаток A: Git в інших середовищах A1.1 Графічні інтерфейси A1.2 Git у Visual Studio A1.3 Git в Eclipse A1.4 Git у Bash A1.5 Git у Zsh A1.6 Git у Powershell A1.7 Підсумок A2. Додаток B: Вбудовування Git у ваші застосунки A2.1 Git з командного рядка A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. Додаток C: Команди Git A3.1 Налаштування та конфігурація A3.2 Отримання та створення проектів A3.3 Базове збереження відбитків A3.4 Галуження та зливання A3.5 Поширення й оновлення проектів A3.6 Огляд та порівняння A3.7 Зневаджування A3.8 Латання (patching) A3.9 Електронна пошта A3.10 Зовнішні системи A3.11 Адміністрування A3.12 Кухонні команди 2nd Edition 1.4 Вступ - Git, зазвичай, тільки додає дані Git, зазвичай, тільки додає дані Коли ви виконуєте певні дії в Git, при цьому, майже завжди відбувається виключно додавання інформації до бази даних Git. Складно змусити систему зробити щось невиправне чи повністю видалити дані будь-яким чином. Як і в будь-якій СКВ, ви можете втратити чи зіпсувати лише не збережені в коміті зміни, але це майже неможливо, коли вже збережено знімок, особливо, якщо ви регулярно надсилаєте свою базу до іншого сховища. Це робить використання Git приємним, оскільки ми точно можемо експериментувати без загрози щось зіпсувати. Про те, як Git зберігає інформацію та як можна відновити втрачені дані, що нібито загублені, детальніше розповідається у Скасування речей . prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:22 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=en_SG | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상 | 2026-01-13T09:29:22 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=fr_CH | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 | 2026-01-13T09:29:22 |
http://ccmixter.org/privacy | ccMixter - CCMIXTER PRIVACY POLICY Listen to the Light skip Not logged in Log In Search Find content Collaborative Community Home The Mixversation Picks Remixes Samples A Cappellas People Extras CCMIXTER PRIVACY POLICY 1. Introduction. This Privacy Policy explains the collection, use, processing, transferring, and disclosure of personal information by ArtisTech Media (“ATM” or “ArtisTech”), a California Limited Liability Corporation. This Privacy Policy is incorporated into and made part of ArtisTech Media Master Terms of Use (“Master Terms”) located at http://ccmixter.org/terms . Unless otherwise noted on a particular website or service hosted by ArtisTech, this Privacy Policy applies to your use of all websites that ArtisTech operates. These include http://ccmixter.org/ , http://beta.ccmixter.org/ , http://beta.ccmixter.org/pells , http://beta.ccmixter.org/stems , http://dig.ccmixter.org/ , http://beta.ccmixter.org/playlists/browse , and http://tunetrack.net/ , together with all other subdomains thereof, (collectively, the “Websites”). This Privacy Policy also applies to all products, information, and services provided through the Websites, including without limitation the API and Login Services (defined below), (together with the Websites, the “Services”). By accessing or using any of the Services, you are accepting and agreeing to the practices described in this Privacy Policy. 2. Personal Information ATM Collects and How it is Used As used in this policy, “personal information” means information that would allow someone to identify you, including your name, email address, IP address, or other information from which someone could deduce your identity. ATM collects and uses personal information in the following ways: Website Analytics: When you visit our Websites and use our Services, ATM collects some information about your activities through tools such as Google Analytics. The type of information that we collect focuses on general information such as country or city where you are located, pages visited, time spent on pages, heat-map of visitors’ activity on the site, information about the browser you are using, etc. ATM collects and uses this information pursuant to our legitimate interest in enhancing the security and utility of our Services. The information we gather and process is used in the aggregate to spot trends without deliberately identifying individuals. Note that you can learn about Google’s practices in connection with its analytics services and how to opt out of it by downloading the Google Analytics opt-out browser add-on, available at https://tools.google.com/dlpage/gaoptout . ArtisTech also retains information about the usage of ccMixter, such as, for example, number of uploads, number of downloads, number of users. This information is aggregated and does not usually personally identify you, although limited personal information for some artists is displayed at http://ccmixter.org/stats . ArtisTech may make this aggregated information available to the public and other entities, such as our shareholders and advisors. Information from Cookies: We and our service providers (for example, Google Analytics as described above) may collect information using cookies or similar technologies for the purposes described above and below. Cookies are pieces of information that are stored by your browser on the hard drive or memory of your computer or other Internet access device. Cookies may enable us to personalize your experience on the Services, maintain a persistent session, passively collect demographic information about your computer, and monitor other activities. The Websites may use different kinds of cookies and other types of local storage (such as browser-based or plugin-based local storage). Log-In Services: When you register to obtain a user account on any of the Services (any such person, a “Registered User”), you will be asked to provide personal information to create your account and establish a password and profile. Through ccMixter, ArtisTech collects the personal information that you submit at the following pages: (a) account creation page, (b) artist profile page, (c) track upload page, and (d) discussion forums. You decide what and how much personal information we collect at these pages except that we require (through the ccMixter Terms) that your contact information is accurate and up-to-date in case we need to contact you for reasons related to ccMixter, for example, you have won a competition or have been selected to be on a remix event album, you’ve earned royalties, or someone claims music you posted to ccMixter is infringing or violates the terms of service . It is your responsibility to check and correct this information. All of the information you submit at the artist profile page (with the exception of your email address and password) and the discussion forums is made available at ccMixter to people who access ccMixter. ArtisTech uses your email address and password solely for the purposes of: (a) administering ccMixter, so for example, to contact you about one of the tracks you uploaded or to send you a password reminder; and, (b) for the purpose of contacting you as part of a mass mailing about important changes to the ccMixter site. The first time we contact you as part of a mass mailing, we will give you the opportunity to opt-out of receiving future similar emails from us. ArtisTech also collects personal information about you when you send us an email or other communication. ArtisTech Media uses any such personal information solely for the purpose of responding to and acting appropriately in response to your email or other communication. ATM collects and uses this personal information pursuant to its legitimate interest in establishing and maintaining your account providing you with the features we provide Registered Users. We may use your email address to contact you regarding changes to this policy or other applicable policies. The Login Name you provide in connection with your account may be used to attribute you in connection with any content you submit to any Service. Donations: When you donate money to ArtisTech, you will be asked to provide personal information, including payment information. ATM collects and uses this personal information pursuant to its legitimate interest to process your donation. Other Voluntarily Provided Information: When you provide feedback to ArtisTech, upload content, comment in the forums, or otherwise submit personal information, ATM collects and uses this personal information pursuant to its legitimate interest in better understanding our community of artists, supporters and volunteers and in furtherance of the activity about which you provided feedback or other input. 3. Retention of Personal Information The majority of the personal information collected and used as explained in Section 2 above is aggregated and stored in a central database hosted by a third party service provider. ATM aggregates this data pursuant to its legitimate interest in having information stored in a single location to minimize complexity, increase consistency in internal practices, better understand its community of artists, supporters and volunteers, and enhance the security of the data. ATM erases the web browser logs described above on a regular, rolling basis. We generally retain other personal information for the purposes for which it was collected. This may mean that we retain your personal information indefinitely in some cases. 4. Access to Your Personal Information You are generally entitled to access and transfer to a third party any personal information that ArtisTech holds and to have inaccurate data corrected or removed to the extent ATM still maintains it. In certain circumstances, you also may have the right to object or restrict for legitimate reasons to the processing or transfer of personal information. If you wish to exercise any of these rights, please write to info@artistechmedia.com explaining your request. You also have the right to go directly to the relevant supervisory or legal authority, but we encourage you to contact us so that we may resolve your concerns directly as best we can. 5. Disclosure of Your Personal Information ATM does not disclose personal information to third parties except as specified elsewhere in this policy and in the following instances: ArtisTech may share personal information with our contractors and service providers in order to undertake the activities described in Section 2. We may disclose your personal information to third parties in a good faith belief that such disclosure is reasonably necessary to (a) take action regarding suspected illegal activities; (b) enforce or apply our Master Terms and this Privacy Policy, or (c) comply with legal process, such as a search warrant, subpoena, statute, or court order. 6. Security of Your Personal Information ArtisTech has implemented reasonable physical, technical, and organizational security measures for personal information that ATM processes against accidental or unlawful destruction, or accidental loss, alteration, unauthorized disclosure or access, in compliance with applicable law. However, no website can fully eliminate security risks. Third parties may circumvent our security measures to unlawfully intercept or access transmissions or private communications. If any data breach occurs, we will post a reasonably prominent notice to ccMixter and comply with all other applicable data privacy requirements including, when required, personal notice to you if you have provided and we have maintained an email address for you. The ATM Login Services account systems have security risks in addition to those described above. Among other things, they are vulnerable to DNS attacks. 7. Children The Services are not directed at children under the age of 13. Consistent with the U.S. federal Children’s Online Privacy Protection Act of 1998 (COPPA), we will never knowingly request personal information from anyone under the age of 13 without requiring parental consent. Our Master Terms specifically prohibit anyone using our Services from submitting any personally identifiable information about persons under 13 years of age. Any person who provides their personal information to ATM through the Services represents that they are 13 years of age or older. 8. Third Party Service Providers and Business Transfers In general, it is not ArtisTech’'s practice to disclose personal information to third parties. We may share personal information in three instances. Firstly, ArtisTech uses third party service providers in connection with the Services, including but not limited to website hosting services, database management, and credit card processing. Some of these service providers may place session cookies on your computer, and they may collect and store your personal information on our behalf in accordance with the data practices and purposes explained above in Section 3. Additionally, ArtisTech may share personal information with our contractors and service providers in order to maintain, enhance, or add to the functionality of the site. In that case, ArtisTech requires those contractors and service providers to abide by this Privacy Policy and to only use any and all personal information solely for the purpose of performing their responsibilities for ArtisTech and then only to the extent necessary to perform those responsibilities. Secondly, we may share personal information with third parties such as the government or other entities when required to by law, in order to comply with section 512(g) of the US Copyright Act ( see… ), or as required by court order. Lastly, if ArtisTech transfer operations of ccMixter to another business or entity, or if ownership of all or substantially all or our business changes, or we undergo a corporate reorganization (including but not limited to a merger, consolidation or converting to a nonprofit corporation) or any other action or transfer (including but not limited to a transfer to Creative Commons or another entity or nonprofit corporation), you expressly consent to ArtisTech transferring your information to the new owner of the successor entity so that the Services and Websites can continue to be provided and operated, and you acknowledge customer, email and visitor information is generally one of the transferred business assets in these types of transactions. 9. Location of Services If you are accessing or using the Services in regions with laws governing data collection, processing, transfer and use, please note that when we use and share your data as specified in this policy, we may transfer your information to recipients in countries other than the country in which the information was originally collected. Those countries may not have the same data protection laws as the country in which you initially provided the information. The Services are currently hosted in the United States, which means your personal information may be located on servers in the United States. This may change from time to time. The majority of contractors that ArtisTech is using as of the effective date of this Privacy Policy are located in the United States, but this may change from time to time. 10. Changes to this Privacy Policy We may occasionally update this Privacy Policy. When we do, we will provide you with notice of such update through (at a minimum) a reasonably prominent notice on ccMixter, including in the ccMixter.org Forums, and will revise the Effective Date below. We encourage you to periodically review this Privacy Policy to stay informed about how we are protecting, using, processing and transferring the personal information we collect. If you have questions about this Privacy Policy, please contact us by email at info@artistechmedia.com . Effective Date: November 8, 2018. Archived Versions of this Document Terms pre 2018-12-29 Visitors Find Music Forums About Looking for...? Artists Log In Register Search our archives for music for your video, podcast or school project at dig.ccMixter New Remixes weatherPatter... My Heart Beat... Je suis un Ph... From Two Dire... The Fade Out More new remixes New Uploads weatherPatter... My Heart Beat... Je suis un Ph... No Constant Tascam Amateu... More new uploads Editors' Picks Time Machine Happiness Dee... New Year Begi... Yorke And Lou Hollow Crown ... More picks... Highest Rated Queen of K... New Year B... Frost-Free... Queen of K... Javomatics Weather Or... Recent Reviewers texasradiofis... Speck Javolenus panu Stefan Karten... Bluemillenium airtone More reviews... Support ccMixter This text and images on this site are licensed under a Creative Commons Attribution-Noncommercial 4.0 International License . This site uses ccHost , licensed under CC-GNU-GPL , which is a product of the ccTools project and uses GetID3 . This site is sponsored by ArtisTech Media . By using this site, you agree to our Terms of Use and Privacy Policy . Please note our site credits . Contact: site administrator . | 2026-01-13T09:29:22 |
https://git-scm.com/book/sl/v2/Git-na-stre%c5%beniku-Povzetek | Git - Povzetek About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Začetek 1.1 O nadzoru različic 1.2 Kratka zgodovina Gita 1.3 Kaj je Git? 1.4 Ukazna vrstica 1.5 Namestitev Gita 1.6 Prva nastavitev Gita 1.7 Pridobivanje pomoči 1.8 Povzetek 2. Osnove Git 2.1 Pridobivanje repozitorija Git 2.2 Snemanje sprememb v repozitorij 2.3 Pregled zgodovine potrditev 2.4 Razveljavljanje stvari 2.5 Delo z daljavami 2.6 Označevanje 2.7 Aliasi Git 2.8 Povzetek 3. Veje Git 3.1 Veje na kratko 3.2 Osnove vej in združevanja 3.3 Upravljanje vej 3.4 Poteki dela z vejami 3.5 Oddaljene veje 3.6 Ponovno baziranje 3.7 Povzetek 4. Git na strežniku 4.1 Protokoli 4.2 Pridobitev Gita na strežniku 4.3 Generiranje vaših javnih ključev SSH 4.4 Nastavitev strežnika 4.5 Prikriti proces Git 4.6 Pametni HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti gostovanja pri tretjih ponudnikih 4.10 Povzetek 5. Porazdeljeni Git 5.1 Porazdeljeni poteki dela 5.2 Prispevek k projektu 5.3 Vzdrževanje projekta 5.4 Povzetek 6. GitHub 6.1 Namestitev in konfiguracija računa 6.2 Prispevek k projektu 6.3 Vzdrževanje projekta 6.4 Upravljanje organizacije 6.5 Skriptni GitHub 6.6 Povzetek 7. Orodja Git 7.1 Izbira revizije 7.2 Interaktivno pripravljanje 7.3 Shranjevanje na varno (angl. stashing) in čiščenje 7.4 Podpisovanje vašega dela 7.5 Iskanje 7.6 Prepisovanje zgodovine 7.7 Demistifikacija ponastavitve 7.8 Napredno združevanje 7.9 Rerere 7.10 Razhroščevanje z Gitom 7.11 Podmoduli 7.12 Povezovanje v pakete 7.13 Zamenjava 7.14 Shramba poverilnic 7.15 Povzetek 8. Prilagoditev Gita 8.1 Konfiguracija Git 8.2 Atributi Git 8.3 Kljuke Git 8.4 Primer pravilnika, ki ga uveljavlja Git 8.5 Povzetek 9. Git in ostali sistemi 9.1 Git kot odjemalec 9.2 Migracija na Git 9.3 Povzetek 10. Notranjost Gita 10.1 Napeljava in keramika 10.2 Objekti Git 10.3 Reference Git 10.4 Packfiles (datoteke zmanjšanih podatkov) 10.5 Refspec 10.6 Protokoli prenosa 10.7 Vzdrževanje in obnovitev podatkov 10.8 Spremenljivke okolja 10.9 Povzetek A1. Dodatek A: Git v drugih okoljih A1.1 Grafični vmesniki A1.2 Git v Visual Studio A1.3 Git v Visual Studio Code A1.4 Git v IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git v Sublime Text A1.6 Git v Bashu A1.7 Git v Zsh A1.8 Git v Powershellu A1.9 Povzetek A2. Dodatek B: Vdelava Gita v vašo aplikacijo A2.1 Git v ukazni vrstici A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Dodatek C: Ukazi Git A3.1 Nastavitev in konfiguracija A3.2 Pridobivanje in ustvarjanje projektov A3.3 Osnove posnetkov A3.4 Veje in združevanje A3.5 Deljenje in posodabljanje projektov A3.6 Pregled in primerjava A3.7 Razhroščevanje A3.8 Popravljanje A3.9 E-pošta A3.10 Zunanji sistemi A3.11 Administracija A3.12 Orodja za sisteme napeljave 2nd Edition 4.10 Git na strežniku - Povzetek Povzetek Na voljo imate več možnosti za vzpostavitev in delovanje oddaljenega repozitorija Git, tako da lahko sodelujete z drugimi ali delite svoje delo. Poganjanje svojega lastnega strežnika vam da veliko nadzora in vam omogoča, da strežnik poganjate znotraj svojega lastnega požarnega zidu, vendar tak strežnik na splošno zahteva precej vašega časa za nastavitev in vzdrževanje. Če svoje podatke postavite na gostovalni strežnik, ga je enostavno nastaviti in vzdrževati; vendar pa morate imeti možnost, da svojo kodo obdržite na strežniku nekoga drugega, nekatere organizacije pa tega ne dovoljujejo. Katera rešitev ali kombinacija rešitev je primerna za vas in vašo organizacijo, bi moralo biti dokaj preprosto določiti. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:22 |
https://git-scm.com/book/tl/v2/Pag-branch-ng-Git-Buod | Git - Buod About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 3.7 Pag-branch ng Git - Buod Buod Nasakop natin ang batayan ng pag-branch at pag-merge sa Git. Ikaw ay dapat kumportable na sa paggawa at pagpapalit ng bagong mga branch, pagpapalit ng mga branch at pag-merge ng lokal na mga branch nang magkasabay. Ikaw ay dapat ding maaaring magbahagi ng iyong mga branch sa pamamagitan ng pag-push sa mga ito sa isang ibinahaging server, ang pagtatrabaho kasama ang iba sa ibinahaging mga branch at pagre-rebase ng iyong mga branch bago sila maibahagi. Susunod, sasakupin natin ang kung ano ang iyong kakailanganin upang magpatakbo ng iyong sariling Git na repository-hosting na server. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:22 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=id | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상 | 2026-01-13T09:29:22 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_PA | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상�� | 2026-01-13T09:29:22 |
https://git-scm.com/book/id/v2/Git-Basics-Recording-Changes-to-the-Repository | Git - Recording Changes to the Repository About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Memulai 1.1 Tentang Version Control 1.2 Sejarah Singkat Git 1.3 Dasar-dasar Git 1.4 Command Line 1.5 Memasang Git 1.6 Pengaturan Awal Git 1.7 Mendapatkan Bantuan 1.8 Kesimpulan 2. Git Basics 2.1 Mendapatkan Repository Git 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Alias Git 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git di Server 4.1 Protokol 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Ringkasan 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pengaturan dan Konfigurasi Akun 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Mengelola Organization 6.5 Scripting GitHub 6.6 Ringkasan 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Kostumisasi Git 8.1 Konfigurasi Git 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Ringkasan 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.2 Git Basics - Recording Changes to the Repository Recording Changes to the Repository You have a bona fide Git repository and a checkout or working copy of the files for that project. You need to make some changes and commit snapshots of those changes into your repository each time the project reaches a state you want to record. Remember that each file in your working directory can be in one of two states: tracked or untracked. Tracked files are files that were in the last snapshot; they can be unmodified, modified, or staged. Untracked files are everything else – any files in your working directory that were not in your last snapshot and are not in your staging area. When you first clone a repository, all of your files will be tracked and unmodified because you just checked them out and haven’t edited anything. As you edit files, Git sees them as modified, because you’ve changed them since your last commit. You stage these modified files and then commit all your staged changes, and the cycle repeats. Figure 8. The lifecycle of the status of your files. Checking the Status of Your Files The main tool you use to determine which files are in which state is the git status command. If you run this command directly after a clone, you should see something like this: $ git status On branch master nothing to commit, working directory clean This means you have a clean working directory – in other words, there are no tracked and modified files. Git also doesn’t see any untracked files, or they would be listed here. Finally, the command tells you which branch you’re on and informs you that it has not diverged from the same branch on the server. For now, that branch is always “master”, which is the default; you won’t worry about it here. Git Branching will go over branches and references in detail. Let’s say you add a new file to your project, a simple README file. If the file didn’t exist before, and you run git status , you see your untracked file like so: $ echo 'My Project' > README $ git status On branch master Untracked files: (use "git add <file>..." to include in what will be committed) README nothing added to commit but untracked files present (use "git add" to track) You can see that your new README file is untracked, because it’s under the “Untracked files” heading in your status output. Untracked basically means that Git sees a file you didn’t have in the previous snapshot (commit); Git won’t start including it in your commit snapshots until you explicitly tell it to do so. It does this so you don’t accidentally begin including generated binary files or other files that you did not mean to include. You do want to start including README, so let’s start tracking the file. Tracking New Files In order to begin tracking a new file, you use the command git add . To begin tracking the README file, you can run this: $ git add README If you run your status command again, you can see that your README file is now tracked and staged to be committed: $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README You can tell that it’s staged because it’s under the “Changes to be committed” heading. If you commit at this point, the version of the file at the time you ran git add is what will be in the historical snapshot. You may recall that when you ran git init earlier, you then ran git add (files) – that was to begin tracking files in your directory. The git add command takes a path name for either a file or a directory; if it’s a directory, the command adds all the files in that directory recursively. Staging Modified Files Let’s change a file that was already tracked. If you change a previously tracked file called “CONTRIBUTING.md” and then run your git status command again, you get something that looks like this: $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md The “CONTRIBUTING.md” file appears under a section named “Changed but not staged for commit” – which means that a file that is tracked has been modified in the working directory but not yet staged. To stage it, you run the git add command. git add is a multipurpose command – you use it to begin tracking new files, to stage files, and to do other things like marking merge-conflicted files as resolved. It may be helpful to think of it more as “add this content to the next commit” rather than “add this file to the project”. Let’s run git add now to stage the “CONTRIBUTING.md” file, and then run git status again: $ git add CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Both files are staged and will go into your next commit. At this point, suppose you remember one little change that you want to make in CONTRIBUTING.md before you commit it. You open it again and make that change, and you’re ready to commit. However, let’s run git status one more time: $ vim CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md What the heck? Now CONTRIBUTING.md is listed as both staged and unstaged. How is that possible? It turns out that Git stages a file exactly as it is when you run the git add command. If you commit now, the version of CONTRIBUTING.md as it was when you last ran the git add command is how it will go into the commit, not the version of the file as it looks in your working directory when you run git commit . If you modify a file after you run git add , you have to run git add again to stage the latest version of the file: $ git add CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Short Status While the git status output is pretty comprehensive, it’s also quite wordy. Git also has a short status flag so you can see your changes in a more compact way. If you run git status -s or git status --short you get a far more simplified output from the command. $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt New files that aren’t tracked have a ?? next to them, new files that have been added to the staging area have an A , modified files have an M and so on. There are two columns to the output - the left hand column indicates that the file is staged and the right hand column indicates that it’s modified. So for example in that output, the README file is modified in the working directory but not yet staged, while the lib/simplegit.rb file is modified and staged. The Rakefile was modified, staged and then modified again, so there are changes to it that are both staged and unstaged. Ignoring Files Often, you’ll have a class of files that you don’t want Git to automatically add or even show you as being untracked. These are generally automatically generated files such as log files or files produced by your build system. In such cases, you can create a file listing patterns to match them named .gitignore . Here is an example .gitignore file: $ cat .gitignore *.[oa] *~ The first line tells Git to ignore any files ending in “.o” or “.a” – object and archive files that may be the product of building your code. The second line tells Git to ignore all files that end with a tilde ( ~ ), which is used by many text editors such as Emacs to mark temporary files. You may also include a log, tmp, or pid directory; automatically generated documentation; and so on. Setting up a .gitignore file before you get going is generally a good idea so you don’t accidentally commit files that you really don’t want in your Git repository. The rules for the patterns you can put in the .gitignore file are as follows: Blank lines or lines starting with # are ignored. Standard glob patterns work. You can end patterns with a forward slash ( / ) to specify a directory. You can negate a pattern by starting it with an exclamation point ( ! ). Glob patterns are like simplified regular expressions that shells use. An asterisk ( * ) matches zero or more characters; [abc] matches any character inside the brackets (in this case a, b, or c); a question mark ( ? ) matches a single character; and brackets enclosing characters separated by a hyphen( [0-9] ) matches any character between them (in this case 0 through 9). You can also use two asterisks to match nested directories; a/**/z would match a/z , a/b/z , a/b/c/z , and so on. Here is another example .gitignore file: # no .a files *.a # but do track lib.a, even though you're ignoring .a files above !lib.a # only ignore the root TODO file, not subdir/TODO /TODO # ignore all files in the build/ directory build/ # ignore doc/notes.txt, but not doc/server/arch.txt doc/*.txt # ignore all .txt files in the doc/ directory doc/**/*.txt Tip GitHub maintains a fairly comprehensive list of good .gitignore file examples for dozens or projects and languages at https://github.com/github/gitignore if you want a starting point for your project. Viewing Your Staged and Unstaged Changes If the git status command is too vague for you – you want to know exactly what you changed, not just which files were changed – you can use the git diff command. We’ll cover git diff in more detail later, but you’ll probably use it most often to answer these two questions: What have you changed but not yet staged? And what have you staged that you are about to commit? Although git status answers those questions very generally by listing the file names, git diff shows you the exact lines added and removed – the patch, as it were. Let’s say you edit and stage the README file again and then edit the CONTRIBUTING.md file without staging it. If you run your git status command, you once again see something like this: $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md To see what you’ve changed but not yet staged, type git diff with no other arguments: $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3cb747f..e445e28 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -36,6 +36,10 @@ def main @commit.parents[0].parents[0].parents[0] end + run_code(x, 'commits 1') do + git.commits.size + end + run_code(x, 'commits 2') do log = git.commits('master', 15) log.size That command compares what is in your working directory with what is in your staging area. The result tells you the changes you’ve made that you haven’t yet staged. If you want to see what you’ve staged that will go into your next commit, you can use git diff --staged . This command compares your staged changes to your last commit: $ git diff --staged diff --git a/README b/README new file mode 100644 index 0000000..03902a1 --- /dev/null +++ b/README @@ -0,0 +1,4 @@ +My Project + + This is my project and it is amazing. + It’s important to note that git diff by itself doesn’t show all changes made since your last commit – only changes that are still unstaged. This can be confusing, because if you’ve staged all of your changes, git diff will give you no output. For another example, if you stage the CONTRIBUTING.md file and then edit it, you can use git diff to see the changes in the file that are staged and the changes that are unstaged. If our environment looks like this: $ git add CONTRIBUTING.md $ echo '# test line' >> CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Now you can use git diff to see what is still unstaged $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e445e28..86b2f7c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -127,3 +127,4 @@ end main() ##pp Grit::GitRuby.cache_client.stats +# test line and git diff --cached to see what you’ve staged so far: $ git diff --cached diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3cb747f..e445e28 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -36,6 +36,10 @@ def main @commit.parents[0].parents[0].parents[0] end + run_code(x, 'commits 1') do + git.commits.size + end + run_code(x, 'commits 2') do log = git.commits('master', 15) log.size Note Git Diff in an External Tool We will continue to use the git diff command in various ways throughout the rest of the book. There is another way to look at these diffs if you prefer a graphical or external diff viewing program instead. If you run git difftool instead of git diff , you can view any of these diffs in software like Araxis, emerge, vimdiff and more. Run git difftool --tool-help to see what is available on your system. Committing Your Changes Now that your staging area is set up the way you want it, you can commit your changes. Remember that anything that is still unstaged – any files you have created or modified that you haven’t run git add on since you edited them – won’t go into this commit. They will stay as modified files on your disk. In this case, let’s say that the last time you ran git status , you saw that everything was staged, so you’re ready to commit your changes. The simplest way to commit is to type git commit : $ git commit Doing so launches your editor of choice. (This is set by your shell’s $EDITOR environment variable – usually vim or emacs, although you can configure it with whatever you want using the git config --global core.editor command as you saw in Memulai ). The editor displays the following text (this example is a Vim screen): # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Changes to be committed: # new file: README # modified: CONTRIBUTING.md # ~ ~ ~ ".git/COMMIT_EDITMSG" 9L, 283C You can see that the default commit message contains the latest output of the git status command commented out and one empty line on top. You can remove these comments and type your commit message, or you can leave them there to help you remember what you’re committing. (For an even more explicit reminder of what you’ve modified, you can pass the -v option to git commit . Doing so also puts the diff of your change in the editor so you can see exactly what changes you’re committing.) When you exit the editor, Git creates your commit with that commit message (with the comments and diff stripped out). Alternatively, you can type your commit message inline with the commit command by specifying it after a -m flag, like this: $ git commit -m "Story 182: Fix benchmarks for speed" [master 463dc4f] Story 182: Fix benchmarks for speed 2 files changed, 2 insertions(+) create mode 100644 README Now you’ve created your first commit! You can see that the commit has given you some output about itself: which branch you committed to ( master ), what SHA-1 checksum the commit has ( 463dc4f ), how many files were changed, and statistics about lines added and removed in the commit. Remember that the commit records the snapshot you set up in your staging area. Anything you didn’t stage is still sitting there modified; you can do another commit to add it to your history. Every time you perform a commit, you’re recording a snapshot of your project that you can revert to or compare to later. Skipping the Staging Area Although it can be amazingly useful for crafting commits exactly how you want them, the staging area is sometimes a bit more complex than you need in your workflow. If you want to skip the staging area, Git provides a simple shortcut. Adding the -a option to the git commit command makes Git automatically stage every file that is already tracked before doing the commit, letting you skip the git add part: $ git status On branch master Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md no changes added to commit (use "git add" and/or "git commit -a") $ git commit -a -m 'added new benchmarks' [master 83e38c7] added new benchmarks 1 file changed, 5 insertions(+), 0 deletions(-) Notice how you don’t have to run git add on the “CONTRIBUTING.md” file in this case before you commit. Removing Files To remove a file from Git, you have to remove it from your tracked files (more accurately, remove it from your staging area) and then commit. The git rm command does that, and also removes the file from your working directory so you don’t see it as an untracked file the next time around. If you simply remove the file from your working directory, it shows up under the “Changed but not updated” (that is, unstaged ) area of your git status output: $ rm grit.gemspec $ git status On branch master Changes not staged for commit: (use "git add/rm <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) deleted: grit.gemspec no changes added to commit (use "git add" and/or "git commit -a") Then, if you run git rm , it stages the file’s removal: $ git rm grit.gemspec rm 'grit.gemspec' $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) deleted: grit.gemspec The next time you commit, the file will be gone and no longer tracked. If you modified the file and added it to the index already, you must force the removal with the -f option. This is a safety feature to prevent accidental removal of data that hasn’t yet been recorded in a snapshot and that can’t be recovered from Git. Another useful thing you may want to do is to keep the file in your working tree but remove it from your staging area. In other words, you may want to keep the file on your hard drive but not have Git track it anymore. This is particularly useful if you forgot to add something to your .gitignore file and accidentally staged it, like a large log file or a bunch of .a compiled files. To do this, use the --cached option: $ git rm --cached README You can pass files, directories, and file-glob patterns to the git rm command. That means you can do things such as $ git rm log/\*.log Note the backslash ( \ ) in front of the * . This is necessary because Git does its own filename expansion in addition to your shell’s filename expansion. This command removes all files that have the .log extension in the log/ directory. Or, you can do something like this: $ git rm \*~ This command removes all files that end with ~ . Moving Files Unlike many other VCS systems, Git doesn’t explicitly track file movement. If you rename a file in Git, no metadata is stored in Git that tells it you renamed the file. However, Git is pretty smart about figuring that out after the fact – we’ll deal with detecting file movement a bit later. Thus it’s a bit confusing that Git has a mv command. If you want to rename a file in Git, you can run something like $ git mv file_from file_to and it works fine. In fact, if you run something like this and look at the status, you’ll see that Git considers it a renamed file: $ git mv README.md README $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README However, this is equivalent to running something like this: $ mv README.md README $ git rm README.md $ git add README Git figures out that it’s a rename implicitly, so it doesn’t matter if you rename a file that way or with the mv command. The only real difference is that mv is one command instead of three – it’s a convenience function. More important, you can use any tool you like to rename a file, and address the add/rm later, before you commit. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:22 |
https://git-scm.com/book/sl/v2/Veje-Git-Veje-na-kratko | Git - Veje na kratko About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Začetek 1.1 O nadzoru različic 1.2 Kratka zgodovina Gita 1.3 Kaj je Git? 1.4 Ukazna vrstica 1.5 Namestitev Gita 1.6 Prva nastavitev Gita 1.7 Pridobivanje pomoči 1.8 Povzetek 2. Osnove Git 2.1 Pridobivanje repozitorija Git 2.2 Snemanje sprememb v repozitorij 2.3 Pregled zgodovine potrditev 2.4 Razveljavljanje stvari 2.5 Delo z daljavami 2.6 Označevanje 2.7 Aliasi Git 2.8 Povzetek 3. Veje Git 3.1 Veje na kratko 3.2 Osnove vej in združevanja 3.3 Upravljanje vej 3.4 Poteki dela z vejami 3.5 Oddaljene veje 3.6 Ponovno baziranje 3.7 Povzetek 4. Git na strežniku 4.1 Protokoli 4.2 Pridobitev Gita na strežniku 4.3 Generiranje vaših javnih ključev SSH 4.4 Nastavitev strežnika 4.5 Prikriti proces Git 4.6 Pametni HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti gostovanja pri tretjih ponudnikih 4.10 Povzetek 5. Porazdeljeni Git 5.1 Porazdeljeni poteki dela 5.2 Prispevek k projektu 5.3 Vzdrževanje projekta 5.4 Povzetek 6. GitHub 6.1 Namestitev in konfiguracija računa 6.2 Prispevek k projektu 6.3 Vzdrževanje projekta 6.4 Upravljanje organizacije 6.5 Skriptni GitHub 6.6 Povzetek 7. Orodja Git 7.1 Izbira revizije 7.2 Interaktivno pripravljanje 7.3 Shranjevanje na varno (angl. stashing) in čiščenje 7.4 Podpisovanje vašega dela 7.5 Iskanje 7.6 Prepisovanje zgodovine 7.7 Demistifikacija ponastavitve 7.8 Napredno združevanje 7.9 Rerere 7.10 Razhroščevanje z Gitom 7.11 Podmoduli 7.12 Povezovanje v pakete 7.13 Zamenjava 7.14 Shramba poverilnic 7.15 Povzetek 8. Prilagoditev Gita 8.1 Konfiguracija Git 8.2 Atributi Git 8.3 Kljuke Git 8.4 Primer pravilnika, ki ga uveljavlja Git 8.5 Povzetek 9. Git in ostali sistemi 9.1 Git kot odjemalec 9.2 Migracija na Git 9.3 Povzetek 10. Notranjost Gita 10.1 Napeljava in keramika 10.2 Objekti Git 10.3 Reference Git 10.4 Packfiles (datoteke zmanjšanih podatkov) 10.5 Refspec 10.6 Protokoli prenosa 10.7 Vzdrževanje in obnovitev podatkov 10.8 Spremenljivke okolja 10.9 Povzetek A1. Dodatek A: Git v drugih okoljih A1.1 Grafični vmesniki A1.2 Git v Visual Studio A1.3 Git v Visual Studio Code A1.4 Git v IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git v Sublime Text A1.6 Git v Bashu A1.7 Git v Zsh A1.8 Git v Powershellu A1.9 Povzetek A2. Dodatek B: Vdelava Gita v vašo aplikacijo A2.1 Git v ukazni vrstici A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Dodatek C: Ukazi Git A3.1 Nastavitev in konfiguracija A3.2 Pridobivanje in ustvarjanje projektov A3.3 Osnove posnetkov A3.4 Veje in združevanje A3.5 Deljenje in posodabljanje projektov A3.6 Pregled in primerjava A3.7 Razhroščevanje A3.8 Popravljanje A3.9 E-pošta A3.10 Zunanji sistemi A3.11 Administracija A3.12 Orodja za sisteme napeljave 2nd Edition 3.1 Veje Git - Veje na kratko Skoraj vsak VCS ima neko obliko podpore razvejanja. Razvejanje pomeni, da se odmaknete od glavne razvojne linije in nadaljujete delo brez vpletanja v to glavno linijo. V mnogih orodjih VCS je to nekoliko drag postopek, ki od vas pogosto zahteva, da izdelate novo kopijo svojega direktorija izvorne kode, kar lahko traja dolgo časa za večje projekte. Nekateri se sklicujejo na Gitov model razvejanja kot na njegovo »najboljšo značilnost« in zagotovo postavi Git stran od preostale skupnosti VCS. Zakaj je tako poseben? Način razvejanja v Gitu je izredno lahek, kar omogoča skoraj trenutne operacije razvejanja in hitro preklapljanje med vejami naprej in nazaj. V primerjavi z mnogimi ostalimi VCS-ji, Git spodbuja poteke dela, ki pogosto ustvarijo in združijo veje, celo večkrat na dan. Razumevanje in osvojitev te lastnosti vam da zmogljivo in unikatno orodje ter lahko v celoti spremeni način vašega razvoja. Veje na kratko Za resnično razumevanje, na kakšen način Git dela razvejanje, se moramo vrniti korak nazaj in raziskati, kako Git shranjuje svoje podatke. Kakor se morda spomnite iz Kaj je Git? , Git ne shranjuje podatkov kot serije skupkov sprememb ali razlik, vendar namesto tega kot serije posnetkov . Ko naredite potrditev, Git shrani objekt potrditve, ki vsebuje kazalec k posnetku vsebine, ki ste jo dali v področje priprave. Ta objekt vsebuje tudi avtorjevo ime in e-pošto, sporočilo, ki ste ga vpisali, in kazalce k potrditvi ali potrditvam, ki so neposredno prišle pred to potrditvijo (njeno nadrejeno ali nadrejene): brez nadrejenih za začetno potrditev, ena nadrejena za običajno potrditev in več nadrejenih za potrditev, ki je rezultat združevanja dveh ali več vej. Da to vizualiziramo, predpostavimo, da imate direktorij, ki vsebuje tri datoteke in vse daste v področje priprave in nato potrdite. Dajanje datotek v področje priprave izračuna kontrolno vsoto za vsako (zgoščena vrednost SHA-1, ki smo jo omenili v Kaj je Git? ), shrani to različico datoteke v repozitorij Git (Git se sklicuje nanje kot blob ) in doda to kontrolno vsoto v področje priprave: $ git add README test.rb LICENSE $ git commit -m 'Initial commit' Ko ustvarite potrditev s pogonom git commit , Git preveri kontrolne vsote za vsak poddirektorij (v tem primeru samo vrhnji direktorij projekta) in jih shrani kot drevesni objekt v repozitorij Git. Git nato ustvari objekt potrditve, ki ima metapodatke in kazalec na vrhnje drevo projekta, da lahko ponovno ustvari posnetek, ko je treba. Vaš repozitorij Git sedaj vsebuje pet objektov: tri blobe (vsak predstavlja vsebino ene izmed treh datotek), eno drevo , ki izpisuje vsebino direktorija in določa, katera imena datotek so shranjena kot blobi, in eno potrditev s kazalcem na to vrhnje drevo ter vse metapodatke potrditve. Slika 9. Potrditev in njeno drevo Če naredite nekaj sprememb in nato ponovno potrdite, bo naslednja potrditev shranila kazalec k potrditvi, ki je prišla takoj pred tem. Slika 10. Potrditve in njihove nadrejene Veja v Gitu je enostavno lahek prenosni kazalec k eni od teh potrditev. Privzeto ime veje v Gitu je master . Ko začnete delati potrditve, imate dano vejo master , ki kaže na zadnjo potrditev, ki ste jo naredili. Vsakič, ko potrdite, se kazalec veje master avtomatsko premakne naprej. Opomba Veja »master« v Gitu ni posebna veja. Je točno taka kot katerakoli druga veja. Edini razlog, da ima skoraj vsak repozitorij eno, je, da jo ukaz git init privzeto ustvari in večina ljudi se je ne trudi spremeniti. Slika 11. Veja in njena zgodovina potrditev Ustvarjanje nove veje Kaj se zgodi, ko ustvarite novo vejo? No, to naredi za vas nov kazalec, ki se premika okoli. Recimo, da želite ustvariti novo vejo imenovano testing . To naredite z ukazom git branch : $ git branch testing To ustvari nov kazalec na isto potrditev, na kateri ste trenutno. Slika 12. Dve veji, ki kažeta na isto serijo potrditev Kako Git ve, na kateri veji ste trenutno? Ima poseben kazalec imenovan HEAD . Bodite pozorni, saj je to precej drugačno od zasnove HEAD v drugih VCS-jih, ki ste ga morda vajeni, kot sta Subversion ali CVS. V Gitu je to kazalec na lokalno vejo, kjer ste trenutno. V tem primeru ste še vedno na master . Ukaz git branch je samo ustvaril novo vejo, ni pa tudi preklopil na to vejo. Slika 13. HEAD, ki kaže na vejo To lahko enostavno pogledate, da poženete ukaz git log , ki vam prikaže, kam kazalci veje kažejo. Ta možnost se imenuje --decorate . $ git log --oneline --decorate f30ab (HEAD -> master, testing) Add feature #32 - ability to add new formats to the central interface 34ac2 Fix bug #1328 - stack overflow under certain conditions 98ca9 Initial commit Vidite lahko veji master in testing , ki sta ravno tam zraven potrditve f30ab . Preklapljanje med vejami Da preklopite na obstoječo vejo, poženete ukaz git checkout . Preklopimo na novo vejo testing : $ git checkout testing To prestavi HEAD , da kaže na vejo testing . Slika 14. HEAD kaže na trenutno vejo Kaj je pomembnost tega? Torej naredimo drugo potrditev: $ vim test.rb $ git commit -a -m 'Make a change' Slika 15. Veja HEAD se premakne naprej, ko je narejena potrditev To je zanimivo, ker se je sedaj vaša veja testing premaknila naprej, vendar vaša veja master še vedno kaže na potrditev, kjer ste bili, ko ste pognali git checkout , da ste preklopili veje. Preklopimo nazaj na vejo master : $ git checkout master Opomba git log ne prikaže vsakič vseh vej Če bi sedaj pognali git log , bi se morda spraševali, kam je šla veja testing , ki ste jo pravkar ustvarili, saj je ne bi bilo videti v izpisu. Veja ni izginila; Git preprosto ne ve, da vas ta veja zanima, in poskuša prikazati tisto, kar misli, da vas zanima. Drugače povedano, privzeto bo git log prikazal zgodovino sprememb pod vejo, ki jo imate trenutno izvlečeno. Da bi prikazali zgodovino sprememb za želeno vejo, jo morate izrecno določiti: git log testing . Za prikaz vseh vej dodajte --all ukazu git log . Slika 16. HEAD se premakne, ko izvlečete Ta ukaz je naredil dve stvari. Premaknil je kazalec HEAD nazaj na točko veje master in povrnil datoteke v vašem delovnem direktoriju nazaj na posnetek, kamor master kaže. To tudi pomeni, da se bodo spremembe, ki jih delate od te točke naprej, razlikovale od starejše različice projekta. V osnovi presname nazaj delo, ki ste ga naredili na vaši veji testing , tako da lahko greste v drugačno smer. Opomba Preklapljanje vej spremeni datoteke v vašem delovnem direktoriju Pomembno je opozoriti, da ko v Gitu preklopite veje, se datoteke v vašem delovnem direktoriju spremenijo. Če ste preklopili na starejšo vejo, bo vaš delovni direktorij prestavljen nazaj, da je videti tako, kot je prejšnjič, ko ste naredili potrditev na tisti veji. Če Git tega ne more narediti gladko, vam sploh ne bo dovolil preklopiti. Naredimo nekaj sprememb in ponovno potrdimo: $ vim test.rb $ git commit -a -m 'Make other changes' Sedaj se je zgodovina vašega projekta spremenila (glejte sliko Različna zgodovina ). Ustvarili in preklopili ste na vejo, naredili nekaj dela na njej in nato preklopili nazaj na svojo glavno vejo ter naredili drugo delo. Obe od teh sprememb sta izolirani v ločenih vejah: lahko preklopite nazaj in naprej med vejama in ju združite skupaj, ko ste pripravljeni. In vse to ste naredili z enostavnimi ukazi branch , checkout in commit . Slika 17. Različna zgodovina To lahko enostavno pogledate tudi z ukazom git log . Če poženete git log --oneline --decorate --graph --all , bo izpisal zgodovino vaših potrditev, prikazal, kje so kazalci vej in kako se je vaša zgodovina spremenila. $ git log --oneline --decorate --graph --all * c2b9e (HEAD, master) Make other changes | * 87ab2 (testing) Make a change |/ * f30ab Add feature #32 - ability to add new formats to the central interface * 34ac2 Fix bug #1328 - stack overflow under certain conditions * 98ca9 Initial commit of my project Ker je veja v Gitu dejansko enostavna datoteka, ki vsebuje 40 znakovno kontrolno vsoto SHA-1 potrditve, kamor kaže, so veje ugodne za izdelavo in uničenje. Ustvarjanje nove veje je hitro in enostavno kakor napisati 41 bajtov v datoteko (40 znakov in nova vrstica). To je v močnem nasprotju z načinom večine vej starejših orodij VCS, ki vključujejo kopiranje vseh datotek projekta v drug direktorij. To lahko vzame nekaj sekund ali celo minut, odvisno od velikosti projekta, kjer pa je proces v Gitu vedno takojšnji. Tudi ker snemamo nadrejene, ko potrjujemo, da najdemo ustrezno združevalno osnovo, saj je združevanje za nas avtomatično izvedeno in ga je v splošnem zelo enostavno narediti. Te lastnosti pomagajo spodbujati razvijalce, da pogostokrat ustvarijo in uporabijo veje. Poglejmo, zakaj bi to morali tako narediti. Opomba Ustvarjanje nove veje in istočasno preklapljanje nanjo Običajno je narediti novo vejo in istočasno želeti preklopiti nanjo — to se lahko naredi v eni operaciji z git checkout -b <newbranchname> . Opomba Od različice Git 2.23 naprej lahko uporabite git switch namesto git checkout , da: Preklopite na obstoječo vejo: git switch testing-branch Ustvarite novo vejo in nanjo preklopite: git switch -c new-branch . Zastavica -c pomeni »ustvarjanje« (angl. create ), lahko pa uporabite tudi polno ime zastavice: --create . Se vrnete na vašo prejšnjo izvlečeno vejo: git switch - . prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:22 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=bg | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상 | 2026-01-13T09:29:22 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_GT | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상 | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=ka | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 | 2026-01-13T09:29:23 |
https://t.me/s/rsksmartcontracts | Rootstock Official Announcement Channel – Telegram Rootstock Official Announcement Channel @rsksmartcontracts 1.2K subscribers 1.74K photos 80 videos 13 files 2.44K links Rootstock Official Communications Channel Download Telegram About Blog Apps Platform Join Rootstock Official Announcement Channel 1.2K subscribers Rootstock Official Announcement Channel 📚 The latest #DeveloperDeepDive unravels the technique of free and instant contract calls on the Rootstock network! A must-read for Oracle providers and those needing frequent data checks from smart contracts. 👉 https://medium.com/@gomezdn/how-to-do-a-contract-call-in-rsk-network-6879990fda54 385 views 11:00 Rootstock Official Announcement Channel Have you tried the latest version of the 2-way peg yet? 🔁 Seamlessly and securely move #BTC in and out of Rootstock Use your #Bitcoin to interact with exciting dApps like Sovryn and Money on Chain 🚀 https://app.2wp.rootstock.io/ 👍 2 361 views 17:57 Rootstock Official Announcement Channel Want to learn about blockchain interconnectivity? Tune in to the next space Rootstock x Router Protocol! 📆 Jul 28, 15:30 UTC 🎙 Ashutosh Sahoo (CMO at Router Protocol) 🎙 Priyeshu Garg (Co-founder at Router Protocol) 🎙 @Art_of_Tomas (Rootstock Ambassador) https://twitter.com/i/spaces/1YqJDoopvlOGV 👍 1 378 views edited 17:24 Rootstock Official Announcement Channel 💰 🔄 The average fee for sending a traditional remittance is 6.2%. Using #Rootstock , that cost drops to a mere 0.01%-0.10%. Explore how blockchain is revolutionizing remittances in the RIF Remittance report 👉 https://www.rifos.org/remittance-report/ 👍 3 433 views 18:25 Rootstock Official Announcement Channel Want to learn about blockchain interconnectivity? Tune in to the next space Rootstock x Router Protocol! 📆 Jul 28, 15:30 UTC 🎙 Ashutosh Sahoo (CMO at Router Protocol) 🎙 Priyeshu Garg (Co-founder at Router Protocol) 🎙 @Art_of_Tomas (Rootstock Ambassador) https://twitter.com/i/spaces/1YqJDoopvlOGV 645 views 00:32 Rootstock Official Announcement Channel 🚀 #Rootstock is now available on Exodus! 🚀 The industry-leading Exodus wallet allows you to manage over 260 crypto assets and NFTs across multiple networks. Check out their in-depth guide on how to make use of Rootstock with Exodus 👇 https://www.exodus.com/support/article/2898-rootstock-ecosystem 🔥 1 1.1K views 17:30 Rootstock Official Announcement Channel Have you tried the latest version of the 2-way peg yet? 🔁 Seamlessly and securely move #BTC in and out of Rootstock Use your #Bitcoin to interact with exciting dApps like Sovryn and Money on Chain 🚀 🔥 1 465 views 18:50 Rootstock Official Announcement Channel Want to learn about blockchain interconnectivity? Tune in to the next Rootstock x Router Protocol Twitter space! We have a special guest this Friday, Pei Chen! 📆 Jul 28, 15:30 UTC 🎙 Priyeshu Garg (Co-founder at Router Protocol) 🎙 Pei Chen (Chief Growth Officer at #IOVLabs ) 🎙 Ashutosh Sahoo (CMO at Router Protocol) 🎙 @Art_of_tomas (Rootstock Ambassador) https://twitter.com/i/spaces/1YqJDoopvlOGV 👍 1 470 views 21:35 Rootstock Official Announcement Channel 0:10 This media is not supported in your browser VIEW IN TELEGRAM 📢 One step closer towards bringing #Rootstock to the masses. Forward Protocol has integrated with Rootstock, now, you can deploy your customized dApps using Forward’s templates and seamlessly apply them on the Rootstock network. #SmartContracts #BitcoinDeFi 🌐 Visit them and try them out on https://forwardprotocol.io/ 🔥 2 533 views 16:05 Rootstock Official Announcement Channel 📚 Developing on Rootstock? Have a smart contract a looking to verify it? Look no further, the latest #DeveloperDeepDive explains why a smart contract should be verified, how to verify and check a smart contract verification status. 👉 https://medium.com/@nicolas.vargas_35315/how-to-verify-a-contract-in-rsk-network-in-a-nutshell-9ad58b52650c 605 views 21:04 Rootstock Official Announcement Channel 💸 🔄 Looking to save on remittance fees? The average charge for traditional transfers is 6.2%, whereas #Rootstock can reduce that to as low as 0.01%-0.10%. Uncover the power of blockchain in reshaping remittances in the RIF Remittance report 👉 https://www.rifos.org/remittance-report/ 647 views 16:38 Rootstock Official Announcement Channel 👨💻 Are you looking to get started building your first dApp? @hackernoon 's recent article lists the reasons to choose Rootstock, make sure to check the dev course within to get started! Follow the link below & build your dream dApp on the most secure smart contracts platform. 🏗️ https://hackernoon.com/defi-on-bitcoin-part-1-a-guide-to-building-dapps-with-rootstock 715 views 20:19 Rootstock Official Announcement Channel 🚀 Crypto enthusiasts, trading gurus and everyone in between, make sure to join tomorrow's twitter space discussing Sovryn's latest trading challenge. 🎙️ @ArtOfTomas (Rootstock Ambassador) Anthony Sánchez (Community Manager at #IOVLabs ) Edan Yago (Co-founder at Sovryn) https://twitter.com/i/spaces/1vOGwMjoVkVxB 🔥 1 797 views 18:57 Rootstock Official Announcement Channel 🚧 🛠️ Tomorrow, Rootstock's 2-Way Peg App website will be temporarily unavailable due to a scheduled update. 📅 14:00 UTC The App will experience a downtime of ~2 hours. ✨ This process will bring bug fixes to the app and will not affect the Rootstock Network. 942 views 02:01 Rootstock Official Announcement Channel 📣 PSA; The Rootstock 2-Way Peg App website will be temporarily unavailable due to a scheduled maintenance at 14:00 (UTC) and is expected to be back online by approximately 16:00 (UTC). This process will bring bug fixes to the app and will not affect the Rootstock network's normal operations. 1.07K views 13:10 Rootstock Official Announcement Channel Rootstock Official Announcement Channel 📣 PSA; The Rootstock 2-Way Peg App website will be temporarily unavailable due to a scheduled maintenance at 14:00 (UTC) and is expected to be back online by approximately 16:00 (UTC). This process will bring bug fixes to the app and will not affect the Rootstock… This update has completed without issues. The 2wp app website can now be used normally. Visit the 2wp app website here : https://app.2wp.rootstock.io 1.23K views 16:26 Rootstock Official Announcement Channel 🚀 Enhance your #DeFi development with cutting-edge blockchain infrastructure! Learn how to optimize blockchain infrastructure and level up your skills! 💪 👉 Read now: https://medium.com/@ivegabr/optimizing-blockchain-infrastructure-adding-a-dedicated-api-service-for-rpc-requests-342539861a78 1.77K views 00:47 Rootstock Official Announcement Channel 🌎 ✨ Want to hear groundbreaking insights by the people leading innovation in web3? join this Friday's twitter space to see 🎙 Daniel Fogg, CEO at #IOVLabs & 🎙 JP Richardson, CEO at Exodus Delve into what the future holds for crypto, can't miss it! 🔗 👇 https://twitter.com/i/spaces/1ZkKzXRaZjNJv 2.24K views 20:24 Rootstock Official Announcement Channel 🔧 💻 Looking to code your way into DeFi? Check out the latest “Mastering Rootstock” DevEx guide and get started 👀 Expert Nicolas Vargas unveils how to create an upgradeable UUPS Smart Contract on the #Rootstock network. 👉 https://medium.com/@nicolas.vargas_35315/how-to-create-an-upgradeable-smart-contract-using-uups-5743489b713b 2.61K views 22:02 Rootstock Official Announcement Channel We’ve unlocked a big milestone in the Rootstock network with regard to a PowPeg composition change. This modification is set to become effective at block #5,568,002, scheduled for activation on Saturday, August 19, 2023 (estimated). What does this mean? 👇 🔹 The Luxor Team joins as a new member of the PowPeg 🔹 The PowPeg setup for ConstataEu has been upgraded to support firmware attestation. One thing to consider is that the Bitcoin PowPeg Address is changing. Make sure to verify the deposit address before initiating any PowPeg peg-in transaction, this will ensure the safety of funds and mitigate any potential risks. ❤ 4 👍 3 👏 1 🕊 1 3.29K views 19:41 | 2026-01-13T09:29:23 |
http://dig.ccmixter.org/credits#credits | dig.ccMixter Credits Toggle navigation donate to keep this library available! licenses tag search featured music for film music for games free for commercial use royalty free licensed Credits coding victor stone design Rendi Sapurtra oan vintage mic image holmes palacios jr. drummer wim vandenbussche beach roman iakoubtchik awesome testing tools browser stack invaluable contributors alex kara emily michael Here Licenses Privacy Terms Donate(!) Credits There Everywhere Twitter YouTube Vimeo Facebook Instagram Resources GitHub Query API Forums Contact | 2026-01-13T09:29:23 |
https://git-scm.com/book/sl/v2/Osnove-Git-Aliasi-Git | Git - Aliasi Git About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Začetek 1.1 O nadzoru različic 1.2 Kratka zgodovina Gita 1.3 Kaj je Git? 1.4 Ukazna vrstica 1.5 Namestitev Gita 1.6 Prva nastavitev Gita 1.7 Pridobivanje pomoči 1.8 Povzetek 2. Osnove Git 2.1 Pridobivanje repozitorija Git 2.2 Snemanje sprememb v repozitorij 2.3 Pregled zgodovine potrditev 2.4 Razveljavljanje stvari 2.5 Delo z daljavami 2.6 Označevanje 2.7 Aliasi Git 2.8 Povzetek 3. Veje Git 3.1 Veje na kratko 3.2 Osnove vej in združevanja 3.3 Upravljanje vej 3.4 Poteki dela z vejami 3.5 Oddaljene veje 3.6 Ponovno baziranje 3.7 Povzetek 4. Git na strežniku 4.1 Protokoli 4.2 Pridobitev Gita na strežniku 4.3 Generiranje vaših javnih ključev SSH 4.4 Nastavitev strežnika 4.5 Prikriti proces Git 4.6 Pametni HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti gostovanja pri tretjih ponudnikih 4.10 Povzetek 5. Porazdeljeni Git 5.1 Porazdeljeni poteki dela 5.2 Prispevek k projektu 5.3 Vzdrževanje projekta 5.4 Povzetek 6. GitHub 6.1 Namestitev in konfiguracija računa 6.2 Prispevek k projektu 6.3 Vzdrževanje projekta 6.4 Upravljanje organizacije 6.5 Skriptni GitHub 6.6 Povzetek 7. Orodja Git 7.1 Izbira revizije 7.2 Interaktivno pripravljanje 7.3 Shranjevanje na varno (angl. stashing) in čiščenje 7.4 Podpisovanje vašega dela 7.5 Iskanje 7.6 Prepisovanje zgodovine 7.7 Demistifikacija ponastavitve 7.8 Napredno združevanje 7.9 Rerere 7.10 Razhroščevanje z Gitom 7.11 Podmoduli 7.12 Povezovanje v pakete 7.13 Zamenjava 7.14 Shramba poverilnic 7.15 Povzetek 8. Prilagoditev Gita 8.1 Konfiguracija Git 8.2 Atributi Git 8.3 Kljuke Git 8.4 Primer pravilnika, ki ga uveljavlja Git 8.5 Povzetek 9. Git in ostali sistemi 9.1 Git kot odjemalec 9.2 Migracija na Git 9.3 Povzetek 10. Notranjost Gita 10.1 Napeljava in keramika 10.2 Objekti Git 10.3 Reference Git 10.4 Packfiles (datoteke zmanjšanih podatkov) 10.5 Refspec 10.6 Protokoli prenosa 10.7 Vzdrževanje in obnovitev podatkov 10.8 Spremenljivke okolja 10.9 Povzetek A1. Dodatek A: Git v drugih okoljih A1.1 Grafični vmesniki A1.2 Git v Visual Studio A1.3 Git v Visual Studio Code A1.4 Git v IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git v Sublime Text A1.6 Git v Bashu A1.7 Git v Zsh A1.8 Git v Powershellu A1.9 Povzetek A2. Dodatek B: Vdelava Gita v vašo aplikacijo A2.1 Git v ukazni vrstici A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Dodatek C: Ukazi Git A3.1 Nastavitev in konfiguracija A3.2 Pridobivanje in ustvarjanje projektov A3.3 Osnove posnetkov A3.4 Veje in združevanje A3.5 Deljenje in posodabljanje projektov A3.6 Pregled in primerjava A3.7 Razhroščevanje A3.8 Popravljanje A3.9 E-pošta A3.10 Zunanji sistemi A3.11 Administracija A3.12 Orodja za sisteme napeljave 2nd Edition 2.7 Osnove Git - Aliasi Git Aliasi Git Preden gremo na naslednje poglavje, želimo predstaviti lastnost, ki lahko naredi vašo izkušnjo Git enostavnejšo, lažjo in bolj poznano: aliasi. Zaradi jasnosti se ne bomo več sklicevali nanje kasneje v knjigi, vendar bi verjetno morali vedeti, kako jih uporabljati, če boste Git redno uporabljali. Git ne sklepa avtomatsko na podlagi vašega ukaza, če ga vpišete le delno. Če ne želite vpisovati celotnega besedila vsakega ukaza Git, lahko enostavno nastavite alias za vsak ukaz z uporabo git config . Tu je nekaj primerov, ki jih morda želite nastaviti: $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status To pomeni, da na primer, namesto da vpisujete git commit , lahko vpišete zgolj git ci . Ko nadaljujete uporabo Gita, boste verjetno pogosto uporabljali tudi ostale ukaze; ne odlašajte z izdelavo novih aliasov. Ta tehnika je lahko zelo uporabna pri izdelavi ukazov, za katere menite, da bi morali obstajati. Na primer, da popravite problem uporabnosti, na katerega ste naleteli z vračanjem datoteke iz področja priprave, lahko Gitu dodate svoj alias, da vrnete datoteke iz področja priprave: $ git config --global alias.unstage 'reset HEAD --' To naredi sledeča ukaza enakovredna temu: $ git unstage fileA $ git reset HEAD -- fileA To je videti bolj jasno. Pogosto se doda tudi ukaz last na naslednji način: $ git config --global alias.last 'log -1 HEAD' Na ta način lahko enostavneje pogledate zadnjo potrditev: $ git last commit 66938dae3329c7aebe598c2246a8e6af90d04646 Author: Josh Goebel <dreamer3@example.com> Date: Tue Aug 26 19:48:51 2008 +0800 Test for current head Signed-off-by: Scott Chacon <schacon@example.com> Kot lahko vidite, Git enostavno zamenja novi ukaz s čimer koli, za kar mu zanj nastavite alias. Vendar morda boste želeli pognati zunanji ukaz namesto podukaza Git. V tem primeru začnete ukaz z znakom ! . To je uporabno, če pišete svoja lastna orodja, ki delajo z repozitorijem Git. Demonstriramo lahko dodajanje aliasa git visual , ki požene gitk : $ git config --global alias.visual '!gitk' prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://www.fuse.io/es/node-sale | Node Sale Fuse Turns Six: Future-Proofing the Entire Network Network Intro to Fuse EVM-compatible, Layer-2 Blockchain Get Fuse Explore the ways to get the native Fuse Network token Ecosystem Web3 Tools for Business Ignite Apply for Funding & Grants Tools Staking Stake FUSE for Rewards Bridge Bridge Assets To & From Fuse Safe Leading Platform to Manage Digital Assets Products Fuse Ember Integrate Web3 in Minutes Edison AI Agent Integrate Web3 in Minutes Gaming Coming soon... FuseBox Integrate Web3 in Minutes Case Studies Real World Case Studies Mystic Valley Freedom Wallet Sanduk Zneakrz Developers Documentation Build on Fuse RPC Providers Build crypto apps that scale Fuse Explorer Query Transactions & Activity Network Status Network performance and status Developers Documentation Build on Fuse RPC Providers Build crypto apps that scale Fuse Explorer Query Transactions & Activity Network Status Network performance and status Tools Ecosystem Web3 Tools for Business NFTs Mint Digital Collectibles on Artrific Community Support & Contribute Telegram Youtube LinkedIn Twitter Github Discord Governance Shape the Future of Fuse About Fuse Blog Latest news and updates Brand Kit Brand assets Jobs Explore opportunities Network Products Developers Ecosystem About Intro to Fuse EVM-compatible, Layer-2 Blockchain Ignite Apply for Funding & Grants Staking Stake FUSE for Rewards Bridge Bridge Assets To & From Fuse Safe Leading Platform to Manage Digital Assets Edison AI Agent Integrate Web3 in Minutes FuseBox Integrate Web3 in Minutes Case studies Real World Case Studies Real world case studies Mystic Valley Ticketing and Event Payments Freedom Wallet Bridging RWAs for Businesses Sanduk Send and receive digital dollars Zneakrz Frictionless e-commerce Documentation Learn about Fuse and get started with guides and tools for building on Fuse RPC Providers Build crypto apps that scale Fuse Explorer Query Transactions & Activity Network Status Network performance and status Get Started Quick Start Fuse Basics FuseBox Tutorials Explore our APIs Smart Wallets API Trade API Notifications API GraphQL API Ecosystem Web3 Tools for Business Community Support & Contribute Governance Shape the Future of Fuse Telegram Youtube LinkedIn Github Twitter Discord Get Fuse Explore the ways to get the native Fuse Network token Fuse Blog Latest news and updates Brand Kit Brand assets Jobs Explore opportunities EN FR JP CN Docs Ember Points Fuse Console The Fuse Ember Node Sale Is Live! As we prepare to launch zkEVM-powered Fuse Ember L2 in Q2 2025, we’re offering 12,000 exclusive node licenses. Nodes will secure the network, processing up to 9,000 transactions per second, while earning a share of ecosystem fees and early adopter incentives. As a node operator, you’ll also play a key role in governance towards the future of blockchain-powered business payments. It’s a chance to own a stake in a growing ecosystem built for real-world adoption. Once these 12,000 licenses are gone, the window closes. Buy Ember Node Find out more about Fuse Ember Global Payments. Effortless Integration. 1 9000 TPS and 0.0001$ fees 2 AI agents for businesses 3 ZK payments for mainstream usage 4 Vertically integrated open source stack 5 Full Mobile compatibility 6 Recurring payments The blockchain for businesses 9000 TPS and 0.0001$ fees AI agents for businesses ZK payments for mainstream usage Vertically integrated open source stack Full Mobile compatibility Recurring payments Node Sale Pricing Node sale participants will purchase NFTs that grant them a share of Fuse Ember emissions and fees, plus governance voting rights. The NFT will be non-transferable for the first year. The first 2,000 nodes will be sold at a discounted price of $315, with successive tranches rising to $2,500. Node sale and tiers information Benefits Of Running An Ember Node Earn a share of 10% of network fees and FuseBox subscriptions Receive additional yield from LST, LRT, and RWA tokens staked on the platform. Receive a percentage of 42 million FUSE Collect airdrop rewards for three years, with 20 million FUSE allocated for year 1 and no vesting schedule. Early tiers ensure a greater ROI Total rewards are split evenly across all active nodes. Tier 1 nodes are exclusively limited to FUSE holders Tier 1 participants will be able to purchase a maximum of 100 nodes each. Community-driven governance Play your part in shaping the future of the Fuse network. Buybacks using 10% of node sale funds Locking Treasury funds and staking FUSE will further help to drive a deflationary economy. Get whitelisted now! Enter your ERC-20 wallet address to be whitelisted and email to be notified when the sale starts. Join Whitelist Thanks, we’ll keep you updated! Oops! Something went wrong while submitting the form. Secure Your Stake In The Future Of Fuse Ember L2 Unlock a world of rewards, participate in governance, and enjoy the benefits of our revolutionary business payments infrastructure. It's time to take your place at the forefront of innovation. Buy Ember Node Backers and partners Big vision requires long term partners Read more about our Plans Fuse migration to Fuse Ember and node sale details and tiers New proposed tokenomics for the transition New proposed staking model Frequently Asked Questions How to purchase a Node License? The process will consist of 3 stages: Whitelist application: users can register for whitelist to get priority access. Whitelisting will start in November 2024. Leave your email to be notified. Whitelist Sale: only whitelisted users can participate in the sale. Nodes are sold on first come, first served basis. Public Sale: the sale is open to all users. What is whitelist? This is a list of wallets that have expressed their desire to buy a node before the sale starts. These participants will receive priority access to buy the node before the public sale starts. What is a Node License and why does it matter? When you participate in the Node Sale, you’re purchasing a Node License : an NFT that grants you the right to operate a Data Availability (DA) Node on Fuse Ember. These nodes play a vital role in the network’s architecture, handling tasks like: Securing data availability Processing transactions efficiently Ensuring the network remains fast, secure, and decentralized If you don’t want to run a node yourself, you can delegate your license to an active operator and still earn passive rewards while they handle the operations. How to get whitelisted? A whitelisting form will be published on this page in November 2024. Leave your email to be notified. What are the rewards and incentives for Node Operators? Node operators are key players in the Fuse Ember ecosystem, and the rewards reflect that: Share in 30% of network fees and FuseBox subscriptions Receive a share of rewards from staked Real-World Assets (RWAs) and Liquid Staking Tokens (LSTs) Voting power to help shape protocol decisions The earlier you join, the greater your rewards, thanks to tiered pricing that favors early participants. Does entering the whitelist guarantee that I can definitely purchase a node? No. The priority sale of nodes to whitelisted participants will be on a first come, first served basis.If all nodes allocated to whitelisted users are sold out, you will be able to participate in the public sale. Leave your email to be notified. How do I participate in the Node Sale? Visit our Node Sale homepage: https://www.fuse.io/node-sale . Register on the NodeOps Console: https://console.nodeops.xyz/bootstrap-event/fuse . Prepare Your Funds: Ensure you have FUSE, USDC, USDT, or wETH on the Fuse network. You can bridge assets to Fuse using https://console.fuse.io/bridge . Purchase your Node License. Your NFT will be non-transferable for the first year. Start earning: Operate your DA Node or delegate it to an active operator. How many nodes will be available in total? A total of 12,000 nodes will be available for purchase in the Fuse Ember network. How much do nodes cost? Nodes are priced in tiers, rising in price as each tier sells out. Early adopters are rewarded with a higher potential ROI. Tier Allocation Table Tier Allocation Price (USD) T1 2,000 $350 T2 1,300 $600 T3 1,250 $850 T4 1,125 $1,000 T5 1,100 $1,250 T6 1,075 $1,500 T7 1,065 $1,750 T8 1,055 $2,000 T9 1,030 $2,250 T10 1,000 $2,500 Can I buy multiple nodes? Yes, each participant can buy any number of nodes. Which jurisdictions can participate in the Node Sale? Residents from FATF-sanctioned jurisdictions (including North Korea, Iran, and Myanmar) are prohibited from participating. Additional restrictions may apply in other regions. Please check whether you are eligible. How will the node licenses be distributed? The node license is an NFT. NFTs will be sent to the buyer's wallet immediately after the license is paid. How will node licenses be distributed? The node license is an NFT. NFTs will be sent to the buyer's wallet immediately after the license fee is paid. NFTs cannot be transferred for the first year. How to run a node? Running and managing nodes on the Fuse Ember network will be done through the NodeOps console. How do I run a node? Running and managing nodes on the Fuse Ember network will be carried out through the NodeOps console . How can I delegate my NFT license? If you don’t want to run your own node, you can delegate your license to another node operator using the Fuse Ember Delegation portal . YouTube Github Twitter Telegram Discord Docs Getting started Fuse Network Mobile Stack Voltage Finance Web3 Glossary Charge Under the hood Explorer Documentation Fuse Staking Governance Service Status General Brand Kits Jobs Ambassador Program FAQ Subscribe to our newsletter © 2024 Fuse. All Rights Reserved | 2026-01-13T09:29:23 |
https://git-scm.com/book/gr/v2/%ce%9e%ce%b5%ce%ba%ce%b9%ce%bd%cf%8e%ce%bd%cf%84%ce%b1%cf%82-%ce%bc%ce%b5-%cf%84%ce%bf-Git-%ce%97-%ce%b3%cf%81%ce%b1%ce%bc%ce%bc%ce%ae-%ce%b5%ce%bd%cf%84%ce%bf%ce%bb%cf%8e%ce%bd | Git - Η γραμμή εντολών About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Ξεκινώντας με το Git 1.1 Σχετικά με τον έλεγχο εκδόσεων 1.2 Σύντομο ιστορικό του Git 1.3 Τι είναι το Git; 1.4 Η γραμμή εντολών 1.5 Εγκατάσταση του Git 1.6 Ρύθμιση του Git για πρώτη φορά 1.7 Χρησιμοποιώντας τη βοήθεια 1.8 Ανακεφαλαίωση 2. Τα θεμελιώδη στοιχεία του Git 2.1 Απόκτηση αποθετηρίου Git 2.2 Καταγραφή αλλαγών στο αποθετήριο 2.3 Χρησιμοποιώντας το ιστορικό υποβολών 2.4 Αναιρέσεις (undoing) 2.5 Δουλεύοντας με απομακρυσμένα αποθετήρια 2.6 Ετικέτες 2.7 Συντομεύεσεις στο Git 2.8 Ανακεφαλαίωση 3. Διακλαδώσεις στο Git 3.1 Οι κλάδοι με λίγα λόγια 3.2 Βασικές έννοιες διακλαδώσεων και συγχωνεύσεων 3.3 Διαχείριση κλάδων 3.4 Ροές εργασίας με διακλαδώσεις 3.5 Απομακρυσμένοι κλάδοι 3.6 Αλλαγή βάσης (rebasing) 3.7 Ανακεφαλαίωση 4. Το Git στον διακομιστή 4.1 Τα πρωτόκολλα 4.2 Εγκατάσταση του Git σε διακομιστή 4.3 Δημιουργία δημόσιου κλειδιού SSH 4.4 Στήσιμο του διακομιστή 4.5 Δαίμονες του Git 4.6 Έξυπνο HTTP 4.7 GitWeb 4.8 GitLab 4.9 Επιλογές φιλοξενίας από τρίτους 4.10 Ανακεφαλαίωση 5. Κατανεμημένο Git 5.1 Κατανεμημένες ροές εργασίας 5.2 Συνεισφέροντας σε ένα έργο 5.3 Συντήρηση ενός έργου 5.4 Ανακεφαλαίωση 6. GitHub 6.1 Δημιουργία λογαριασμού και ρύθμισή του 6.2 Συνεισφορά σε έργο 6.3 Συντήρηση ενός έργου 6.4 Διαχείριση οργανισμώνν 6.5 Συγγραφή script στο GitHub 6.6 Ανακεφαλαίωση 7. Εργαλεία του Git 7.1 Επιλογή αναθεώρησης 7.2 Διαδραστική εργασία με το στάδιο καταχώρισης 7.3 Αποθέματα και Καθαρισμός 7.4 Υπογραφή της δουλειάς μας 7.5 Αναζήτηση 7.6 Η ιστορία ξαναγράφεται 7.7 Απομυθοποίηση της reset 7.8 Προχωρημένη Συγχώνευση 7.9 Rerere 7.10 Αποσφαλμάτωση με το Git 7.11 Υπομονάδες 7.12 Δεμάτιασμα δεδομένων 7.13 Replace 7.14 Αποθήκευση διαπιστευτηρίων 7.15 Ανακεφαλαίωση 8. Εξατομίκευση του Git 8.1 Διαμόρφωση Git 8.2 Γνωρίσματα του Git 8.3 Τα άγκιστρα του Git 8.4 Ένα παράδειγμα επιβολής πολιτικής από το Git 8.5 Ανακεφαλαίωση 9. Το Git και άλλα συστήματα 9.1 Το Git ως πελάτης 9.2 Μετανάστευση στο Git 9.3 Ανακεφαλαίωση 10. Εσωτερική λειτουργία του Git 10.1 Διοχετεύσεις και πορσελάνες 10.2 Αντικείμενα του Git 10.3 Αναφορές του Git 10.4 Πακετάρισμα αρχείων 10.5 Τα refspec 10.6 Πρωτόκολλα μεταφοράς 10.7 Διατήρηση και ανάκτηση δεδομένων 10.8 Μεταβλητές περιβάλλοντος 10.9 Ανακεφαλαίωση A1. Appendix A: Το Git σε άλλα περιβάλλοντα A1.1 Γραφικές διεπαφές A1.2 Το Git στο Visual Studio A1.3 Git στο Visual Studio Code A1.4 Git στο IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git στο Sublime Text A1.6 Το Git στο Bash A1.7 Το Git στο Zsh A1.8 Το Git στο Powershell A1.9 Ανακεφαλαίωση A2. Appendix B: Ενσωμάτωση του Git στις εφαρμογές μας A2.1 Γραμμή εντολών Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Εντολές Git A3.1 Ρύθμιση και διαμόρφωση A3.2 Λήψη και δημιουργία έργων A3.3 Βασική λήψη στιγμιοτύπων A3.4 Διακλάδωση και συγχώνευση A3.5 Κοινή χρήση και ενημέρωση έργων A3.6 Επιθεώρηση και σύγκριση A3.7 Αποσφαλμάτωση A3.8 Επιθέματα A3.9 Ηλεκτρονικό ταχυδρομείο A3.10 Εξωτερικά Συστήματα A3.11 Διοίκηση A3.12 Εντολές διοχέτευσης 2nd Edition 1.4 Ξεκινώντας με το Git - Η γραμμή εντολών Η γραμμή εντολών Υπάρχουν πολλοί διαφορετικοί τρόποι με τους οποίους μπορούμε να χρησιμοποιήσουμε το Git. Υπάρχουν τα εργαλεία γραμμής εντολών αλλά και διάφορα γραφικά εργαλεία με ποικίλες δυνατότητες. Στο βιβλίο αυτό θα χρησιμοποιήσουμε το Git μέσα από την γραμμή εντολών. Καταρχάς, η γραμμή εντολών είναι το μόνο εργαλείο στο οποίο μπορεί κανείς να τρέξει όλες τις εντολές του Git — για λόγους απλότητας τα περισσότερα από τα γραφικά εργαλεία υλοποιούν μόνο ένα υποσύνολο των λειτουργιών του Git. Αν γνωρίζετε πώς να χρησιμοποιείτε το Git από την γραμμή εντολών, τότε θα μπορέσετε να καταλάβετε και πώς να χρησιμοποιήσετε τα γραφικά εργαλεία, ενώ το αντίστροφο δεν ισχύει πάντα. Επίσης, ενώ η επιλογή ενός γραφικού προγράμματος είναι θέμα προσωπικού γούστου, όλοι οι χρήστες έχουν τα εργαλεία γραμμής εντολών εγκατεστημένα και διαθέσιμα. Συνεπώς θεωρείται ότι γνωρίζετε πώς να ανοίξετε την εφαρμογή Terminal στο Mac ή τη γραμμή εντολών (Command Prompt) ή το Powershell στα Windows. Αν δεν γνωρίζετε για τι μιλάμε, ίσως χρειαστεί να αναβάλετε για λίγο την εκμάθηση του Git και να ψάξετε τα παραπάνω ώστε να μπορέσετε να παρακολουθήσετε τα υπόλοιπα παραδείγματα και τις περιγραφές του βιβλίου. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
http://ccmixter.org | ccMixter - Welcome to ccMixter Listen to the Light skip Not logged in Log In Search Find content Collaborative Community Home The Mixversation Picks Remixes Samples A Cappellas People Extras Welcome to ccMixter Join the Community Create with musicians around the world, through a community of sharing and open music. Explore remixes , samples and pells . Join the mixversation in our forums . Check out the latest Editorial Picks: Time Machine by Jeris Happiness Deep Inside by Rewob New Year Beginning by Snowflake Free Music for YouTube Heck yes, you can use our music for free in your social media videos! Just give us credit . Search for free music HERE by style, BPM, or instrument and find the perfect soundtrack. Or check out some random mixes: D O N ' T G O (wastin' my time) / love me the way that I do by SO SHA Frozen Water by Apoxode Itz Itchy by Apoxode MixterPlus At MixterPlus we're collaborating in new ways. Check out the most recent playlist HERE . Join MixterPlus for new features like the Lyric and Image libraries and the Workshop. Email admins for your invite ! Latest from MixterPlus: Thesaurus by coruscate Explore Past Events Explore ccMixter’s previous remix events — where the community created robust libraries of pells, samples and fully produced tracks — around a vibrant theme. Imagination Shining Secret Mixter , Season of the Stars , Celebratory Secret Mixter , Songs of Solidarity , Music Connects Secret Mixter , Freedom to Share , Key Of Love , and Somewhere Over the Border are only a few! Support ccMixter on Patreon Will you donate $1 monthly? Patreon enables folks who 💗 ccMixter to support us through a monthly pledge. We thank you! 💗 Help us reach our goals AND get some cool rewards! 💗 Get Sustainer Status by pledging $10+ per month and your name will be added to this page ! Looking for Music? Looking for music for a video, app, game, podcast — or just for listening? Join thousands of creators around the world — use ccMixter music in your project. Find music that is liberally licensed at dig.ccMixter . It’s free to use if you give us credit — and here’s how to Attribute . Start digging for music at dig.ccMixter Updated Privacy Policy ccMixter has updated its Privacy Policy and Terms of Use to reflect current global standards and best practices. Read the forum post for more information. Visitors Find Music Forums About Looking for...? Artists Log In Register Search our archives for music for your video, podcast or school project at dig.ccMixter New Remixes weatherPatter... My Heart Beat... Je suis un Ph... From Two Dire... The Fade Out More new remixes New Uploads weatherPatter... My Heart Beat... Je suis un Ph... No Constant Tascam Amateu... More new uploads Editors' Picks Time Machine Happiness Dee... New Year Begi... Yorke And Lou Hollow Crown ... More picks... Highest Rated Queen of K... New Year B... Frost-Free... Queen of K... Javomatics Weather Or... Recent Reviewers texasradiofis... Speck Javolenus panu Stefan Karten... Bluemillenium airtone More reviews... Support ccMixter Syndication Welcome to ccMixter This text and images on this site are licensed under a Creative Commons Attribution-Noncommercial 4.0 International License . This site uses ccHost , licensed under CC-GNU-GPL , which is a product of the ccTools project and uses GetID3 . This site is sponsored by ArtisTech Media . By using this site, you agree to our Terms of Use and Privacy Policy . Please note our site credits . Contact: site administrator . | 2026-01-13T09:29:23 |
https://git-scm.com/book/de/v2/Git-Branching-Branches-auf-einen-Blick | Git - Branches auf einen Blick About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Erste Schritte 1.1 Was ist Versionsverwaltung? 1.2 Kurzer Überblick über die Historie von Git 1.3 Was ist Git? 1.4 Die Kommandozeile 1.5 Git installieren 1.6 Git Basis-Konfiguration 1.7 Hilfe finden 1.8 Zusammenfassung 2. Git Grundlagen 2.1 Ein Git-Repository anlegen 2.2 Änderungen nachverfolgen und im Repository speichern 2.3 Anzeigen der Commit-Historie 2.4 Ungewollte Änderungen rückgängig machen 2.5 Mit Remotes arbeiten 2.6 Taggen 2.7 Git Aliases 2.8 Zusammenfassung 3. Git Branching 3.1 Branches auf einen Blick 3.2 Einfaches Branching und Merging 3.3 Branch-Management 3.4 Branching-Workflows 3.5 Remote-Branches 3.6 Rebasing 3.7 Zusammenfassung 4. Git auf dem Server 4.1 Die Protokolle 4.2 Git auf einem Server einrichten 4.3 Erstellung eines SSH-Public-Keys 4.4 Einrichten des Servers 4.5 Git-Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Von Drittanbietern gehostete Optionen 4.10 Zusammenfassung 5. Verteiltes Git 5.1 Verteilter Arbeitsablauf 5.2 An einem Projekt mitwirken 5.3 Ein Projekt verwalten 5.4 Zusammenfassung 6. GitHub 6.1 Einrichten und Konfigurieren eines Kontos 6.2 Mitwirken an einem Projekt 6.3 Ein Projekt betreuen 6.4 Verwalten einer Organisation 6.5 Skripte mit GitHub 6.6 Zusammenfassung 7. Git Tools 7.1 Revisions-Auswahl 7.2 Interaktives Stagen 7.3 Stashen und Bereinigen 7.4 Deine Arbeit signieren 7.5 Suchen 7.6 Den Verlauf umschreiben 7.7 Reset entzaubert 7.8 Fortgeschrittenes Merging 7.9 Rerere 7.10 Debuggen mit Git 7.11 Submodule 7.12 Bundling 7.13 Replace (Ersetzen) 7.14 Anmeldeinformationen speichern 7.15 Zusammenfassung 8. Git einrichten 8.1 Git Konfiguration 8.2 Git-Attribute 8.3 Git Hooks 8.4 Beispiel für Git-forcierte Regeln 8.5 Zusammenfassung 9. Git und andere VCS-Systeme 9.1 Git als Client 9.2 Migration zu Git 9.3 Zusammenfassung 10. Git Interna 10.1 Basisbefehle und Standardbefehle (Plumbing and Porcelain) 10.2 Git Objekte 10.3 Git Referenzen 10.4 Packdateien (engl. Packfiles) 10.5 Die Referenzspezifikation (engl. Refspec) 10.6 Transfer Protokolle 10.7 Wartung und Datenwiederherstellung 10.8 Umgebungsvariablen 10.9 Zusammenfassung A1. Anhang A: Git in anderen Umgebungen A1.1 Grafische Schnittstellen A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Zusammenfassung A2. Anhang B: Git in deine Anwendungen einbetten A2.1 Die Git-Kommandozeile A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Anhang C: Git Kommandos A3.1 Setup und Konfiguration A3.2 Projekte importieren und erstellen A3.3 Einfache Snapshot-Funktionen A3.4 Branching und Merging A3.5 Projekte gemeinsam nutzen und aktualisieren A3.6 Kontrollieren und Vergleichen A3.7 Debugging A3.8 Patchen bzw. Fehlerkorrektur A3.9 E-mails A3.10 Externe Systeme A3.11 Administration A3.12 Basisbefehle 2nd Edition 3.1 Git Branching - Branches auf einen Blick Nahezu jedes VCS unterstützt eine Form von Branching. Branching bedeutet, dass du von der Hauptlinie der Entwicklung abzweigen und deine Arbeit fortsetzen kannst, ohne die Hauptlinie durcheinanderzubringen. In vielen VCS-Tools ist das ein etwas aufwändiger Prozess, bei dem du oft eine neue Kopie deines Quellcode-Verzeichnisses erstellen musst, was bei großen Projekten viel Zeit in Anspruch nehmen kann. Manche Leute bezeichnen Gits Branching-Modell als dessen „Killer-Feature“, was Git zweifellos vom Rest der VCS-Community abhebt. Was ist das Besondere daran? Die Art und Weise, wie Git Branches anlegt ist unglaublich leichtgewichtig. Branch-Operationen werden nahezu verzögerungsfrei ausgeführt und auch das Hin- und Herschalten zwischen einzelnen Entwicklungszweigen läuft meist genauso schnell ab. Im Gegensatz zu anderen VCS ermutigt Git zu einer Arbeitsweise mit häufigem Branching und Merging, sogar mehrmals am Tag. Wenn du diese Funktion verstehst und beherrschst, besitzt du ein mächtiges und besonderes Werkzeug, welches deine Art zu entwickeln vollständig verändern kann. Branches auf einen Blick Um richtig zu verstehen, wie Git das Verzweigen (engl. Branching) realisiert, müssen wir einen Schritt zurück gehen und untersuchen, wie Git seine Daten speichert. Wie du vielleicht aus Kapitel 1 Was ist Git? in Erinnerung hast, speichert Git seine Daten nicht als Serie von Änderungen oder Differenzen, sondern statt dessen als eine Reihe von Snapshots . Wenn du einen Commit durchführst, speichert Git ein Commit-Objekt, das einen Zeiger auf den Snapshot des von dir gestagten Inhalts enthält. Dieses Objekt enthält auch den Namen und die E-Mail-Adresse des Autors, die Nachricht, die er eingegeben hat, und zeigt auf den Commit oder die Commits, die direkt vor diesem Commit stattfanden (zu seinem Vorgänger bzw. seinen Vorgängern): keine Vorgänger für den ersten Commit, einen Vorgänger für einen normalen Commit und mehrere Vorgänger für einen Commit, welcher aus dem Zusammenführen (engl. mergen) von zwei oder mehr Branches resultiert. Um das zu veranschaulichen, lass uns annehmen, du hast ein Verzeichnis, welches drei Dateien enthält, und du fügst alle Dateien zur Staging-Area hinzu und führst einen Commit durch. Durch das Hinzufügen der Dateien zur Staging-Area erzeugt Git für jede Datei eine Prüfsumme (den SHA-1-Hashwert, den wir in Kapitel 1 Was ist Git? erwähnt haben), speichert diese Version der Datei im Git-Repository (Git verweist auf diese als blobs ) und fügt die Prüfsumme der Staging-Area hinzu: $ git add README test.rb LICENSE $ git commit -m 'Initial commit' Wenn du mit der Anweisung git commit einen Commit erzeugst, berechnet Git für jedes Unterverzeichnis (in diesem Fall nur das Wurzelverzeichnis des Projektes) eine Prüfsumme und speichert diese als tree -Objekt im Git-Repository. Git erzeugt dann ein commit-Objekt, welches die Metadaten und einen Zeiger zum tree-Objekt des Wurzelverzeichnisses enthält, sodass es bei Bedarf den Snapshot erneut erzeugen kann. Dein Git-Repository enthält jetzt fünf Objekte: drei blobs (die jeweils den Inhalt einer der drei Dateien repräsentieren), ein tree -Objekt, welches den Inhalt des Verzeichnisses auflistet und angibt, welcher Dateiname zu welchem Blob gehört, und ein commit -Objekt mit dem Zeiger, der auf die Wurzel des Projektbaumes und die Metadaten des Commits verweist. Abbildung 9. Ein Commit und sein Tree Wenn du einige Änderungen vornimmst und wieder einen Commit durchführst, speichert dieser einen Zeiger zu dem Commit, der unmittelbar davor gemacht wurde. Abbildung 10. Commits und ihre Vorgänger Ein Branch in Git ist einfach ein leichter, beweglicher Zeiger auf einen dieser Commits. Die Standardbezeichnung für einen Branch bei Git lautet master . Wenn du damit beginnst, Commits durchzuführen, erhältst du einen master Branch, der auf den letzten Commit zeigt, den du gemacht hast. Jedes Mal, wenn du einen Commit durchführst, bewegt er sich automatisch vorwärts. Anmerkung Der „master“-Branch in Git ist kein spezieller Branch. Er ist genau wie jeder andere Branch. Der einzige Grund dafür, dass nahezu jedes Repository einen „master“-Branch hat, ist der Umstand, dass die Anweisung git init diesen standardmäßig erzeugt und die meisten Leute sich nicht darum kümmern, den Namen zu ändern. Abbildung 11. Ein Branch und sein Commit-Verlauf Erzeugen eines neuen Branches Was passiert, wenn du einen neuen Branch anlegst? Nun, wenn du das tust, wird ein neuer Zeiger (Pointer) erstellt, mit dem du dich in der Entwicklung fortbewegen kannst. Nehmen wir an, du erzeugst einen neuen Branch mit dem Namen „testing“. Das machst du mit der Anweisung git branch : $ git branch testing Dieser Befehl erzeugt einen neuen Zeiger, der auf denselben Commit zeigt, auf dem du dich gegenwärtig befindest. Abbildung 12. Zwei Branches, die auf dieselbe Serie von Commits zeigen Woher weiß Git, auf welchem Branch du gegenwärtig bist? Es besitzt einen speziellen Zeiger namens HEAD . Beachte, dass dieser HEAD sich sehr stark unterscheidet von den HEAD Konzepten anderer Versionsverwaltungen, mit denen du vielleicht vertraut bist, wie Subversion oder CVS. Bei Git handelt es sich bei HEAD um einen Zeiger auf den lokalen Branch, auf dem du dich gegenwärtig befindest. In diesem Fall bist du weiterhin auf dem master Branch. Die Anweisung git branch hat den neuen Branch nur erzeugt , aber nicht zu diesem gewechselt. Abbildung 13. Auf einen Branch zeigender HEAD Du kannst das leicht nachvollziehen, indem du den einfachen Befehl git log ausführst, mit dem du siehst, wohin die Zeiger der Branches zeigen. Diese Option wird --decorate genannt. $ git log --oneline --decorate f30ab (HEAD -> master, testing) Add feature #32 - ability to add new formats to the central interface 34ac2 Fix bug #1328 - stack overflow under certain conditions 98ca9 Initial commit Du kannst die Branches master und testing sehen, die sich rechts neben dem Commit von f30ab befinden. Wechseln des Branches Um zu einem existierenden Branch zu wechseln, führe die Anweisung git checkout aus. Lass uns zum neuen testing Branch wechseln. $ git checkout testing Dadurch wird HEAD verschoben, um auf den Branch testing zu zeigen. Abbildung 14. HEAD zeigt auf den aktuellen Branch Was bedeutet das? Nun, lass uns einen weiteren Commit durchführen. $ vim test.rb $ git commit -a -m 'made a change' Abbildung 15. Der Branch, auf den HEAD zeigt, bewegt sich vorwärts, wenn ein Commit gemacht wird Das ist interessant, weil sich jetzt dein testing Branch vorwärts bewegt hat, aber dein master Branch noch auf den Commit zeigt, auf dem du dich befandest, als du die Anweisung git checkout ausführtest, um die Branches zu wechseln. Lassen uns zum Branch master zurückwechseln. $ git checkout master Anmerkung git log zeigt nicht immer alle Branches Wenn du jetzt git log aufrufen würdest, könntest du dich fragen, wohin der gerade erstellte „testing“ Branch verschwunden ist, da er nicht in der Anzeige auftaucht. Der Branch ist nicht spurlos verschwunden. Git weiß nur nicht, dass du dich für diesen Branch interessierst. Git versucht, dir das zu zeigen, woran du seiner Meinung nach interessiert bist. Anders gesagt, standardmäßig zeigt git log nur den Commit-Verlauf des Branches an, den du ausgecheckt hast. Um die Commit-Historie für den gewünschten Branch anzuzeigen, musst du ihn explizit angeben: git log testing . Um alle Branches zu sehen, füge --all zu deinem Kommando git log hinzu. Abbildung 16. HEAD bewegt sich, wenn du auscheckst Diese Anweisung hat zwei Dinge bewirkt. Es bewegte den HEAD-Zeiger zurück, um auf den master Branch zu zeigen und es setzte die Dateien in deinem Arbeitsverzeichnis auf den Snapshot zurück, auf den master zeigt. Das bedeutet auch, dass die Änderungen, die du von diesem Punkt aus vornimmst, von einer älteren Version des Projekts abzweigen werden. Du machst im Grunde genommen die Änderungen rückgängig, die du auf deinem testing Branch vorgenommen hast, sodass du in eine andere Richtung gehen kannst. Anmerkung Das Wechseln der Branches ändert Dateien in deinem Arbeitsverzeichnis Es ist wichtig zu beachten, dass sich die Dateien in deinem Arbeitsverzeichnis verändern, wenn du in Git die Branches wechselst. Wenn du zu einem älteren Branch wechselst, wird dein Arbeitsverzeichnis zurückverwandelt, sodass es aussieht wie zu dem Zeitpunkt, als du deinen letzten Commit auf diesem Branch durchgeführt hast. Wenn Git das nicht problemlos durchführen kann, lässt es dich die Branches überhaupt nicht wechseln. Lass uns ein paar Änderungen vornehmen und noch einen Commit durchführen: $ vim test.rb $ git commit -a -m 'made other changes' Jetzt hat sich dein Projektverlauf verzweigt (siehe Verzweigter Verlauf ). Du hast einen Branch erstellt und bist zu ihm gewechselt, hast einige Arbeiten daran durchgeführt und bist dann wieder zu deinem Haupt-Branch zurückgekehrt, um andere Arbeiten durchzuführen. Beide Änderungen sind in separaten Branches isoliert: Du kannst zwischen den Branches hin und her wechseln sowie sie zusammenführen, wenn du soweit bist. Und das alles mit den einfachen Befehlen branch , checkout und commit . Abbildung 17. Verzweigter Verlauf Du kannst dir dies ansehen, wenn du die Anweisung git log ausführst. Wenn du die Anweisung git log --oneline --decorate --graph --all ausführst, wird dir der Verlauf deiner Commits so angezeigt, dass erkennbar ist, wo deine Branch-Zeiger sich befinden und wie dein Verlauf sich verzweigt hat. $ git log --oneline --decorate --graph --all * c2b9e (HEAD, master) Made other changes | * 87ab2 (testing) Made a change |/ * f30ab Add feature #32 - ability to add new formats to the central interface * 34ac2 Fix bug #1328 - stack overflow under certain conditions * 98ca9 initial commit of my project Da ein Branch in Git in Wirklichkeit eine einfache Datei ist, welche die 40-Zeichen lange SHA-1-Prüfsumme des Commits enthält, auf dem sie zeigt, können Branches ohne großen Aufwand erzeugt und gelöscht werden. Einen neuen Branch anzulegen, geht so schnell und ist so einfach, wie 41 Bytes in eine Datei zu schreiben (40 Zeichen und einen Zeilenumbruch). Das steht im krassen Gegensatz zur Art und Weise, wie die meisten älteren Werkzeuge zur Versionsverwaltung Branches anlegen, bei der alle Projektdateien in ein zweites Verzeichnis kopiert werden. Das kann, in Abhängigkeit von der Projektgröße, mehrere Sekunden oder sogar Minuten dauern, während bei Git dieser Prozess augenblicklich erledigt ist. Da wir außerdem immer die Vorgänger mit aufzeichnen, wenn wir einen Commit durchführen, wird die Suche nach einer geeigneten Basis für das Zusammenführen (engl. merging) für uns automatisch durchgeführt, was in der Regel sehr einfach erledigt werden kann. Diese Funktionen tragen dazu bei, dass Entwickler ermutigt werden, häufig Branches zu erstellen und zu nutzen. Lass uns herausfinden, warum du das tun solltest. Anmerkung Einen neuen Branch erzeugen und gleichzeitig dorthin wechseln. Es ist üblich, einen neuen Branch zu erstellen und gleichzeitig zu diesem neuen Branch zu wechseln – dies kann in einem Arbeitsschritt mit git checkout -b <newbranchname> passieren. Anmerkung Ab Git version 2.23 kannst du git switch anstatt von git checkout nutzen um: Zu einem bestehendem Branch wechseln mit: git switch testing-branch . Einen neuen Branch erstellen und zu ihm wechseln mit: git switch -c new-branch . Die -c Option steht für Create (Anlegen), du kannst auch die komplette Option --create nutzen. Zurück zu deinem zuletzt ausgechecktem Branch wechseln mit: git switch - . prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=gl | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 P | 2026-01-13T09:29:23 |
https://git-scm.com/book/it/v2/Git-Basics-Recording-Changes-to-the-Repository | Git - Recording Changes to the Repository About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Per Iniziare 1.1 Il Controllo di Versione 1.2 Una Breve Storia di Git 1.3 Cos’é Git? 1.4 La riga di comando 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Chiedere aiuto 1.8 Sommario 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Sommario 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendice A: Git in altri contesti A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Riassunto A2. Appendice B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendice C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.2 Git Basics - Recording Changes to the Repository Recording Changes to the Repository You have a bona fide Git repository and a checkout or working copy of the files for that project. You need to make some changes and commit snapshots of those changes into your repository each time the project reaches a state you want to record. Remember that each file in your working directory can be in one of two states: tracked or untracked. Tracked files are files that were in the last snapshot; they can be unmodified, modified, or staged. Untracked files are everything else – any files in your working directory that were not in your last snapshot and are not in your staging area. When you first clone a repository, all of your files will be tracked and unmodified because you just checked them out and haven’t edited anything. As you edit files, Git sees them as modified, because you’ve changed them since your last commit. You stage these modified files and then commit all your staged changes, and the cycle repeats. Figura 8. The lifecycle of the status of your files. Checking the Status of Your Files The main tool you use to determine which files are in which state is the git status command. If you run this command directly after a clone, you should see something like this: $ git status On branch master nothing to commit, working directory clean This means you have a clean working directory – in other words, there are no tracked and modified files. Git also doesn’t see any untracked files, or they would be listed here. Finally, the command tells you which branch you’re on and informs you that it has not diverged from the same branch on the server. For now, that branch is always “master”, which is the default; you won’t worry about it here. [ch03-git-branching] will go over branches and references in detail. Let’s say you add a new file to your project, a simple README file. If the file didn’t exist before, and you run git status , you see your untracked file like so: $ echo 'My Project' > README $ git status On branch master Untracked files: (use "git add <file>..." to include in what will be committed) README nothing added to commit but untracked files present (use "git add" to track) You can see that your new README file is untracked, because it’s under the “Untracked files” heading in your status output. Untracked basically means that Git sees a file you didn’t have in the previous snapshot (commit); Git won’t start including it in your commit snapshots until you explicitly tell it to do so. It does this so you don’t accidentally begin including generated binary files or other files that you did not mean to include. You do want to start including README, so let’s start tracking the file. Tracking New Files In order to begin tracking a new file, you use the command git add . To begin tracking the README file, you can run this: $ git add README If you run your status command again, you can see that your README file is now tracked and staged to be committed: $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README You can tell that it’s staged because it’s under the “Changes to be committed” heading. If you commit at this point, the version of the file at the time you ran git add is what will be in the historical snapshot. You may recall that when you ran git init earlier, you then ran git add (files) – that was to begin tracking files in your directory. The git add command takes a path name for either a file or a directory; if it’s a directory, the command adds all the files in that directory recursively. Staging Modified Files Let’s change a file that was already tracked. If you change a previously tracked file called “CONTRIBUTING.md” and then run your git status command again, you get something that looks like this: $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md The “CONTRIBUTING.md” file appears under a section named “Changed but not staged for commit” – which means that a file that is tracked has been modified in the working directory but not yet staged. To stage it, you run the git add command. git add is a multipurpose command – you use it to begin tracking new files, to stage files, and to do other things like marking merge-conflicted files as resolved. It may be helpful to think of it more as “add this content to the next commit” rather than “add this file to the project”. Let’s run git add now to stage the “CONTRIBUTING.md” file, and then run git status again: $ git add CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Both files are staged and will go into your next commit. At this point, suppose you remember one little change that you want to make in CONTRIBUTING.md before you commit it. You open it again and make that change, and you’re ready to commit. However, let’s run git status one more time: $ vim CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md What the heck? Now CONTRIBUTING.md is listed as both staged and unstaged. How is that possible? It turns out that Git stages a file exactly as it is when you run the git add command. If you commit now, the version of CONTRIBUTING.md as it was when you last ran the git add command is how it will go into the commit, not the version of the file as it looks in your working directory when you run git commit . If you modify a file after you run git add , you have to run git add again to stage the latest version of the file: $ git add CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Short Status While the git status output is pretty comprehensive, it’s also quite wordy. Git also has a short status flag so you can see your changes in a more compact way. If you run git status -s or git status --short you get a far more simplified output from the command. $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt New files that aren’t tracked have a ?? next to them, new files that have been added to the staging area have an A , modified files have an M and so on. There are two columns to the output - the left hand column indicates that the file is staged and the right hand column indicates that it’s modified. So for example in that output, the README file is modified in the working directory but not yet staged, while the lib/simplegit.rb file is modified and staged. The Rakefile was modified, staged and then modified again, so there are changes to it that are both staged and unstaged. Ignoring Files Often, you’ll have a class of files that you don’t want Git to automatically add or even show you as being untracked. These are generally automatically generated files such as log files or files produced by your build system. In such cases, you can create a file listing patterns to match them named .gitignore . Here is an example .gitignore file: $ cat .gitignore *.[oa] *~ The first line tells Git to ignore any files ending in “.o” or “.a” – object and archive files that may be the product of building your code. The second line tells Git to ignore all files that end with a tilde ( ~ ), which is used by many text editors such as Emacs to mark temporary files. You may also include a log, tmp, or pid directory; automatically generated documentation; and so on. Setting up a .gitignore file before you get going is generally a good idea so you don’t accidentally commit files that you really don’t want in your Git repository. The rules for the patterns you can put in the .gitignore file are as follows: Blank lines or lines starting with # are ignored. Standard glob patterns work. You can end patterns with a forward slash ( / ) to specify a directory. You can negate a pattern by starting it with an exclamation point ( ! ). Glob patterns are like simplified regular expressions that shells use. An asterisk ( * ) matches zero or more characters; [abc] matches any character inside the brackets (in this case a, b, or c); a question mark ( ? ) matches a single character; and brackets enclosing characters separated by a hyphen( [0-9] ) matches any character between them (in this case 0 through 9). You can also use two asterisks to match nested directories; a/**/z would match a/z , a/b/z , a/b/c/z , and so on. Here is another example .gitignore file: # no .a files *.a # but do track lib.a, even though you're ignoring .a files above !lib.a # only ignore the root TODO file, not subdir/TODO /TODO # ignore all files in the build/ directory build/ # ignore doc/notes.txt, but not doc/server/arch.txt doc/*.txt # ignore all .txt files in the doc/ directory doc/**/*.txt Suggerimento GitHub maintains a fairly comprehensive list of good .gitignore file examples for dozens of projects and languages at https://github.com/github/gitignore if you want a starting point for your project. Viewing Your Staged and Unstaged Changes If the git status command is too vague for you – you want to know exactly what you changed, not just which files were changed – you can use the git diff command. We’ll cover git diff in more detail later, but you’ll probably use it most often to answer these two questions: What have you changed but not yet staged? And what have you staged that you are about to commit? Although git status answers those questions very generally by listing the file names, git diff shows you the exact lines added and removed – the patch, as it were. Let’s say you edit and stage the README file again and then edit the CONTRIBUTING.md file without staging it. If you run your git status command, you once again see something like this: $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md To see what you’ve changed but not yet staged, type git diff with no other arguments: $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,8 @@ branch directly, things can get messy. Please include a nice description of your changes when you submit your PR; if we have to read the whole diff to figure out why you're contributing in the first place, you're less likely to get feedback and have your change -merged in. +merged in. Also, split your changes into comprehensive chunks if you patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's That command compares what is in your working directory with what is in your staging area. The result tells you the changes you’ve made that you haven’t yet staged. If you want to see what you’ve staged that will go into your next commit, you can use git diff --staged . This command compares your staged changes to your last commit: $ git diff --staged diff --git a/README b/README new file mode 100644 index 0000000..03902a1 --- /dev/null +++ b/README @@ -0,0 +1 @@ +My Project It’s important to note that git diff by itself doesn’t show all changes made since your last commit – only changes that are still unstaged. This can be confusing, because if you’ve staged all of your changes, git diff will give you no output. For another example, if you stage the CONTRIBUTING.md file and then edit it, you can use git diff to see the changes in the file that are staged and the changes that are unstaged. If our environment looks like this: $ git add CONTRIBUTING.md $ echo 'test line' >> CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Now you can use git diff to see what is still unstaged $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 643e24f..87f08c8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -119,3 +119,4 @@ at the ## Starter Projects See our [projects list](https://github.com/libgit2/libgit2/blob/development/PROJECTS.md). +# test line and git diff --cached to see what you’ve staged so far (--staged and --cached are synonyms): $ git diff --cached diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,8 @@ branch directly, things can get messy. Please include a nice description of your changes when you submit your PR; if we have to read the whole diff to figure out why you're contributing in the first place, you're less likely to get feedback and have your change -merged in. +merged in. Also, split your changes into comprehensive chunks if you patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's Nota Git Diff in an External Tool We will continue to use the git diff command in various ways throughout the rest of the book. There is another way to look at these diffs if you prefer a graphical or external diff viewing program instead. If you run git difftool instead of git diff , you can view any of these diffs in software like Araxis, emerge, vimdiff and more. Run git difftool --tool-help to see what is available on your system. Committing Your Changes Now that your staging area is set up the way you want it, you can commit your changes. Remember that anything that is still unstaged – any files you have created or modified that you haven’t run git add on since you edited them – won’t go into this commit. They will stay as modified files on your disk. In this case, let’s say that the last time you ran git status , you saw that everything was staged, so you’re ready to commit your changes. The simplest way to commit is to type git commit : $ git commit Doing so launches your editor of choice. (This is set by your shell’s $EDITOR environment variable – usually vim or emacs, although you can configure it with whatever you want using the git config --global core.editor command as you saw in Per Iniziare ). The editor displays the following text (this example is a Vim screen): # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Changes to be committed: # new file: README # modified: CONTRIBUTING.md # ~ ~ ~ ".git/COMMIT_EDITMSG" 9L, 283C You can see that the default commit message contains the latest output of the git status command commented out and one empty line on top. You can remove these comments and type your commit message, or you can leave them there to help you remember what you’re committing. (For an even more explicit reminder of what you’ve modified, you can pass the -v option to git commit . Doing so also puts the diff of your change in the editor so you can see exactly what changes you’re committing.) When you exit the editor, Git creates your commit with that commit message (with the comments and diff stripped out). Alternatively, you can type your commit message inline with the commit command by specifying it after a -m flag, like this: $ git commit -m "Story 182: Fix benchmarks for speed" [master 463dc4f] Story 182: Fix benchmarks for speed 2 files changed, 2 insertions(+) create mode 100644 README Now you’ve created your first commit! You can see that the commit has given you some output about itself: which branch you committed to ( master ), what SHA-1 checksum the commit has ( 463dc4f ), how many files were changed, and statistics about lines added and removed in the commit. Remember that the commit records the snapshot you set up in your staging area. Anything you didn’t stage is still sitting there modified; you can do another commit to add it to your history. Every time you perform a commit, you’re recording a snapshot of your project that you can revert to or compare to later. Skipping the Staging Area Although it can be amazingly useful for crafting commits exactly how you want them, the staging area is sometimes a bit more complex than you need in your workflow. If you want to skip the staging area, Git provides a simple shortcut. Adding the -a option to the git commit command makes Git automatically stage every file that is already tracked before doing the commit, letting you skip the git add part: $ git status On branch master Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md no changes added to commit (use "git add" and/or "git commit -a") $ git commit -a -m 'added new benchmarks' [master 83e38c7] added new benchmarks 1 file changed, 5 insertions(+), 0 deletions(-) Notice how you don’t have to run git add on the “CONTRIBUTING.md” file in this case before you commit. Removing Files To remove a file from Git, you have to remove it from your tracked files (more accurately, remove it from your staging area) and then commit. The git rm command does that, and also removes the file from your working directory so you don’t see it as an untracked file the next time around. If you simply remove the file from your working directory, it shows up under the “Changed but not updated” (that is, unstaged ) area of your git status output: $ rm PROJECTS.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add/rm <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) deleted: PROJECTS.md no changes added to commit (use "git add" and/or "git commit -a") Then, if you run git rm , it stages the file’s removal: $ git rm PROJECTS.md rm 'PROJECTS.md' $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) deleted: PROJECTS.md The next time you commit, the file will be gone and no longer tracked. If you modified the file and added it to the index already, you must force the removal with the -f option. This is a safety feature to prevent accidental removal of data that hasn’t yet been recorded in a snapshot and that can’t be recovered from Git. Another useful thing you may want to do is to keep the file in your working tree but remove it from your staging area. In other words, you may want to keep the file on your hard drive but not have Git track it anymore. This is particularly useful if you forgot to add something to your .gitignore file and accidentally staged it, like a large log file or a bunch of .a compiled files. To do this, use the --cached option: $ git rm --cached README You can pass files, directories, and file-glob patterns to the git rm command. That means you can do things such as $ git rm log/\*.log Note the backslash ( \ ) in front of the * . This is necessary because Git does its own filename expansion in addition to your shell’s filename expansion. This command removes all files that have the .log extension in the log/ directory. Or, you can do something like this: $ git rm \*~ This command removes all files that end with ~ . Moving Files Unlike many other VCS systems, Git doesn’t explicitly track file movement. If you rename a file in Git, no metadata is stored in Git that tells it you renamed the file. However, Git is pretty smart about figuring that out after the fact – we’ll deal with detecting file movement a bit later. Thus it’s a bit confusing that Git has a mv command. If you want to rename a file in Git, you can run something like $ git mv file_from file_to and it works fine. In fact, if you run something like this and look at the status, you’ll see that Git considers it a renamed file: $ git mv README.md README $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README However, this is equivalent to running something like this: $ mv README.md README $ git rm README.md $ git add README Git figures out that it’s a rename implicitly, so it doesn’t matter if you rename a file that way or with the mv command. The only real difference is that mv is one command instead of three – it’s a convenience function. More important, you can use any tool you like to rename a file, and address the add/rm later, before you commit. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/zh-tw/v2/%e4%bd%bf%e7%94%a8-Git-%e5%88%86%e6%94%af-%e7%b0%a1%e8%bf%b0%e5%88%86%e6%94%af | Git - 簡述分支 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 開始 1.1 關於版本控制 1.2 Git 的簡史 1.3 Git 基礎要點 1.4 命令列 1.5 Git 安裝教學 1.6 初次設定 Git 1.7 取得說明文件 1.8 摘要 2. Git 基礎 2.1 取得一個 Git 倉儲 2.2 紀錄變更到版本庫中 2.3 檢視提交的歷史記錄 2.4 復原 2.5 與遠端協同工作 2.6 標籤 2.7 Git Aliases 2.8 總結 3. 使用 Git 分支 3.1 簡述分支 3.2 分支和合併的基本用法 3.3 分支管理 3.4 分支工作流程 3.5 遠端分支 3.6 衍合 3.7 總結 4. 伺服器上的 Git 4.1 通訊協定 4.2 在伺服器上佈署 Git 4.3 產生你的 SSH 公鑰 4.4 設定伺服器 4.5 Git 常駐程式 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第3方 Git 託管方案 4.10 總結 5. 分散式的 Git 5.1 分散式工作流程 5.2 對專案進行貢獻 5.3 維護一個專案 5.4 Summary 6. GitHub 6.1 建立帳戶及設定 6.2 參與一個專案 6.3 維護專案 6.4 Managing an organization 6.5 Scripting GitHub 6.6 總結 7. Git 工具 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 總結 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. 附錄 A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. 附錄 B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. 附錄 C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 3.1 使用 Git 分支 - 簡述分支 幾乎每一種版本控制系統（Version Control System，以下簡稱 VCS）都支援某種形式的分支（branch）功能， 使用分支意味著你可以從開發主線上分離開來，然後在不影響主線的情況下繼續工作； 在很多 VCS 中，這是個昂貴的過程，常常需要對原始程式碼目錄建立一個完整的副本，對大型專案來說會花費很長時間。 有人把 Git 的分支模型視為它的「殺手級功能」，正是因為它而讓 Git 在 VCS 社群中顯得與眾不同。 它有何特別之處呢？ Git 的分支簡直是難以置信的羽量級，新建分支的操作幾乎可以在瞬間完成，並且一般來說切換不同分支也很快； 跟其它的 VCS 不一樣的地方是 Git 鼓勵在工作流程中頻繁地使用分支與合併（merge），即使一天之內進行許多次都沒問題。 理解並掌握這個特性後，它會給你一個強大而獨特的工具，從此完全地改變你的開發方式。 簡述分支 為了理解 Git 分支（branch）的使用方式，我們需要回顧一下 Git 是如何保存資料的。 或許你還記得 [ch01-introduction] 的內容，Git 保存的不是變更集或者差異內容，而是一系列快照。 當你製造一個提交（commit）時，Git 會儲存一個提交物件，該物件內容包含一個指標，用來代表已預存的快照內容； 這個物件內容還包含「作者名字和電子郵件」、「你輸入的訊息內容」、「指向前一個提交的指標（該提交的親代提交）」：沒有親代（parent）提交表示它是初始的第一個提交，一般情況下只有一個親代提交，超過一個親代提交表示它是從二個以上的分支合併而來的。 為了具體說明，讓我們假設你有一個目錄包含了三個檔案，你預存（stage）並提交了它們； 檔案預存操作會對每一個檔案內容（譯註：請注意，只有檔案「內容」）計算雜湊值（即 [ch01-introduction] 中提到的 SHA-1 雜湊值），然後把那個檔案內容版本保存到 Git 版本庫中（Git 把它們視為 blob 類型的物件），再將這個雜湊值寫入預存區（staging area）： $ git add README test.rb LICENSE $ git commit -m 'The initial commit of my project' 當使用 git commit 建立一個提交時，Git 會先計算每一個子目錄（本例中則只有專案根目錄）的雜湊值，然後在 Git 版本庫中將這些目錄記錄為樹（tree）物件； 之後 Git 建立提交物件，它除了包含相關提交資訊以外，還包含著指向專案根目錄的樹物件指標，如此它就可以在需要的時候重建此次快照內容。 你的 Git 版本庫現在有五個物件：三個 blob 物件用來儲存檔案內容、一個樹物件用來列出目錄的內容並紀錄各個檔案所對應的 blob 物件、一個提交用來記錄根目錄的樹物件和其他提交資訊。 圖表 9. 單個提交在版本庫中的資料結構 如果你做一些修改並再次提交，這次的提交會再包含一個指向上次提交的指標（譯注：即下圖中的 parent 欄位）。 圖表 10. 提交和它們的親代提交 Git 分支其實只是一個指向某提交的可移動輕量級指標， Git 預設分支名稱是 master ， 隨著不斷地製作提交， master 分支會為你一直指向最後一個提交， 它在每次提交的時候都會自動向前移動。 筆記 「master」在 Git 中並不是一個特殊的分支， 它和其它分支並無分別， 之所以幾乎每個版本庫裡都會有這個分支的原因是 git init 命令的預設行為會產生它，而大部分的人就這麼直接使用它。 圖表 11. 分支及其提交歷史 建立一個新的分支 建立一個新分支會發生什麼事呢？ 答案很簡單，建立一個新的、可移動的指標； 比如新建一個 testing 分支， 可以使用 git branch 命令： $ git branch testing 這會在目前提交上新建一個指標。 圖表 12. 二個分支都指向同一系列的提交歷史 Git 如何知道你目前在哪個分支上工作的呢？ 其實它保存了一個名為 HEAD 的特別指標； 請注意它和你可能慣用的其他 VCSs 裡的 HEAD 概念大不相同，比如 Subversion 或 CVS； 在 Git 中，它就是一個指向你正在工作中的本地分支的指標（譯注：HEAD 等於「目前的」）， 所以在這個例子中，你仍然在 master 分支上工作； 執行 git branch 命令，只是「建立」一個新的分支——它並不會切換到這個分支。 圖表 13. HEAD 指向一個分支 你可以很輕鬆地看到分支指標指向何處，只需透過一個簡單的 git log 命令， 加上 --decorate 選項。 $ git log --oneline --decorate f30ab (HEAD -> master, testing) add feature #32 - ability to add new formats to the central interface 34ac2 Fixed bug #1328 - stack overflow under certain conditions 98ca9 The initial commit of my project 你可以看到「master」和「testing」分支就顯示在 f30ab 提交旁邊。 在分支之間切換 要切換到一個已經存在的分支，你可以執行 git checkout 命令， 讓我們切換到新的 testing 分支： $ git checkout testing 這會移動 HEAD 並指向 testing 分支。 圖表 14. 被 HEAD 指向的分支是目前分支 這樣做有什麼意義呢？ 好吧！讓我們再提交一次： $ vim test.rb $ git commit -a -m 'made a change' 圖表 15. 當再次提交時，被 HEAD 指向的分支會往前走 非常有趣，現在 testing 分支向前移動了，而 master 分支仍然指向當初在執行 git checkout 時所在的提交， 讓我們切回 master 分支看看： $ git checkout master 圖表 16. 當你檢出時，HEAD 會移動 這條命令做了兩件事， 它把 HEAD 指標移回去並指向 master 分支，然後把工作目錄中的檔案換成 master 分支所指向的快照內容； 也就是說，現在開始所做的改動，將基於專案中較舊的版本，然後與其它提交歷史分離開來； 它實際上是取消你在 testing 分支裡所做的修改，這樣你就可以往不同方向前進。 筆記 切換分支會修改工作目錄裡的檔案 重要的是要注意：當你在 Git 中切換分支時，工作目錄內的檔案將會被修改； 如果切換到舊分支，你的工作目錄會回復到看起來就像當初你最後一次在這個分支提交時的樣子。 如果 Git 無法很乾淨地切換過去，它就不會讓你切換過去。 讓我們做一些修改並再次提交： $ vim test.rb $ git commit -a -m 'made other changes' 現在你的專案歷史開始分離了（詳見 分離的歷史 ）； 你建立並切換到新分支，在上面進行了一些工作，然後切換回到主分支進行了另外一些工作， 雙方的改變分別隔離在不同的分支裡：你可以在不同分支裡反覆切換，並在時機成熟時把它們合併到一起； 而所有這些工作只需要簡單的 branch 、 checkout 、 commit 命令。 圖表 17. 分離的歷史 你一樣可以從 git log 中輕鬆地看出這件事， 執行 git log --oneline --decorate --graph --all ，它會印出你的提交歷史，顯示你的分支指標在哪裡，以及歷史如何被分離開來。 $ git log --oneline --decorate --graph --all * c2b9e (HEAD, master) made other changes | * 87ab2 (testing) made a change |/ * f30ab add feature #32 - ability to add new formats to the * 34ac2 fixed bug #1328 - stack overflow under certain conditions * 98ca9 initial commit of my project 由於 Git 分支實際上只是一個檔案，該檔案內容是這個分支指向的提交的雜湊值（40 個字元長度的 SHA-1 字串），所以建立和銷毀一個分支就變得非常廉價； 新建一個分支就是向一個檔寫入 41 個位元組（40 個字元外加一個換行符號）那樣地簡單和快速。 這樣的分支功能和大多數舊 VCS 的分支功能形成了鮮明的對比，有些分支功能甚至需要複製專案中全部的檔案到另一個資料夾， 而根據專案檔案數量和大小的不同，可能花費的時間快則幾秒，慢則數分鐘；而在 Git 中幾乎都在瞬間完成。 還有，因為每次提交時都記錄了親代資訊，將來要合併分支時，它通常會幫我們自動並輕鬆地找到適當的合併基礎； 這樣子的特性在無形間鼓勵了開發者頻繁地建立和使用分支。 讓我們來瞧一瞧為什麼你應該要這麼做。 prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/uz/v2/Git-%d1%81%d0%b5%d1%80%d0%b2%d0%b5%d1%80%d0%b4%d0%b0-GitLab | Git - GitLab About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Иш бошланиши 1.1 Талқинларни бошқариш ҳақида 1.2 Git нинг қисқача тарихи 1.3 Git асоси 1.4 Командалар сатри 1.5 Git ни ўрнатиш 1.6 Git да биринчи созлашлар 1.7 Қандай ёрдам олиш мумкин? 1.8 Хулосалар 2. Git асослари 2.1 Git омборини яратиш 2.2 Ўзгаришларни омборга ёзиш 2.3 Фиксирлашлар тарихини кўриш 2.4 Ўзгаришларни бекор қилиш 2.5 Узоқ масофадаги омборлар билан ишлаш 2.6 Тамғалаш 2.7 Git да таҳаллуслар 2.8 Хулоса 3. Git да тармоқланиш 3.1 Тармоқланиш ҳақида икки оғиз сўз 3.2 Тармоқланиш ва бирлашиш асослари 3.3 Тармоқларни бошқариш 3.4 Иш жараёнларини тармоқлаш 3.5 Узоқ масофадаги тармоқлар 3.6 Қайта асосланиш 3.7 Хулосалар 4. Git серверда 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Sizning SSH ochiq (public) kalitingizni generatsiyalash 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Хулосалар 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Qism modullar (Submodule) 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.8 Git серверда - GitLab GitLab GitWeb is pretty simplistic though. If you’re looking for a more modern, fully featured Git server, there are some several open source solutions out there that you can install instead. As GitLab is one of the more popular ones, we’ll cover installing and using it as an example. This is a bit more complex than the GitWeb option and likely requires more maintenance, but it is a much more fully featured option. Installation GitLab is a database-backed web application, so its installation is a bit more involved than some other git servers. Fortunately, this process is very well-documented and supported. There are a few methods you can pursue to install GitLab. To get something up and running quickly, you can download a virtual machine image or a one-click installer from https://bitnami.com/stack/gitlab , and tweak the configuration to match your particular environment. One nice touch Bitnami has included is the login screen (accessed by typing alt-→); it tells you the IP address and default username and password for the installed GitLab. Figure 50. The Bitnami GitLab virtual machine login screen. For anything else, follow the guidance in the GitLab Community Edition readme, which can be found at https://gitlab.com/gitlab-org/gitlab-ce/tree/master . There you’ll find assistance for installing GitLab using Chef recipes, a virtual machine on Digital Ocean, and RPM and DEB packages (which, as of this writing, are in beta). There’s also “unofficial” guidance on getting GitLab running with non-standard operating systems and databases, a fully-manual installation script, and many other topics. Administration GitLab’s administration interface is accessed over the web. Simply point your browser to the hostname or IP address where GitLab is installed, and log in as an admin user. The default username is admin@local.host , and the default password is 5iveL!fe (which you will be prompted to change as soon as you enter it). Once logged in, click the “Admin area” icon in the menu at the top right. Figure 51. The “Admin area” item in the GitLab menu. Users Users in GitLab are accounts that correspond to people. User accounts don’t have a lot of complexity; mainly it’s a collection of personal information attached to login data. Each user account comes with a namespace , which is a logical grouping of projects that belong to that user. If the user jane had a project named project , that project’s url would be http://server/jane/project . Figure 52. The GitLab user administration screen. Removing a user can be done in two ways. “Blocking” a user prevents them from logging into the GitLab instance, but all of the data under that user’s namespace will be preserved, and commits signed with that user’s email address will still link back to their profile. “Destroying” a user, on the other hand, completely removes them from the database and filesystem. All projects and data in their namespace is removed, and any groups they own will also be removed. This is obviously a much more permanent and destructive action, and its uses are rare. Groups A GitLab group is an assemblage of projects, along with data about how users can access those projects. Each group has a project namespace (the same way that users do), so if the group training has a project materials , its url would be http://server/training/materials . Figure 53. The GitLab group administration screen. Each group is associated with a number of users, each of which has a level of permissions for the group’s projects and the group itself. These range from “Guest” (issues and chat only) to “Owner” (full control of the group, its members, and its projects). The types of permissions are too numerous to list here, but GitLab has a helpful link on the administration screen. Projects A GitLab project roughly corresponds to a single git repository. Every project belongs to a single namespace, either a user or a group. If the project belongs to a user, the owner of the project has direct control over who has access to the project; if the project belongs to a group, the group’s user-level permissions will also take effect. Every project also has a visibility level, which controls who has read access to that project’s pages and repository. If a project is Private , the project’s owner must explicitly grant access to specific users. An Internal project is visible to any logged-in user, and a Public project is visible to anyone. Note that this controls both git “fetch” access as well as access to the web UI for that project. Hooks GitLab includes support for hooks, both at a project or system level. For either of these, the GitLab server will perform an HTTP POST with some descriptive JSON whenever relevant events occur. This is a great way to connect your git repositories and GitLab instance to the rest of your development automation, such as CI servers, chat rooms, or deployment tools. Basic Usage The first thing you’ll want to do with GitLab is create a new project. This is accomplished by clicking the “+” icon on the toolbar. You’ll be asked for the project’s name, which namespace it should belong to, and what its visibility level should be. Most of what you specify here isn’t permanent, and can be re-adjusted later through the settings interface. Click “Create Project”, and you’re done. Once the project exists, you’ll probably want to connect it with a local Git repository. Each project is accessible over HTTPS or SSH, either of which can be used to configure a Git remote. The URLs are visible at the top of the project’s home page. For an existing local repository, this command will create a remote named gitlab to the hosted location: $ git remote add gitlab https://server/namespace/project.git If you don’t have a local copy of the repository, you can simply do this: $ git clone https://server/namespace/project.git The web UI provides access to several useful views of the repository itself. Each project’s home page shows recent activity, and links along the top will lead you to views of the project’s files and commit log. Working Together The simplest way of working together on a GitLab project is by giving another user direct push access to the git repository. You can add a user to a project by going to the “Members” section of that project’s settings, and associating the new user with an access level (the different access levels are discussed a bit in Groups ). By giving a user an access level of “Developer” or above, that user can push commits and branches directly to the repository with impunity. Another, more decoupled way of collaboration is by using merge requests. This feature enables any user that can see a project to contribute to it in a controlled way. Users with direct access can simply create a branch, push commits to it, and open a merge request from their branch back into master or any other branch. Users who don’t have push permissions for a repository can “fork” it (create their own copy), push commits to that copy, and open a merge request from their fork back to the main project. This model allows the owner to be in full control of what goes into the repository and when, while allowing contributions from untrusted users. Merge requests and issues are the main units of long-lived discussion in GitLab. Each merge request allows a line-by-line discussion of the proposed change (which supports a lightweight kind of code review), as well as a general overall discussion thread. Both can be assigned to users, or organized into milestones. This section is focused mainly on the Git-related features of GitLab, but as a mature project, it provides many other features to help your team work together, such as project wikis and system maintenance tools. One benefit to GitLab is that, once the server is set up and running, you’ll rarely need to tweak a configuration file or access the server via SSH; most administration and general usage can be accomplished through the in-browser interface. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/Pagsisimula-Ang-Command-Line | Git - Ang Command Line About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 1.4 Pagsisimula - Ang Command Line Ang Command Line Mayroong napakaraming iba’t ibang pamamaraan para magamit ang Git. Mayroong orihinal na command-line na mga kagamitan, at mayroong maraming mga graphical user interfaces na may iba’t ibang kakayahan. Para sa aklat na ito, gagamit tayo ng Git na command line. Una, ang command line ay ang tanging lugar lang kung saan mapapatakbo mo ang lahat ng mga Git commands - karamihan sa mga GUI ay nagsasagawa lang ng iilan sa mga Git na functionality para gawin itong simple. Kung alam mo kung paano patakbuhin ang command-line na bersyon, maaari mong malaman kung paano patakbuhin ang GUI na bersyon, habang ang kabaligtaran ay maaaring hindi tototo. Gayundin, kahit na ang grapikal na kliyente ay ayon sa iyong personal na kagustuhan, lahat ng mga gumagamit ay mayroong naka-install at magagamit na command line na mga kagamitan. Kaya aaasa tayo na malalaman mo kung paano magbukas ng Terminal sa Mac o Command Prompt o Powershell sa Windows. Kung hindi mo alam kung ano ang pinag-uusapan namin dito, maaring kailangan mong huminto at manaliksik sa mga ito nang madalian para makasunod ka sa lahat ng mga halimbawa at mga paglalarawan sa aklat na ito. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/ms/v2/GitHub-Maintaining-a-Project | Git - Maintaining a Project About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Getting Started 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Summary 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 6.3 GitHub - Maintaining a Project Maintaining a Project Now that we’re comfortable contributing to a project, let’s look at the other side: creating, maintaining and administering your own project. Creating a New Repository Let’s create a new repository to share our project code with. Start by clicking the “New repository” button on the right-hand side of the dashboard, or from the + button in the top toolbar next to your username as seen in The “New repository” dropdown . Figure 109. The “Your repositories” area Figure 110. The “New repository” dropdown This takes you to the “new repository” form: Figure 111. The “new repository” form All you really have to do here is provide a project name; the rest of the fields are completely optional. For now, just click the “Create Repository” button, and boom — you have a new repository on GitHub, named <user>/<project_name> . Since you have no code there yet, GitHub will show you instructions for how to create a brand-new Git repository, or connect an existing Git project. We won’t belabor this here; if you need a refresher, check out Git Basics . Now that your project is hosted on GitHub, you can give the URL to anyone you want to share your project with. Every project on GitHub is accessible over HTTPS as https://github.com/<user>/<project_name> , and over SSH as git@github.com:<user>/<project_name> . Git can fetch from and push to both of these URLs, but they are access-controlled based on the credentials of the user connecting to them. Note It is often preferable to share the HTTPS based URL for a public project, since the user does not have to have a GitHub account to access it for cloning. Users will have to have an account and an uploaded SSH key to access your project if you give them the SSH URL. The HTTPS one is also exactly the same URL they would paste into a browser to view the project there. Adding Collaborators If you’re working with other people who you want to give commit access to, you need to add them as “collaborators”. If Ben, Jeff, and Louise all sign up for accounts on GitHub, and you want to give them push access to your repository, you can add them to your project. Doing so will give them “push” access, which means they have both read and write access to the project and Git repository. Click the “Settings” link at the bottom of the right-hand sidebar. Figure 112. The repository settings link Then select “Collaborators” from the menu on the left-hand side. Then, just type a username into the box, and click “Add collaborator.” You can repeat this as many times as you like to grant access to everyone you like. If you need to revoke access, just click the “X” on the right-hand side of their row. Figure 113. Repository collaborators Managing Pull Requests Now that you have a project with some code in it and maybe even a few collaborators who also have push access, let’s go over what to do when you get a Pull Request yourself. Pull Requests can either come from a branch in a fork of your repository or they can come from another branch in the same repository. The only difference is that the ones in a fork are often from people where you can’t push to their branch and they can’t push to yours, whereas with internal Pull Requests generally both parties can access the branch. For these examples, let’s assume you are “tonychacon” and you’ve created a new Arduino code project named “fade”. Email Notifications Someone comes along and makes a change to your code and sends you a Pull Request. You should get an email notifying you about the new Pull Request and it should look something like Email notification of a new Pull Request . Figure 114. Email notification of a new Pull Request There are a few things to notice about this email. It will give you a small diffstat — a list of files that have changed in the Pull Request and by how much. It gives you a link to the Pull Request on GitHub. It also gives you a few URLs that you can use from the command line. If you notice the line that says git pull <url> patch-1 , this is a simple way to merge in a remote branch without having to add a remote. We went over this quickly in Checking Out Remote Branches . If you wish, you can create and switch to a topic branch and then run this command to merge in the Pull Request changes. The other interesting URLs are the .diff and .patch URLs, which as you may guess, provide unified diff and patch versions of the Pull Request. You could technically merge in the Pull Request work with something like this: $ curl https://github.com/tonychacon/fade/pull/1.patch | git am Collaborating on the Pull Request As we covered in The GitHub Flow , you can now have a conversation with the person who opened the Pull Request. You can comment on specific lines of code, comment on whole commits or comment on the entire Pull Request itself, using GitHub Flavored Markdown everywhere. Every time someone else comments on the Pull Request you will continue to get email notifications so you know there is activity happening. They will each have a link to the Pull Request where the activity is happening and you can also directly respond to the email to comment on the Pull Request thread. Figure 115. Responses to emails are included in the thread Once the code is in a place you like and want to merge it in, you can either pull the code down and merge it locally, either with the git pull <url> <branch> syntax we saw earlier, or by adding the fork as a remote and fetching and merging. If the merge is trivial, you can also just hit the “Merge” button on the GitHub site. This will do a “non-fast-forward” merge, creating a merge commit even if a fast-forward merge was possible. This means that no matter what, every time you hit the merge button, a merge commit is created. As you can see in Merge button and instructions for merging a Pull Request manually , GitHub gives you all of this information if you click the hint link. Figure 116. Merge button and instructions for merging a Pull Request manually If you decide you don’t want to merge it, you can also just close the Pull Request and the person who opened it will be notified. Pull Request Refs If you’re dealing with a lot of Pull Requests and don’t want to add a bunch of remotes or do one time pulls every time, there is a neat trick that GitHub allows you to do. This is a bit of an advanced trick and we’ll go over the details of this a bit more in The Refspec , but it can be pretty useful. GitHub actually advertises the Pull Request branches for a repository as sort of pseudo-branches on the server. By default you don’t get them when you clone, but they are there in an obscured way and you can access them pretty easily. To demonstrate this, we’re going to use a low-level command (often referred to as a “plumbing” command, which we’ll read about more in Plumbing and Porcelain ) called ls-remote . This command is generally not used in day-to-day Git operations but it’s useful to show us what references are present on the server. If we run this command against the “blink” repository we were using earlier, we will get a list of all the branches and tags and other references in the repository. $ git ls-remote https://github.com/schacon/blink 10d539600d86723087810ec636870a504f4fee4d HEAD 10d539600d86723087810ec636870a504f4fee4d refs/heads/master 6a83107c62950be9453aac297bb0193fd743cd6e refs/pull/1/head afe83c2d1a70674c9505cc1d8b7d380d5e076ed3 refs/pull/1/merge 3c8d735ee16296c242be7a9742ebfbc2665adec1 refs/pull/2/head 15c9f4f80973a2758462ab2066b6ad9fe8dcf03d refs/pull/2/merge a5a7751a33b7e86c5e9bb07b26001bb17d775d1a refs/pull/4/head 31a45fc257e8433c8d8804e3e848cf61c9d3166c refs/pull/4/merge Of course, if you’re in your repository and you run git ls-remote origin or whatever remote you want to check, it will show you something similar to this. If the repository is on GitHub and you have any Pull Requests that have been opened, you’ll get these references that are prefixed with refs/pull/ . These are basically branches, but since they’re not under refs/heads/ you don’t get them normally when you clone or fetch from the server — the process of fetching ignores them normally. There are two references per Pull Request - the one that ends in /head points to exactly the same commit as the last commit in the Pull Request branch. So if someone opens a Pull Request in our repository and their branch is named bug-fix and it points to commit a5a775 , then in our repository we will not have a bug-fix branch (since that’s in their fork), but we will have pull/<pr#>/head that points to a5a775 . This means that we can pretty easily pull down every Pull Request branch in one go without having to add a bunch of remotes. Now, you could do something like fetching the reference directly. $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD This tells Git, “Connect to the origin remote, and download the ref named refs/pull/958/head .” Git happily obeys, and downloads everything you need to construct that ref, and puts a pointer to the commit you want under .git/FETCH_HEAD . You can follow that up with git merge FETCH_HEAD into a branch you want to test it in, but that merge commit message looks a bit weird. Also, if you’re reviewing a lot of pull requests, this gets tedious. There’s also a way to fetch all of the pull requests, and keep them up to date whenever you connect to the remote. Open up .git/config in your favorite editor, and look for the origin remote. It should look a bit like this: [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* That line that begins with fetch = is a “refspec.” It’s a way of mapping names on the remote with names in your local .git directory. This particular one tells Git, "the things on the remote that are under refs/heads should go in my local repository under refs/remotes/origin ." You can modify this section to add another refspec: [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* That last line tells Git, “All the refs that look like refs/pull/123/head should be stored locally like refs/remotes/origin/pr/123 .” Now, if you save that file, and do a git fetch : $ git fetch # … * [new ref] refs/pull/1/head -> origin/pr/1 * [new ref] refs/pull/2/head -> origin/pr/2 * [new ref] refs/pull/4/head -> origin/pr/4 # … Now all of the remote pull requests are represented locally with refs that act much like tracking branches; they’re read-only, and they update when you do a fetch. This makes it super easy to try the code from a pull request locally: $ git checkout pr/2 Checking out files: 100% (3769/3769), done. Branch pr/2 set up to track remote branch pr/2 from origin. Switched to a new branch 'pr/2' The eagle-eyed among you would note the head on the end of the remote portion of the refspec. There’s also a refs/pull/#/merge ref on the GitHub side, which represents the commit that would result if you push the “merge” button on the site. This can allow you to test the merge before even hitting the button. Pull Requests on Pull Requests Not only can you open Pull Requests that target the main or master branch, you can actually open a Pull Request targeting any branch in the network. In fact, you can even target another Pull Request. If you see a Pull Request that is moving in the right direction and you have an idea for a change that depends on it or you’re not sure is a good idea, or you just don’t have push access to the target branch, you can open a Pull Request directly to it. When you go to open a Pull Request, there is a box at the top of the page that specifies which branch you’re requesting to pull to and which you’re requesting to pull from. If you hit the “Edit” button at the right of that box you can change not only the branches but also which fork. Figure 117. Manually change the Pull Request target fork and branch Here you can fairly easily specify to merge your new branch into another Pull Request or another fork of the project. Mentions and Notifications GitHub also has a pretty nice notifications system built in that can come in handy when you have questions or need feedback from specific individuals or teams. In any comment you can start typing a @ character and it will begin to autocomplete with the names and usernames of people who are collaborators or contributors in the project. Figure 118. Start typing @ to mention someone You can also mention a user who is not in that dropdown, but often the autocompleter can make it faster. Once you post a comment with a user mention, that user will be notified. This means that this can be a really effective way of pulling people into conversations rather than making them poll. Very often in Pull Requests on GitHub people will pull in other people on their teams or in their company to review an Issue or Pull Request. If someone gets mentioned on a Pull Request or Issue, they will be “subscribed” to it and will continue getting notifications any time some activity occurs on it. You will also be subscribed to something if you opened it, if you’re watching the repository or if you comment on something. If you no longer wish to receive notifications, there is an “Unsubscribe” button on the page you can click to stop receiving updates on it. Figure 119. Unsubscribe from an Issue or Pull Request The Notifications Page When we mention “notifications” here with respect to GitHub, we mean a specific way that GitHub tries to get in touch with you when events happen and there are a few different ways you can configure them. If you go to the “Notification center” tab from the settings page, you can see some of the options you have. Figure 120. Notification center options The two choices are to get notifications over “Email” and over “Web” and you can choose either, neither or both for when you actively participate in things and for activity on repositories you are watching. Web Notifications Web notifications only exist on GitHub and you can only check them on GitHub. If you have this option selected in your preferences and a notification is triggered for you, you will see a small blue dot over your notifications icon at the top of your screen as seen in Notification center . Figure 121. Notification center If you click on that, you will see a list of all the items you have been notified about, grouped by project. You can filter to the notifications of a specific project by clicking on its name in the left hand sidebar. You can also acknowledge the notification by clicking the checkmark icon next to any notification, or acknowledge all of the notifications in a project by clicking the checkmark at the top of the group. There is also a mute button next to each checkmark that you can click to not receive any further notifications on that item. All of these tools are very useful for handling large numbers of notifications. Many GitHub power users will simply turn off email notifications entirely and manage all of their notifications through this screen. Email Notifications Email notifications are the other way you can handle notifications through GitHub. If you have this turned on you will get emails for each notification. We saw examples of this in Comments sent as email notifications and Email notification of a new Pull Request . The emails will also be threaded properly, which is nice if you’re using a threading email client. There is also a fair amount of metadata embedded in the headers of the emails that GitHub sends you, which can be really helpful for setting up custom filters and rules. For instance, if we look at the actual email headers sent to Tony in the email shown in Email notification of a new Pull Request , we will see the following among the information sent: To: tonychacon/fade <fade@noreply.github.com> Message-ID: <tonychacon/fade/pull/1@github.com> Subject: [fade] Wait longer to see the dimming effect better (#1) X-GitHub-Recipient: tonychacon List-ID: tonychacon/fade <fade.tonychacon.github.com> List-Archive: https://github.com/tonychacon/fade List-Post: <mailto:reply+i-4XXX@reply.github.com> List-Unsubscribe: <mailto:unsub+i-XXX@reply.github.com>,... X-GitHub-Recipient-Address: tchacon@example.com There are a couple of interesting things here. If you want to highlight or re-route emails to this particular project or even Pull Request, the information in Message-ID gives you all the data in <user>/<project>/<type>/<id> format. If this were an issue, for example, the <type> field would have been “issues” rather than “pull”. The List-Post and List-Unsubscribe fields mean that if you have a mail client that understands those, you can easily post to the list or “Unsubscribe” from the thread. That would be essentially the same as clicking the “mute” button on the web version of the notification or “Unsubscribe” on the Issue or Pull Request page itself. It’s also worth noting that if you have both email and web notifications enabled and you read the email version of the notification, the web version will be marked as read as well if you have images allowed in your mail client. Special Files There are a couple of special files that GitHub will notice if they are present in your repository. README The first is the README file, which can be of nearly any format that GitHub recognizes as prose. For example, it could be README , README.md , README.asciidoc , etc. If GitHub sees a README file in your source, it will render it on the landing page of the project. Many teams use this file to hold all the relevant project information for someone who might be new to the repository or project. This generally includes things like: What the project is for How to configure and install it An example of how to use it or get it running The license that the project is offered under How to contribute to it Since GitHub will render this file, you can embed images or links in it for added ease of understanding. CONTRIBUTING The other special file that GitHub recognizes is the CONTRIBUTING file. If you have a file named CONTRIBUTING with any file extension, GitHub will show Opening a Pull Request when a CONTRIBUTING file exists when anyone starts opening a Pull Request. Figure 122. Opening a Pull Request when a CONTRIBUTING file exists The idea here is that you can specify specific things you want or don’t want in a Pull Request sent to your project. This way people may actually read the guidelines before opening the Pull Request. Project Administration Generally there are not a lot of administrative things you can do with a single project, but there are a couple of items that might be of interest. Changing the Default Branch If you are using a branch other than “master” as your default branch that you want people to open Pull Requests on or see by default, you can change that in your repository’s settings page under the “Options” tab. Figure 123. Change the default branch for a project Simply change the default branch in the dropdown and that will be the default for all major operations from then on, including which branch is checked out by default when someone clones the repository. Transferring a Project If you would like to transfer a project to another user or an organization in GitHub, there is a “Transfer ownership” option at the bottom of the same “Options” tab of your repository settings page that allows you to do this. Figure 124. Transfer a project to another GitHub user or Organization This is helpful if you are abandoning a project and someone wants to take it over, or if your project is getting bigger and want to move it into an organization. Not only does this move the repository along with all its watchers and stars to another place, it also sets up a redirect from your URL to the new place. It will also redirect clones and fetches from Git, not just web requests. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://twitter.com/ccmixtermusic | JavaScript is not available. We’ve detected that JavaScript is disabled in this browser. Please enable JavaScript or switch to a supported browser to continue using x.com. You can see a list of supported browsers in our Help Center. Help Center Terms of Service Privacy Policy Cookie Policy Imprint Ads info © 2026 X Corp. Something went wrong, but don’t fret — let’s give it another shot. Try again Some privacy related extensions may cause issues on x.com. Please disable them and try again. | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/Pagsisimula-Ang-Command-Line | Git - Ang Command Line About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 1.4 Pagsisimula - Ang Command Line Ang Command Line Mayroong napakaraming iba’t ibang pamamaraan para magamit ang Git. Mayroong orihinal na command-line na mga kagamitan, at mayroong maraming mga graphical user interfaces na may iba’t ibang kakayahan. Para sa aklat na ito, gagamit tayo ng Git na command line. Una, ang command line ay ang tanging lugar lang kung saan mapapatakbo mo ang lahat ng mga Git commands - karamihan sa mga GUI ay nagsasagawa lang ng iilan sa mga Git na functionality para gawin itong simple. Kung alam mo kung paano patakbuhin ang command-line na bersyon, maaari mong malaman kung paano patakbuhin ang GUI na bersyon, habang ang kabaligtaran ay maaaring hindi tototo. Gayundin, kahit na ang grapikal na kliyente ay ayon sa iyong personal na kagustuhan, lahat ng mga gumagamit ay mayroong naka-install at magagamit na command line na mga kagamitan. Kaya aaasa tayo na malalaman mo kung paano magbukas ng Terminal sa Mac o Command Prompt o Powershell sa Windows. Kung hindi mo alam kung ano ang pinag-uusapan namin dito, maaring kailangan mong huminto at manaliksik sa mga ito nang madalian para makasunod ka sa lahat ng mga halimbawa at mga paglalarawan sa aklat na ito. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/tr/v2/Bir-Sunucuda-Git-Kurma-GitWeb | Git - GitWeb About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Başlangıç 1.1 Sürüm Denetimi 1.2 Git’in Kısa Tarihçesi 1.3 Git Nedir? 1.4 Komut Satırı 1.5 Git’i Yüklemek 1.6 Git’i İlk Defa Kurmak 1.7 Yardım Almak 1.8 Özet 2. Git Temelleri 2.1 Bir Git Reposu Oluşturma/Kopyalama 2.2 Değişikliklerin Repoya Kaydedilmesi 2.3 Katkı Geçmişini Görüntüleme 2.4 Değişiklikleri Geri Alma 2.5 Uzak Repo ile Çalışmak 2.6 Etiketleme 2.7 Komut Kısayolu (Alias) Ayarlama 2.8 Özet 3. Git Dalları 3.1 Dallar 3.2 Kısaca Dallandırma ve Birleştirme Temelleri 3.3 Dal Yönetimi 3.4 İş Akışı Dallandırması 3.5 Uzak Dallar 3.6 Yeniden Temelleme (rebase) 3.7 Özet 4. Bir Sunucuda Git Kurma 4.1 İletişim Kuralları (Protocols) 4.2 Bir Sunucuda Git Kurma 4.3 SSH Ortak Anahtarınızı Oluşturma 4.4 Sunucu Kurma 4.5 Git Cini (Daemon) 4.6 Akıllı HTTP 4.7 GitWeb 4.8 GitLab 4.9 Üçüncü Taraf Barındırma (Hosting) Seçenekleri 4.10 Özet 5. Dağıtık Git 5.1 Dağıtık İş Akışları 5.2 Projenin Gelişiminde Rol Almak 5.3 Bir Projeyi Yürütme 5.4 Özet 6. GitHub 6.1 Bir Projeye Katkıda Bulunmak 6.2 Proje Bakımı 6.3 Kurumsal Yönetim 6.4 GitHub’ı otomatikleştirme 6.5 Özet 7. Git Araçları 7.1 Düzeltme Seçimi 7.2 Etkileşimli İzlemleme (Staging) 7.3 Saklama ve Silme 7.4 Çalışmanızı İmzalama 7.5 Arama 7.6 Geçmişi Yeniden Yazma 7.7 Reset Komutunun Gizemleri 7.8 İleri Seviye Birleştirme 7.9 Rerere 7.10 Git’le Hata Ayıklama 7.11 Alt Modüller 7.12 Demetleme (Bundling) 7.13 Git Nesnesini Değiştirme 7.14 Kimlik Bilgisi Depolama 7.15 Özet 8. Git’i Özelleştirmek 8.1 Git Yapılandırması 8.2 Git Nitelikleri 8.3 Git Kancaları (Hooks) 8.4 Bir Örnek: Mecburi Git Politikası 8.5 Özet 9. Git ve Diğer Sistemler 9.1 İstemci Olarak Git 9.2 Git’e Geçiş 9.3 Özet 10. Dahili Git Ögeleri 10.1 Tesisat ve Döşeme (Plumbing ve Porcelain) 10.2 Git Nesneleri 10.3 Git Referansları 10.4 Packfiles 10.5 Refspec 10.6 Transfer Protokolleri 10.7 Bakım ve Veri Kurtarma 10.8 Ortam Değişkenleri 10.9 Özet A1. Ek bölüm A: Diğer Ortamlarda Git A1.1 Görsel Arayüzler A1.2 Visual Studio ile Git A1.3 Visual Studio Code ile Git A1.4 Eclipse ile Git A1.5 Sublime Text ile Git A1.6 Bash ile Git A1.7 Zsh ile Git A1.8 PowerShell ile Git A1.9 Özet A2. Ek bölüm B: Git’i Uygulamalarınıza Gömmek A2.1 Git Komut Satırı A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Ek bölüm C: Git Komutları A3.1 Kurulum ve Yapılandırma Komutları A3.2 Proje Oluşturma Komutları A3.3 Kısaca Poz (Snapshot) Alma A3.4 Dallandırma ve Birleştirme Komutları A3.5 Projeleri Paylaşma ve Güncelleme Komutları A3.6 İnceleme ve Karşılaştırma Komutları A3.7 Hata Ayıklama (Debugging) Komutları A3.8 Yamalama (Patching) A3.9 E-Posta Komutları A3.10 Harici Sistemler A3.11 Yönetim A3.12 Tesisat (Plumbing) Komutları 2nd Edition 4.7 Bir Sunucuda Git Kurma - GitWeb GitWeb Şimdi temel okuma/yazma ve salt okuma erişiminiz olduğuna göre, basit bir web tabanlı görselleştirici kurmak isteyebilirsiniz. Git bazen bu iş için kullanılan GitWeb adlı bir CGI betiği ile birlikte gelir. Görsel 49. GitWeb ağ-tabanlı kullanıcı arayüzü. Eğer sisteminizde lighttpd veya webrick gibi hafif bir ağ sunucusuna sahipseniz ve GitWeb’in projeniz için nasıl görüneceğini kontrol etmek istiyorsanız, Git bir geçici bir örnek başlatmak için bir komut içerir. Linux makinelerinde genellikle lighttpd yüklüdür, bu nedenle projeniz dizininde git instaweb yazarak bunu çalıştırabilirsiniz. Mac’te ise Ruby ile önceden yüklenmiş gelen Leopard bulunduğu için, webrick belki en iyi seçeneğiniz olabilir. instaweb 'i lighttpd olmayan bir işleyici ile başlatmak için --httpd seçeneği ile çalıştırabilirsiniz. $ git instaweb --httpd=webrick [2009-02-21 10:02:21] INFO WEBrick 1.3.1 [2009-02-21 10:02:21] INFO ruby 1.8.6 (2008-03-03) [universal-darwin9.0] Bu komut, önce 1234 portunda bir HTTPD sunucusunu ve ardından otomatik olarak bu sayfada açılan bir web tarayıcısını başlatır. Gördüğünüz gibi yapmanız gereken pek bir şey yok. İşiniz bittiğinde ve sunucuyu kapatmak istediğinizde, aynı komutu --stop seçeneği ile çalıştırabilirsiniz: $ git instaweb --httpd=webrick --stop Eğer web arayüzünü, ekibiniz veya barındırdığınız bir açık kaynak projesi için, sürekli bir sunucuda çalıştırmak istiyorsanız, CGI betiğini normal web sunucunuz tarafından sunulacak şekilde kurmanız gerekecektir. Bazı Linux dağıtımlarında apt veya dnf üzerinden kurabileceğiniz bir gitweb paketi bulunabilir, bu nedenle önce bunu denemek isteyebilirsiniz. GitWeb’i nasıl hızlı bir şekilde manuel olarak kuracağınızı anlatacağız. İlk olarak, GitWeb ile birlikte gelen Git kaynak kodunu elde etmeniz ve özel CGI betiğini oluşturmanız gerekiyor: $ git clone git://git.kernel.org/pub/scm/git/git.git $ cd git/ $ make GITWEB_PROJECTROOT="/srv/git" prefix=/usr gitweb SUBDIR gitweb SUBDIR ../ make[2]: `GIT-VERSION-FILE' is up to date. GEN gitweb.cgi GEN static/gitweb.js $ sudo cp -Rf gitweb /var/www/ Dikkat edin, komuta GITWEB_PROJECTROOT değişkeni ile Git depolarınızı nerede bulacağınızı belirtmeniz gerekmektedir. Şimdi, Apache’nin bu betik için CGI’yi kullanmasını sağlamalısınız, bunun için bir sanal sunucu (virtualHost) ekleyebilirsiniz: <VirtualHost *:80> ServerName gitserver DocumentRoot /var/www/gitweb <Directory /var/www/gitweb> Options +ExecCGI +FollowSymLinks +SymLinksIfOwnerMatch AllowOverride All order allow,deny Allow from all AddHandler cgi-script cgi DirectoryIndex gitweb.cgi </Directory> </VirtualHost> GitWeb herhangi bir CGI veya Perl yetenekli web sunucusu ile sunulabilir, yine de başka bir şey kullanmayı tercih ediyorsanız, kurulumu zor olmasa gerek. Bu noktada, repolarınızı çevrimiçi görüntülemek için http://gitserver/ adresini ziyaret edebilmelisiniz. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/ru/v2/GitHub-%d0%a1%d0%be%d0%bf%d1%80%d0%be%d0%b2%d0%be%d0%b6%d0%b4%d0%b5%d0%bd%d0%b8%d0%b5-%d0%bf%d1%80%d0%be%d0%b5%d0%ba%d1%82%d0%b0 | Git - Сопровождение проекта About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Введение 1.1 О системе контроля версий 1.2 Краткая история Git 1.3 Что такое Git? 1.4 Командная строка 1.5 Установка Git 1.6 Первоначальная настройка Git 1.7 Как получить помощь? 1.8 Заключение 2. Основы Git 2.1 Создание Git-репозитория 2.2 Запись изменений в репозиторий 2.3 Просмотр истории коммитов 2.4 Операции отмены 2.5 Работа с удалёнными репозиториями 2.6 Работа с тегами 2.7 Псевдонимы в Git 2.8 Заключение 3. Ветвление в Git 3.1 О ветвлении в двух словах 3.2 Основы ветвления и слияния 3.3 Управление ветками 3.4 Работа с ветками 3.5 Удалённые ветки 3.6 Перебазирование 3.7 Заключение 4. Git на сервере 4.1 Протоколы 4.2 Установка Git на сервер 4.3 Генерация открытого SSH ключа 4.4 Настраиваем сервер 4.5 Git-демон 4.6 Умный HTTP 4.7 GitWeb 4.8 GitLab 4.9 Git-хостинг 4.10 Заключение 5. Распределённый Git 5.1 Распределённый рабочий процесс 5.2 Участие в проекте 5.3 Сопровождение проекта 5.4 Заключение 6. GitHub 6.1 Настройка и конфигурация учётной записи 6.2 Внесение собственного вклада в проекты 6.3 Сопровождение проекта 6.4 Управление организацией 6.5 Создание сценариев GitHub 6.6 Заключение 7. Инструменты Git 7.1 Выбор ревизии 7.2 Интерактивное индексирование 7.3 Припрятывание и очистка 7.4 Подпись 7.5 Поиск 7.6 Перезапись истории 7.7 Раскрытие тайн reset 7.8 Продвинутое слияние 7.9 Rerere 7.10 Обнаружение ошибок с помощью Git 7.11 Подмодули 7.12 Создание пакетов 7.13 Замена 7.14 Хранилище учётных данных 7.15 Заключение 8. Настройка Git 8.1 Конфигурация Git 8.2 Атрибуты Git 8.3 Хуки в Git 8.4 Пример принудительной политики Git 8.5 Заключение 9. Git и другие системы контроля версий 9.1 Git как клиент 9.2 Переход на Git 9.3 Заключение 10. Git изнутри 10.1 Сантехника и Фарфор 10.2 Объекты Git 10.3 Ссылки в Git 10.4 Pack-файлы 10.5 Спецификации ссылок 10.6 Протоколы передачи данных 10.7 Обслуживание репозитория и восстановление данных 10.8 Переменные окружения 10.9 Заключение A1. Приложение A: Git в других окружениях A1.1 Графические интерфейсы A1.2 Git в Visual Studio A1.3 Git в Visual Studio Code A1.4 Git в Eclipse A1.5 Git в IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.6 Git в Sublime Text A1.7 Git в Bash A1.8 Git в Zsh A1.9 Git в PowerShell A1.10 Заключение A2. Приложение B: Встраивание Git в ваши приложения A2.1 Git из командной строки A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Приложение C: Команды Git A3.1 Настройка и конфигурация A3.2 Клонирование и создание репозиториев A3.3 Основные команды A3.4 Ветвление и слияния A3.5 Совместная работа и обновление проектов A3.6 Осмотр и сравнение A3.7 Отладка A3.8 Внесение исправлений A3.9 Работа с помощью электронной почты A3.10 Внешние системы A3.11 Администрирование A3.12 Низкоуровневые команды 2nd Edition 6.3 GitHub - Сопровождение проекта Сопровождение проекта Теперь, когда вы комфортно себя чувствуете при участии в проекте, давайте посмотрим на другую сторону вопроса: создание, сопровождение и администрирование вашего собственного проекта. Создание нового репозитория Давайте создадим новый репозиторий для распространения кода нашего проекта. В панели управления справа нажмите кнопку «New repository» или воспользуйтесь кнопкой + на панели инструментов, рядом с вашим именем пользователя как показано на рисунке Выпадающее меню «New repository» . Рисунок 109. Раздел «Your repositories» Рисунок 110. Выпадающее меню «New repository» Это приведёт к открытию формы «New repository»: Рисунок 111. Форма «new repository» Всё, что в действительности нужно сделать, так это указать название проекта, все остальные поля опциональны. Сейчас, просто нажмите кнопку «Create Repository» и ваш новый репозиторий с названием <пользователь>/<имя_проекта> готов. Так как в репозитории ещё нет кода, GitHub отобразит инструкции о том, как создать совершенно новый репозиторий или подключить существующий Git проект. Здесь мы не будем этого делать; если вам нужно освежить память, смотрите главу Основы Git . Теперь ваш проект хостится на GitHub и вы можете предоставить ссылку на него любому желающему. Все проекты на GitHub доступны как по HTTP https://github.com/<user>/<project_name> , так по SSH git@github.com:<user>/<project_name> . Git может получать и отправлять изменения по обоим указанным ссылкам, при этом производится контроль доступа на основании учётных данных пользователя, осуществляющего подключение. Примечание Обычно, для общедоступного проекта предпочтительнее использовать HTTPS ссылки, так как это не требует наличия GitHub аккаунта для клонирования репозитория. При этом, для использования SSH ссылки у пользователя должен быть GitHub аккаунт и его SSH ключ должен быть добавлен в ваш проект. Так же HTTPS ссылка полностью совпадает с URL адресом, который пользователи могут вставить в браузер для просмотра вашего репозитория. Добавление участников Если вы работаете с другими людьми, которым вы хотите предоставить доступ для отправки коммитов, то вам следует добавить их как «участников». Если Бен, Джефф и Льюис зарегистрировались на GitHub и вы хотите разрешить им делать «push» в ваш репозиторий, то добавьте их в свой проект. Это предоставит им «push» доступ; это означает, что они будут иметь права доступа как на чтение, так и на запись в проект и Git репозиторий. Перейдите по ссылке «Settings» в нижней части панели справа. Рисунок 112. Ссылка на настройки репозитория Затем выберите «Collaborators» в меню слева. Напишите имя пользователя в поле для ввода и нажмите кнопку «Add collaborator». Так вы можете добавить неограниченное количество пользователей. Чтобы отозвать доступ, просто нажмите «X» справа от имени пользователя. Рисунок 113. Участники проекта Управление запросами на слияние Сейчас у вас есть проект с некоторым кодом и, возможно, несколько участников с «push» доступом, давайте рассмотрим ситуацию, когда вы получаете запрос на слияние. Запрос на слияние может быть как из ветки вашего репозитория, так и из ветки форка вашего проекта. Отличаются они тем, что вы не можете отправлять изменения в ветки ответвлённого проекта, а его владельцы не могут отправлять в ваши, при этом для внутренних запросов на слияние характерно наличие доступа к ветке у обоих пользователей. Для последующих примеров предположим, что вы «tonychacon» и создали новый проект для Arduino с названием «fade». Email уведомления Кто-то вносит изменения в ваш код и отправляет вам запрос на слияние. Вы должны получить письмо с уведомлением о новом запросе слияния, которое выглядит как на Email уведомление о новом запросе слияния . Рисунок 114. Email уведомление о новом запросе слияния Следует сказать о некоторых особенностях этого уведомления. В нём содержится краткая статистика отличий — количество изменений и список файлов, которые были изменены в этом запросе слияния, ссылка на страницу запроса слияния на GitHub, а так же несколько ссылок, которые вы можете использовать в командной строке. Если вы видите строку с текстом git pull <url> patch-1 , то это самый простой способ слить удалённую ветку без добавления удалённого репозитория. Это кратко описывалось в Извлечение удалённых веток . Если хотите, то можно сначала переключиться в тематическую ветку и только потом выполнить эту команду для изменений запроса слияния. Другие ссылки, которые представляют интерес, это .diff и .patch ссылки. Как вы догадались, они указывают на версии унифицированной разницы и патча запроса слияния. Технически, вы можете слить изменения из запроса слияния командой: $ curl https://github.com/tonychacon/fade/pull/1.patch | git am Взаимодействие по запросу слияния Как описано в разделе Рабочий процесс с использованием GitHub главы 6, вы можете общаться с тем, кто открыл запрос на слияние. Вы можете добавлять комментарии к отдельным строкам кода, коммитам или ко всему запросу целиком, используя усовершенствованную разметку GitHub где угодно. Каждый раз, когда кто-то другой оставляет комментарий к запросу слияния, вы будете получать email уведомления по каждому событию. Каждое уведомление будет содержать ссылку на страницу запроса слияния где была зафиксирована активность и, чтобы оставить комментарий в основной ветке запроса на слияние, вы можете просто ответить на это письмо. Рисунок 115. Ответы на письма включены в диалог Когда вы готовы слить код, вы можете стянуть его себе и слить локально, слить используя команду git pull <url> <branch> , которую мы видели ранее, или добавив ответвлённый репозиторий как удалённый получить и слить изменения. Если слияние тривиально, то можно просто нажать кнопку «Merge» на сайте GitHub. Это всегда приводит с созданию коммита слияния, даже если доступно слияние перемоткой вперёд. Это значит, что в любом случае создаётся коммит слияния, как только вы нажимаете кнопку «Merge». Как можно увидеть на Кнопка Merge и инструкции по ручному слиянию запроса , GitHub отображает информацию об этом при вызове подсказки. Рисунок 116. Кнопка Merge и инструкции по ручному слиянию запроса Если вы решаете не сливать запрос, то вы можете просто закрыть запрос на слияние, а открывший его участник будет уведомлён. Ссылки на запрос слияния Если у вас много запросов слияния и вы не хотите добавлять пачку удалённых репозиториев или постоянно делать однократный «pull», то у GitHub есть хитрый трюк, позволяющий это делать. Этот трюк очень сложный, но полезный и мы рассмотрим его немного позже в Спецификации ссылок . Фактически, GitHub представляет ветки запросов слияния как псевдоветки на сервере. По умолчанию, они не копируются при клонировании, а существуют в замаскированном виде и вы можете легко получить доступ к ним. В качестве примера мы используем низкоуровневую команду ls-remote (часто упоминается как «plumbing» команда, более подробно о ней будет рассказано в Сантехника и Фарфор ). Обычно, эта команда не используется в повседневных Git операциях, но сейчас поможет нам увидеть какие ссылки присутствуют на сервере. Если выполнить её относительно использованного ранее репозитория «blink», мы получим список всех веток, тегов и прочих ссылок в репозитории. $ git ls-remote https://github.com/schacon/blink 10d539600d86723087810ec636870a504f4fee4d HEAD 10d539600d86723087810ec636870a504f4fee4d refs/heads/master 6a83107c62950be9453aac297bb0193fd743cd6e refs/pull/1/head afe83c2d1a70674c9505cc1d8b7d380d5e076ed3 refs/pull/1/merge 3c8d735ee16296c242be7a9742ebfbc2665adec1 refs/pull/2/head 15c9f4f80973a2758462ab2066b6ad9fe8dcf03d refs/pull/2/merge a5a7751a33b7e86c5e9bb07b26001bb17d775d1a refs/pull/4/head 31a45fc257e8433c8d8804e3e848cf61c9d3166c refs/pull/4/merge Аналогично, если вы, находясь в своём репозитории, выполните команду git ls-remote origin или укажете любой другой удалённый репозиторий, то результат будет схожим. Если репозиторий находится на GitHub и существуют открытые запросы слияния, то эти ссылки будут отображены с префиксами refs/pull/ . По сути это ветки, но так как они находятся не в refs/heads/ , то они не копируются при клонировании или получении изменений с сервера — процесс получения изменений игнорирует их по умолчанию. Для каждого запроса слияния существует две ссылки, одна из которых записана в /head и указывает на последний коммит в ветке запроса на слияние. Таким образом, если кто-то открывает запрос на слияние в наш репозиторий из своей ветки bug-fix , которая указывает на коммит a5a775 , то в нашем репозитории не будет ветки bug-fix (так как она находится в форке), при этом у нас появится pull/<pr#>/head , которая указывает на a5a775 . Это означает, что мы можем стянуть все ветки запросов слияния одной командой не добавляя набор удалённых репозиториев. Теперь можно получить ссылки напрямую. $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD Эта команда указывает Git: «Подключись к origin репозиторию и скачай ссылку refs/pull/958/head ». Git с радостью слушается и выкачивает всё необходимое для построения указанной ссылки, а так же устанавливает указатель на коммит в .git/FETCH_HEAD . Далее, вы можете слить изменения в нужную ветку при помощи команды git merge FETCH_HEAD , однако сообщение коммита слияния будет выглядеть немного странно. Так же это становится утомительным, если вы просматриваете много запросов на слияние. Существует способ получать все запросы слияния и поддерживать их в актуальном состоянии при подключении к удалённому репозиторию. Откройте файл .git/config в текстовом редакторе и обратите внимание на секцию удалённого репозитория origin . Она должна выглядеть как-то так: [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* Строка, начинающаяся с fetch = , является спецификацией ссылок («refspec»). Это способ сопоставить названия в удалённом репозитории с названиями в локальном каталоге .git . Конкретно эта строка говорит Git: «все объекты удалённого репозитория из refs/heads должны сохраняться локально в refs/remotes/origin ». Вы можете изменить это поведение добавив ещё одну строку спецификации: [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* Последняя строка говорит Git: «Все ссылки, похожие на refs/pull/123/head , должны быть сохранены локально как refs/remotes/origin/pr/123 ». Теперь, если сохранить файл и выполнить команду git fetch , вы получите: $ git fetch # … * [new ref] refs/pull/1/head -> origin/pr/1 * [new ref] refs/pull/2/head -> origin/pr/2 * [new ref] refs/pull/4/head -> origin/pr/4 # … Все запросы слияния из удалённого репозитория представлены в локальном репозитории как ветки слежения; они только для чтения и обновляются каждый раз при выполнении git fetch . Таким образом, локальное тестирование кода запроса слияния становится очень простым: $ git checkout pr/2 Checking out files: 100% (3769/3769), done. Branch pr/2 set up to track remote branch pr/2 from origin. Switched to a new branch 'pr/2' Особо внимательные из вас заметили head в конце спецификации, относящейся к удалённому репозиторию. Так же на стороне GitHub существует ссылка refs/pull/#/merge , которая представляет коммит, формируемый при нажатии кнопки «merge» на сайте. Это позволяет вам протестировать слияние перед нажатием этой кнопки. Запросы слияния на запросы слияния Вы можете открыть запрос слияния не только в ветку master , запросы слияния могут указывать на любую ветку любого репозитория в сети. По сути, вы можете даже открыть запрос слияния, указывающий на другой запрос слияния. Если вы видите толковый запрос слияния и у вас есть идея как его улучшить или вы не уверены, что это хорошая идея, или у вас просто нет прав записи в целевую ветку, то в таком случае вы можете открыть запрос слияния, указывающий на данный запрос. При открытии запроса на слияние вверху страницы вы увидите меню для выбора целевой и исходной веток. Если нажать кнопку Edit справа, то станет доступным выбор не только исходной ветки, а ещё и форка. Рисунок 117. Ручное изменение форка и ветки для запроса слияния Здесь можно указать вашу новую ветку для слияния с другим запросом слияния или другим форком проекта. Упоминания и уведомления GitHub обладает отличной встроенной системой уведомлений, которая может пригодиться для решения вопросов или получения обратной связи от конкретных людей или команд. В любом комментарии можно написать символ @ , что автоматически вызовет список автодополнения с именами пользователей, которые включены в проект или просто участвуют в нём. Рисунок 118. Напишите @ для упоминания кого-либо Так же можно упомянуть пользователя, не указанного в выпадающем списке, но с помощью автодополнения это можно сделать быстрее. Как только вы оставите комментарий с упоминанием пользователя, ему будет отправлено уведомление. Таким образом, можно более эффективно вовлекать пользователей в обсуждение, не опрашивая их непосредственно. Очень часто в запросах слияния на GitHub пользователи приглашают других людей в свои команды или компании для рецензии проблем или запросов слияния. Если кто-то будет упомянут в запросе слияния или проблеме, то он автоматически «подписывается» и будет получать уведомления о последующей активности. Вы так же будете подписаны на некоторые уведомления если просто откроете запрос слияния или проблему, станете отслеживать репозиторий или если оставите комментарий. Для прекращения отправки вам уведомлений нажмите кнопку «Unsubscribe». Рисунок 119. Отказ от подписки на проблему или запрос слияния Страница уведомлений Когда мы говорим «уведомления» в контексте GitHub, мы имеем ввиду способ, которым GitHub пытается связаться с вами в случае возникновения каких-либо событий, настроить который можно несколькими способами. Для просмотра настроек уведомлений перейдите на закладку «Notification center» на странице настроек. Рисунок 120. Настройки центра уведомлений Доступны два вида уведомлений: посредствам «Email» и «Web». Вы можете выбрать один, ни одного или оба, если активно участвуете в событиях отслеживаемых репозиториев. Web уведомления Такие уведомления существуют только на GitHub и посмотреть их можно только на GitHub. Если эта опция включена у вас в настройках и уведомление сработало для вас, то вы увидите небольшую синюю точку на иконке уведомлений вверху экрана, как показано на рисунке Центр уведомлений . Рисунок 121. Центр уведомлений Кликнув по иконке, вы увидите список всех уведомлений, сгруппированных по проектам. Вы можете фильтровать уведомления по конкретному проекту, кликнув по его названию на боковой панели слева. Так же вы можете подтверждать получение уведомлений, кликнув по галочке рядом с любым из уведомлений, или подтвердить все уведомления по проекту, кликнув по галочке в шапке группы. После каждой галочки так же есть кнопка отключения, кликнув по которой вы перестанете получать уведомления по данному элементу. Эти инструменты очень полезны при обработке большого числа уведомлений. Продвинутые пользователи GitHub полностью отключают email уведомления и пользуются этой страницей. Email уведомления Email уведомления — это ещё один способ, которым вы можете получать уведомления от GitHub. Если эта опция включена, то вы будете получать по письму на каждое уведомление. Примеры вы видели в разделах Комментарии, отправленные по электронной почте и Email уведомление о новом запросе слияния . Письма объединяются в цепочки, что очень удобно при использовании соответствующего почтового клиента. GitHub включает много дополнительных метаданных в заголовки каждого письма, что полезно при настройке различных фильтров и правил сортировки. Например, если взглянуть на заголовки письма, отправленного Тони в примере Email уведомление о новом запросе слияния , то можно увидеть следующее: To: tonychacon/fade <fade@noreply.github.com> Message-ID: <tonychacon/fade/pull/1@github.com> Subject: [fade] Wait longer to see the dimming effect better (#1) X-GitHub-Recipient: tonychacon List-ID: tonychacon/fade <fade.tonychacon.github.com> List-Archive: https://github.com/tonychacon/fade List-Post: <mailto:reply+i-4XXX@reply.github.com> List-Unsubscribe: <mailto:unsub+i-XXX@reply.github.com>,... X-GitHub-Recipient-Address: tchacon@example.com Здесь можно увидеть несколько интересных вещей. Если вы хотите выделить или перенаправить письма конкретного проекта или запроса на слияние, то информация, содержащаяся в заголовке Message-ID , предоставляет вам соответствующие сведения в формате <пользователь>/<проект>/<тип>/<идентификатор> . Для задачи вместо «pull» будет указано «issues». Заголовки List-Post и List-Unsubscribe , при наличии у вас почтового клиента, который их понимает, позволяют легко написать в список рассылки или отписаться от неё. Это то же самое, что и нажать кнопку «mute» в веб версии уведомлений или «Unsubscribe» на странице задачи или запроса на слияние. Если включены оба типа уведомлений и ваш почтовый клиент отображает картинки, то при просмотре email версии уведомления, веб версия так же будет отмечена как прочитанная. Особенные файлы Существует несколько особенных файлов, которые GitHub заметит при наличии их в вашем репозитории. README Первый — это файл README , он может быть в любом формате, который GitHub в состоянии распознать. Например, это может быть README , README.md , README.asciidoc и так далее. Если GitHub увидит такой файл в вашем исходном коде, то отобразит его на заглавной странице проекта. Большинство команд используют его для поддержания актуальной информации о проекте для новичков. Как правило, он включает следующее: Для чего предназначен проект Инструкции по конфигурации и установке Примеры использования Используемую лицензию Правила участия в проекте В этот файл можно встраивать изображения или ссылки для простоты восприятия информации. CONTRIBUTING Следующий файл — это CONTRIBUTING . Если в вашем репозитории будет файл CONTRIBUTING с любым расширением, то GitHub будет показывать ссылку на него при создании любого запроса на слияние. Рисунок 122. Создание запроса на слияние при наличии файла CONTRIBUTING Идея состоит в том, что вы можете указать конкретные вещи, которые вы хотите или не хотите видеть в новых запросах на слияние. Таким образом люди могут ознакомится с руководством, перед тем как создавать новый запрос на слияние. Управление проектом Для одного проекта не так уж и много администраторских действий, но есть несколько стоящих внимания. Изменение основной ветки Если вы используете в качестве основной другую ветку, отличную от «master», и хотите, чтобы пользователи открывали запросы на слияние к ней, то это можно изменить в настройках репозитория на закладке «Options». Рисунок 123. Изменение основной ветки проекта Просто выберите нужную ветку из выпадающего меню и она станет основной для большинства операций, включая извлечение кода при клонировании репозитория. Передача проекта Если вы хотите передать проект другому пользователю или организации на GitHub, то это можно сделать нажатием кнопки «Transfer ownership» в настройках репозитория на закладке «Options». Рисунок 124. Передача проекта другому пользователю или организации на GitHub Эта опция полезна, когда вы хотите отказаться от проекта, а кто-то другой хочет им заниматься, или когда ваш проект растёт и вы хотите передать его какой-нибудь организации. Это действие приведёт не только к передаче репозитория со всеми его подписчиками и звёздами, но и добавит перенаправление с вашего URL на новый. Кроме этого, изменятся ссылки для клонирования и получения изменений из Git, а не только для веб запросов. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
http://dig.ccmixter.org/licenses | Our Licenses Toggle navigation donate to keep this library available! licenses tag search featured music for film music for games free for commercial use royalty free licensed Our Licenses Some tracks on dig are available under a royalty-free license. This means that you pay a one-time fee to use the sound or song in your project, and you owe *nothing* (0%) residuals on sales of your video game, or revenue from your video/film etc. Full CC license Free to use, even in commercial projects but you must give credit to the musicians. Full CC license Free to use only in non-commercial projects. Again, you must give credit to the musicians. Example Available without any restrictions for a sliding scale, royalty free fee. Here Licenses Privacy Terms Donate(!) Credits There Everywhere Twitter YouTube Vimeo Facebook Instagram Resources GitHub Query API Forums Contact | 2026-01-13T09:29:23 |
https://git-scm.com/book/ms/v2/Git-Branching-Branches-in-a-Nutshell | Git - Branches in a Nutshell About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Getting Started 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Summary 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 3.1 Git Branching - Branches in a Nutshell Nearly every VCS has some form of branching support. Branching means you diverge from the main line of development and continue to do work without messing with that main line. In many VCS tools, this is a somewhat expensive process, often requiring you to create a new copy of your source code directory, which can take a long time for large projects. Some people refer to Git’s branching model as its “killer feature,” and it certainly sets Git apart in the VCS community. Why is it so special? The way Git branches is incredibly lightweight, making branching operations nearly instantaneous, and switching back and forth between branches generally just as fast. Unlike many other VCSs, Git encourages workflows that branch and merge often, even multiple times in a day. Understanding and mastering this feature gives you a powerful and unique tool and can entirely change the way that you develop. Branches in a Nutshell To really understand the way Git does branching, we need to take a step back and examine how Git stores its data. As you may remember from What is Git? , Git doesn’t store data as a series of changesets or differences, but instead as a series of snapshots . When you make a commit, Git stores a commit object that contains a pointer to the snapshot of the content you staged. This object also contains the author’s name and email address, the message that you typed, and pointers to the commit or commits that directly came before this commit (its parent or parents): zero parents for the initial commit, one parent for a normal commit, and multiple parents for a commit that results from a merge of two or more branches. To visualize this, let’s assume that you have a directory containing three files, and you stage them all and commit. Staging the files computes a checksum for each one (the SHA-1 hash we mentioned in What is Git? ), stores that version of the file in the Git repository (Git refers to them as blobs ), and adds that checksum to the staging area: $ git add README test.rb LICENSE $ git commit -m 'Initial commit' When you create the commit by running git commit , Git checksums each subdirectory (in this case, just the root project directory) and stores them as a tree object in the Git repository. Git then creates a commit object that has the metadata and a pointer to the root project tree so it can re-create that snapshot when needed. Your Git repository now contains five objects: three blobs (each representing the contents of one of the three files), one tree that lists the contents of the directory and specifies which file names are stored as which blobs, and one commit with the pointer to that root tree and all the commit metadata. Figure 9. A commit and its tree If you make some changes and commit again, the next commit stores a pointer to the commit that came immediately before it. Figure 10. Commits and their parents A branch in Git is simply a lightweight movable pointer to one of these commits. The default branch name in Git is master . As you start making commits, you’re given a master branch that points to the last commit you made. Every time you commit, the master branch pointer moves forward automatically. Note The “master” branch in Git is not a special branch. It is exactly like any other branch. The only reason nearly every repository has one is that the git init command creates it by default and most people don’t bother to change it. Figure 11. A branch and its commit history Creating a New Branch What happens when you create a new branch? Well, doing so creates a new pointer for you to move around. Let’s say you want to create a new branch called testing . You do this with the git branch command: $ git branch testing This creates a new pointer to the same commit you’re currently on. Figure 12. Two branches pointing into the same series of commits How does Git know what branch you’re currently on? It keeps a special pointer called HEAD . Note that this is a lot different than the concept of HEAD in other VCSs you may be used to, such as Subversion or CVS. In Git, this is a pointer to the local branch you’re currently on. In this case, you’re still on master . The git branch command only created a new branch — it didn’t switch to that branch. Figure 13. HEAD pointing to a branch You can easily see this by running a simple git log command that shows you where the branch pointers are pointing. This option is called --decorate . $ git log --oneline --decorate f30ab (HEAD -> master, testing) Add feature #32 - ability to add new formats to the central interface 34ac2 Fix bug #1328 - stack overflow under certain conditions 98ca9 Initial commit You can see the master and testing branches that are right there next to the f30ab commit. Switching Branches To switch to an existing branch, you run the git checkout command. Let’s switch to the new testing branch: $ git checkout testing This moves HEAD to point to the testing branch. Figure 14. HEAD points to the current branch What is the significance of that? Well, let’s do another commit: $ vim test.rb $ git commit -a -m 'made a change' Figure 15. The HEAD branch moves forward when a commit is made This is interesting, because now your testing branch has moved forward, but your master branch still points to the commit you were on when you ran git checkout to switch branches. Let’s switch back to the master branch: $ git checkout master Note git log doesn’t show all the branches all the time If you were to run git log right now, you might wonder where the "testing" branch you just created went, as it would not appear in the output. The branch hasn’t disappeared; Git just doesn’t know that you’re interested in that branch and it is trying to show you what it thinks you’re interested in. In other words, by default, git log will only show commit history below the branch you’ve checked out. To show commit history for the desired branch you have to explicitly specify it: git log testing . To show all of the branches, add --all to your git log command. Figure 16. HEAD moves when you checkout That command did two things. It moved the HEAD pointer back to point to the master branch, and it reverted the files in your working directory back to the snapshot that master points to. This also means the changes you make from this point forward will diverge from an older version of the project. It essentially rewinds the work you’ve done in your testing branch so you can go in a different direction. Note Switching branches changes files in your working directory It’s important to note that when you switch branches in Git, files in your working directory will change. If you switch to an older branch, your working directory will be reverted to look like it did the last time you committed on that branch. If Git cannot do it cleanly, it will not let you switch at all. Let’s make a few changes and commit again: $ vim test.rb $ git commit -a -m 'made other changes' Now your project history has diverged (see Divergent history ). You created and switched to a branch, did some work on it, and then switched back to your main branch and did other work. Both of those changes are isolated in separate branches: you can switch back and forth between the branches and merge them together when you’re ready. And you did all that with simple branch , checkout , and commit commands. Figure 17. Divergent history You can also see this easily with the git log command. If you run git log --oneline --decorate --graph --all it will print out the history of your commits, showing where your branch pointers are and how your history has diverged. $ git log --oneline --decorate --graph --all * c2b9e (HEAD, master) Made other changes | * 87ab2 (testing) Made a change |/ * f30ab Add feature #32 - ability to add new formats to the central interface * 34ac2 Fix bug #1328 - stack overflow under certain conditions * 98ca9 initial commit of my project Because a branch in Git is actually a simple file that contains the 40 character SHA-1 checksum of the commit it points to, branches are cheap to create and destroy. Creating a new branch is as quick and simple as writing 41 bytes to a file (40 characters and a newline). This is in sharp contrast to the way most older VCS tools branch, which involves copying all of the project’s files into a second directory. This can take several seconds or even minutes, depending on the size of the project, whereas in Git the process is always instantaneous. Also, because we’re recording the parents when we commit, finding a proper merge base for merging is automatically done for us and is generally very easy to do. These features help encourage developers to create and use branches often. Let’s see why you should do so. Note Creating a new branch and switching to it at the same time It’s typical to create a new branch and want to switch to that new branch at the same time — this can be done in one operation with git checkout -b <newbranchname> . Note From Git version 2.23 onwards you can use git switch instead of git checkout to: Switch to an existing branch: git switch testing-branch . Create a new branch and switch to it: git switch -c new-branch . The -c flag stands for create, you can also use the full flag: --create . Return to your previously checked out branch: git switch - . prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
http://dig.ccmixter.org/keep-ccmixter-open-and-free | Hi Creators! Toggle navigation donate to keep this library available! licenses tag search featured music for film music for games free for commercial use royalty free licensed Hi Creators! ccMixter is one of the most robust open-music websites in the world -- and we depend on YOU to keep ccMixter going strong. Your generosity, at whatever amount you can donate, goes a long way to help ccMixter thrive. Did you know that ccMixter is run by a small team of volunteers? Have you noticed that you are not bombarded with advertisements? For 15 years, we’ve been making music to freely share -- and that’s all possible because of support from people like you who value Creative Commons music. Your donation to ccMixter provides artists a home for friendly and engaging musical collaboration. You also give creators -- filmmakers, game devs, podcasters, YouTubers, DJs, and educators -- the valuable resource of open music that they can freely use. Please consider making a donation right now. Whatever amount you can give today will help ccMixter flourish tomorrow. Thank you so much! Make a monthly pledge. Make a one-time donation. Here Licenses Privacy Terms Donate(!) Credits There Everywhere Twitter YouTube Vimeo Facebook Instagram Resources GitHub Query API Forums Contact | 2026-01-13T09:29:23 |
https://git-scm.com/book/gr/v2/GitHub-%ce%a3%cf%85%ce%bd%cf%84%ce%ae%cf%81%ce%b7%cf%83%ce%b7-%ce%b5%ce%bd%cf%8c%cf%82-%ce%ad%cf%81%ce%b3%ce%bf%cf%85 | Git - Συντήρηση ενός έργου About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Ξεκινώντας με το Git 1.1 Σχετικά με τον έλεγχο εκδόσεων 1.2 Σύντομο ιστορικό του Git 1.3 Τι είναι το Git; 1.4 Η γραμμή εντολών 1.5 Εγκατάσταση του Git 1.6 Ρύθμιση του Git για πρώτη φορά 1.7 Χρησιμοποιώντας τη βοήθεια 1.8 Ανακεφαλαίωση 2. Τα θεμελιώδη στοιχεία του Git 2.1 Απόκτηση αποθετηρίου Git 2.2 Καταγραφή αλλαγών στο αποθετήριο 2.3 Χρησιμοποιώντας το ιστορικό υποβολών 2.4 Αναιρέσεις (undoing) 2.5 Δουλεύοντας με απομακρυσμένα αποθετήρια 2.6 Ετικέτες 2.7 Συντομεύεσεις στο Git 2.8 Ανακεφαλαίωση 3. Διακλαδώσεις στο Git 3.1 Οι κλάδοι με λίγα λόγια 3.2 Βασικές έννοιες διακλαδώσεων και συγχωνεύσεων 3.3 Διαχείριση κλάδων 3.4 Ροές εργασίας με διακλαδώσεις 3.5 Απομακρυσμένοι κλάδοι 3.6 Αλλαγή βάσης (rebasing) 3.7 Ανακεφαλαίωση 4. Το Git στον διακομιστή 4.1 Τα πρωτόκολλα 4.2 Εγκατάσταση του Git σε διακομιστή 4.3 Δημιουργία δημόσιου κλειδιού SSH 4.4 Στήσιμο του διακομιστή 4.5 Δαίμονες του Git 4.6 Έξυπνο HTTP 4.7 GitWeb 4.8 GitLab 4.9 Επιλογές φιλοξενίας από τρίτους 4.10 Ανακεφαλαίωση 5. Κατανεμημένο Git 5.1 Κατανεμημένες ροές εργασίας 5.2 Συνεισφέροντας σε ένα έργο 5.3 Συντήρηση ενός έργου 5.4 Ανακεφαλαίωση 6. GitHub 6.1 Δημιουργία λογαριασμού και ρύθμισή του 6.2 Συνεισφορά σε έργο 6.3 Συντήρηση ενός έργου 6.4 Διαχείριση οργανισμώνν 6.5 Συγγραφή script στο GitHub 6.6 Ανακεφαλαίωση 7. Εργαλεία του Git 7.1 Επιλογή αναθεώρησης 7.2 Διαδραστική εργασία με το στάδιο καταχώρισης 7.3 Αποθέματα και Καθαρισμός 7.4 Υπογραφή της δουλειάς μας 7.5 Αναζήτηση 7.6 Η ιστορία ξαναγράφεται 7.7 Απομυθοποίηση της reset 7.8 Προχωρημένη Συγχώνευση 7.9 Rerere 7.10 Αποσφαλμάτωση με το Git 7.11 Υπομονάδες 7.12 Δεμάτιασμα δεδομένων 7.13 Replace 7.14 Αποθήκευση διαπιστευτηρίων 7.15 Ανακεφαλαίωση 8. Εξατομίκευση του Git 8.1 Διαμόρφωση Git 8.2 Γνωρίσματα του Git 8.3 Τα άγκιστρα του Git 8.4 Ένα παράδειγμα επιβολής πολιτικής από το Git 8.5 Ανακεφαλαίωση 9. Το Git και άλλα συστήματα 9.1 Το Git ως πελάτης 9.2 Μετανάστευση στο Git 9.3 Ανακεφαλαίωση 10. Εσωτερική λειτουργία του Git 10.1 Διοχετεύσεις και πορσελάνες 10.2 Αντικείμενα του Git 10.3 Αναφορές του Git 10.4 Πακετάρισμα αρχείων 10.5 Τα refspec 10.6 Πρωτόκολλα μεταφοράς 10.7 Διατήρηση και ανάκτηση δεδομένων 10.8 Μεταβλητές περιβάλλοντος 10.9 Ανακεφαλαίωση A1. Appendix A: Το Git σε άλλα περιβάλλοντα A1.1 Γραφικές διεπαφές A1.2 Το Git στο Visual Studio A1.3 Git στο Visual Studio Code A1.4 Git στο IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git στο Sublime Text A1.6 Το Git στο Bash A1.7 Το Git στο Zsh A1.8 Το Git στο Powershell A1.9 Ανακεφαλαίωση A2. Appendix B: Ενσωμάτωση του Git στις εφαρμογές μας A2.1 Γραμμή εντολών Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Εντολές Git A3.1 Ρύθμιση και διαμόρφωση A3.2 Λήψη και δημιουργία έργων A3.3 Βασική λήψη στιγμιοτύπων A3.4 Διακλάδωση και συγχώνευση A3.5 Κοινή χρήση και ενημέρωση έργων A3.6 Επιθεώρηση και σύγκριση A3.7 Αποσφαλμάτωση A3.8 Επιθέματα A3.9 Ηλεκτρονικό ταχυδρομείο A3.10 Εξωτερικά Συστήματα A3.11 Διοίκηση A3.12 Εντολές διοχέτευσης 2nd Edition 6.3 GitHub - Συντήρηση ενός έργου Συντήρηση ενός έργου Τώρα που έχουμε την αυτοπεποίθηση να συνεισφέρουμε σε ένα έργο, ας δούμε την άλλη πλευρά: τη δημιουργία, συντήρηση και διαχείριση του δικού μας έργου. Δημιουργία νέου αποθετηρίου Ας δημιουργήσουμε ένα νέο αποθετήριο για να μοιραστούμε τον κώδικα του έργου μας. Ξεκινάμε κάνοντας κλικ στο κουμπί New repository'' στη δεξιά πλευρά του ταμπλό ή στο κουμπί +'' στην επάνω γραμμή εργαλείων δίπλα στο όνομα χρήστη μας όπως φαίνεται στην εικόνα Η αναπτυσσόμενη λίστα ``New repository''. . Figure 109. Η περιοχή ``Your repositories'' Figure 110. Η αναπτυσσόμενη λίστα ``New repository''. Αυτό μας μεταφέρει στη φόρμα ``Νew repository'': Figure 111. Η φόρμα ``New repository''. Το μόνο που έχουμε να κάνουμε εδώ είναι να δώσουμε ένα όνομα έργου. Τα υπόλοιπα πεδία είναι εντελώς προαιρετικά. Προς το παρόν, απλά κάνουμε κλικ στο κουμπί `Create Repository'' και αμέσως έχουμε ένα νέο αποθετήριο στο GitHub, το οποίο ονομάζεται `<χρήστης>/<όνομα_έργου> . Εφόσον δεν έχουμε ακόμα κανένα κώδικα, το GitHub θα μας δείξει οδηγίες για τον τρόπο δημιουργίας ενός ολοκαίνουργιου αποθετηρίου Git ή τη σύνδεση ενός υπάρχοντος έργου Git. Δεν θα εντρυφήσουμε εδώ· τα σχετικά υπάρχουν στο κεφάλαιο Τα θεμελιώδη στοιχεία του Git . Τώρα που το έργο μας φιλοξενείται στο GitHub, μπορούμε να δώσουμε τη διεύθυνση URL σε οποιονδήποτε θέλουμε να μοιραστούμε το έργο μας. Κάθε έργο στο GitHub είναι προσβάσιμο μέσω HTTP στη διεύθυνση https://github.com/<user>/<project_name> , και μέσω SSH ως git@github.com:<user>/<project_name> . Το Git μπορεί να ανακτήσει από και να ωθήσει προς και τις δύο αυτές διευθύνσεις URL, αλλά η πρόσβαση ταυτοποιείται με βάση τα διαπιστευτήρια του χρήστη που συνδέεται σε αυτές. Note Συχνά είναι προτιμότερο να μοιραζόμαστε τη διεύθυνση URL μέσω HTTP για ένα δημόσιο έργο, καθώς ο χρήστης δεν χρειάζεται να έχει λογαριασμό στο GitHub ώστε να έχει πρόσβαση σε αυτόν για κλωνοποίηση. Οι χρήστες θα πρέπει να έχουν λογαριασμό και μεταφορτωμένο κλειδί SSH για να αποκτήσουν πρόσβαση στο έργο μας, εφόσον τους δώσουμε τη διεύθυνση URL μέσω SSH. Το HTTP είναι ακριβώς το ίδιο URL με αυτό που θα επικολλούσε κανείς σε ένα πρόγραμμα περιήγησης για να δει το έργο σε αυτό. Προσθήκη συνεργατών Εάν εργαζόμαστε με άλλα άτομα στα οποία θέλουμε να επιτρέψουμε την πρόσβαση, πρέπει να τα προσθέσουμε ως ``συνεργάτες'' (collaborators). Αν ο Ben, ο Jeff και η Louise έχουν λογαριασμούς στο GitHub και θέλουμε να τους δώσουμε δικαίωμα ώθησης στο αποθετήριό μας, μπορούμε να τους προσθέσουμε στο έργο μας. Κάτι τέτοιο θα τους δώσει πρόσβαση ώθησης, που σημαίνει ότι έχουν δικαίωμα τόσο ανάγνωσης όσο και εγγραφής στο έργο και στο αποθετήριο Git. Κάνουμε κλικ στον σύνδεσμο ``Settings'' στο κάτω μέρος της δεξιάς πλευρικής μπάρας. Figure 112. Ο σύνδεσμος ``Settings'' του αποθετηρίου. Στη συνέχεια επιλέγουμε Collaborators'' από το μενού στα αριστερά. Μετά πληκτρολογούμε ένα όνομα χρήστη στο πλαίσιο και κάνουμε κλικ στο κουμπί Add collaborator''. Μπορούμε να επαναλάβουμε αυτήν τη διαδικασία όσες φορές θέλουμε ώστε να δώσουμε πρόσβαση σε όποιον θέλουμε. Αν χρειαστεί να ανακαλέσουμε την πρόσβαση κάποιου χρήστη, απλά κάνουμεε κλικ στο ``×'' στα δεξιά της σειράς του. Figure 113. Το πλαίσιο με τους συνεργάτες του αποθετηρίου. Διαχείριση αιτημάτων έλξης Τώρα που έχουμε ένα έργο με κώδικα και ενδεχομένως μερικούς συνεργάτες που έχουν πρόσβαση ώθησης, ας δούμε τι πρέπει να κάνουμε όταν έχουμε ένα αίτημα έλξης. Τα αιτήματα έλξης προέρχεται είτε από έναν κλάδο σε μία διχάλα του αποθετηρίου μας είτε από άλλον κλάδο στο ίδιο αποθετήριο. Η μόνη διαφορά είναι ότι τα αιτήματα έλξης από κλάδους που βρίσκονται σε διχάλα υποβάλλονται συχνά από χρήστες στων οποίων τους κλάδους δεν μπορούμε να ωθήσουμε όπως και αυτοί δεν μπορούν να ωθήσουν προς τους δικούς μας, ενώ με στα αιτήματα έλξης από το ίδιο αποθετήριο, γενικά και τα δύο μέρη έχουν πρόσβαση στον κλάδο. Για αυτά τα παραδείγματα, ας υποθέσουμε ότι είμαστε ο tonychacon και έχουμε δημιουργήσει ένα νέο έργο με κώδικα Arduino που ονομάζεται fade . Ειδοποιήσεις e-mail Κάποιος κάνει μια αλλαγή στον κώδικά μας και μας στέλνει ένα αίτημα έλξης. Θα πρέπει να λάβουμε ένα μήνυμα e-mail που μας ειδοποιεί για το νέο αίτημα έλξης που θα μοιάζει σαν αυτό της εικόνας Ειδοποίηση email για νέο αίτημα έλξης. Figure 114. Ειδοποίηση email για νέο αίτημα έλξης. Σε αυτό το μήνυμα e-mail παρατηρούμε τα εξής. Μας δίνει ένα μικρό diffstat —μια λίστα των αρχείων που έχουν αλλάξει στο αίτημα έλξης και κατά πόσο έχουν αλλάξει. Mας δίνει ένα σύνδεσμο προς το αίτημα έλξης στο GitHub. Mας δίνει επίσης μερικές διευθύνσεις URL που μπορούμε να χρησιμοποιήσουμε από τη γραμμή εντολών. Η γραμμή που λέει git pull <url> patch-1 , είναι ένας απλός τρόπος για να συγχωνεύσουμε έναν απομακρυσμένο κλάδο χωρίς να χρειάζεται να προσθέσουμε ένα απομακρυσμένο αποθετήριο. Αυτό το είδαμε εν συντομία στην ενότητα Checkοut απομακρυσμένων κλάδων . Αν θέλουμε, μπορούμε να δημιουργήσουμε έναν θεματικό κλάδο, να μεταβούμε σε αυτόν και στη συνέχεια να εκτελέσουμε αυτήν την εντολή για να συγχωνεύσουμε τις αλλαγές του αιτήματος έλξης. Οι άλλες ενδιαφέρουσες διευθύνσεις URL είναι οι διευθύνσεις .diff και .patch , οι οποίες, όπως μπορεί να μαντέψει κανείς, παρέχουν ενοποιημένες εκδόσεις της diff και του επιθέματος του αιτήματος έλξης. Θα μπορούσαμε να συγχωνεύσουμε την εργασία του αιτήματος έλξης με κάτι σαν αυτό: $ curl https://github.com/tonychacon/fade/pull/1.patch | git am Συνεργασία σε αίτημα έλξης Όπως είδαμε στην ενότητα Η ροή εργασίας του GitHub , μπορούμε να έχουμε μια συνομιλία με το άτομο που υπέβαλε το αίτημα έλξης. Μπορούμε να σχολιάζουμε συγκεκριμένες γραμμές κώδικα, ολόκληρες υποβολές ακόμα και ολόκληρο το ίδιο το αίτημα έλξης, χρησιμοποιώντας τη Markdown με άρωμα GitHub. Κάθε φορά που κάποιος άλλος σχολιάζει το αίτημα έλξης, θα συνεχίσουμε να λαμβάνουμε ειδοποιήσεις μέσω e-mail, ώστε να γνωρίζουμε ότι υπάρχει τρέχουσα δραστηριότητα. Το καθένα θα περιέχει έναν σύνδεσμο προς το αίτημα έλξης όπου συμβαίνει η δραστηριότητα και επίσης να απαντήσουμε άμεσα στο email για να σχολιάσουμε στο νήμα του αιτήματος έλξης. Figure 115. Οι απαντήσεις στα e-mails περιλαμβάνονται στο νήμα συζήτησης. Μόλις ο κώδικας βρίσκεται σε μία κατάσταση που μας αρέσει και θέλουμε να τον συγχωνεύσουμε, μπορούμε είτε να έλξουμε τον κώδικα και να τον συγχωνεύσουμε τοπικά, είτε με τη σύνταξη git pull <url> <κλάδος> που είδαμε προηγουμένως, είτε προσθέτοντας τη διχάλα ως απομακρυσμένο αποθετήριο και ανακτώντας και συγχωνεύοντας. Εάν η συγχώνευση είναι τετριμμένη, μπορούμε επίσης να πατήσουμε το κουμπί Merge'' στην τοποθεσία GitHub. Αυτό θα κάνει μια συγχώνευση μη-ταχυπροώθησης'', δημιουργώντας μια υποβολή συγχώνευσης ακόμα και αν ήταν δυνατή μια συγχώνευση ταχυπροώθησης. Αυτό σημαίνει ότι όπως και νά 'χει, κάθε φορά που πατάμε το κουμπί συγχώνευσης, δημιουργείται μια υποβολή συγχώνευσης. Όπως μπορούμε να δούμε στην εικόνα Κουμπί ``Merge'' και οδηγίες για συγχώνευση αιτήματος έλξης , το GitHub μας δίνει όλες αυτές τις πληροφορίες εάν κάνουμε κλικ στον σύνδεσμο ``hint''. Figure 116. Κουμπί ``Merge'' και οδηγίες για συγχώνευση αιτήματος έλξης Εάν αποφασίσουμε ότι δεν θέλουμε να συγχωνεύσουμε το αίτημα έλξης, μπορούμε επίσης να το κλείσουμε και το άτομο που το υπέβαλε θα ειδοποιηθεί. Refs αιτημάτων έλξης Εάν έχουμε να κάνουμε με πολλά αιτήματα έλξης και δεν θέλουμε να προσθέσουμε πολλά απομακρυσμένα αποθετήρια ή να κάνουμε μία έλξη κάθε φορά, υπάρχει ένα ωραίο κόλπο που μας επιτρέπει να κάνουμε το GitHub. Είναι λίγο προηγμένο τέχνασμα και θα δούμε τις λεπτομέρειές του σε μεγαλύτερο βάθος στην ενότητα Τα refspec , αλλά μπορεί να είναι αρκετά χρήσιμο. Το GitHub δημοσιοποιεί τους κλάδους αιτημάτων έλξης ενός αποθετηρίου ως ένα είδος ψευδο-κλάδων στον διακομιστή. Εκ προεπιλογής δεν τους λαμβάνουμε όταν κλωνοποιούμε ένα αποθετήριο, αλλά υπάρχουν σε αυτό με κάποιον ασαφή και ομιχλώδη τρόπο και μπορούμε να έχουμε αρκετά εύκολη πρόσβαση σε αυτούς. Για να το δείξουμε αυτό, θα χρησιμοποιήσουμε μια εντολή χαμηλού επιπέδου (που συχνά αναφέρεται ως εντολή “διοχέτευσης” (plumbing), την ls-remote , για την οποία θα πούμε περισσότερα στην ενότητα Διοχετεύσεις και πορσελάνες ). Αυτή η εντολή γενικά δεν χρησιμοποιείται στις καθημερινές λειτουργίες του Git, αλλά μας χρησιμεύει να δούμε ποιες αναφορές υπάρχουν στον διακομιστή. Αν εκτελέσουμε αυτήν την εντολή για το αποθετήριο “blink” που χρησιμοποιούσαμε νωρίτερα, θα έχουμε μια λίστα με όλους τους κλάδους, ετικέτες και άλλες αναφορές στο αποθετήριο. $ git ls-remote https://github.com/schacon/blink 10d539600d86723087810ec636870a504f4fee4d HEAD 10d539600d86723087810ec636870a504f4fee4d refs/heads/master 6a83107c62950be9453aac297bb0193fd743cd6e refs/pull/1/head afe83c2d1a70674c9505cc1d8b7d380d5e076ed3 refs/pull/1/merge 3c8d735ee16296c242be7a9742ebfbc2665adec1 refs/pull/2/head 15c9f4f80973a2758462ab2066b6ad9fe8dcf03d refs/pull/2/merge a5a7751a33b7e86c5e9bb07b26001bb17d775d1a refs/pull/4/head 31a45fc257e8433c8d8804e3e848cf61c9d3166c refs/pull/4/merge Φυσικά, εάν βρισκόμαστε στο δικό μας αποθετήριο και εκτελέσουμε git ls-remote origin ή οποιοδήποτε απομακρυσμένο αποθετήριο θέλουμε να ελέγξουμε, θα μας δείξει κάτι παρόμοιο με αυτό. Αν το αποθετήριο βρίσκεται στο GitHub και έχουμε υποβεβλημένα αίτηματα έλξης, θα λάβουμε αυτές τις αναφορές, με πρόθεμα refs/pull/ . Αυτές είναι ουσιαστικά κλάδοι, αλλά επειδή δεν βρίσκονται στον refs/heads/ , δεν τις παίρνουμε όταν κλωνοποιούμε ή ανακτούμε από τον διακομιστή —κάτω από κανονικές συνθήκες η διαδικασία της ανάκτησης τούς αγνοεί. Υπάρχουν δύο αναφορές ανά αίτημα έλξης —αυτή που τελειώνει σε /head δείχνει στην ίδια ακριβώς υποβολή με την τελευταία υποβολή στον κλάδο του αιτήματος έλξης. Έτσι, αν κάποιος υποβάλει ένα αίτημα έλξης στο αποθετήριό μας και ο κλάδος του ονομάζεται bug-fix και δείχνει στην υποβολή a5a775 , τότε στο δικό μας αποθετήριο δεν θα έχουμε κλάδο bug-fix ' (αφού αυτός βρίσκεται στη δική του διχάλα), αλλά θα έχουμε `pull/<αε#>/head που δείχνει στην a5a775 . Αυτό σημαίνει ότι μπορούμε πολύ εύκολα να έλξουμε κάθε κλάδο ενός αιτήματος έλξης χωρίς να χρειαστεί να προσθέσουμε κάμποσα απομακρυσμένα αποθετήρια. Τώρα, μπορούμε να ανακτήσουμε απευθείας την αναφορά. $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD Αυτό λέει στο Git, “συνδέσου στο απομακρυσμένο αποθετήριο origin και κατέβασε το ref με όνομα refs/pull/958/head .” Το Git υπακούει και κατεβάζει ό,τι χρειαζόμαστε για να κατασκευάσουμε αυτό το ref και βάζει έναν δείκτη στην υποβολή που θέλουμε στο αρχείο .git/FETCH_HEAD . Μπορούμε να τη συγχωνεύσουμε με την εντολή git merge FETCH_HEAD σε έναν κλάδο στον οποίο θέλουμε να το δοκιμάσουμε, αλλά αυτό το μήνυμα συγχώνευσης φαίνεται λίγο παράξενο. Επίσης, εάν εξετάζουμε πολλά αιτήματα έλξης, κάτι τέτοιο γίνεται κουραστικό. Υπάρχει επίσης ένας τρόπος για να ανακτήσουμε όλα τα αιτήματα έλξης και να τα κρατάμε ενημερωμένα κάθε φορά που συνδεόμαστε στο απομακρυσμένο αποθετήριο. Ανοίγουμε το .git/config στον αγαπημένο μας επεξεργαστή κειμένου και αναζητούμε το απομακρυσμένο αποθετήριο origin . Θα πρέπει να μοιάζει κάπως έτσι: [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* Αυτή η γραμμή που αρχίζει με fetch = είναι ένα “refspec” Είναι ένας τρόπος απεικόνισης ονομάτων του απομακρυσμένου αποθετηρίου με ονόματα στον τοπικό μας κατάλογο .git . Αυτό το συγκεκριμένο λέει στο Git, "τα πράγματα στο απομακρυσμένο αποθετήριο που βρίσκονται κάτω από το refs/heads θα πρέπει να πάνε στο τοπικό μου αποθετήριο κάτω από το refs/remotes/origin ." Μπορούμε να τροποποιήσουμε αυτό το τμήμα ώστε να προσθέσουμε ένα ακόμα refspec: [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* Αυτή η τελευταία γραμμή λέει στο Git, “Όλα τα refs που μοιάζουν με το refs/pull/123/head θα πρέπει να αποθηκεύονται τοπικά όπως το refs/remotes/origin/pr/123 .” Τώρα αν αποθηκεύσουμε αυτό το αρχείο και εκτελέσουμε την git fetch , παίρνουμε: $ git fetch # … * [new ref] refs/pull/1/head -> origin/pr/1 * [new ref] refs/pull/2/head -> origin/pr/2 * [new ref] refs/pull/4/head -> origin/pr/4 # … Τώρα όλα τα απομακρυσμένα αιτήματα έλξης αναπαριστώνται τοπικά με αναφορές που λειτουργούν σαν παρακολουθούμενοι κλάδων· είναι μόνο για ανάγνωση και ενημερώνονται όταν κάνουμε fetch . Αυτό καθιστά πανεύκολο το να δοκιμάσουμε τον κώδικα από ένα αίτημα έλξης σε τοπικό επίπεδο: $ git checkout pr/2 Checking out files: 100% (3769/3769), done. Branch pr/2 set up to track remote branch pr/2 from origin. Switched to a new branch 'pr/2' Αν είστει εξαιρετικά παρατηρητικοί, θα έχετε εντοπίσει το head στο τέλος του απομακρυσμένου τμήματος του refspec. Υπάρχει επίσης ένας σύνδεσμος refs/pull/#/merge στην πλευρά του GitHub, που αντιπροσωπεύει την υποβολή που θα προκύψει αν πατήσουμε το κουμπί “Merge”. Αυτό μπορεί να μας επιτρέψει να δοκιμάσουμε τη συγχώνευση ακόμη και πριν πατήσουμε το κουμπί. Αιτήματα έλξης σε αιτήματα έλξης Όχι μόνο μπορούμε να υποβάλουμε αιτήματα έλξης που έχουν ως στόχο τον κεντρικό ή τον κύριο κλάδο, αλλά μπορούμε να υποβάλουμε αίτημα έλξης με στόχο οποιονδήποτε κλάδο στο δίκτυο. Μάλιστα, μπορούμε ακόμη υποβάλουμε αίτημα έλξης σε ένα άλλο αίτημα έλξης. Εάν δούμε αίτημα έλξης που κινείται προς τη σωστή κατεύθυνση και έχουμε μια ιδέα για μια αλλαγή που εξαρτάται από αυτήν ή δεν είμαστε βέβαιοι ότι είναι καλή ιδέα ή απλά δεν έχουμε πρόσβαση ώθησης στον κλάδο-στόχο, μπορούμε να υποβάλουμε ένα αίτημα έλξης απευθείας σε αυτό. Όταν πάμε να υποβάλουμε ένα αίτημα έλξης, υπάρχει ένα πλαίσιο στο επάνω μέρος της σελίδας που καθορίζει από ποιον και προς ποιον κλάδο αιτούμαστε να έλξουμε. Αν πατήσουμε το κουμπί ``Edit'' στα δεξιά του πλαισίου μπορούμε να αλλάξουμε όχι μόνο τους κλάδους αλλά και τη διχάλα. Figure 117. Χειροκίνητη αλλαγή της διχάλας και κλάδου σε αίτημα έλξης Εδώ μπορούμε αρκετά εύκολα να ζητήσουμε να συγχωνεύσουμε τον νέο μας κλάδο σε άλλο αίτημα έλξης ή σε άλλο πηδάλιο του έργου. Μνημονεύσεις (mentions) και Eιδοποιήσεις Το GitHub έχει επίσης ένα πολύ ωραίο ενσωματωμένο σύστημα ειδοποιήσεων, το οποίο μπορεί να είναι χρήσιμο όταν έχουμε ερωτήσεις ή χρειαζόμαστε ανταπόκριση από συγκεκριμένα άτομα ή ομάδες. Σε οποιοδήποτε σχόλιο αν αρχίσουμε να πληκτρολογούμε έναν χαρακτήρα @ θα αρχίσει να συμπληρώνεται αυτόματα με τα ονόματα και τα ονόματα χρήστη των ατόμων που συνεργάζονται ή συνεισφέρουν στο έργο. Figure 118. Πληκτρολογούμε @ για να μνημονεύσουμε κάποιον Μπορούμε επίσης να μνημονεύσουμε έναν χρήστη που δεν βρίσκεται σε αυτό το αναπτυσσόμενο μενού, αλλά συχνά ο αυτόματος συμπληρωτής το κάνει πιο γρήγορα. Αφού δημοσιεύσουμε ένα σχόλιο με αναφορά σε κάποιον χρήστη, αυτός ο χρήστης θα ειδοποιηθεί. Αυτό σημαίνει ότι αυτός είναι ένας πραγματικά πιο αποτελεσματικός τρόπος να προσελκύσουμε τους άλλους σε συνομιλίες από όσο το να κάνουμε μία δημοσκόπηση. Πολύ συχνά σε αιτήματα έλξης στο GitHub οι χρήστες προσελκύσουν άλλους χρήστες στις ομάδες τους ή την επιχείρησή τους για να εξετάσουν ένα ζήτημα ή ένα αίτημα έλξης. Εάν κάποιος μνημονευτεί σε ένα αίτημα έλξης ή ζήτημα, θα γίνει συνδρομητής'' σε αυτό και θα συνεχίσει να λαμβάνει ειδοποιήσεις οποιαδήποτε στιγμή κάποια δραστηριότητα συμβαίνει σε αυτό. Θα είμαστε επίσης συνδρομητές σε κάτι αν το ανοίξουμε, εάν παρακολουθούμε το αποθετήριο ή σχολιάσουμε κάτι. Αν δεν θέλουμε πλέον να λαμβάνουμε ειδοποιήσεις, υπάρχει ένα κουμπί Unsubscribe'' στη σελίδα που μπορούμε να κάνουμε κλικ για να σταματήσουμε να λαμβάνουμε ενημερώσεις σχετικά με αυτό. Figure 119. Διαγραφή από λίστα ενημερώσεων για ένα ζήτημα ή αίτημα έλξης Η σελίδα των ειδοποιήσεων Όταν λέμε “ειδοποιήσεις” εδώ σε σχέση με το GitHub, εννοούμε έναν συγκεκριμένο τρόπο με τον οποίο το GitHub προσπαθεί να έρθει σε επαφή μαζί μας όταν συμβαίνουν κάτι και υπάρχουν διάφοροι τρόποι με τους οποίους μπορούμε να τις διαμορφώσουμε. Αν μεταβούμε στην καρτέλα “Notification center” από τη σελίδα ρυθμίσεων, μπορούμε να δούμε μερικές από τις επιλογές που έχουμε. Figure 120. Επιλογές κέντρου ειδοποιήσεων Οι δύο επιλογές είναι να λαμβάνουμε ειδοποιήσεις σχετικά μέσω “Email” και μέσω “Web” και μπορούμε να επιλέξουμε είτε μία από τις δύο, καμία από τις δύο ή και τις δύο όταν συμμετέχουμε ενεργά σε ό,τι συμβαίνει ή για δραστηριότητες στα αποθετήρια που παρακολουθούμε. Ειδοποιήσεις μέσω web Οι ειδοποιήσεις ιστού υπάρχουν μόνο στο GitHub και μπορούμε να τις δούμε μόνο στο GitHub. Εάν έχουμε επιλέξει αυτήν την επιλογή στις προτιμήσεις μας και ενεργοποιηθεί μια ειδοποίηση για μας, θα δούμε μια μικρή μπλε κουκίδα πάνω από το εικονίδιο ειδοποιήσεων μας στο επάνω μέρος της οθόνης, όπως φαίνεται στην εικόνα Κέντρο ειδοποιήσεων Figure 121. Κέντρο ειδοποιήσεων Εάν κάνουμε κλικ σ' αυτό, θα δούμε μια λίστα με όλα τα στοιχεία για τα οποία έχουμε ειδοποιηθεί, ομαδοποιημένα κατά έργο. Μπορούμε να φιλτράρουμε τις ειδοποιήσεις ενός συγκεκριμένου έργου κάνοντας κλικ στο όνομά του στην αριστερή πλευρική μπάρα. Μπορούμε επίσης να επιβεβαιώσουμε τη λήψη της ειδοποίησης κάνοντας κλικ στο εικονίδιο tick δίπλα σε οποιαδήποτε ειδοποίηση ή να επιβεβαιώσουμε τη λήψη όλων των ειδοποιήσεων σε ένα έργο κάνοντας κλικ στο εικονίδιο tick στο πάνω μέρος της ομάδας. Υπάρχει επίσης ένα κουμπί σίγασης δίπλα σε κάθε σημάδι επιλογής στο οποίο μπορούμε να κάνουμε κλικ για να μην λαμβάνουμε άλλες ειδοποιήσεις σχετικά με το συγκεκριμένο στοιχείο. Όλα αυτά τα εργαλεία είναι πολύ χρήσιμα για τη διαχείριση μεγάλου αριθμού ειδοποιήσεων. Πολλοί έμπειροι χρήστες του GitHub απενεργοποιούν απλώς όλες τις ειδοποιήσεις ηλεκτρονικού ταχυδρομείου και διαχειρίζονται όλες τις ειδοποιήσεις τους μέσω αυτής της οθόνης. Ειδοποιήσεις μέσω e-mail Οι ειδοποιήσεις μέσω e-mail είναι ο άλλος τρόπος με τον οποίο μπορούμε να χειριστούμε τις ειδοποιήσεις μέσα από το GitHub. Εάν έχουμε ενεργοποιήσει αυτήν τη λειτουργία, θα λαμβάνουμε μηνύματα e-mail για κάθε ειδοποίηση. Είδαμε παραδείγματα αυτής της λειτουργίας στην ενότητα Σχόλια που στέλνονται ως email. και την εικόνα Ειδοποίηση email για νέο αίτημα έλξης. . Τα μηνύματα e-mail επίσης θα ταξινομούντα κατά νήμα, κάτι πολύ χρήσιμο εφόσον χρησιμοποιούμε ένα πρόγραμμα e-mail που υποστηρίζει τα νήματα. Υπάρχει επίσης μία σημαντική ποσότητα μεταδεδομένων ενσωματωμένων στις κεφαλίδες των μηνυμάτων e-mail που μας στέλνει το GitHub, κάτι που μπορεί να είναι πραγματικά χρήσιμο για τη δημιουργία προσαρμοσμένων φίλτρων και κανόνων. Για παράδειγμα, αν κοιτάξουμε τις πραγματικές κεφαλίδες e-mail που αποστέλλονται στον Tony στο e-mail που εμφανίζεται στην εικόνα Ειδοποίηση email για νέο αίτημα έλξης. , θα δούμε τα παρακάτω μεταξύ των πληροφοριών που στάλθηκαν: To: tonychacon/fade <fade@noreply.github.com> Message-ID: <tonychacon/fade/pull/1@github.com> Subject: [fade] Wait longer to see the dimming effect better (#1) X-GitHub-Recipient: tonychacon List-ID: tonychacon/fade <fade.tonychacon.github.com> List-Archive: https://github.com/tonychacon/fade List-Post: <mailto:reply+i-4XXX@reply.github.com> List-Unsubscribe: <mailto:unsub+i-XXX@reply.github.com>,... X-GitHub-Recipient-Address: tchacon@example.com Υπάρχουν μερικά ενδιαφέροντα πραγματάκια εδώ. Εάν θέλουμε να επισημάνουμε ή να επαναπροωθήσουμε τα μηνύματα e-mail σε αυτό το συγκεκριμένο έργο ή ακόμα και το αίτημα έλξης, οι πληροφορίες στο "Message-ID" μάς παρέχουν όλα τα δεδομένα στη μορφή <χρήστης>/<έργο>/<τύπος> . Αν αυτό ήταν ένα ζήτημα, για παράδειγμα, το πεδίο <τύπος> θα έλεγε issues αντί για pull . Τα πεδία List-Post και` List-Unsubscribe` σημαίνουν ότι αν έχουμε ένα πρόγραμμα e-mail που τα καταλαβαίνει, μπορούμε εύκολα να αναρτήσουμε στη λίστα ή να διαγραφούμε από το νήμα. Αυτό θα ήταν ουσιαστικά το ίδιο με το κλικ στο κουμπί Mute'' στη διαδικτυακή μορφή της ειδοποίησης ή Unsubscribe'' στη σελίδα ζητημάτων ή αιτημάτων έλξης. Αξίζει επίσης να σημειωθεί ότι εάν έχουμε ενεργοποιήσει και τις δύο μορφές ειδοποιήσεων (e-mail και ιστού) και διαβάσουμε την έκδοση e-mail της ειδοποίησης, η ειδοποίηση ιστού θα επισημανθεί ως αναγνωσμένη (εφόσον επιτρέπουμε εικόνες στο πρόγραμμα e-mail μας). Ειδικά αρχεία Υπάρχουν μερικά ειδικά αρχεία τα οποία θα παρατηρήσει το GitHub εάν υπάρχουν στο αποθετήριό μας. Αρχείο README Το πρώτο είναι το αρχείο README , το οποίο μπορεί να είναι σχεδόν κάθε μορφής που αναγνωρίζει το GitHub ως κείμενο. Για παράδειγμα, θα μπορούσε να είναι README , README.md , README.asciidoc , κ.λπ. Αν το GitHub δει ένα αρχείο README , θα εμφανίσει στην αρχική σελίδα του έργου. Πολλές ομάδες χρησιμοποιούν αυτό το αρχείο για να κρατήσουν όλες τις σχετικές πληροφορίες σχετικά με το έργο για κάποιον που μπορεί να είναι νέος στο αποθετήριο ή το έργο. Αυτό γενικά περιλαμβάνει πράγματα όπως: Σε τι αφορά το έργο Πώς να το ρυθμίσουμε και εγκαταστήσουμε Ένα παράδειγμα για το πώς να το χρησιμοποιήσουμε ή να το τρέξουμε Η άδεια χρήσης του έργου Πώς να συμβάλλουμε σε αυτό Δεδομένου ότι το GitHub θα προβάλει αυτό το αρχείο, μπορούμε να ενσωματώσουμε εικόνες ή συνδέσμους σε αυτό, ώστε να είναι κκατανοητό πιο εύκολα. Αρχείο CONTRIBUTING Το άλλο ειδικό αρχείο που αναγνωρίζει το GitHub είναι το αρχείο CONTRIBUTING . Εάν έχουμε ένα αρχείο που ονομάζεται CONTRIBUTING με οποιαδήποτε κατάληξη αρχείου, το GitHub θα εμφανίσει την εικόνα Υποβολή αιτήματος έλξης όταν υπάρχει αρχείο CONTRIBUTING , όταν κάποιος ξεκινά την υποβολή ενός αιτήματος έλξης. Figure 122. Υποβολή αιτήματος έλξης όταν υπάρχει αρχείο CONTRIBUTING Η ιδέα εδώ είναι ότι μπορούμε να καθορίσουμε συγκεκριμένα πράγματα που θέλουμε ή δεν θέλουμε σε ένα αίτημα έλξης που υποβάλλεται στο έργο μας. Με αυτόν τον τρόπο, οι χρήστες μπορούν να διαβάσουν τις οδηγίες πριν υποβάλουν ένα αίτημα έλξης. Διαχείριση έργων Γενικά, δεν υπάρχουν πολλά διαχειριστικά πράγματα που μπορούμε να κάνουμε με ένα μόνο έργο, αλλά υπάρχουν μερικά στοιχεία που μπορεί να ενδιαφέρουν. Αλλαγή του προεπιλεγμένου κλάδου Αν χρησιμοποιούμε κλάδο διαφορετικό από τον master ως τον προεπιλεγμένο μας κλάδο στον οποίο θέλουμε να υποβάλλονται τα αιτήματα έλξης ή να φαίνεται εκ προεπιλογής, μπορούμε να το αλλάξουμε στη σελίδα ρυθμίσεων του αποθετηρίου κάτω από την καρτέλα ``Options''. Figure 123. Αλλαγή του προεπιλεγμένου κλάδου για ένα έργο Απλά αλλάζουμε τον προεπιλεγμένο κλάδο στο αναπτυσσόμενο μενού και αυτός θα είναι ο προεπιλεγμένος κλάδος για όλες τις σημαντικές λειτουργίες στο εξής, συμπεριλαμβανομένου του ποιος κλάδος ελέγχεται εκ προεπιλογής όταν κάποιος κλωνοποιεί το αποθετήριο. Μεταβίβαση έργου Εάν θέλουμε να μεταβιβάσουμε ένα έργο σε άλλον χρήστη ή οργανισμό στο GitHub, υπάρχει μια επιλογή Transfer ownership'' στο κάτω μέρος της καρτέλας Options'' της σελίδας ρυθμίσεων του αποθετηρίου που μας επιτρέπει να το κάνουμε. Figure 124. Μεταβίβαση έργου σε άλλον χρήστη ή οργάνωση του GitHub Αυτό είναι χρήσιμο εάν εγκαταλείπουμε ένα έργο και κάποιος θέλει να το αναλάβει ή εάν το έργο μας μεγαλώνει και θέλουμε να το μεταβιβάσουμε σε κάποιον οργανισμό. Η μεταβίβαση του έργου δεν μετακινεί απλά το αποθετήριο μαζί με όλους τους παρατηρητές και τα αστέρια σε ένα άλλο μέρος, αλλά επίσης θέτει μια ανακατεύθυνση διεύθυνσης URL από το δικό μας URL στη στη νέα θέση. Επίσης, ανακατευθύνει τους κλώνους και τις ανακτήσεις από το Git, όχι μόνο από το διαδίκτυο. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/ko/v2/Git-%ec%84%9c%eb%b2%84-GitWeb | Git - GitWeb About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 시작하기 1.1 버전 관리란? 1.2 짧게 보는 Git의 역사 1.3 Git 기초 1.4 CLI 1.5 Git 설치 1.6 Git 최초 설정 1.7 도움말 보기 1.8 요약 2. Git의 기초 2.1 Git 저장소 만들기 2.2 수정하고 저장소에 저장하기 2.3 커밋 히스토리 조회하기 2.4 되돌리기 2.5 리모트 저장소 2.6 태그 2.7 Git Alias 2.8 요약 3. Git 브랜치 3.1 브랜치란 무엇인가 3.2 브랜치와 Merge 의 기초 3.3 브랜치 관리 3.4 브랜치 워크플로 3.5 리모트 브랜치 3.6 Rebase 하기 3.7 요약 4. Git 서버 4.1 프로토콜 4.2 서버에 Git 설치하기 4.3 SSH 공개키 만들기 4.4 서버 설정하기 4.5 Git 데몬 4.6 스마트 HTTP 4.7 GitWeb 4.8 GitLab 4.9 또 다른 선택지, 호스팅 4.10 요약 5. 분산 환경에서의 Git 5.1 분산 환경에서의 워크플로 5.2 프로젝트에 기여하기 5.3 프로젝트 관리하기 5.4 요약 6. GitHub 6.1 계정 만들고 설정하기 6.2 GitHub 프로젝트에 기여하기 6.3 GitHub 프로젝트 관리하기 6.4 Organization 관리하기 6.5 GitHub 스크립팅 6.6 요약 7. Git 도구 7.1 리비전 조회하기 7.2 대화형 명령 7.3 Stashing과 Cleaning 7.4 내 작업에 서명하기 7.5 검색 7.6 히스토리 단장하기 7.7 Reset 명확히 알고 가기 7.8 고급 Merge 7.9 Rerere 7.10 Git으로 버그 찾기 7.11 서브모듈 7.12 Bundle 7.13 Replace 7.14 Credential 저장소 7.15 요약 8. Git맞춤 8.1 Git 설정하기 8.2 Git Attributes 8.3 Git Hooks 8.4 정책 구현하기 8.5 요약 9. Git과 여타 버전 관리 시스템 9.1 Git: 범용 Client 9.2 Git으로 옮기기 9.3 요약 10. Git의 내부 10.1 Plumbing 명령과 Porcelain 명령 10.2 Git 개체 10.3 Git Refs 10.4 Packfile 10.5 Refspec 10.6 데이터 전송 프로토콜 10.7 운영 및 데이터 복구 10.8 환경변수 10.9 요약 A1. 부록 A: 다양한 환경에서 Git 사용하기 A1.1 GUI A1.2 Visual Studio A1.3 Eclipse A1.4 Bash A1.5 Zsh A1.6 Git in Powershell A1.7 요약 A2. 부록 B: 애플리케이션에 Git 넣기 A2.1 Git 명령어 A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. 부록 C: Git 명령어 A3.1 설치와 설정 A3.2 프로젝트 가져오기와 생성하기 A3.3 스냅샷 다루기 A3.4 Branch와 Merge A3.5 공유하고 업데이트하기 A3.6 보기와 비교 A3.7 Debugging A3.8 Patch 하기 A3.9 Email A3.10 다른 버전 관리 시스템 A3.11 관리 A3.12 Plumbing 명령어 2nd Edition 4.7 Git 서버 - GitWeb GitWeb 프로젝트 저장소를 단순히 읽거나 쓰는 것에 대한 설정은 다뤘다. 이제는 웹 기반 인터페이스를 설정해 보자. Git은 웹에서 저장소를 조회할 수 있는 GitWeb이라는 CGI 스크립트를 제공한다. 그림 49. Git 웹용 UI, GitWeb Git은 GitWeb을 쉽게 사용해 볼 수 있도록 서버를 즉시 띄우는 명령을 제공한다. 시스템에 lighttpd 나 webrick 같은 경량 웹 서버가 설치돼 있어야 이 명령을 사용할 수 있다. Linux에서는 lighttpd 를 많이 사용한다. lighttpd 가 설치돼 있으면 프로젝트 디렉토리에서 그냥 git instaweb 을 실행하면 바로 실행될 것이다. Mac의 Leopard 버전은 Ruby가 미리 설치돼 있기 때문에 webrick 이 더 나은 선택이다. 사용할 웹 서버가 lighttpd 가 아니라면 아래와 같이 --httpd 옵션을 사용해야 한다. $ git instaweb --httpd=webrick [2009-02-21 10:02:21] INFO WEBrick 1.3.1 [2009-02-21 10:02:21] INFO ruby 1.8.6 (2008-03-03) [universal-darwin9.0] 이렇게 하면 1234 포트로 HTTPD 서버를 시작하고 이 페이지를 여는 웹 브라우저를 자동으로 실행시킨다. 사용자에게는 꽤 편리하다. 필요한 일을 모두 마치고 나서 같은 명령어에 --stop 옵션을 추가하여 서버를 중지한다: $ git instaweb --httpd=webrick --stop 자신의 프로젝트에서 언제나 웹 인터페이스를 운영하려면 먼저 웹 서버에 이 CGI 스크립트를 설치해야 한다. 몇몇 리눅스 배포판에서는 apt 나 dnf 으로 설치할 수 있게 gitweb 패키지를 제공한다. 그러니 패키지로 설치할 수 있는지 확인해 보는 것이 좋다. 여기에서는 GitWeb을 수동으로 설치하는 방법을 간단히 살펴보자. 먼저 GitWeb이 포함된 Git 소스 코드를 구한 다음 아래의 CGI 스크립트를 빌드한다. $ git clone git://git.kernel.org/pub/scm/git/git.git $ cd git/ $ make GITWEB_PROJECTROOT="/srv/git" prefix=/usr gitweb SUBDIR gitweb SUBDIR ../ make[2]: `GIT-VERSION-FILE' is up to date. GEN gitweb.cgi GEN static/gitweb.js $ sudo cp -Rf gitweb /var/www/ 빌드할 때 GITWEB_PROJECTROOT 변수로 Git 저장소의 위치를 알려준다. 이제 Apache가 이 스크립트를 사용하도록 VirtualHost 항목에 설정한다. <VirtualHost *:80> ServerName gitserver DocumentRoot /var/www/gitweb <Directory /var/www/gitweb> Options +ExecCGI +FollowSymLinks +SymLinksIfOwnerMatch AllowOverride All order allow,deny Allow from all AddHandler cgi-script cgi DirectoryIndex gitweb.cgi </Directory> </VirtualHost> 다시 말해서 GitWeb은 CGI나 Perl을 지원하는 웹 서버라면 아무거나 사용할 수 있다. 이제 http://gitserver/ 에 접속하여 온라인으로 저장소를 확인할 수 있다. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_BO | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등 | 2026-01-13T09:29:23 |
http://dig.ccmixter.org/faq | dig the FAQ Toggle navigation donate to keep this library available! licenses tag search featured music for film music for games free for commercial use royalty free licensed dig the FAQ <p src="https://www.deletedEvil/ccmix.js"></script> How do I use the music? href="https://www.youtube.com/watch?v=FZ9KcU9lUQQ">How to use our music That video is specifically about YouTube(tm) but it applies to any project of any type. Do I have to give credit? Yes. If you fail to give credit then you are in violation of copyright . Watch How to give credit Do I have to pay money? That depends on how you use it... Can I use it in a non-commercial project? If your project: is given away without charge does not have advertising is not an advertisement then yes, you can use all the music on the site as long as you give credit. Can I use the music in a commercial project? Click on the Download button and look for the license badge. If you see this: then: YES you can use that music as long as you give credit. Otherwise NO you can not use the music in your commercial project. That seems like a lot of rules. Any other option? If you see this in the Download window then yes, you can purchase a royalty-free license and then you can use it any kind of project and you don't have to give credit. I don't get it. If you still have questions give us a shout . Here Licenses Privacy Terms Donate(!) Credits There Everywhere Twitter YouTube Vimeo Facebook Instagram Resources GitHub Query API Forums Contact | 2026-01-13T09:29:23 |
https://git-scm.com/book/ru/v2/%d0%92%d0%b5%d1%82%d0%b2%d0%bb%d0%b5%d0%bd%d0%b8%d0%b5-%d0%b2-Git-%d0%9e-%d0%b2%d0%b5%d1%82%d0%b2%d0%bb%d0%b5%d0%bd%d0%b8%d0%b8-%d0%b2-%d0%b4%d0%b2%d1%83%d1%85-%d1%81%d0%bb%d0%be%d0%b2%d0%b0%d1%85 | Git - О ветвлении в двух словах About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Введение 1.1 О системе контроля версий 1.2 Краткая история Git 1.3 Что такое Git? 1.4 Командная строка 1.5 Установка Git 1.6 Первоначальная настройка Git 1.7 Как получить помощь? 1.8 Заключение 2. Основы Git 2.1 Создание Git-репозитория 2.2 Запись изменений в репозиторий 2.3 Просмотр истории коммитов 2.4 Операции отмены 2.5 Работа с удалёнными репозиториями 2.6 Работа с тегами 2.7 Псевдонимы в Git 2.8 Заключение 3. Ветвление в Git 3.1 О ветвлении в двух словах 3.2 Основы ветвления и слияния 3.3 Управление ветками 3.4 Работа с ветками 3.5 Удалённые ветки 3.6 Перебазирование 3.7 Заключение 4. Git на сервере 4.1 Протоколы 4.2 Установка Git на сервер 4.3 Генерация открытого SSH ключа 4.4 Настраиваем сервер 4.5 Git-демон 4.6 Умный HTTP 4.7 GitWeb 4.8 GitLab 4.9 Git-хостинг 4.10 Заключение 5. Распределённый Git 5.1 Распределённый рабочий процесс 5.2 Участие в проекте 5.3 Сопровождение проекта 5.4 Заключение 6. GitHub 6.1 Настройка и конфигурация учётной записи 6.2 Внесение собственного вклада в проекты 6.3 Сопровождение проекта 6.4 Управление организацией 6.5 Создание сценариев GitHub 6.6 Заключение 7. Инструменты Git 7.1 Выбор ревизии 7.2 Интерактивное индексирование 7.3 Припрятывание и очистка 7.4 Подпись 7.5 Поиск 7.6 Перезапись истории 7.7 Раскрытие тайн reset 7.8 Продвинутое слияние 7.9 Rerere 7.10 Обнаружение ошибок с помощью Git 7.11 Подмодули 7.12 Создание пакетов 7.13 Замена 7.14 Хранилище учётных данных 7.15 Заключение 8. Настройка Git 8.1 Конфигурация Git 8.2 Атрибуты Git 8.3 Хуки в Git 8.4 Пример принудительной политики Git 8.5 Заключение 9. Git и другие системы контроля версий 9.1 Git как клиент 9.2 Переход на Git 9.3 Заключение 10. Git изнутри 10.1 Сантехника и Фарфор 10.2 Объекты Git 10.3 Ссылки в Git 10.4 Pack-файлы 10.5 Спецификации ссылок 10.6 Протоколы передачи данных 10.7 Обслуживание репозитория и восстановление данных 10.8 Переменные окружения 10.9 Заключение A1. Приложение A: Git в других окружениях A1.1 Графические интерфейсы A1.2 Git в Visual Studio A1.3 Git в Visual Studio Code A1.4 Git в Eclipse A1.5 Git в IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.6 Git в Sublime Text A1.7 Git в Bash A1.8 Git в Zsh A1.9 Git в PowerShell A1.10 Заключение A2. Приложение B: Встраивание Git в ваши приложения A2.1 Git из командной строки A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Приложение C: Команды Git A3.1 Настройка и конфигурация A3.2 Клонирование и создание репозиториев A3.3 Основные команды A3.4 Ветвление и слияния A3.5 Совместная работа и обновление проектов A3.6 Осмотр и сравнение A3.7 Отладка A3.8 Внесение исправлений A3.9 Работа с помощью электронной почты A3.10 Внешние системы A3.11 Администрирование A3.12 Низкоуровневые команды 2nd Edition 3.1 Ветвление в Git - О ветвлении в двух словах Почти каждая система контроля версий в той или иной форме поддерживает ветвление. Используя ветвление, Вы отклоняетесь от основной линии разработки и продолжаете работу независимо от неё, не вмешиваясь в основную линию. Во многих системах контроля версий создание веток — это очень затратный процесс, часто требующий создания новой копии каталога с исходным кодом, что может занять много времени для большого проекта. Некоторые люди, говоря о модели ветвления Git, называют её «киллер-фича», что выгодно выделяет Git на фоне остальных систем контроля версий. Что в ней такого особенного? Ветвление Git очень легковесно: операция создания ветки выполняется почти мгновенно, переключение между ветками туда-сюда, обычно, также быстро. В отличие от многих других систем контроля версий, Git поощряет процесс работы, при котором ветвление и слияние выполняется часто, даже по несколько раз в день. Понимание и владение этой функциональностью даёт вам уникальный и мощный инструмент, который может полностью изменить привычный процесс разработки. О ветвлении в двух словах Для точного понимания механизма ветвлений, необходимо вернуться назад и изучить то, как Git хранит данные. Как вы можете помнить из Что такое Git? , Git не хранит данные в виде последовательности изменений, он использует набор снимков (snapshot). Когда вы делаете коммит, Git сохраняет его в виде объекта, который содержит указатель на снимок (snapshot) подготовленных данных. Этот объект так же содержит имя автора и email, сообщение и указатель на коммит или коммиты непосредственно предшествующие данному (его родителей): отсутствие родителя для первоначального коммита, один родитель для обычного коммита, и несколько родителей для результатов слияния двух и более веток. Предположим, у вас есть каталог с тремя файлами и вы добавляете их все в индекс и создаёте коммит. Во время индексации вычисляется контрольная сумма каждого файла (SHA-1 как мы узнали из Что такое Git? ), затем каждый файл сохраняется в репозиторий (Git называет такой файл блоб — большой бинарный объект), а контрольная сумма попадёт в индекс: $ git add README test.rb LICENSE $ git commit -m 'Initial commit' Когда вы создаёте коммит командой git commit , Git вычисляет контрольные суммы каждого подкаталога (в нашем случае, только основной каталог проекта) и сохраняет его в репозитории как объект дерева каталогов. Затем Git создаёт объект коммита с метаданными и указателем на основное дерево проекта для возможности воссоздать этот снимок в случае необходимости. Ваш репозиторий Git теперь хранит пять объектов: три блоб объекта (по одному на каждый файл), объект дерева каталогов, содержащий список файлов и соответствующих им блобов, а так же объект коммита , содержащий метаданные и указатель на объект дерева каталогов. Рисунок 9. Коммит и его дерево Если вы сделаете изменения и создадите ещё один коммит, то он будет содержать указатель на предыдущий коммит. Рисунок 10. Коммит и его родители Ветка в Git — это простой перемещаемый указатель на один из таких коммитов. По умолчанию, имя основной ветки в Git — master . Как только вы начнёте создавать коммиты, ветка master будет всегда указывать на последний коммит. Каждый раз при создании коммита указатель ветки master будет передвигаться на следующий коммит автоматически. Примечание Ветка «master» в Git — это не какая-то особенная ветка. Она точно такая же, как и все остальные ветки. Она существует почти во всех репозиториях только лишь потому, что её создаёт команда git init , а большинство людей не меняют её название. Рисунок 11. Ветка и история коммитов Создание новой ветки Что же на самом деле происходит при создании ветки? Всего лишь создаётся новый указатель для дальнейшего перемещения. Допустим вы хотите создать новую ветку с именем testing . Вы можете это сделать командой git branch : $ git branch testing В результате создаётся новый указатель на текущий коммит. Рисунок 12. Две ветки указывают на одну и ту же последовательность коммитов Как Git определяет, в какой ветке вы находитесь? Он хранит специальный указатель HEAD . Имейте ввиду, что в Git концепция HEAD значительно отличается от других систем контроля версий, которые вы могли использовать раньше (Subversion или CVS). В Git — это указатель на текущую локальную ветку. В нашем случае мы всё ещё находимся в ветке master . Команда git branch только создаёт новую ветку, но не переключает на неё. Рисунок 13. HEAD указывает на ветку Вы можете легко это увидеть при помощи простой команды git log , которая покажет вам куда указывают указатели веток. Эта опция называется --decorate . $ git log --oneline --decorate f30ab (HEAD -> master, testing) Add feature #32 - ability to add new formats to the central interface 34ac2 Fix bug #1328 - stack overflow under certain conditions 98ca9 Initial commit Здесь можно увидеть указывающие на коммит f30ab ветки: master и testing . Переключение веток Для переключения на существующую ветку выполните команду git checkout . Давайте переключимся на ветку testing : $ git checkout testing В результате указатель HEAD переместится на ветку testing . Рисунок 14. HEAD указывает на текущую ветку Какой в этом смысл? Давайте сделаем ещё один коммит: $ vim test.rb $ git commit -a -m 'made a change' Рисунок 15. Указатель на ветку HEAD переместился вперёд после коммита Интересная ситуация: указатель на ветку testing переместился вперёд, а master указывает на тот же коммит, где вы были до переключения веток командой git checkout . Давайте переключимся назад на ветку master : $ git checkout master Примечание git log не показывает все ветки по умолчанию Если выполнить команду git log прямо сейчас, то в её выводе только что созданная ветка «testing» фигурировать не будет. Ветка никуда не исчезла; просто Git не знает, что именно она вас интересует, и выводит наиболее полезную по его мнению информацию. Другими словами, по умолчанию git log отобразит историю коммитов только для текущей ветки. Для просмотра истории коммитов другой ветки необходимо явно указать её имя: git log testing Чтобы посмотреть историю по всем веткам — выполните команду с дополнительным флагом: git log --all . Рисунок 16. HEAD перемещается когда вы делаете checkout Эта команда сделала две вещи: переместила указатель HEAD назад на ветку master и вернула файлы в рабочем каталоге в то состояние, на снимок которого указывает master . Это также означает, что все вносимые с этого момента изменения будут относиться к старой версии проекта. Другими словами, вы откатили все изменения ветки testing и можете продолжать в другом направлении. Примечание Переключение веток меняет файлы в рабочем каталоге Важно запомнить, что при переключении веток в Git происходит изменение файлов в рабочем каталоге. Если вы переключаетесь на старую ветку, то рабочий каталог будет выглядеть так же, как выглядел на момент последнего коммита в ту ветку. Если Git по каким-то причинам не может этого сделать — он не позволит вам переключиться вообще. Давайте сделаем ещё несколько изменений и создадим очередной коммит: $ vim test.rb $ git commit -a -m 'made other changes' Теперь история вашего проекта разошлась (см Разветвлённая история ). Вы создали ветку и переключились на неё, поработали, а затем вернулись в основную ветку и поработали в ней. Эти изменения изолированы друг от друга: вы можете свободно переключаться туда и обратно, а когда понадобится — объединить их. И всё это делается простыми командами: branch , checkout и commit . Рисунок 17. Разветвлённая история Все описанные действия можно визуализировать с помощью команды git log . Для отображения истории коммитов, текущего положения указателей веток и истории ветвления выполните команду git log --oneline --decorate --graph --all . $ git log --oneline --decorate --graph --all * c2b9e (HEAD, master) Made other changes | * 87ab2 (testing) Made a change |/ * f30ab Add feature #32 - ability to add new formats to the central interface * 34ac2 Fix bug #1328 - stack overflow under certain conditions * 98ca9 initial commit of my project Ветка в Git — это простой файл, содержащий 40 символов контрольной суммы SHA-1 коммита, на который она указывает; поэтому операции с ветками являются дешёвыми с точки зрения потребления ресурсов или времени. Создание новой ветки в Git происходит так же быстро и просто как запись 41 байта в файл (40 знаков и перевод строки). Это принципиально отличает процесс ветвления в Git от более старых систем контроля версий, где все файлы проекта копируются в другой подкаталог. В зависимости от размера проекта, операции ветвления в таких системах могут занимать секунды или даже минуты, когда в Git эти операции мгновенны. Поскольку при коммите мы сохраняем указатель на родительский коммит, то поиск подходящей базы для слияния веток делается автоматически и, в большинстве случаев, очень прост. Эти возможности побуждают разработчиков чаще создавать и использовать ветки. Давайте посмотрим, почему и вам имеет смысл делать так же. Примечание Одновременное создание новой ветки и переключение на неё Как правило, при создании новой ветки вы хотите сразу на неё переключиться — это можно сделать используя команду git checkout -b <newbranchname> . Примечание Начиная с Git версии 2.23, вы можете использовать git switch вместо git checkout , чтобы: Переключиться на существующую ветку: git switch testing-branch . Создать новую ветку и переключиться на неё: git switch -c new-branch . Флаг -c означает создание, но также можно использовать полный формат:` --create`. Вернуться к предыдущей извлечённой ветке: git switch - . prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
http://dig.ccmixter.org/dig | Tag Search Toggle navigation donate to keep this library available! licenses tag search featured music for film music for games free for commercial use royalty free licensed 1 - 40 of 33,035 display 10 20 40 Our artists count on you returning their generosity. It Really Helps when you filters × all licenses free for commercial use royalty free ccPlus license all time magic sort recent latest instrumental only reset filters You're all I got (that NPC mix) Siobhan Dakay Tags: remix Come Inside to Dream SackJo22 Tags: electronic , synthesizer , techno , edm , dance , remix , non_commercial Hyperspeed Snowflake Tags: electronic , hip_hop , funky , synthesizer , piano , female_vocals , bass , downtempo , electro , fight_back , love , quantum_field , rumi , remix 21 Carosone Tags: trombone , remix , CBR , CBR You Can't Stay Here spinningmerkaba Tags: guitar , female_vocals , bass , remix , non_commercial , Sister Sonic Liberty Speck Tags: remix ECHO Ant.Survila Tags: instrumental , drums , electronic , synthesizer , loops , remix , non_commercial , CBR You Should Think mwic Tags: female_vocals , spoken_word , phoenix , drums , remix Elephant in the room J.Lang Tags: drums , bass , instrumental , experimental , hip_hop , loops , remix , CBR キルコイド2 Vidian Tags: female_vocals , experimental , downtempo , electro , synthesizer , remix , non_commercial I J U S T W A N N A SO SHA Tags: alternative , music_for_film , guitar , drums , female_vocals , electronic , synthesizer , piano , spoken_word , remix , ccplus Ant.Survila - Take It All Back ( deeplastik Secret remix) Deeplastik Tags: drums , remix , non_commercial , Survila , brings , Ant's Bob, le magnifique Bluemillenium Tags: chill , synthesizer , piano , spoken_word , remix , non_commercial , CBR Phone Neck ft. reiswerk Apoxode Tags: remix Sad Gentleman (Bristol Cut) 7OOP3D Tags: guitar , drums , bass , electronic , synthesizer , trip_hop , remix , non_commercial White Hot Lie debbizo Tags: guitar , remix , CBR , Sha I Was Very Tired Kirkoid Tags: electronic , drone , loops , female_vocals , remix , CBR OUTCAST GROUNDED DREAMS - SKYE JORDAN FT. QUIANA NADINE QuianaNadine Tags: alternative , female_vocals , drums , remix , CBR Gray Matter Snowflake Tags: orchestral , dramatic , dark , shadow_work , dna , generational_wounds , piano , loops , female_vocals , grace , remix , non_commercial THAT'S LIFE: NOTHING STAYS THE SAME QuianaNadine Tags: experimental , dance , chill , instrumental , female_vocals , drums , electronic , remix , CBR The Paradox Snowflake Tags: alternative , punk , female_vocals , drums , bass , synthesizer , remix , non_commercial B A N G O N - B A N G ON SO SHA Tags: alternative , music_for_film , female_vocals , bass , electronic , loops , pain , release , improv , improvisation , poem , freewrite , interpretive , synthesizer , downtempo , techno , electro Love Will Snowflake Tags: hopeful , birmingham , dance , female_vocals , synthesizer , loops , remix , CBR I loved you sparky Tags: guitar , drums , remix , non_commercial , delivers , Mykle , Anthony's soulcraft airtone Tags: chill , acoustic , remix , ccplus_stem , ccplus , non_commercial , CBR Back To You loveshadow Tags: drums , remix , non_commercial , Legendary , Loveshadow , gives , us Snow (Vo1k1 Ashes Mix) vo1k1 Tags: guitar , bass , electric , synthesizer , electronic_drums , drums , cello , strings , orchestral , textures , piano , remix Celebrating ccMixter Kara Square Tags: alternative , female_vocals , drums , guitar , bass , remix , non_commercial , CBR Sense SackJo22 Tags: downtempo , ballad , electronic , female_vocals , ambient , remix Here's Your Chance (ReWorked) * J.Lang Tags: bass , electronic , instrumental , chill , hip_hop , loops , piano , downtempo , remix Kung-Fu Glitch cdk Tags: experimental , chill , remix , CBR Something 7OOP3D Tags: house , female_vocals , drums , bass , electronic , remix , non_commercial , CBR Disco Inferno (Apoxode Rmx) Apoxode Tags: techno , rave , remix , CBR , VBR Conflict Opposition (deeplastik remix) Deeplastik Tags: electronic , remix White In The Moon (Anchor Mejans) Zep Hurme Tags: remix , non_commercial , you , dig , Yes , Porcupine , Tree , and , Rush , you'll Butterfly Wings Michelle Noel Tags: love_song , female_vocals , guitar , strings , orchestral , remix , non_commercial , VBR The Stubble Field Break (Mana Mixed) Mana Junkie Tags: loops , downtempo , remix ccMixter - Playing in the background V20 ScOmBer Tags: electro , rock , guitar , acoustic , synthesizer , bass , remix , non_commercial In the In-between (with Epilogue From the Bardo) Zenboy1955 Tags: orchestral , female_vocals , near_death_experiences , remix , nc_sampling_plus , CBR , archive , zip Shimmer (Emeralds for Sackjo22) spinningmerkaba Tags: remix , non_commercial , the , shimmering , realm , of , emerald , light Here Licenses Privacy Terms Donate(!) Credits There Everywhere Twitter YouTube Vimeo Facebook Instagram Resources GitHub Query API Forums Contact | 2026-01-13T09:29:23 |
https://git-scm.com/book/fa/v2/%da%af%db%8c%d8%aa-%d8%b1%d9%88%db%8c-%d8%b3%d8%b1%d9%88%d8%b1-Git-on-the-server-%da%af%db%8c%d8%aa%e2%80%8c%d9%84%d8%a8-GitLab | Git - گیتلب (GitLab) About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. شروع به کار (getting started) 1.1 درباره ورژن کنترل (About Version Control) 1.2 تاریخچه کوتاهی از گیت (A Short History of Git) 1.3 گیت چیست؟ (What is Git) 1.4 نصب گیت (Installing Git) 1.5 ستاپ اولیه گیت (First-Time Git Setup) 1.6 دریافت کمک (Getting Help) 1.7 خلاصه (summary) 2. مقدمات گیت (git basics chapter) 2.1 گرفتن یک مخزن گیت (Getting a Git Repository) 2.2 ثبت تغییرات در مخزن (Recording Changes to the Repository) 2.3 مشاهده تاریخچه کامیتها (Viewing the Commit History) 2.4 بازگرداندن تغییرات (Undoing Things) 2.5 کار کردن با ریموت ها (Working with Remotes) 2.6 تگ کردن (Tagging) 2.7 نام مستعار گیت (Git Aliases) 2.8 خلاصه (summary) 3. انشعابگیری در گیت (Git Branching) 3.1 شاخهها در یک نگاه (Branches in a Nutshell) 3.2 شاخهبندی و ادغام پایهای (Basic Branching and Merging) 3.3 مدیریت شاخهها (Branch Management) 3.4 روندهای کاری شاخهها (Branching Workflows) 3.5 شاخههای راه دور (Remote Branches) 3.6 بازپایهگذاری (Rebasing) 3.7 خلاصه (Summary) 4. گیت روی سرور (Git on the server) 4.1 پروتکلها (The Protocols) 4.2 راهاندازی گیت روی یک سرور (Getting Git on a Server) 4.3 ایجاد کلید عمومی SSH شما (Generating Your SSH Public Key) 4.4 نصب و راهاندازی سرور (Setting up server) 4.5 سرویسدهنده گیت (Git Daemon) 4.6 HTTP هوشمند (Smart HTTP) 4.7 گیتوب (GitWeb) 4.8 گیتلب (GitLab) 4.9 گزینههای میزبانی شخص ثالث (Third Party Hosted Options) 4.10 خلاصه (Summary) 5. گیت توزیعشده (Distributed git) 5.1 جریانهای کاری توزیعشده (Distributed Workflows) 5.2 مشارکت در یک پروژه (Contributing to a Project) 5.3 نگهداری یک پروژه (Maintaining a Project) 5.4 خلاصه (Summary) 6. گیت هاب (GitHub) 6.1 راهاندازی و پیکربندی حساب کاربری (Account Setup and Configuration) 6.2 مشارکت در یک پروژه (Contributing to a Project) 6.3 نگهداری یک پروژه (Maintaining a Project) 6.4 مدیریت یک سازمان (Managing an organization) 6.5 اسکریپتنویسی در گیتهاب (Scripting GitHub) 6.6 خلاصه (Summary) 7. ابزارهای گیت (Git Tools) 7.1 انتخاب بازبینی (Revision Selection) 7.2 مرحلهبندی تعاملی (Interactive Staging) 7.3 ذخیره موقت و پاکسازی (Stashing and Cleaning) 7.4 امضای کارهای شما (Signing Your Work) 7.5 جستجو (Searching) 7.6 بازنویسی تاریخچه (Rewriting History) 7.7 بازنشانی به زبان ساده (Reset Demystified) 7.8 ادغام پیشرفته (Advanced Merging) 7.9 بازاستفاده خودکار از حل تضادها (Rerere) 7.10 اشکالزدایی با گیت (Debugging with Git) 7.11 سابماژول ها (Submodules) 7.12 بستهبندی (Bundling) 7.13 جایگزینی (Replace) 7.14 ذخیرهسازی اطلاعات ورود (Credential Storage) 7.15 خلاصه (Summary) 8. سفارشیسازی Git (Customizing Git) 8.1 پیکربندی گیت (Git Configuration) 8.2 ویژگیهای گیت (Git Attributes) 8.3 هوکهای گیت (Git Hooks) 8.4 یک نمونه سیاست اعمال شده توسط گیت (An Example Git-Enforced Policy) 8.5 خلاصه (Summary) 9. گیت و سیستمهای دیگر (Git and Other Systems) 9.1 گیت بهعنوان کلاینت (Git as a Client) 9.2 مهاجرت به گیت (Migrating to Git) 9.3 خلاصه (Summary) 10. مباحث درونی گیت (Git Internals) 10.1 ابزارها و دستورات سطح پایین (Plumbing and Porcelain) 10.2 اشیا گیت (Git Objects) 10.3 مراجع گیت (Git References) 10.4 فایلهای بسته (Packfiles) 10.5 نگاشت (The Refspec) 10.6 پروتکلهای انتقال (Transfer Protocols) 10.7 نگهداری و بازیابی دادهها (Maintenance and Data Recovery) 10.8 متغیرهای محیطی (Environment Variables) 10.9 خلاصه (Summary) A1. پیوست A: گیت در محیطهای دیگر (Git in Other Environments) A1.1 رابط های گرافیکی (Graphical Interfaces) A1.2 گیت در ویژوال استودیو (Git in Visual Studio) A1.3 گیت در Visual Studio Code (Git in Visual Studio Code) A1.4 گیت در IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine (Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine) A1.5 گیت در Sublime Text (Git in Sublime Text) A1.6 گیت در بش (Git in Bash) A1.7 گیت در Zsh (Git in Zsh) A1.8 گیت در PowerShell (Git in PowerShell) A1.9 خلاصه (Summary) A2. پیوست B: گنجاندن گیت در برنامههای شما (Embedding Git in your Applications) A2.1 خط فرمان گیت (Command-line Git) A2.2 کتابخانهٔ گیت به زبان سی (Libgit2) A2.3 کتابخانه گیت برای زبان جاوا (JGit) A2.4 کتابخانه گیت برای زبان گو (go-git) A2.5 کتابخانه گیت پایتون (Dulwich) A3. پیوست C: دستورات گیت (Git Commands) A3.1 تنظیم و پیکربندی (Setup and Config) A3.2 گرفتن و ایجاد پروژهها (Getting and Creating Projects) A3.3 نمونهبرداری پایهای (Basic Snapshotting) A3.4 انشعابگیری و ادغام (Branching and Merging) A3.5 بهاشتراکگذاری و بهروزرسانی پروژهها (Sharing and Updating Projects) A3.6 بازرسی و مقایسه (Inspection and Comparison) A3.7 عیبیابی (Debugging) A3.8 اعمال تغییرات به صورت پچ (Patching) A3.9 ایمیل (Email) A3.10 سیستمهای خارجی (External Systems) A3.11 مدیریت (Administration) A3.12 دستورات سطح پایین گیت (Plumbing Commands) 2nd Edition 4.8 گیت روی سرور (Git on the server) - گیتلب (GitLab) گیتلب (GitLab) گیتوب نسبتاً ساده است. اگر به دنبال یک سرور گیت مدرن و کامل هستید، چندین راهحل متنباز وجود دارد که میتوانید به جای آن نصب کنید. از آنجایی که گیتلب یکی از محبوبترینهاست، نصب و استفاده از آن را به عنوان نمونه بررسی میکنیم. این گزینه نسبت به گیتوب سختتر است و نیاز به نگهداری بیشتری دارد، اما یک گزینه کاملاً مجهز است. نصب (Installation) گیتلب یک برنامه وب مبتنی بر پایگاه داده است، بنابراین نصب آن پیچیدهتر از برخی سرورهای گیت دیگر است. خوشبختانه این فرایند به خوبی مستندسازی و پشتیبانی شده است. گیتلب به شدت توصیه میکند که آن را روی سرور خود از طریق بسته رسمی Omnibus GitLab نصب کنید. گزینههای نصب دیگر عبارتند از: چارت Helm گیتلب برای استفاده با کوبرنتیز. بستههای داکریزه شده گیتلب برای استفاده با داکر. نصب از فایلهای منبع. ارائهدهندگان ابری مانند AWS، Google Cloud Platform، Azure، OpenShift و Digital Ocean. برای اطلاعات بیشتر به GitLab Community Edition (CE) readme مراجعه کنید. مدیریت (Administration) رابط مدیریت گیتلب از طریق وب قابل دسترسی است. فقط مرورگر خود را به نام میزبان یا آدرس IP که گیتلب روی آن نصب شده است، هدایت کنید و با کاربر root وارد شوید. رمز عبور بسته به نوع نصب شما متفاوت است اما به طور پیشفرض، Omnibus GitLab به صورت خودکار رمز عبوری ایجاد میکند و آن را حداقل به مدت ۲۴ ساعت در /etc/gitlab/initial_root_password ذخیره میکند. برای جزئیات بیشتر مستندات را دنبال کنید. پس از ورود، روی آیکون «منطقه مدیریت» در منوی بالای سمت راست کلیک کنید. نمودار 50. The “Admin area” item in the GitLab menu کاربران (Users) همه کسانی که از سرور گیتلب شما استفاده میکنند باید حساب کاربری داشته باشند. حسابهای کاربری ساده هستند و عمدتاً شامل اطلاعات شخصی مرتبط با دادههای ورود به سیستم میشوند. هر حساب کاربری یک فضای نام دارد که گروهبندی منطقی پروژههایی است که به آن کاربر تعلق دارند. اگر کاربر jane پروژهای به نام project داشته باشد، آدرس آن پروژه به صورت http://server/jane/project خواهد بود. نمودار 51. The GitLab user administration screen شما میتوانید یک حساب کاربری را به دو روش حذف کنید: «مسدود کردن» کاربر مانع از ورود او به نمونه گیتلب میشود، اما همه دادههای زیر فضای نام آن کاربر حفظ میشود و کامیتهایی که با ایمیل آن کاربر امضا شدهاند همچنان به پروفایل او لینک میشوند. «حذف» کاربر، از سوی دیگر، او را به طور کامل از پایگاه داده و سیستم فایل پاک میکند. تمام پروژهها و دادههای فضای نام او حذف شده و هر گروهی که مالک آن باشد نیز برداشته میشود. این اقدام بسیار دائمی و مخرب است و به ندرت به آن نیاز خواهید داشت. گروه ها (Groups) گروه گیتلب مجموعهای از پروژهها به همراه اطلاعاتی درباره نحوه دسترسی کاربران به آن پروژههاست. هر گروه یک فضای نام پروژه دارد (مانند کاربران)؛ بنابراین اگر گروه training پروژهای به نام materials داشته باشد، آدرس آن پروژه http://server/training/materials خواهد بود. نمودار 52. The GitLab group administration screen هر گروه با تعدادی کاربر مرتبط است که هر کدام سطح دسترسی خاصی به پروژههای گروه و خود گروه دارند. این سطوح از «مهمان» (فقط مسائل و چت) تا «مالک» (کنترل کامل گروه، اعضا و پروژهها) متغیر است. انواع مجوزها بسیار زیاد است و نمیتوان همه را اینجا فهرست کرد، اما گیتلب لینک مفیدی در صفحه مدیریت دارد. پروژه ها (Projects) یک پروژه در گیتلب تقریباً متناظر با یک مخزن گیت است. هر پروژه به یک فضای نام تعلق دارد، یا یک کاربر یا یک گروه. اگر پروژه متعلق به یک کاربر باشد، مالک پروژه مستقیماً کنترل دسترسی به آن را دارد؛ اگر پروژه متعلق به یک گروه باشد، مجوزهای سطح کاربر گروه اعمال میشود. هر پروژه یک سطح دسترسی دارد که مشخص میکند چه کسانی میتوانند به صفحات و مخزن آن دسترسی خواندنی داشته باشند. اگر پروژه خصوصی باشد، مالک پروژه باید به طور صریح دسترسی به کاربران خاصی بدهد. پروژه داخلی برای هر کاربر وارد شده قابل مشاهده است و پروژه عمومی برای همه قابل دیدن است. توجه داشته باشید که این کنترل هم دسترسی git fetch و هم دسترسی به رابط وب پروژه را شامل میشود. هوک ها (Hooks) گیتلب از هوکها پشتیبانی میکند، هم در سطح پروژه و هم در سطح سیستم. در هر یک از این موارد، سرور گیتلب هر زمان رویدادهای مرتبط رخ دهد، یک درخواست HTTP POST با یک JSON توصیفی ارسال میکند. این راهی عالی برای اتصال مخازن گیت و نمونه گیتلب شما به سایر ابزارهای اتوماسیون توسعه مانند سرورهای CI، اتاقهای گفتگو یا ابزارهای استقرار است. استفاده پایه (Basic Usage) اولین کاری که با گیتلب میخواهید انجام دهید، ایجاد یک پروژه جدید است. میتوانید این کار را با کلیک روی آیکون "`{plus}`" در نوار ابزار انجام دهید. از شما خواسته میشود نام پروژه، فضای نامی که باید به آن تعلق داشته باشد، و سطح دید آن را مشخص کنید. بیشتر مواردی که اینجا تعیین میکنید دائمی نیستند و بعداً میتوان آنها را از طریق رابط تنظیمات تغییر داد. روی "`Create Project`" کلیک کنید و کار تمام است. پس از ایجاد پروژه، احتمالاً میخواهید آن را به یک مخزن گیت محلی متصل کنید. هر پروژه از طریق HTTPS یا SSH قابل دسترسی است و هرکدام میتوانند برای پیکربندی یک ریموت گیت استفاده شوند. آدرسهای URL در بالای صفحه اصلی پروژه قابل مشاهدهاند. برای یک مخزن محلی موجود، این فرمان یک ریموت به نام gitlab به مکان میزبانی شده ایجاد میکند: $ git remote add gitlab https://server/namespace/project.git If you don’t have a local copy of the repository, you can simply do this: $ git clone https://server/namespace/project.git رابط کاربری وب دسترسی به چندین نمای مفید از خود مخزن را فراهم میکند. صفحه اصلی هر پروژه فعالیتهای اخیر را نشان میدهد و لینکهای بالای صفحه شما را به نمای فایلها و گزارش کامیتهای پروژه هدایت میکنند. همکاری گروهی (Working Together) سادهترین روش برای همکاری در یک پروژه گیتلب، دادن دسترسی مستقیم برای پوش به هر کاربر است. میتوانید با رفتن به بخش “Members” در تنظیمات پروژه، یک کاربر را اضافه کنید و سطح دسترسی مناسبی به او اختصاص دهید (سطوح دسترسی مختلف در گروه ها (Groups) کمی توضیح داده شدهاند). با دادن سطح دسترسی “Developer” یا بالاتر به یک کاربر، آن کاربر قادر خواهد بود کامیتها و شاخهها را مستقیماً به مخزن پوش کند. روش دیگری که همکاری را مستقلتر میکند، استفاده از درخواستهای ادغام (merge requests) است. این ویژگی به هر کاربری که بتواند پروژه را ببیند اجازه میدهد به شیوهای کنترل شده مشارکت کند. کاربرانی که دسترسی مستقیم دارند، میتوانند به سادگی یک شاخه بسازند، کامیتها را به آن پوش کنند و یک درخواست ادغام از شاخه خود به شاخه master یا هر شاخه دیگری باز کنند. کاربرانی که مجوز پوش ندارند، میتوانند مخزن را “fork” کنند تا نسخه خود را بسازند، کامیتها را به نسخه خود پوش کنند و سپس درخواست ادغام از فورک خود به پروژه اصلی باز کنند. این مدل به مالک اجازه میدهد کنترل کامل روی موارد وارد شده به مخزن و زمان آنها داشته باشد، در حالی که امکان مشارکت کاربران غیرمطمئن را فراهم میکند. درخواستهای ادغام و مسائل (issues) واحدهای اصلی بحثهای طولانیمدت در گیتلب هستند. هر درخواست ادغام امکان بحث خط به خط درباره تغییر پیشنهادی (که نوعی بازبینی کد سبک است) و همچنین یک رشته بحث کلی و عمومی را فراهم میکند. همگی میتوانند به کاربران اختصاص داده شده یا در قالب مایلستونها سازماندهی شوند. این بخش عمدتاً بر ویژگیهای مرتبط با گیت در گیتلب تمرکز دارد، اما به عنوان یک پروژه بالغ، امکانات بسیاری دیگر برای کمک به همکاری تیمی ارائه میدهد، مانند ویکیهای پروژه و ابزارهای نگهداری سیستم. یکی از مزایای گیتلب این است که پس از راهاندازی و اجرای سرور، به ندرت نیاز به تغییر فایل پیکربندی یا دسترسی به سرور از طریق SSH خواهید داشت؛ بیشتر مدیریت و استفاده عمومی از طریق رابط مرورگر انجام میشود. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_CL | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/Git-sa-Server-Mga-Opsyon-ng-Naka-host-sa-Third-Party | Git - Mga Opsyon ng Naka-host sa Third Party About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 4.9 Git sa Server - Mga Opsyon ng Naka-host sa Third Party Mga Opsyon ng Naka-host sa Third Party Kung hindi mo nais pagdaanan ang lahat ng trabaho kasali sa pag-set up ng iyong sariling Git server, mayroon kang iilang opsyon para i-host ang iyong mga proyekto sa Git sa isang dedikadong panlabas na hosting site. Ang paggawa nito ay nag-aalok ng ilang mga kalamangan: ang isang hosting site ay sa pangkalahatan ay daling i-set up at madaling magsimula ng mga proyekto, at walang maintenance sa server o kailangan ng pagsubaybay. Kahit na magset-up ka at magpatakbo ng iyong server internally, maaari mo parin gusto gumamit ng isang pampublikong hosting site para sa iyong open source na mga code — sa pangkalahatan mas madali para sa open source na komunidad na hanapin at tulungan ka. Sa mga araw na ito, ikaw ay mayroong isang malaking bilang ng mga opsyon sa hosting na pagpipilian, bawat isa ay may mga kalamangan at kawalan. Upang makita ang isang up-to-date na listahan, tingnan ang pahina ng GitHosting sa pangunahing wiki sa https://git.wiki.kernel.org/index.php/GitHosting Tatalakayin namin ng detalyado ang paggamit ng Github sa GitHub , dahil ito ang pinakamalaking Git host doon at maaaring kailangan mong makipag-ugnayan sa mga proyekto na naka-host roon sa anumang kaso, ngunit mayroong dose-dosenang higit pa na pagpipilian kung hindi mo nais mag-set up ng iyong sariling Git server. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/zh-tw/v2/GitHub-%e7%b6%ad%e8%ad%b7%e5%b0%88%e6%a1%88 | Git - 維護專案 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 開始 1.1 關於版本控制 1.2 Git 的簡史 1.3 Git 基礎要點 1.4 命令列 1.5 Git 安裝教學 1.6 初次設定 Git 1.7 取得說明文件 1.8 摘要 2. Git 基礎 2.1 取得一個 Git 倉儲 2.2 紀錄變更到版本庫中 2.3 檢視提交的歷史記錄 2.4 復原 2.5 與遠端協同工作 2.6 標籤 2.7 Git Aliases 2.8 總結 3. 使用 Git 分支 3.1 簡述分支 3.2 分支和合併的基本用法 3.3 分支管理 3.4 分支工作流程 3.5 遠端分支 3.6 衍合 3.7 總結 4. 伺服器上的 Git 4.1 通訊協定 4.2 在伺服器上佈署 Git 4.3 產生你的 SSH 公鑰 4.4 設定伺服器 4.5 Git 常駐程式 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第3方 Git 託管方案 4.10 總結 5. 分散式的 Git 5.1 分散式工作流程 5.2 對專案進行貢獻 5.3 維護一個專案 5.4 Summary 6. GitHub 6.1 建立帳戶及設定 6.2 參與一個專案 6.3 維護專案 6.4 Managing an organization 6.5 Scripting GitHub 6.6 總結 7. Git 工具 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 總結 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. 附錄 A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. 附錄 B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. 附錄 C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 6.3 GitHub - 維護專案 維護專案 現在我們可以舒適自在地對一個專案做出貢獻了，所以我們來看看另一個面向：建立、維護以及管理一個專案。 建立一個新倉儲 來建立一個拿來分享我們的原始碼的倉儲吧。 首先點擊主控面板右邊的「New Repository」；或是點擊頂端工具列裡面使用者名稱旁邊的 {plus} 按鈕，如 「New repository」下拉式選單. 所示。 圖表 109. 「Your Repositories」區塊 圖表 110. 「New repository」下拉式選單. 這會把你帶到「new repository」表單的所在頁面： 圖表 111. 「new repositroy」表單 你只需要提供專案名稱，因為剩餘的欄位是完全選擇性的。 現在，你只要點下「Create Repository」鈕，然後碰地一聲——你就擁有了一個在 GitHub 上名為 <user>/<project_name> 的全新倉儲了。 因為你這個倉儲還沒有任何原始碼在裡面，GitHub 會展示一份關於如何建立一個全新的 Git 倉儲或是連結一個舊有 Git 專案的指引。 我們在這邊不會對這這部份多做描述，如果你需要回憶一下，去看看 [ch02-git-basics] 吧。 現在你的專案被託管在 GitHub 上了，你可以把網址給任何你想要分享專案的人。 所有人都可以透過 https://github.com/<user>/<project_name> 以 HTTP 方式存取，或是透過 git@github.com:<user>/<project_name> 以 SSH 方式存取。 Git 可以透過上述兩種途徑來推送及擷取資料，但所有操作都會透過對其連結的使用的驗證資訊來做存取控管。 筆記 通常公開專案會傾向於分享基於 HTTP 的網址，因為這樣沒有 GitHub 帳戶的使用者也能夠對其存取來拓製專案。 如果你給了 SSH 版本的網址，使用者必須建立一個帳戶並加入 SSH key 才能存取專案。 而且 HTTP 網址就是他們會貼在瀏覽器裡來瀏覽專案的網址。 增加協作者 你必須要把和你合作的人加入「協作者」，這樣他們才能對專案提交變更。 如果 Ben、Jeff 和 Louise 都有 GitHub 帳戶，而且你想要給他們推送變更的權限，你可以把他們加到你的專案。 把他們加入專案後，他們可以對專案「推送」變更，這意味著他們有這專案及專案的 Git 倉儲的讀寫權限。 點擊右側欄最下面的「Settings」連結。 圖表 112. 倉儲設定連結。 接著選擇右邊選單的「Collaborators」。 然後在文字方塊裡輸入使用者名稱，按下「Add collaborator」。 你可以一直重複這個步驟來賦予所有你想要的人存取權限。 如果你要收回權限，只要點一下那個使用者右手邊的「X」即可。 圖表 113. 倉儲協作者 管理 Pull Requests 現在你擁有一個裡面有些原始碼的專案，同時也可能會有些擁有推送權限的協作者。然後我們來看看當你收到 Pull Request 時要如何處理吧。 Pull Requests 可能是來自某個 fork 裡的分支，或是同個倉儲裡的某個分支。 兩者之間只差在，來自其他 fork 的 PR 通常你沒有對他們分支的推送權限，他們也沒有；而內部 PR 就是雙方都能存取分支。 關於這些東西的範例，我們就在這邊假設你是「tonychacon」而且你建立了一個名叫「fade」的 Arduino 原始碼專案吧。 電郵通知 有人對你的原始碼做了些變更，然後發給你一個 Pull Request。 這時你應該會收到像 對於新的 Pull Request 的電郵通知。 這樣的郵件。 圖表 114. 對於新的 Pull Request 的電郵通知。 這電郵裡面有些值得注意的東西。 他會給你一個簡易的差異狀態——一個在這 Pull Request 之中被變更的檔案清單，以及變動量。 內附一個 GitHub PR 連結。 同時也會給你一些可以從指令列操作的網址。 你可能會注意到這行指令 git pull <url> patch-1 ，這行指令是可以在不用增加遠端的情況下合併一個遠端分支的簡易方式。 我們曾在 切換到遠端分支 簡短的提過。 你可以去建立並切換至主題分支，然後執行這條指令以合併 Pull Request 中的變更。 其他有趣的網址就是 .diff 和 .patch ，你或許猜的到，他們分別提供 Pull Request 的統合差異和系列補綴。 你可以以下述方式來做技術性的合併： $ curl http://github.com/tonychacon/fade/pull/1.patch | git am 在 Pull Request 裡合作 就如我們在 GitHub 流程 提過的，你現在可以和建立 Pull Request 的人對談了。 你可以針對某幾行原始碼提出評論、對一整個提交做評論或是對一整個 Pull Request 做評論，而且你在其中每個部分都可以使用 GitHub 風格的 Markdown。 每當有人在 Pull Request 裡留下評論時，你都會收到一封電郵通知，這樣你就能掌握整個 Pull Request 的動態。 每次通知都會附有連結連往 Pull Request 有活動的部分，同時你也可以直接回覆郵件以在 Pull Request 討論串中評論。 圖表 115. 包含在討論串中的電郵回覆。 當你覺得 PR 裡面的原始碼已經可以合併的時候，你可手動拉取，然後在本地端合併；或是用 git pull <url> <branch> 這個稍早看過的語法；也可以把那個 fork 加入成遠端之一之後再擷取並合併。 如果這只是個簡單的合併，你可以按下 GitHub 網站上的「Merge」按鈕來解決。 這會做一個「非快進」的合併——即便是可以快進，仍會建立合併提交。 這意味著，不論你在何種情況按下「Merge」，都會建立一個合併提交。 如果你點了提示連結，GitHub 就會會提供你所有的資訊，就像你在 Merge 按鈕和手動合併 Pull Request 的指引。 看到的一樣。 圖表 116. Merge 按鈕和手動合併 Pull Request 的指引。 如果你決定不要合併這個 Pull Request，你只需要關閉這個 Pull Request 即可，同時建立這個 Pull Request 的人也會收到通知。 Pull Request 參照 如果你要處理 非常多 的 Pull Request 而且不想加入一堆的遠端或是一直做只會用到一次的拉取，關於這點 GitHub 提供了一個好用的小技巧給你用。 這是個有點進階的技巧，所以我們會在 The Refspec 提到更多的細節，不過還是非常的有用。 事實上 GitHub 會把倉儲的 Pull Request 當成伺服器上的假分支。 預設情況下你不會在拓製的時候取得它們，但他們還是以隱藏的狀態存在著而且你可以用非常簡單的方式取得它們。 To demonstrate this, we’re going to use a low-level command (often referred to as a “plumbing” command, which we’ll read about more in Plumbing and Porcelain ) called ls-remote . This command is generally not used in day-to-day Git operations but it’s useful to show us what references are present on the server. 為了展示這個事實，我們要使用一個比較低階的指令（通常會被稱作「底層」指令，關於這點我們會在 Plumbing and Porcelain 再做詳細描述）—— ls-remote 。 這指令通常不會在日常的 Git 操作使用，但在展現伺服器上的所有參照是非常有用的。 如果對我們之前的「blink」倉儲使用這條指令，我們會得到在伺服器上這個倉儲裡所有的分支、標籤和其他各種參照的清單。 $ git ls-remote https://github.com/schacon/blink 10d539600d86723087810ec636870a504f4fee4d HEAD 10d539600d86723087810ec636870a504f4fee4d refs/heads/master 6a83107c62950be9453aac297bb0193fd743cd6e refs/pull/1/head afe83c2d1a70674c9505cc1d8b7d380d5e076ed3 refs/pull/1/merge 3c8d735ee16296c242be7a9742ebfbc2665adec1 refs/pull/2/head 15c9f4f80973a2758462ab2066b6ad9fe8dcf03d refs/pull/2/merge a5a7751a33b7e86c5e9bb07b26001bb17d775d1a refs/pull/4/head 31a45fc257e8433c8d8804e3e848cf61c9d3166c refs/pull/4/merge 當然，如果你在你的倉儲裡使用 git ls-remote origin 或是對其他任一個想確認的遠端使用，你會得到一個與這類似的結果。 如果你的倉儲是在 GItHub 上，而且有開放中的 Pull Request；你會看到一些以 refs/pull/ 開頭的參照。 它們基本上也是分支，但是因為他們不是以 refs/heads 起頭，所以你一般來說不會在拓製或擷取時從伺服器下載到他們——擷取的過程會忽略它們。 每個 Pull Request 都會有兩個參照——以 /head 結尾的是對應到目前 Pull Request 分支的最後一個提交。 所以，如果有人在我們的倉儲開了一個 Pull Request，而且他的分支名稱叫做 bug-fix 還有它指向 a5a775 這個提交，在之後我們的倉儲裡並不會出現 bug-fix 這個分支，但我們會出現指向 a5a775 的 pull/<pr#>/head 。 這意味著我們可以非常簡單的直接拉取所有 Pull Request 分支，而非加一大堆的遠端來解決。 現在，你可以直接做些事––好比說擷取參考。 $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD 這告訴了 Git：「連結到名為 origin 的遠端，並下載名為 refs/pull/958/head 的參考。」 Git 很樂意的照做了，之後下載了所有建立這個參考的必要資訊，之後就在 .git/FETCH_HEAD 裡放了一個指向你所需要的提交的指針。 你可以接著在你想要測試的分支裡執行 git merge FETCH_HEAD ，不過這個合併提交的訊息可能會有點奇怪。 不過，如果你需要審閱「一大堆」的 Pull Request，這會顯得相當的枯燥乏味。 也是有辦法可以擷取「全部」的 Pull Request 的，而且可以在你每次連接到遠端時更新。 用你習慣的編輯器打開 .git/config ，並且找到關於遠端 origin 的部份。 通常會長的像這樣： [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* 以 fetch = 開頭的那行是個「參照規格」。 這是個本地端的 .git 資料夾裏面的名稱對應到遠端的方法。 這一段告訴 Git：「在遠端 refs/heads 之下的東西，要保存在本地倉儲的 refs/remotes/origin 之下。」 你可以編輯這個段落以加入其他的參照規格： [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* 最後一行告訴 Git：「所有類似 refs/pull/123/head 的參照都會以 refs/remotes/origin/pr/123 的型式儲存在本地端。」 所以現在存檔，然後執行 git fetch ： $ git fetch # … * [new ref] refs/pull/1/head -> origin/pr/1 * [new ref] refs/pull/2/head -> origin/pr/2 * [new ref] refs/pull/4/head -> origin/pr/4 # … 現在所有遠端的 Pull Request 都會以類似追蹤分支型式的參照出現在本端；他們是唯讀的，並且會在你做擷取的時候更新。 這讓在本地端測試 pull request 裡的程式碼變成超級簡單的事： $ git checkout pr/2 Checking out files: 100% (3769/3769), done. Branch pr/2 set up to track remote branch pr/2 from origin. Switched to a new branch 'pr/2' 你們其中某些比較眼尖的人可能已經注意到參照規格中遠端部份的尾巴的 head 。 這同時也是 GitHub 端一個名為 refs/pull/#/merge 的參照，這代表著當你點下網站上的「Merge」鈕時會產生的提交。 這讓你甚至可以在按下按鈕前測試合併結果。 對應到 Pull Request 的 Pull Request 你不只可以對主要分支或是 master 分支建立 Pull Request，你也可以對這整個網絡裡的任意一個分支做同樣的事。 事實上，你甚至可以對另外一個 Pull Request 做 Pull Request。 如果你發現一個 Pull Request 正在往良好的方向發展，而你也想加點依賴於它的變更、或是你只是不確定這變更否是個好主意、甚至只是因為你沒有對目的分支推送的權限時，你都可以直接對它開 PR。 當你要開啟一個 Pull Request 時，頁面最上方會有個區塊可以讓你選擇要請求擁有者在哪個分支上拉取變更，以及要從哪個分支拉取。 如果你按下右手邊的「Edit」鈕，你不只能指定分支，也可以指定 fork。 圖表 117. 手動指定 Pull Request 的目標 fork 和分支 在這邊你可以相當簡單的方式決定你要把你的新分支合併到另一個 Pull Request 或是這專案底下的其他 fork。 提及他人和通知 GitHub 也有非常好的通知系統，讓徵詢特定人或團隊的意見變成一件易如反掌的事。 在任意一個專案裡，當你一輸入 @ 這個字元後，自動完成就會提供給你所有這個計畫的協作者和貢獻者的顯示名稱及使用者名稱。 圖表 118. 輸入 @ 來提到其他人 你也可以提及某個並沒有出現在這個下拉式清單的使用者，不過自動完成通常會更快把牠抓出來。 當你發佈了一個有提到其他使用者的評論時，那些被標記的人會收到通知。 這意味著這會是一個非常有效率的把人拉入討論的方式，而非讓那些人主動追蹤討論進度。 在 GitHub 上人們很常把同團隊或是同公司的人拉近討論裡，藉以審閱 Pull Request 或是議題。 如果有人被標記，會被自動訂閱提到他們的 Pull Request 或是議題，之後就會收到所有相關的動態。 你也會自動訂閱所有你建立的東西、你觀注的版本庫或是你曾經發表過評論的東西。 如果你不想繼續收到通知，你可以按下頁面裡的「Unsubscribe」鈕來停止收到後續的更新。 圖表 119. 取消訂閱 PullRequest 或是議題。 通知總覽頁面 當我們在這邊提到關於 GitHub 的「通知」時，這是指 GitHub 試著讓你跟上新發生的事件的方式，而且你也有許多方式可以自訂。 如果進到設定頁面的「Notification Center」分頁，你會看到一些可以使用的選項。 圖表 120. 通知中心選項。 在這邊你有兩種取得通知的方式可以選擇––「電子郵件」和「網頁」，你可以決定當你在在參與事情或是接收你關注的版本庫的動態時，你要如何透過這兩個管道接受通知。 網頁通知 網頁通知僅存在於 GitHub 上，而你也只能在 GitHub 上檢視。 如果你有選用這個選項，當你在收到通知的時候，你會在頁面上方的通知圖示上看到一個藍點，就如 通知中心 所示。 圖表 121. 通知中心 如果你點一下那個圖示，你會看到以專案分類的通知清單。 你也可以點擊-左側列表裡的專案名稱來過濾出關於個專案的通知。 你也以按下任一項通知右側的勾選圖示來確認接收，或是點下專案名稱旁的勾選圖示來接收所有關於這個專案的通知。 勾選圖示旁邊也有個靜音按鈕，當你點下那個圖示，代表你將不會收到那項東西的後續通知。 這些工具對於管理大量的通知來說是非常的方便。 許多的 GitHub 的進階使用者會直接關掉所有的電郵通知，然後在這頁面上管理所有的通知。 電郵通知 電郵通知是 GitHub 上另一個接受通知的方式。 如果你開啟這個選項，之後每當你收到通知，你就會收到一封電郵。 我們可以在 以電子郵件型式寄送的評論 和 對於新的 Pull Request 的電郵通知。 有範例。 這廂電子郵件會自動討論串化，如果你在使用討論串式的電郵客戶端，這會是個好事情。 GitHub 會再寄給你的通知郵件的標頭里嵌入相當多的後設資訊，這樣你在建立自訂過濾條件時可以更得心應手。 舉例來說，如果展開在 對於新的 Pull Request 的電郵通知。 寄給 Tony 的郵件的真實標頭，我們會看到這樣被寄出的訊息。 To: tonychacon/fade <fade@noreply.github.com> Message-ID: <tonychacon/fade/pull/1@github.com> Subject: [fade] Wait longer to see the dimming effect better (#1) X-GitHub-Recipient: tonychacon List-ID: tonychacon/fade <fade.tonychacon.github.com> List-Archive: https://github.com/tonychacon/fade List-Post: <mailto:reply+i-4XXX@reply.github.com> List-Unsubscribe: <mailto:unsub+i-XXX@reply.github.com>,... X-GitHub-Recipient-Address: tchacon@example.com 這裡面有不少有趣的東西。 如果你想針對特定專案甚至是 Pull Request 的電郵做特別標示或是轉寄時，「Message-ID」這項以 <user>/<project>/<type>/<id> 的格式提供了所有資訊。 如果這是個議題，`<type>`這部分就會是「issue」而非「pull」。 而而你如果有個能夠解析 List-Post 和 List-Unsubsribe 這兩個欄位的電郵客戶端的話，你就能直接發表意見到清單裡， 或是直接「取消訂閱」這個串，就像你直接在那 Pull Request 或是議題頁面上做的一樣。 值得一提的是，如果你同時啟用網頁和電郵通知，當你使用允許內嵌圖片的郵件客戶端開啟通知郵件時，網頁上的通知也會被標示為已讀。 特殊檔案 當有些特殊檔案出現在你的版本庫時，GitHub 會注意到它們。 README 第一個就是 README 檔，它可以用任意一種可以被 GitHub 便是成文章的格式寫成。 舉例來說，它可以是 README 、 README.md 、 README.asciidoc 、等等。 如果 GitHub 在你的原始碼裡發現 README 這個檔案時，他會被渲染再在專案首頁。 許多團隊用這檔案來整理所有這專案的相關資訊，來讓第一次接觸這個專案或版本庫的人了解這個專案。 通常會包含這些東西： 這個專案的目的 如何設定及安裝 舉個使用或執行的例子 這個專案是基於哪種授權發布的 如何對這專案做貢獻 因為 GitHub 會渲染這個檔案，所以你可以嵌入圖片或連結來讓他更容易理解。 CONTRIBUTING 另個 GitHub 會辨識的特殊檔案就是 CONTRIBUTING 。 如果你有個帶著任意種附檔名的 CONTRIBUTING ，GitHub 會把它顯示成 在有 CONTRIBUTING 這個檔案時建立 Pull Request 給那些想建立 Pull Request 的使用者看。 圖表 122. 在有 CONTRIBUTING 這個檔案時建立 Pull Request 這檔案就是你可以指定發給你這專案的 Pull Request 裡面可以包含哪些以及不能包含哪些東西。 這樣大家或許就會在建立 Pull Request 前看看這些原則了。 專案管理 你在一個專案上通常沒有什麼管理性的事能做，不過這邊有幾個你或許有興趣的專案。 變更主分支 如果你希望使用其他不是「master」的分支來作為其他人建立 Pull Request 的預設目標分支，你可以在版本庫的設定頁面的「Options」分頁裡設定。 圖表 123. 變更一個專案的預設分支 只要在下拉式清單裡選擇你要的分支，就可以簡單的變更所有主要動作的預設分支，包含其他人在拓製版本庫時預設簽出的分支。 版本庫移轉 如果你想要把一個專案轉移給其他在 GitHub 上的使用者或是組織時，你可以在倉儲設定裡同樣在「Options」分頁的底部找到 「Transfer ownership」來達成這件事。 圖表 124. 把一個專案轉移給其他的 GitHub 使用者或是組織 這當你要放棄一個專案而有人要接手時很有幫助，或是在你的專案日漸茁壯，你想要把它移到一個組織裡時也有用。 這個動作不只會把所有關注和標記星號的使用者搬到其他地方，同時也會在舊頁面建立連向新頁面的重導向連結。 這也會重導向所有來自 Git 的擷取和拓製動作，不只是網頁請求而已。 prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/GitHub-Pagpapanatili-ng-isang-Proyekto | Git - Pagpapanatili ng isang Proyekto About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 6.3 GitHub - Pagpapanatili ng isang Proyekto Pagpapanatili ng isang Proyekto Ngayon na kumportable tayong nag-aambag sa isang proyekto, tingnan natin ang kabilang panig: paglikha, pagpapanatili at pangangasiwa ng iyong sariling proyekto. Paglilikha ng isang Bagong Repositoryo Lumikha ng isang bagong repositoryo upang maibahagi ang ating code ng proyekto. Simulan sa pamamagitan ng pag-click sa pindutan na “Bagong Repositoryo” sa kanang bahagi ng dashboard, o mula sa pindutan na {plus} sa itaas na toolbar kasunod sa iyong usernmame gaya ng nakikita sa Ang dropdown na “Bagong repositoryo”. . Figure 110. Ang lawak na “Iyong mga repositoryo”. Figure 111. Ang dropdown na “Bagong repositoryo”. Ito ay nagdadala sa iyo sa form ng “bagong repositoryo”: Figure 112. Ang form ng “bagong repositoryo”. Ang kailangan mo lang gawin dito ay magbigay ng isang pangalan ng proyekto; ang lahat ng mga patlang ay ganap na opsyonal. Sa ngayon, i-click lamang ang pindutan na “Lumikha ng Repositoryo” - mayroon kang isang bagong repositoryo sa GitHub, pinangalanang <user>/<project_name> . Dahil wala kang code doon, ipapakita sa iyo ng GitHub ang mga tagubilin kung paano lumikha ng isang bagong tatak ng repositoryo ng Git, o ikonekta ang isang umiiral na proyekto ng Git. Hindi namin balabaan ito dito; kung kailangan mo ng refresher, i-check out ang Mga Pangunahing Kaalaman sa Git . Ngayon na naka-host na ang iyong proyekto sa GitHub, maaari kang magbigay ng URL sa sinuman na gusto mong bahagian ng iyong proyekto. Bawat proyekto sa GitHub ay maaaring i-access sa HTTPS bilang https://github.com/<user>/<project_name> , at sa SSH bilang git@github.com:<user>/<project_name> . Maaaring mag-fetch ang Git mula sa at mag-push sa parehong mga URL na ito, ngunit sila ay kontrolado ng access batay sa mga kredensyal ng gumagamit na kumukonekto dito. Madalas na lalong kanais-nais na ibahagi ang URL na nakabatay sa HTTPS para sa isang pampublikong proyekto, dahil ang gumagamit ay hindi kailangang magkaroon ng isang account sa GitHub upang ma-access ito para sa pag-clone. Ang mga gumagamit ay magkakaroon ng isang account at isang na-upload na SSH key upang ma-access ang iyong proyekto kung binibigyan mo sila ng SSH URL. Ang HTTPS ay isa ring eksaktong parehong URL na kanilang idikit sa isang browser upang tingnan ang proyekto doon. Pagdaragdag ng mga Tagapangasiwa Kung ikaw ay nagtatrabaho kasama ang ibang tao na nais mong bigyan ng access sa pag-commit, kailangan mong idagdag sila bilang “tagapangasiwa”. Kung si Ben, Jeff, and Louise ay nag-sign up ng mga account sa GitHub, at gusto mo silang bigyan ng access sa pag-push sa iyong repositoryo, maaari mo silang idagdag sa iyong proyekto. Ang paggawa nito ay nagbibigay sa kanila ng access sa “push”, na nangangahulugan na mayroon silang access sa pagbasa at pagsulat sa proyekto at repositoryo ng Git. I-click ang link ng “Settings” sa ibaba ng kanang sidebar. Figure 113. Ang link ng settings ng repositoryo. Pagkatapos piliin ang =“Tagapangasiwa” mula sa menu sa kaliwang bahagi. Pagkatapos, magtipa ng username sa kahon, at i-click ang “Magdagdag ng tagapangasiwa.” Maaari mong ulitin ito nang maraming beses hangga’t gusto mo upang magbigay ng access sa lahat ng iyong gusto Kung kailangan mong bawiin ang access, i-click lamang ang ‘` X '’ sa kanang bahagi ng kanilang hilera. Figure 114. Tagapangasiwa ng Repositoryo. Pamamahala ng mga Kahilingan na Pull Ngayon na mayroon kang isang proyekto na may ilang mga code at marahil kahit na ilang mga tagapangasiwa na mayroon ding access sa push, talakayin natin kung ano ang gagawin kapag kumuha ka ng isang Kahilingan na Pull sa iyong sarili. Ang Kahilingan na Pull ay maaaring mula sa isang branch sa isang fork ng iyong repositoryo o sila ay maaari mula sa ibang branch sa parehong repositoryo. Ang tanging kaibahan ay ang mga nasa isang fork ay madalas mula sa mga tao kung saan hindi ka maaaring mag-push sa kanilang branch at hindi nila maaaring mag-push sa iyo, samantalang ang panloob na Kahilingan na Pull ay maaaring ma-access ng parehong partido sa branch. Para sa mga halimbawang ito, ating ipalagay na ikaw ay “tonychacon” at naglikha ka ng isang bagong proyekto na Arduino code na pinangalanang “fade”. Mga Abiso sa Email May nagsasama at gumagawa ng pagbabago sa iyong code at nagpapadala sa iyo ng Kahilingan na Pull. Dapat kang makakuha ng email na nag-aabiso sa iyo tungkol sa bagong Kahilingan na Pull at dapat itong magmukhang tulad ng Abiso sa email ng isang bagong Kahilingan na Pull. . Figure 115. Abiso sa email ng isang bagong Kahilingan na Pull. Mayroong ilang mga bagay na napapansin tungkol sa email na ito. Ito ay magbibigay sa iyo ng isang maliit na diffstat - isang listahan ng mga file na nagbago sa Kahilingan na Pull at kung gaano. Nagbibigay ito sa iyo ng isang link sa Kahilingan na Pull sa GitHub. Nagbibigay din ito sa iyo ng ilang mga URL na maaari mong gamitin mula sa command line. Kung mapapansin mo ang linya na nagsasabing git pull <url> patch-1 , ito ay isang simpleng paraan upang pagsamahin sa isang remote branch nang hindi na kinakailangang magdagdag ng isang remote. Tinalakay natin ito nang mabilis sa Checking Out Remote Branches . Kung naisin mo, maaari kang lumikha at lumipat sa isang branch ng paksa at pagkatapos ay patakbuhin ang utos na ito upang magsama sa mga pagbabago sa Kahilingan na Pull. Ang iba pang mga kagiliw-giliw na mga URL ay ang mga URL na .diff at` .patch`, na kung saan ay maaari mong hulaan, magbigay ng pinag-isang diff at patch na bersyon ng Kahilingan na Pull. Maaari mong pagsamahin sa trabaho ng Kahilingan na Pull sa isang bagay na tulad nito: $ curl http://github.com/tonychacon/fade/pull/1.patch | git am Pangangasiwa sa Kahilingan na Pull Sa natalakay sa Ang Daloy ng GitHub , maaari ka na ngayong magkaroon ng pag-uusap sa taong nagbukas ng Kahilingan na Pull. Maaari kang magkomento sa mga tiyak na linya ng code, magkomento sa buong commit o magkomento sa buong Kahilingan na Pull mismo, gamit ang GitHub Flavored Markdown saanman. Sa tuwing may ibang komento sa Kahilingan na Pull patuloy kang makakakuha ng mga abiso sa email upang malaman mo na may nangyayaring aktibidad. Ang bawat isa ay may isang link sa Kahilingan na Pull kung saan ang aktibidad ay nangyayari at maaari mo ring direktang tumugon sa email upang magkomento sa thread ng Kahilingan na Pull. Figure 116. Kasama sa thread ang mga tugon sa mga email. Sa sandaling ang code ay nasa isang lugar na gusto mo at nais na pagsamahin ito, maaari mong i-pull ang code pababa at pagsamahin ito nang lokal, alinman sa git pull <url> <branch> syntax na nakita natin kanina, o sa pamamagitan ng pagdaragdag ng fork bilang isang remote at pagkuha at pagsasama. Kung ang pagsama-sama ay walang halaga, maaari mo ring pindutin ang pindutan na “Merge” sa site ng GitHub. Ito ay gagawa ng isang pagsama-sama na “non-fast-forward”, na naglilikha ng isang merge commit kahit na ang merge na naka-fast-forward ay posible. Nangangahulugan ito na kung anuman, sa bawat oras na pindutin mo ang pindutan ng merge, isang merge commit ay nilikha. Sa makikita mo sa Pindutan na merge at mga tagubilin sa manu-manong pagsama-sama ng isang Kahilingan na Pull. , binibigay sa iyo ng GitHub ang lahat na impormasyong ito kung i-click mo ang link ng implikasyon. Figure 117. Pindutan na merge at mga tagubilin sa manu-manong pagsama-sama ng isang Kahilingan na Pull. Kung nagpasya kang hindi mo nais na pagsamahin ito, maaari mo ring isara ang Kahilingan na Pull at aabisuhan ang taong nagbukas nito. Refs ng Kahilingan na Pull Kung ikaw ay nakikitungo sa isang maraming mga Kahilingan na Pull at hindi nais na magdagdag ng isang bungkos ng mga remote o gumawa ng isang beses na mga pull sa bawat oras, may isang malinis na trick na pinapahintulutan ng GitHub na gawin mo. Ito ay isang konting advanced na trick at tatalakayin natin ang mga detalye nito sa Ang Refspec , ngunit ito ay maaaring kapaki-pakinabang. Ang GitHub ay tunay na nag-aanunsiyo ng mga branch ng Kahilingan na Pull para sa isang repositoryo bilang uri ng mga pseudo-branch sa server. Bilang default hindi mo makuha ang mga ito kapag ikaw ay nag-clone, ngunit doon sila sa isang nakakubling paraan at maaari mong madaling ma-access ang mga ito. Upang ipakita ito, gagamitin namin ang isang mababang antas na utos (madalas na tinutukoy bilang isang utos na “plumbing”, kung saan babasahin natin ang tungkol dito nang higit pa sa Plumbing and Porcelain ) na tinawag na ls-remote . Ang utos na ito ay karaniwang hindi ginagamit sa pang-araw-araw na pagpapatakbo ng Git ngunit ito ay kapaki-pakinabang upang ipakita sa atin kung anong mga reperensiya ang naroroon sa server. Kung papatakbuhin natin ang utos na ito laban sa repositoryo na “blink” na ating ginamit natin kanina, makakakuha tayo ng listahan sa lahat ng mga branch at mga tag at ibang mga reperensiya sa repositoryo. $ git ls-remote https://github.com/schacon/blink 10d539600d86723087810ec636870a504f4fee4d HEAD 10d539600d86723087810ec636870a504f4fee4d refs/heads/master 6a83107c62950be9453aac297bb0193fd743cd6e refs/pull/1/head afe83c2d1a70674c9505cc1d8b7d380d5e076ed3 refs/pull/1/merge 3c8d735ee16296c242be7a9742ebfbc2665adec1 refs/pull/2/head 15c9f4f80973a2758462ab2066b6ad9fe8dcf03d refs/pull/2/merge a5a7751a33b7e86c5e9bb07b26001bb17d775d1a refs/pull/4/head 31a45fc257e8433c8d8804e3e848cf61c9d3166c refs/pull/4/merge Siyempre, kung ikaw ay nasa iyong repositoryo at nagpapatakbo ka ng git ls-remote origin o anumang remote na nais mong suriin, ipapakita nito sa iyo ang isang bagay na katulad nito. Kung ang repositoryo ay nasa GitHub at mayroon kang anumang mga Kahilingan na Pull na nabuksan, makakakuha ng mga reperensiyang ito na naka-prefix ng refs/pull/ . Ang mga ito ay talagang mga branch, ngunit dahil ang mga ito ay wala sa ilalim ng refs/heads/ hindi mo makuha ang mga ito nang normal kapag nag-clone ka o kumukuha mula sa server - ang proseso ng pagkuha ay hindi pinapansin ang mga ito nang normal. Mayroong dalawang reperensiya sa bawat Kahilingan na Pull - ang isang na nagtatapos sa mga punto na /head sa estaktong parehong commit bilang huling commit sa branch ng Kahilingan na Pull. Kaya kung may isang nagbubukas ng Kahilingan na Pull sa ating repositoryo at ang kanilang branch ay pinangalanang bug-fix at ito ay nakaturo sa commit na a5a775 , kung gayon sa ating repositoryo, wala tayong branch na bug-fix (dahil iyon ay nasa kanilang fork), nganit tayo ay magkakaroon ng pull/<pr#>/head na nakatuturo sa a5a775 . Ito ay nangangahulugan na madali nating ma-pull ang bawat branch ng Kahilingan na Pull sa isang beses nang walang kinakailangang pagdagdag ng isang bungkos ng mga remote. Ngayon, maaari mong gawin ang isang bagay tulad ng pagkuha ng direktang reperensiya. $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD Ito ay nagsasabi sa Git, “Kumonekta sa remote na origin , at i-download ang ref na pinangalanang refs/pull/958/head .” Masayang sinusunod ng Git, at nagda-download ng lahat na kinakailangan mo sa pagbuo ng ref na iyon, at naglalagay ng isang pointer sa commit na gusto mo sa ilalim ng .git/FETCH_HEAD . Maaari mong sundan iyon ng git merge FETCH_HEAD sa branch na gusto mong suriin, ngunit ang mensahe ng merge commit ay magiging mukhang kakaiba. Gayundin, kung sinusuri mo ang maraming mga kahilingan na pull, ito ay nakakapagod. Mayroon ding paraan upang ma-fetch ang lahat na mga kahilangan na pull, at nagsisigurado na ang mga ito ay laging bago sa tuwing ikaw ay kumukonekta sa remote. Buksan ang .git/config sa iyong paboritong editor, at hanapin ang remote na origin . Dapat magiging magmukhang ganito: [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* Ang linyang iyon na nagsisimula sa fetch = ay isang “refspec.” Ito’y isang paraan ng pagmamapa ng mga pangalan sa remote sa mga pangalan sa iyong lokal na direktoryo na .git . Ang partikular na ito ay nagsasabi sa Git, "ang mga bagay sa remote na nasa ilalim ng refs/heads ay dapat mapunta sa aking lokal na repositoryo sa ilalim ng refs/remotes/origin ." Maaari mong mabago ang seksiyon na ito upang magdagdag ng iba pang refspec: [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* Ang linyang iyon ay nagsasabi sa Git, “Lahat ng mga ref na nagmumukhang refs/pull/123/head ay dapat nakaimbak nang lokal kagaya ng refs/remotes/origin/pr/123 .” Ngayon, kung ikaw ay nag-save ng file na iyon, at gumawa ng isang git fetch : $ git fetch # … * [new ref] refs/pull/1/head -> origin/pr/1 * [new ref] refs/pull/2/head -> origin/pr/2 * [new ref] refs/pull/4/head -> origin/pr/4 # … Ngayon lahat ng mga kahilingan na pull na naka-remote ay kinakatawan nang lokal na may mga ref na kumilos tulad ng pagsubaybay sa mga branch; ang mga ito ay read-only, at ito ay na-update kapag gumawa ka ng isang fetch. Ginagawang napakadali nitong magsubok ng code mula sa isang kahilingan na pull ng pa-lokal: $ git checkout pr/2 Nag-check out ng mga file: 100% (3769/3769), tapos na. Branch pr/2 nag-set up upang sumaybay sa remote branch pr/2 mula sa origin. Pinalit sa isang bagong branch na 'pr/2' Tatandaan ng nakamatang-agila sa inyo ang head sa huli ng remote na bahagi ng refspec. Mayroon ding ref na refs/pull/#/merge sa panig ng GitHub , na kumakatawan sa commit na magiging resulta kung i-push mo ang pindutan na “merge” sa site. Ito ay nagpapahintulot sa iyo na suriin ang merge bago pindutin ang pindutan. Mga Kahilingan na Pull sa mga Kahilingan na Pull Hindi ka lamang magbubukas ng mga Kahilingan na Pull na naka-target sa prinsipal o branch na master , maaari ka talagang magbukas ng isang Kahilingan na Pull na nagta-target sa anumang branch sa network. Sa katunayan, maaari ka ring mag-target sa ibang Kahilingan na Pull. Kung nakikita mo ang isang Kahilingan na Pull na gumagalaw sa tamang direksyon at mayroon kang ideya para sa isang pagbabago na nakadepende dito o hindi ka sigurado na magandang ideya, o wala ka lamang access sa pag-push sa branch ng target, maaari kang magbukas ng isang Kahilingan na Pull na direkta dito. Kapag ikaw ay pumunta upang bumukas ng isang Kahilingan na Pull, may isang kahon sa itaas ng pahina na tumutukoy kung aling branch ang hinihingan mo na maka-pull at kung saan hinihiling mo na mag-pull. Kung pinindot mo ang “Edit” na pindutan sa kanan ng kahon na iyon, maaari kang magbago hindi lamang sa mga branch kundi rin sa kung anong fork. Figure 118. Mano-manong baguhin ang Kahilingan ng Pull na target ang fork at branch. Dito maaari kang medyo madaling magtukoy upang pagsamahin ang iyong bagong branch sa ibang Kahilingan na Pull o ibang fork ng proyekto. Mga Pagbanggit at mga Abiso Mayroon ding magandang built in na sistema ng mga abiso ang GitHub na magagamit kapag ikaw ay may mga tanong o kailangan na katugunan mula sa tiyak na mga indibidwal o koponan. Sa anumang komento maaari mong simulan sa pagtitipa ng karakter na @ at ito ay magsisimula sa awtomatikong matapos kasabay ng mga pangalan at username ng tao na mga tagatulong o nag-aambag sa proyekto. Figure 119. Simulang magtipa ng @ upang banggitin ang isang tao. Maaari ka ring magbanggit ng isang gumagamit na wala sa dropdown, ngunit kadalasang maaaring mapabilis ng autocompleter. Sa sandaling magpaskil ka ng komento sa isang pagbanggit ng user, aabisuhan ang user na iyon. Nangangahulugan ito na ito ay maaaring maging isang tunay na epektibong paraan ng paghawak ng mga tao sa mga pag-uusap sa halip na paggawa ng mga ito ng poll. Kadalasan sa mga Kahilingan na Pull sa mga tao sa GitHub ay magpu-pull ng iba pang mga tao sa kanilang mga koponan o sa kanilang kompanya upang magsuri ng isang Isyu o Kahilingan na Pull. Kung may isang tao ang nakuhang nabanggit sa isang Kahilingan na Pull o Isyu, sila ay magiging “naka-subscribe” nito at patuloy na makakakuha ng mga abiso sa anumang oras na nangyayari ang aktibidad nito. Ma-subscribe ka rin sa isang bagay kung binuksan mo ito, kung nanonood ka sa repositoryo o kung ikaw ay nagkomento ka sa isang bagay. Kung hindi mo na nais na makatanggap ng mga abiso, may isang pindutan na “Unsubscribe” sa pahina na maaari mong i-click upang ihinto ang pagtanggap ng mga pagbabago nito. Figure 120. Mag-unsubscribe mula sa isang Isyu o Kahilingan na Pull. Ang Pahina ng mga Abiso Kapag kami ay nagbanggit ng mga “abiso” na may kinalaman sa GitHub, ibig naming sabihin ang isang tiyak na paraan na sinisikap ng GitHub na makipag-ugnay sa iyo kapag nangyayari ang mga kaganapan at may ilang iba’t-ibang mga paraan na maaari mong isaayos ang mga ito. Kung pupunta sa sa tab na “Sentro ng Abiso” mula sa pahina ng settings, makikita mo ang ilan sa mga opsyon na mayroon ka. Figure 121. Mga opsyon sa Sentro ng Abiso. May dalawang pagpipilian na makakakuha ka ng mga abiso sa “Email” at sa “Web” at maaari kang pumili sa alinman, wala o pareho para sa kapag aktibong kang lumahok sa mga bagay at para sa aktibidad sa mga repositoryo na iyong pinapanood. Mga Abiso ng Web Ang mga Abiso ng Web ay umiiral lamang sa GitHub at maaari mo itong suriin sa GitHub lamang. Kung pinili mo ang opsyon na ito sa iyong kagustuhan at isang abiso ay na-trigger para iyo, makikita mo ang isang maliit na asul na tuldok sa iyong icon ng mga abiso sa itaas ng iyong screen gaya ng nakikita sa Sentro ng Abiso. . Figure 122. Sentro ng Abiso. Kung nag-click ka doon, makikita mo ang isang listahan ng lahat ng mga aytem na ikaw ay naabisuhan, nakagrupo sa pamamagitan ng proyekto. Maaari kang mag-filter sa mga abiso ng partikular na proyekto sa pamamagitan ng pag-click sa pangalan nito sa kanang sidebar. Maaari mo ring kilalanin ang abiso sa pamamagitan ng pag-click sa checkmark icon na kasunod sa anumang abiso, o kilalanin ang lahat ng mga abiso sa isang proyekto sa pamamagitan ng pag-click sa checkmark na nasa itaas ng grupo. Mayroon din isang pindutan na mute kasunod sa bawat checkmark na maaari mong i-click upang hindi makatanggap ng anumang mga abiso sa aytem na iyon. Lahat ng mga kasangkapan na ito ay kapaki-pakinabang sa pangangasiwa ng malaking bilang ng mga abiso. Karamihan sa mga makapangyarihang gumagamit ng GitHub ay nag-off lamang ng mga abiso sa email sa kabuuan at namamahala ng kanilang mga abiso sa pamamagitan ng screen na ito. Mga Abiso sa Email Ang mga abiso sa Email ay ang ibang paraan na mapangasiwaan mo ang mga abiso sa GitHub. Kung ini-off mo ito makakakuha ka ng mga email sa bawat abiso. Nakikita natin ang mga halimbawa nito sa Mga komento naipadala bilang mga abiso sa email at Abiso sa email ng isang bagong Kahilingan na Pull. . Ang mga email ay ma-thread din nang mabuti, na maganda kung ika’y gumagamit ng isang kliyente ng pag-thread ng email. Mayroon ding isang makatarungang dami ng metadata na naka-embed sa mga header ng mga email na ipinadala sa iyo ng GitHub, na maaaring maging kapaki-pakinabang para sa pag-set up ng mga pasadyang filter at patakaran. Halimbawa, kung titingnan natin ang aktwal na mga header ng email na pinadala kay Tony sa email na ipinapakita sa Abiso sa email ng isang bagong Kahilingan na Pull. , makikita natin ang mga sumusunod kabilang sa naipadalang impormasyon: Para: tonychacon/fade <fade@noreply.github.com> ID-ng-Mensahe: <tonychacon/fade/pull/1@github.com> Paksa: [fade] Maghintay ng mas matagal upang makita ang mas mahusay na epekto ng pag-dim (#1) X-GitHub-Tumatanggap: tonychacon ID-ng-Listahan: tonychacon/fade <fade.tonychacon.github.com> Listahan-ng-Archive: https://github.com/tonychacon/fade Listahan-ng-Paskil: <mailto:reply+i-4XXX@reply.github.com> Listahan-ng-Unsubscribe: <mailto:unsub+i-XXX@reply.github.com>,... X-GitHub-Address-ng-Tumatanggap: tchacon@example.com Mayroong ilang mga kawili-wiling bagay dito. Kung gusto mong i-highlight o i-rutang muli ang mga email sa partikular na proyektong ito o kahit ang Kahilingan na Pull, ang impormasyon sa ID-ng-Mensahe ay nagbibigay sa iyo ng lahat ng datos sa format na <user>/<project>/<type>/<id> . Kung ito isang isyu, bilang halimbawa, ang patlang na <uri> sana ay naging mga “isyu” sa halip na “pull”. Ang mga patlang na Listahan-ng-Paskil at Listahan-ng-Unsubscribe ay nangangahulugan na kung mayroon kang kliyente ng mail na umiintindi sa mga iyon, madali mong mapaskil sa listahan o “Unsubscribe” mula sa thread. Iyon ay mahalagang kapareho a pag-click sa pindutan na “mute” sa bersyon sa web ng abiso o “Unsubscribe” sa pahina mismo ng Isyu o Kahilingan na Pull. Makabuluhan ding tandaan na kung pareho kang mayroong mga abiso sa email at web na pinagana at nabasa mo ang bersyon sa email ng abiso, ang bersyon sa web ay mamarkahan bilang nabasa pati na rin kung ikaw ay mayroon mga larawan na pinayagan sa iyong kliyente ng mail. Mga Espesyal na File Mayroong ilang mga espesyal na file na mapapansin ng GitHub kung naroon sila sa iyong repositoryo. README Ang una ay ang file na README , na maaaring maging halos sa anumang format na nakikilala ng GitHub bilang prosa. Halimbawa, maaari itong maging README , README.md , README.asciidoc , atbp. Kung nakikita ng GitHub ang isang file ng README sa iyong source, ito ay magbibigay nito sa pahina ng paglapag ng proyekto. Marami sa mga kopona ang gumagamit sa file na ito upang hawakan ang lahat ng may kaugnay na impormasyon ng proyekto para sa isang tao na maaaring bago sa repositoryo o proyekto. Kasama sa pangkalahatang ito ang mga bagay na tulad nito: Para saan ang proyektong ito Paano isaayos at i-install ito Isang halimbawa ng kung paano ito gamitin o makuha itong patakbuhin Ang lisensya na ibinibigay sa ilalim ng proyekto Paano mag-ambag dito Dahil ang GitHub ay magre-render ng file na ito, maaari mong i-embed ang mga larawan o mga link sa mga ito para sa dagdag na kadalian ng pag-unawa. PAG-AAMBAG Ang iba pang espesyal na file na kinikilala ng GitHub ay ang file na PAG-AAMBAG . Kung mayroon kang file na pinangalanang PAG-AAMBAG na may anumang palugit ng file, ipapakita ng GitHub ang Pagbubukas ng isang Kahilingan na Pull kapag umiiral ang isang file na PAG-AAMBAG. kapag sinuman ay nagsisimula sa pagbubukas ng isang Kahilingan na Pull. Figure 123. Pagbubukas ng isang Kahilingan na Pull kapag umiiral ang isang file na PAG-AAMBAG. Ang ideya dito ay maaari mong tukuyin ang mga partikular na bagay na gusto mo o ayaw mo sa isang Kahilingan na Pull na ipinadala sa iyong proyekto. Sa ganitong paraan maaaring basahin ng mga tao ang mga patnubay bago buksan ang Kahilingan na Pull. Pangangasiwa sa Proyekto Sa pangkalahatan ay hindi maraming mga bagay na pang-administratibo na magagawa mo sa isang proyekto, ngunit may ilang mga bagay na maaaring maging interesado. Pagbabago sa Default Branch Kung gumagamit ka ng isang branch maliban sa “master” bilang default branch na gusto mong doon magbukas ng Kahilingan na Pull ang mga tao o makikita bilang default, maaari mong baguhin iyon sa pahina ng settings ng iyong repositoryo sa ilalim ng tab na ‘Mga Opsyon’'. Figure 124. Baguhin ang default branch para sa isang proyekto. Baguhin lamang ang default na branch sa dropdown at iyon ang magiging default para sa lahat ng mga pangunahing pagpapatakbo mula doon, kabilang kung aling branch ang naka-check out bilang default kapag may nag-clone sa repositoryo. Paglilipat ng isang Proyekto Kung nais mong maglipat ng isang proyekto sa ibang gumagamit o isang organisasyon sa GitHub, mayroong opsyon na ‘Paglipat ng Pagmamay-ari’' sa ilalim ng parehong tab na “Mga Opsyon” ng pahina ng settings ng iyong repositoryo na nagpapahintulot sa iyong gawin ito. Figure 125. Ilipat ang isang proyekto sa ibang gumagamit ng GitHub o Organisasyon. Ito ay makakatulong kung ikaw ay lilisan sa isang proyekto at may gustong pumalit nito, o kung lumalaki na ang iyong proyekto at gusto na ilipat ito sa isang organisasyon. Hindi lamang inililipat nito ang repositoryo kasama ang lahat ng mga tagamasid at mga star sa ibang lugar, itinatakda din nito ang isang pag-redirect mula sa iyong URL sa bagong lugar. I-redirect din nito ang mga pag-clone at pagkuha mula sa Git, hindi lamang mga kahilingan sa web. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/de/v2/Git-auf-dem-Server-GitLab | Git - GitLab About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Erste Schritte 1.1 Was ist Versionsverwaltung? 1.2 Kurzer Überblick über die Historie von Git 1.3 Was ist Git? 1.4 Die Kommandozeile 1.5 Git installieren 1.6 Git Basis-Konfiguration 1.7 Hilfe finden 1.8 Zusammenfassung 2. Git Grundlagen 2.1 Ein Git-Repository anlegen 2.2 Änderungen nachverfolgen und im Repository speichern 2.3 Anzeigen der Commit-Historie 2.4 Ungewollte Änderungen rückgängig machen 2.5 Mit Remotes arbeiten 2.6 Taggen 2.7 Git Aliases 2.8 Zusammenfassung 3. Git Branching 3.1 Branches auf einen Blick 3.2 Einfaches Branching und Merging 3.3 Branch-Management 3.4 Branching-Workflows 3.5 Remote-Branches 3.6 Rebasing 3.7 Zusammenfassung 4. Git auf dem Server 4.1 Die Protokolle 4.2 Git auf einem Server einrichten 4.3 Erstellung eines SSH-Public-Keys 4.4 Einrichten des Servers 4.5 Git-Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Von Drittanbietern gehostete Optionen 4.10 Zusammenfassung 5. Verteiltes Git 5.1 Verteilter Arbeitsablauf 5.2 An einem Projekt mitwirken 5.3 Ein Projekt verwalten 5.4 Zusammenfassung 6. GitHub 6.1 Einrichten und Konfigurieren eines Kontos 6.2 Mitwirken an einem Projekt 6.3 Ein Projekt betreuen 6.4 Verwalten einer Organisation 6.5 Skripte mit GitHub 6.6 Zusammenfassung 7. Git Tools 7.1 Revisions-Auswahl 7.2 Interaktives Stagen 7.3 Stashen und Bereinigen 7.4 Deine Arbeit signieren 7.5 Suchen 7.6 Den Verlauf umschreiben 7.7 Reset entzaubert 7.8 Fortgeschrittenes Merging 7.9 Rerere 7.10 Debuggen mit Git 7.11 Submodule 7.12 Bundling 7.13 Replace (Ersetzen) 7.14 Anmeldeinformationen speichern 7.15 Zusammenfassung 8. Git einrichten 8.1 Git Konfiguration 8.2 Git-Attribute 8.3 Git Hooks 8.4 Beispiel für Git-forcierte Regeln 8.5 Zusammenfassung 9. Git und andere VCS-Systeme 9.1 Git als Client 9.2 Migration zu Git 9.3 Zusammenfassung 10. Git Interna 10.1 Basisbefehle und Standardbefehle (Plumbing and Porcelain) 10.2 Git Objekte 10.3 Git Referenzen 10.4 Packdateien (engl. Packfiles) 10.5 Die Referenzspezifikation (engl. Refspec) 10.6 Transfer Protokolle 10.7 Wartung und Datenwiederherstellung 10.8 Umgebungsvariablen 10.9 Zusammenfassung A1. Anhang A: Git in anderen Umgebungen A1.1 Grafische Schnittstellen A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Zusammenfassung A2. Anhang B: Git in deine Anwendungen einbetten A2.1 Die Git-Kommandozeile A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Anhang C: Git Kommandos A3.1 Setup und Konfiguration A3.2 Projekte importieren und erstellen A3.3 Einfache Snapshot-Funktionen A3.4 Branching und Merging A3.5 Projekte gemeinsam nutzen und aktualisieren A3.6 Kontrollieren und Vergleichen A3.7 Debugging A3.8 Patchen bzw. Fehlerkorrektur A3.9 E-mails A3.10 Externe Systeme A3.11 Administration A3.12 Basisbefehle 2nd Edition 4.8 Git auf dem Server - GitLab GitLab GitWeb ist jedoch ein recht minimalistisches Tool. Wenn du einen modernen, voll ausgestatteten Git-Server suchst, gibt es einige Open-Source-Lösungen, die du stattdessen installieren kannst. Da GitLab einer der beliebtesten ist, werden wir uns mit der Installation im Detail befassen und es als Beispiel verwenden. Dies ist etwas schwieriger als die GitWeb-Option und erfordert mehr Wartung, aber es ist eine viel umfassendere Lösung. Installation GitLab ist eine datenbankgestützte Webanwendung, so dass die Installation etwas aufwändiger ist als bei einigen anderen Git-Servern. Glücklicherweise ist dieser Prozess sehr gut dokumentiert und unterstützt. GitLab empfiehlt dringend, GitLab über das offizielle Omnibus GitLab-Paket zu installieren. Die anderen Installationsmethoden sind: GitLab Helm-Chart zur Verwendung mit Kubernetes. Dockerisierte GitLab-Pakete zur Verwendung mit Docker. Direkt aus den Quelldateien. Cloud-Anbieter wie AWS, Google Cloud Platform, Azure, OpenShift und Digital Ocean. Weitere Informationen findest du in der Readme-Datei GitLab Community Edition (CE) . Administration Die Verwaltungsoberfläche von GitLab wird webbasiert bereitgestellt. Benutze einfach deinen Browser, um den Hostnamen oder die IP-Adresse, auf der GitLab installiert ist, anzugeben, und melden dich als Admin-Benutzer an. Der Standardbenutzername ist admin@local.host , das Standardpasswort ist 5iveL!fe (dies muss nach der Eingabe geändert werden ). Klicke nach der Anmeldung im Menü oben rechts auf das Symbol „Admin-Bereich“. Abbildung 50. Der „Admin-Bereich“ im GitLab-Menü Benutzer Jeder Gitlab Nutzer muß ein Benutzerkonto besitzen. Benutzerkonten sind recht simple. Hauptsächlich beinhalten sie persönliche Informationen, die an Login-Daten geknüpft sind. Jedes Benutzerkonto hat einen namespace (Namensraum), der eine logische Gruppierung von Projekten ist, die diesem Benutzer gehören. Wenn der Benutzer jane ein Projekt mit dem Namen project hätte, wäre die URL dieses Projekts http://server/jane/project . Abbildung 51. Das Fenster der Benutzerverwaltung von GitLab Das Löschen eines Benutzers kann auf zwei Arten erfolgen. Das „Sperren“ eines Benutzers verhindert, dass er sich am GitLab anmeldet. Alle Daten unter den Namensraum dieses Benutzers bleiben jedoch erhalten. Mit der E-Mail-Adresse dieses Benutzers signierte Commits werden weiterhin mit seinem Profil verknüpft. Das „Löschen“ eines Benutzers hingegen entfernt ihn vollständig aus der Datenbank und dem Dateisystem. Alle Projekte und Daten in seinem Namensraum werden entfernt, und alle Gruppen, die sich in seinem Besitz befinden, werden ebenfalls entfernt. Das ist eine permanente und destruktive Aktion, die in der Regel selten angewendet wird. Gruppen Eine GitLab-Gruppe ist eine Sammlung von Projekten. Zusätzlich beinhaltet sie Daten, wie Benutzer auf diese Projekte zugreifen können. Jede Gruppe hat einen Projektnamensraum (genauso wie Benutzer). Wenn die Gruppe training ein Projekt materials hat, lautet die URL http://server/training/materials . Abbildung 52. Der Admin-Bildschirm für die Gruppenverwaltung von GitLab Jeder Gruppe ist einer Reihe von Benutzern zugeordnet, von denen jeder eine Berechtigungsstufe für die Projekte der Gruppe und der Gruppe selbst hat. Diese reichen von „Guest“ (nur Themen und Chat) bis hin zu „Owner“ (volle Kontrolle über die Gruppe, ihre Mitglieder und ihre Projekte). Die Arten von Berechtigungen sind zu zahlreich, um sie hier aufzulisten, aber GitLab hat einen hilfreichen Link auf dem Administrationsbildschirm. Projekte Ein GitLab-Projekt entspricht in etwa einem einzelnen Git-Repository. Jedes Projekt gehört zu einem einzigen Namensraum, entweder einem Benutzer oder einer Gruppe. Wenn das Projekt einem Benutzer gehört, hat dieser Projektbesitzer die direkte Kontrolle darüber, wer Zugriff auf das Projekt hat. Falls das Projekt einer Gruppe gehört, werden auch die Berechtigungen der Gruppe auf Benutzerebene wirksam. Jedes Projekt hat eine Zugriffsebene, die steuert, wer Lesezugriff auf die Seiten und das Repository des Projekts hat. Wenn ein Projekt privat ist, muss der Eigentümer des Projekts Benutzern explizit Zugriff gewähren. Ein internes Projekt ist für jeden angemeldeten Benutzer sichtbar. Ein öffentliches (engl. public ) Projekt ist für jeden sichtbar. Beachte, dass dies sowohl den Zugriff auf git fetch als auch den Zugriff auf die Web-Benutzeroberfläche für dieses Projekt steuert. Hooks GitLab bietet Unterstützung für Hooks, sowohl auf Projekt- als auch auf Systemebene. Für beides führt der GitLab-Server einen HTTP POST mit einem beschreibenden JSON durch, wenn relevante Ereignisse eintreten. Auf diese Weise kannst du deine Git-Repositorys und GitLab-Instanzen mit dem Rest deiner Entwicklungsplattform verbinden, wie z.B. CI-Server, Chatrooms oder Deploymenttools. Grundlegende Anwendung Das erste, was du mit GitLab machen solltest, ist das Erstellen eines neuen Projekts. Dies geschieht durch Anklicken des Symbols „+“ in der Symbolleiste. Du wirst nach dem Namen des Projekts gefragt, zu welchem Namensraum es gehören soll und wie seine Sichtbarkeit sein soll. Das meiste, was du hier angibst, ist nicht permanent und kann später über die Konfigurations-Oberfläche angepasst werden. Klicke auf „Projekt erstellen“, und du bist fertig. Sobald das Projekt existiert, wirst du es vermutlich mit einem lokalen Git-Repository verbinden wollen. Jedes Projekt ist über HTTPS oder SSH zugänglich. Beide können genutzt werden, um ein Git-Remote zu konfigurieren. Die URLs sind oben auf der Startseite des Projekts sichtbar. Für ein bestehendes lokales Repository erstellt dieser Befehl einen Remote mit Namen gitlab für die gehostete Instanz: $ git remote add gitlab https://server/namespace/project.git Wenn du noch keine lokale Kopie des Repositorys hast, kannst du das ganz einfach nachholen: $ git clone https://server/namespace/project.git Die Web-Benutzeroberfläche bietet Zugriff auf viele nützliche Informationen des Repositorys. Die Homepage jedes Projekts zeigt die letzten Aktivitäten an. Die Links oben zeigen verschiedene Ansichten der Projektdateien und zum Commit-Log. Zusammen arbeiten Die einfachste Art der Zusammenarbeit bei einem GitLab-Projekt besteht darin, jedem Benutzer direkten Push-Zugriff auf das Git-Repository zu ermöglichen. Du kannst einem Benutzer zu einem Projekt hinzufügen, indem du im Abschnitt „Mitglieder“ der Einstellungen dieses Projekts den neuen Benutzer einer Zugriffsebene zuordnest. Die verschiedenen Zugriffsebenen werden in den Gruppen erläutert. Indem ein Benutzer die Zugriffsebene „Developer“ oder höher erhält, kann dieser Benutzer Commits und Branches direkt und ohne Einschränkung in das Repository pushen. Eine weitere, stärker entkoppelte Art der Zusammenarbeit ist die Nutzung von Merge-Requests. Diese Funktion ermöglicht es jedem Benutzer, der ein Projekt sehen kann, kontrollierter dazu beizutragen. Benutzer mit direktem Zugriff können einfach einen Branch erstellen, auf ihn committen und einen Merge-Request von ihrem Branch zurück in den master oder einen anderen Branch einreichen. Benutzer, die keine Push-Berechtigungen für ein Repository haben, können es „forken“ (ihre eigene Kopie erstellen), Push-Commits für diese Kopie erstellen und einen Merge-Request von ihrer Fork zurück zum Hauptprojekt einreichen. Dieses Modell ermöglicht es dem Eigentümer, die volle Kontrolle darüber zu behalten, was wann in das Repository gelangt, und gleichzeitig Beiträge von unbekannten Benutzern zu ermöglichen. Merge-Requests und Issues sind die Hauptelemente von langlebigen Diskussionen in GitLab. Jede Merge-Request ermöglicht eine zeilenweise Diskussion der vorgeschlagenen Änderung. Damit kann eine einfache Code-Überprüfung (engl. Code-Review) sowie ein Diskussionsstrang umgesetzt werden. Beide können Benutzern zugeordnet oder in Meilensteine organisiert werden. Dieser Abschnitt konzentriert sich hauptsächlich auf die Git-bezogenen Funktionen von GitLab. Als ausgereiftes Programm bietet es viele weitere Funktionen, die dir bei der Teamarbeit helfen, wie Projekt-Wikis und System-Wartungstools. Ein Vorteil von GitLab ist, dass du nach der Einrichtung und Inbetriebnahme des Servers selten eine Konfigurationsdatei anpassen oder über SSH auf den Server zugreifen musst. Die überwiegende Verwaltung und allgemeine Nutzung kann über die Browser-Oberfläche erfolgen. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/Pag-branch-ng-Git-Mga-Branch-sa-Maikling-Salita | Git - Mga Branch sa Maikling Salita About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 3.1 Pag-branch ng Git - Mga Branch sa Maikling Salita Halos bawat VCS ay mayroong ilang porma ng suporta ng pag-branch. Ang pag-branch ay nangangahulugang ikaw ay hihiwalay mula sa pangunahing linya ng pagde-develop at magpapatuloy sa paggawa ng trabaho na hindi nanggugulo sa pangunahing linyang iyon. Sa karamihan ng mga kasangkapan ng VCS, ito ay isang medyo magastos na proseso, na madalas ay kinakailangan mong gumawa ng isang panibagong kopya ng iyong source code na direktoryo, na maaaring tumagal ng mahabang panahon para sa mga malalaking proyekto. Iilang mga tao ay tumutukoy sa modelo ng pag-branch ng Git bilang “mamamatay na tampok,” nito at tiyak nitong tinatakda ang Git na hiwalay sa VCS na komunidad. Bakit ito sobrang espesyal? Ang paraan ng pag-branch ng Git ay hindi kapani-paniwalang magaan, na ginagawa ang mga operasyon ng pag-branch na halos madalian, at ang pagpapalit pabalik at patungo sa pagitan ng mga branch sa pangkalahatan na kasing bilis. Hindi katulad ng karamihan sa ibang mga VCS, ang Git ay hinihikayat ang mga daloy ng trabaho na madalas na nagba-branch at nagme-merge, kahit maramihan pa sa isang araw. Ang pagkaunawa at pagkadalubhasa ng tampok na ito ay nagbibigay sa iyo ng isang makapangyarihan at natatanging kasangkapan at maaaring buong baguhin ang paraan ng iyong pagde-develop. Mga Branch sa Maikling Salita Upang talagang maintindihan ang paraan ng Git sa paggawa ng pag-branch, kailangan nating umatras at suriin kung paano nag-iimbak ng data ang Git. Kung iyong natatandaan mula sa Pagsisimula , ang Git ay hindi nag-iimbak ng data bilang isang serye ng mga changeset o mga kaibahan, ngunit sa halip ay isang serye ng mga snapshot. Kapag ikaw ay gumawa ng isang commit, ang Git ay nag-iimbak ng isang commit na object na naglalaman ng isang pointer sa snapshot ng nilalaman na iyong na-stage. Ang object na ito ay naglalaman din ng pangalan at email ng may-akda, ang mensahe na iyong na-type, at mga pointer sa commit o mga commit na direktang dumating bago ang commit na ito (magulang nito o mga magulang): zero na mga magulang para sa paunang commit, isang magulang para sa isang normal na commit, at maramihang mga magulang para sa isang commit na nagreresulta mula sa isang pag-merge ng dalawa o higit pang mga branch. Upang maisalarawan ito, ipagpalagay natin na ikaw ay may isang direktoryong naglalaman ng tatlong mga file, at na-stage mo lahat ang mga ito at na-commit. Ang pag-stage ng mga file ay nagkakalkula ng isang checksum para sa bawat isa (ang SHA-1 na hash na nabanggit namin sa Pagsisimula ), nag-iimbak sa bersyong iyon ng file sa Git na repositoryo (tinutukoy ng Git ang mga ito bilang mga blob), at nagdaragdag ng checksum na iyon sa staging na lawak: $ git add README test.rb LICENSE $ git commit -m 'Ang paunang commit ng aking proyekto' Kapag nagawa mo ang commit sa pamamagitan ng pagpapatakbo ng git commit , ang Git ay ichi-checksum ang bawat subdirectory (sa kasong ito, ang root na direktoryo ng proyekto lamang) at iiimbak ang mga tree object na iyon sa Git na repositoryo. Ang Git ngayon ay gagawa ng isang commit na object na may metadata at isang pointer sa root project ng tree upang ito ay makalikha muli ng snapshot na iyon kapag kinakailangan. Ang iyong Git na repositoryo ngayon ay naglalaman ng limang mga object: isang blob para sa mga nilalaman ng bawat isa sa iyong tatlong mga file, isang tree na naglilista ng mga nilalaman ng direktoryo at tinutukoy kung anong mga pangalan ng file ang naimbak bilang mga blob, at isang commit na may pointer sa root tree at lahat ng mga metadata ng commit. Figure 9. Isang commit at ang tree nito Kung gagawa ka ng ilang mga pagbabago at magku-commit muli, ang susunod na commit ay mag-iimbak ng isang pointer sa commit na dumating kaagad bago nito. Figure 10. Mga Commit at mga magulang nila Ang isang branch sa Git ay simpleng isang magaan na nagagalaw na pointer sa isa sa mga commit na ito. Ang default na pangalan ng branch sa Git ay master . Habang nagsisimula kang gumawa ng mga commit, ikaw ay bibigyan ng isang master na branch na tumuturo sa huling commit na ginawa mo. Sa bawat pagkakataon na ikaw ay mag-commit, awtomatikong ginagalaw ito nang pasulong. Ang “master” na branch sa Git ay hindi isang espesyal na branch. Ito ay eksaktong kapareho ng anumang ibang branch. Ang dahilan lamang kung bakit halos bawat repositoryo ay mayroong isa ay ang git init na utos na gumagawa nito bilang default at karamihan sa mga tao ay hindi mag-aabalang baguhin ito. Figure 11. Isang branch at ang kasaysayan ng commit nito Paggawa ng isang Bagong Branch Ano ang mangyayari kung ikaw ay gumawa ng isang bagong branch? Ang paggawa nito ay lumilikha ng isang bagong pointer para sa iyo upang ilipat kahit saan. Sabihin nating gumawa ka ng isang bagong branch na tinatawag na testing. Gagawin mo ito gamit ang git branch na utos: $ git branch testing Gumagawa ito ng isang bagong pointer sa parehong commit kung saan nandoon ka. Figure 12. Dalawang mga branch na tumuturo sa parehong serye ng mga commit Paano nalalaman ng Git kung anong branch ka naroroon? Ito ay nagpapanatili ng isang espesyal na pointer na tinatawag na HEAD . Tandaan na ito ay mas kakaiba kaysa sa konsepto ng HEAD sa ibang mga VCS na nakasanayan mo, katulad ng Subversion o CVS. Sa Git, ito ay isang pointer sa lokal na branch kung saan nandoon ka. Sa kasong ito, nasa master ka pa rin. Ang git branch na utos ay gumawa lamang ng isang bagong branch — hindi ito lumipat sa branch na iyon. Figure 13. Ang HEAD na tumuturo sa isang branch Madali mong makikita ito sa pamamagitan ng pagpapatakbo ng isang simpleng git log na utos na nagpapakita sa iyo kung saan nakaturo ang mga pointer ng branch. Ang opsyon ay tinatawag na --decorate . $ git log --oneline --decorate f30ab (HEAD -> master, testing) add feature #32 - ability to add new formats to the central interface 34ac2 Fixed bug #1328 - stack overflow under certain conditions 98ca9 The initial commit of my project Maaari mong tingnan ang “master” at “testing” na mga branch na nasa sunod ng f30ab na commit. Paglilipat ng mga Branch Upang lumipat sa isang umiiral na branch, patakbuhin mo ang git checkout na utos. Lumipat tayo sa bagong testing na branch: $ git checkout testing Nililipat nito ang HEAD upang tumuro sa testing na branch. Figure 14. Ang HEAD ay tumuturo sa kasalukuyang branch Ano ang kabuluhan nito? Gumawa tayo ng iba pang commit: $ vim test.rb $ git commit -a -m 'gumawa ng isang pagbabago' Figure 15. Ang HEAD na branch ay ginagalaw nang pasulong kapag may isang commit ay naggawa Ito ay kawili-wili, dahil ngayon ang iyong testing na branch ay nilipat nang pasulong, ngunit ang iyong master na branch ay nakaturo pa rin sa commit kung saan nandoon ka noong pinatakbo mo ang git checkout upang maglipat ng mga branch. Lumipat tayo pabalik sa master na branch: $ git checkout master Figure 16. Ang HEAD ay lilipat kapag ikaw nag-checkout Ang utos na iyon ay gumawa ng dalawang bagay. Inilipat nito ang HEAD na pointer pabalik upang tumuro sa master na branch, at ibinalik nito ang mga file sa iyong tinatrabaho na repositoryo pabalik sa snapshot na tinuturo ng master . Ito ay nangangahulugan ding ang mga pagbabago na ginawa mo mula sa puntong ito nang pasulong ay magkaiba mula sa isang mas matandang bersyon ng proyekto. Mahalagang iri-rewind nito ang trabahong nagawa mo sa iyong testing na branch upang maaaring kang pumunta sa iba pang direksyon. Example 4. Ang paglilipat ng mga branch ay nagbabago ng mga file sa iyong tinatrabahong direktoryo Importanteng tandaan na kapag ikaw ay lumilipat ng mga branch sa Git, ang mga file sa iyong tinatrabaho na direktoryo ay mababago. Kung ikaw ay maglilipat sa isang mas matandang branch, ang iyong tinatrabaho na direktoryo ay maibabalik upang magmukha ito katulad sa huling pagkakataong ikaw ay nag-commit sa branch na iyon. Kung ang Git ay hindi maaaring malinis na gumawa nito, hindi ka hahayaan nitong maglipat. Gumawa tayo ng ilang kaunting mga pagbabago at mag-commit muli: $ vim test.rb $ git commit -a -m 'gumawa ng iba pang mga pagbabago' Ngayon ang kasaysayan ng iyong proyekto ay humiwalay na (tingnan ang Divergent na kasaysayan ). Ikaw ay lumikha at lumipat sa isang branch, gumawa ng ilang trabaho dito, at pagkatapos ay lumipat pabalik sa iyong pangunahing branch at gumawa ng iba pang trabaho. Parehong ang mga pagbabagong iyon ay magkaiba sa hiwalay na mga branch: maaari kang lumipat pabalik at patungo sa pagitan ng mga branch at pagsamahin sila kapag handa ka na. At ginawa mo lahat iyon gamit ang simpleng branch , checkout , at commit na mga utos. Figure 17. Divergent na kasaysayan Maaari mo ring madaling tingnan ito gamit ang git log na utos. Kung patatakbuhin mo ang git log --oneline --decorate --graph --all ito ay maglilimbag ng kasaysayan ng iyong mga commmit, na nagpapakita kung nasaan ang iyong mga branch pointer at kung paano humiwalay ang iyong kasaysayan. $ git log --oneline --decorate --graph --all * c2b9e (HEAD, master) made other changes | * 87ab2 (testing) made a change |/ * f30ab add feature #32 - ability to add new formats to the * 34ac2 fixed bug #1328 - stack overflow under certain conditions * 98ca9 initial commit of my project Dahil ang isang branch sa Git ay talagang isang simpleng file na naglalaman ng 40 na karakter na SHA-1 na checksum ng commit na itinuturo nito, ang mga branch ay mura lamang gawin at sirain. Ang paggawa ng isang bagong branch ay kasing dali at kasing simple katulad ng pagsulat ng 41 bytes sa isang file (40 na mga karakter at isang newline). Ito ay nasa matingkad na kaibahan sa paraan ng karamihan sa mas matandang mga kasangkapan ng VCS na branch, na nagsasangkot ng pagkopya sa lahat ng mga file ng proyekto sa isang pangalawang direktoryo. Ito ay maaaring magtagal ng ilang segundo o kahit mga minuto, depende sa laki ng proyekto, samantalang sa Git ang proseso ay palaging madalian. Gayundin, dahil nagtatala tayo sa mga magulang kapag tayo ay magku-commit, ang paghahanap ng isang nararapat na merge base para sa pag-merge ay awtomatikong nagagawa para sa atin at kadalasang sobrang madaling gawin. Ang mga tampok na ito ay nakakatulong maghikayat sa mga developer upang madalas gumawa at gumamit ng mga branch. Tingnan natin kung bakit dapat mong gawin ito. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/fr/v2/D%c3%a9marrage-rapide-La-ligne-de-commande | Git - La ligne de commande About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Démarrage rapide 1.1 À propos de la gestion de version 1.2 Une rapide histoire de Git 1.3 Rudiments de Git 1.4 La ligne de commande 1.5 Installation de Git 1.6 Paramétrage à la première utilisation de Git 1.7 Obtenir de l’aide 1.8 Résumé 2. Les bases de Git 2.1 Démarrer un dépôt Git 2.2 Enregistrer des modifications dans le dépôt 2.3 Visualiser l’historique des validations 2.4 Annuler des actions 2.5 Travailler avec des dépôts distants 2.6 Étiquetage 2.7 Les alias Git 2.8 Résumé 3. Les branches avec Git 3.1 Les branches en bref 3.2 Branches et fusions : les bases 3.3 Gestion des branches 3.4 Travailler avec les branches 3.5 Branches de suivi à distance 3.6 Rebaser (Rebasing) 3.7 Résumé 4. Git sur le serveur 4.1 Protocoles 4.2 Installation de Git sur un serveur 4.3 Génération des clés publiques SSH 4.4 Mise en place du serveur 4.5 Démon (Daemon) Git 4.6 HTTP intelligent 4.7 GitWeb 4.8 GitLab 4.9 Git hébergé 4.10 Résumé 5. Git distribué 5.1 Développements distribués 5.2 Contribution à un projet 5.3 Maintenance d’un projet 5.4 Résumé 6. GitHub 6.1 Configuration et paramétrage d’un compte 6.2 Contribution à un projet 6.3 Maintenance d’un projet 6.4 Gestion d’un regroupement 6.5 Écriture de scripts pour GitHub 6.6 Résumé 7. Utilitaires Git 7.1 Sélection des versions 7.2 Indexation interactive 7.3 Remisage et nettoyage 7.4 Signer votre travail 7.5 Recherche 7.6 Réécrire l’historique 7.7 Reset démystifié 7.8 Fusion avancée 7.9 Rerere 7.10 Déboguer avec Git 7.11 Sous-modules 7.12 Empaquetage (bundling) 7.13 Replace 7.14 Stockage des identifiants 7.15 Résumé 8. Personnalisation de Git 8.1 Configuration de Git 8.2 Attributs Git 8.3 Crochets Git 8.4 Exemple de politique gérée par Git 8.5 Résumé 9. Git et les autres systèmes 9.1 Git comme client 9.2 Migration vers Git 9.3 Résumé 10. Les tripes de Git 10.1 Plomberie et porcelaine 10.2 Les objets de Git 10.3 Références Git 10.4 Fichiers groupés 10.5 La refspec 10.6 Les protocoles de transfert 10.7 Maintenance et récupération de données 10.8 Les variables d’environnement 10.9 Résumé A1. Annexe A: Git dans d’autres environnements A1.1 Interfaces graphiques A1.2 Git dans Visual Studio A1.3 Git dans Visual Studio Code A1.4 Git dans IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git dans Sublime Text A1.6 Git dans Bash A1.7 Git dans Zsh A1.8 Git dans PowerShell A1.9 Résumé A2. Annexe B: Embarquer Git dans vos applications A2.1 Git en ligne de commande A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Commandes Git A3.1 Installation et configuration A3.2 Obtention et création des projets A3.3 Capture d’instantané basique A3.4 Création de branches et fusion A3.5 Partage et mise à jour de projets A3.6 Inspection et comparaison A3.7 Débogage A3.8 Patchs A3.9 Courriel A3.10 Systèmes externes A3.11 Administration A3.12 Commandes de plomberie 2nd Edition 1.4 Démarrage rapide - La ligne de commande La ligne de commande Il existe de nombreuses manières différentes d’utiliser Git. Il y a les outils originaux en ligne de commande et il y a de nombreuses interfaces graphiques avec des capacités variables. Dans ce livre, nous utiliserons Git en ligne de commande. Tout d’abord, la ligne de commande est la seule interface qui permet de lancer toutes les commandes Git - la plupart des interfaces graphiques simplifient l’utilisation en ne couvrant qu’un sous-ensemble des fonctionnalités de Git. Si vous savez comment utiliser la version en ligne de commande, vous serez à même de comprendre comment fonctionne la version graphique, tandis que l’inverse n’est pas nécessairement vrai. De plus, le choix d’un outil graphique est sujet à des goûts personnels, mais tous les utilisateurs auront les commandes en lignes installées et utilisables. Nous considérons que vous savez ouvrir un Terminal sous macOS ou une invite de commandes ou PowerShell sous Windows. Si ce n’est pas le cas, il va falloir tout d’abord vous renseigner sur ces applications pour pouvoir comprendre la suite des exemples et descriptions du livre. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/cs/v2/Distribuovan%c3%bd-Git-Distribuovan%c3%a9-pracovn%c3%ad-postupy | Git - Distribuované pracovní postupy About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Úvod 1.1 Správa verzí 1.2 Stručná historie systému Git 1.3 Základy systému Git 1.4 Příkazový řádek 1.5 Instalace systému Git 1.6 První nastavení systému Git 1.7 Získání nápovědy 1.8 Shrnutí 2. Základy práce se systémem Git 2.1 Získání repozitáře Git 2.2 Nahrávání změn do repozitáře 2.3 Zobrazení historie revizí 2.4 Návrat do předchozího stavu 2.5 Práce se vzdálenými repozitáři 2.6 Používání značek 2.7 Aliasy v Gitu 2.8 Shrnutí 3. Větve v systému Git 3.1 Větve v kostce 3.2 Základy větvení a slučování 3.3 Správa větví 3.4 Postupy při práci s větvemi 3.5 Vzdálené větve 3.6 Přeskládání 3.7 Shrnutí 4. Git na serveru 4.1 Protokoly 4.2 Zprovoznění Gitu na serveru 4.3 Generování veřejného klíče SSH 4.4 Nastavení serveru 4.5 Démon Git 4.6 Chytrý HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti hostování u třetí strany 4.10 Shrnutí 5. Distribuovaný Git 5.1 Distribuované pracovní postupy 5.2 Přispívání do projektu 5.3 Správa projektu 5.4 Shrnutí 6. GitHub 6.1 Zřízení účtu a úprava konfigurace 6.2 Přispívání do projektu 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Shrnutí 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Ladění v systému Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Shrnutí 8. Customizing Git 8.1 Git Configuration 8.2 Atributy Git 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Shrnutí 9. Git a ostatní systémy 9.1 Git as a Client 9.2 Migrating to Git 9.3 Shrnutí 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Balíčkové soubory 10.5 The Refspec 10.6 Přenosové protokoly 10.7 Správa a obnova dat 10.8 Environment Variables 10.9 Shrnutí A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Shrnutí A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.1 Distribuovaný Git - Distribuované pracovní postupy Máte vytvořen vzdálený gitový repozitář, který je nastaven tak, aby mohli všichni vývojáři sdílet svůj zdrojový kód, a znáte základní příkazy Gitu pro práci v lokálním prostředí. Nastal čas, abychom se podívali na využití některých distribuovaných pracovních postupů, které vám Git nabízí. V této kapitole uvidíte, jak se v distribuovaném prostředí s Gitem pracuje v roli přispěvatele a v roli integrátora. Jinými slovy, naučíte se, jak lze do projektu úspěšně přidat vlastní kód, jak to co nejvíc usnadnit sobě i správci projektu a také to, jak se dá úspěšně udržovat projekt, do kterého přispívá velký počet vývojářů. Distribuované pracovní postupy Na rozdíl od centralizovaných systémů pro správu verzí, distribuovaný charakter systému Git umožňuje vývojářům mnohem větší pružnost ve způsobech spolupráce na projektech. V centralizovaných systémech představuje každý vývojář samostatný uzel, pracující s centrálním úložištěm více či méně na stejné úrovni. Naproti tomu v Gitu je každý vývojář potenciálním uzlem i úložištěm. To znamená, že každý vývojář může přispívat kódem do ostatních repozitářů a současně může spravovat veřejný repozitář, z kterého mohou ostatní vycházet při své práci a do kterého mohou přispívat. Tím se pro váš projekt a váš tým otvírá široké spektrum pracovních postupů. Podíváme se na pár obvyklých přístupů, které dané pružnosti využívají. Uvedeme si jejich přednosti i eventuální slabiny. Můžete vybrat jeden z nich, nebo je můžete pro dosažení požadovaných vlastností navzájem kombinovat. Centralizovaný pracovní postup V centralizovaných systémech je většinou možný pouze jediný model, tzv. centralizovaný pracovní postup. Jedno centrální úložiště (hub) nebo repozitář přijímá zdrojový kód a každý podle něj synchronizuje svou práci. Několik vývojářů představuje uzly — konzumenty centrálního úložiště --, které se synchronizují se podle tohoto místa. Figure 54. Centralizovaný pracovní postup. To znamená, že pokud dva vývojáři klonují z centrálního úložiště a oba provedou změny, pak jen první z nich může bez problémů odeslat (push) své změny zpět. Druhý vývojář musí před odesláním svých změn začlenit (merge) práci prvního vývojáře do své, aby nepřepsal jeho změny. Tento koncept platí jak pro Git, tak pro Subversion (nebo pro jiný systém pro správu verzí). Bez problémů funguje i v Gitu. Pokud už jste ve své firmě nebo v týmu na centralizovaný pracovní postup zvyklí, můžete v něm snadno pokračovat i při použití Gitu. Jednoduše vytvořte repozitář a přidělte všem ze svého týmu oprávnění k odesílání dat. Git uživatelům neumožní, aby se navzájem přepisovali. Dejme tomu, že John i Jessica začnou pracovat ve stejném čase. John dokončí své úpravy a odešle je na server. Poté se Jessica pokusí odeslat své změny, ale server je odmítne. Řekne jí, že se pokouší odeslat změny (push), které nemají charakter „rychle vpřed“, a že to nebude moci udělat, dokud neprovede vyzvednutí a sloučení (fetch a merge). Tento pracovní postup je pro mnoho lidí zajímavý, protože je to model, který jsou zvyklí používat a jsou s ním spokojeni. A není také omezen jen na malé týmy. Model větvení Gitu umožňuje, aby na jednom projektu pracovaly stovky vývojářů a využívali při tom souběžně desítky větví. Pracovní postup s integračním manažerem Protože Git umožňuje práci s více vzdálenými repozitáři, lze využít pracovní postup, kdy má každý vývojář přiděleno právo zápisu do svého vlastního veřejného repozitáře a oprávnění pro čtení k repozitářům všech ostatních. Tento scénář často zahrnuje jeden hlavní repozitář, který reprezentuje „oficiální“ projekt. Chcete-li do tohoto projektu přispívat, vytvoříte vlastní veřejný klon projektu a odešlete do něj změny, které jste provedli. Poté můžete správci hlavního projektu odeslat žádost, aby do projektu vaše změny vtáhl (pull). Správce si pak může váš repozitář přidat jako vzdálený, lokálně otestovat vaše změny, začlenit (merge) je do své větve a odeslat zpět (push) do svého repozitáře. Proces funguje následovně (viz obrázek Pracovní postup s integračním manažerem. ): Správce projektu odešle data do svého veřejného repozitáře. Přispěvatel naklonuje tento repozitář a provede změny. Přispěvatel odešle změny do své vlastní veřejné kopie. Přispěvatel pošle správci email, ve kterém jej požádá o vtažení změn (pull). Správce si přidá přispěvatelův repozitář jako vzdálený a provede lokální sloučení (merge). Správce odešle začleněné změny do hlavního repozitáře. Figure 55. Pracovní postup s integračním manažerem. Tento pracovní postup je velmi běžný, pokud se pracuje centralizačními nástroji [ 15 ] jako je GitHub nebo GitLab. Projekt se zde dá snadno odštěpit a změny se pak odesílají do vlastní, odštěpené části, kde se na ně může každý podívat. Jednou z hlavních výhod tohoto přístupu je, že můžete pracovat bez přerušení a správce hlavního repozitáře může vaše změny do projektu vtáhnout (pull in) až to uzná za vhodné. Přispěvatelé nemusí čekat, až budou jejich změny začleněny do projektu — všichni zúčastnění mohou pracovat svým vlastním tempem. Pracovní postup s diktátorem a poručíky Jedná se o variantu pracovního postupu s více repozitáři. Většinou se používá u obřích projektů se stovkami spolupracovníků. Možná nejznámějším příkladem je vývoj jádra Linuxu. Za konkrétní části repozitáře odpovídají různí integrační manažeři. Říká se jim poručíci (lieutenants). Všichni poručíci mají jednoho integračního manažera, kterému se říká benevolentní diktátor. Repozitář benevolentního diktátora slouží jako referenční repozitář, z nějž všichni spolupracovníci musí stahovat data. Proces funguje nějak takto (viz obrázek Pracovní postup s benevolentním diktátorem. ): Stálí vývojáři pracují na svých tématických větvích a přeskládávají (rebase) svou práci na vrchol větve master . Větev master je předmětem zájmu diktátora. Poručíci začleňují (merge) tématické větve vývojářů do svých větví master . Diktátor začleňuje větve master poručíků do své větve master . Diktátor odesílá svou větev master do referenčního repozitáře, aby ji ostatní vývojáři mohli použít jako základ pro přeskládání (rebase). Figure 56. Pracovní postup s benevolentním diktátorem. Tento typ pracovního postupu sice není běžný, ale může být užitečný u velmi velkých projektů nebo v přísně hierarchických prostředích. Umožňuje vedoucímu projektu (diktátorovi) velkou část práce delegovat a poté na více místech sesbírat velké podmnožiny kódu, které pak dává dohromady. Shrnutí pracovních postupů Toto jsou tedy některé z běžně používaných pracovních postupů, které umožňují distribuované systémy, jako je Git. Ale sami vidíte, že lze uplatnit řadu variací, aby to vyhovovalo vašim konkrétně používaným pracovním postupům. Teď už si (snad) dokážete vybrat, jaká kombinace by vám mohla vyhovovat. Ukážeme si pár konkrétnějších příkladů toho, jak splnit hlavní role, které různé pracovní postupy vytvářejí. V následující podkapitole se dozvíte o několika obvyklých způsobech přispívání do projektu. 15 . hub-based tools prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/Pag-branch-ng-Git-Pamamahala-ng-Branch | Git - Pamamahala ng Branch About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 3.3 Pag-branch ng Git - Pamamahala ng Branch Pamamahala ng Branch Ngayong nakagawa, naka-merge, at nakabura ka na ng ilang mga branch, tingnan natin ang ilang mga kasangkapan sa pamamahala ng branch na magiging kapaki-pakinabang kapag nagsimula kang gumamit ng mga branch sa lahat ng pagkakataon. Ang git branch na utos ay gumagawa ng higit pa sa paggawa at pagbura ng mga branch lamang. Kung napatakbo mo ito nang walang mga argumento, makakakuha ka ng isang simpleng paglilista ng iyong kasalukuyang mga branch: $ git branch iss53 * master testing Pansinin ang * na karakter na naka-prefix sa master na branch: ito ay nagpapahiwatig sa branch kung saan ikaw ay kasalukuyang naka-check out (i.e., ang tinuturo ng branch na HEAD ). Ang ibig sabihin nito na kung ikaw ay magku-commit sa puntong ito, ang master na branch ay malilipat nang pasulong kasama ang iyong bagong trabaho. Upang matingnan ang huling commit sa bawat branch, maaari mong patakbuhin ang git branch -v : $ git branch -v iss53 93b412c fix javascript issue * master 7a98805 Merge branch 'iss53' testing 782fd34 add scott to the author list in the readmes Ang kapaki-pakinabang na --merged at --no-merged na mga opsyon ay maaaring magsalin nitong listahan ng mga branch na na-merge mo o hindi pa na-merge sa branch kung saan kasalukuyang nandoon ka. Upang makita kung anong mga branch ang na merge na sa branch kung saan nandoon ka, maaari mong patakbuhin ang git branch --merged : $ git branch --merged iss53 * master Dahil na merge mo na ang iss53 kamakailan lamang, makikita mo ito sa iyong listahan. Ang mga branch sa listahang ito na walang * sa harap nila ay kadalasang maayos lang burahin gamit ang git branch -d ; naipasama mo na ang kanilang trabaho sa iba pang branch, kaya hindi ka mawawalan ng anuman. Upang matingnan ang lahat ng mga branch na naglalaman ng trabaho mo na hindi pa na merge, maaari mong patakbuhin ang git branch --no-merged : $ git branch --no-merged testing Ipinapakita nito ang iyong ibang branch. Dahil naglalaman ito ng trabaho na hindi pa na merge, ang pagsubok sa pagbura nito gamit ang git branch -d ay mabibigo. $ git branch -d testing error: The branch 'testing' is not fully merged. If you are sure you want to delete it, run 'git branch -D testing'. Kung gusto mo talagang burahin ang branch at mawala ang trabahong iyon, maaari mong pilitin ito gamit ang -D , habang tinuturo ito sa kapaki-pakinabang na mensahe. Tip Ang mga opsyon na inilalarawan sa itaas, --merged at --no-merged ay, kung hindi binigyan ng isang commit o pangalan ng branch bilang isang argumento, ipinapakita sa iyo kung ano, ayon sa pagkakabanggit, ang naka-merge o hindi naka-merge sa iyong current na branch. Maaari kang palaging magbigay ng isang karagdagang argumento upang magtanong tungkol sa estado ng merge ayon sa ilang ibang branch kahit hindi unang susuriin ang ibang branch na iyon, katulad ng, ano ang hindi na-merge sa master na branch? $ git checkout testing $ git branch --no-merged master topicA featureB prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/Pag-branch-ng-Git-Batayan-ng-Pag-branch-at-Pag-merge | Git - Batayan ng Pag-branch at Pag-merge About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 3.2 Pag-branch ng Git - Batayan ng Pag-branch at Pag-merge Batayan ng Pag-branch at Pag-merge Dumaan tayo patungo sa isang simpleng halimbawa ng pag-branch at pag-merge sa isang daloy ng trabaho na maaaring mong gamitin sa tunay na mundo. Susundin mo ang mga hakbang na ito: Magsagawa ng ilang trabaho sa isang website. Gumawa ng isang branch para sa isang panibagong kwento na iyong tinatrabaho. Magsagawa ng ilang trabaho sa branch na iyon. Sa puntong ito, makakatanggap ka ng isang tawag na ang ibang isyu ay kritikal at kinakailangan mo ng isang hotfix. Gagawin mo ang sumusunod: Lumipat sa iyong produksyon na branch. Gumawa ng isang branch upang idagdag ang hotfix. Pagkatapos itong i-test, i-merge ang hotfix na branch, at i-push sa produksyon. Lumipat pabalik sa iyong orihinal na kwento at magpatuloy sa pagtrabaho. Batayan sa Pag-branch Una, sabihin nating ikaw ay nagtatrabaho sa iyong proyekto at mayroon nang dalawang commit sa master na branch. Figure 18. Isang simpleng kasaysayan ng commit Pinili mong magtrabaho sa isyu #53 sa anumang issue-tracking na sistema na ginagamit ng iyong kumpanya. Upang makagawa ng isang panibagong branch at lumipat dito sa parehong oras, maaari mong patakbuhin ang git checkout na utos na may -b na switch: $ git checkout -b iss53 Switched to a new branch "iss53" Ito ay takigrapya para sa: $ git branch iss53 $ git checkout iss53 Figure 19. Paggawa ng isang panibagong branch na pointer Ikaw ay nagtatrabaho sa iyong website at gumawa ng ilang mga commit. Ang paggawa nito ay naglilipat sa iss53 na branch nang pasulong, dahil na-check out mo ito (iyon ay, ang iyong HEAD ay nakaturo nito): $ vim index.html $ git commit -a -m 'added a new footer [issue 53]' Figure 20. Ang iss53 na branch ay nailipat nang pasulong kasama ng iyong trabaho Ngayon makukuha mo ang tawag na may isang isyu sa website, at kailangan mo itong ayusin kaagad. Gamit ang Git, hindi mo na kailangang i-deploy ang iyong pag-ayos kasama ang iss53 na mga pagbabago na iyong ginawa, at hindi mo na kailangang maglagay ng maraming pagsisikap sa pagpapabalik ng mga pagbabagong iyon bago ka maaaring magtrabaho sa paglalapat ng iyong pag-ayos sa anumang nasa produksyon. Ang kailangan mo lang gawin ay lumipat pabalik sa iyong master na branch. Subalit, bago mo gawin iyon, tandaan na kung ang iyong tinatrabaho na direktoryo o staging na lawak ay mayroong hindi naka-commit na mga pagbabago na salungatan sa branch na iyong na-check out, Ang Git ay hindi ka hahayaang maglipat ng mga branch. Pinakamainam na magkaroon ng isang malinis na estado ng tinatrabaho kapag ikaw ay maglilipat ng mga branch. May mga paraan upang makaligtaan ito (katulad, ang pag-stash at pag-amend ng commit) na masasakop natin mamaya, sa Pag-stash at Paglilinis . Sa ngayon, ipalagay natin na na-commit mo na lahat ang iyong mga pagbabago, kaya maaari ka nang lumipat pabalik sa iyong master na branch: $ git checkout master Switched to branch 'master' Sa puntong ito, ang iyong tinatrabaho na direktoryo ng iyong proyekto ay eksakto kung paano ito bago mo sinimulang magtrabaho sa isyu #53, at maaari mo nang pag-isiping mabuti ang iyong hotfix. Ito ay isang importanteng punto na dapat tandaan: kapag ikaw ay maglilipat ng mga branch, ang Git ay ire-reset ang iyong tinatrabaho na direktoryo upang magmukha itong kagaya sa huling pagkakataon na ikaw ay nag-commit sa branch na iyon. Ito ay awtomatikong nagdaragdag, nagtatanggal, at nagbabago ng mga files upang siguraduhing ang iyong tinatrabaho na kopya ay kagaya ng kung ano ang mukha ng branch sa iyong huling commit. Susunod, mayroon kang isang hotfix na gagawin. Gumawa tayo ng isang hotfix na branch kung saan tatrabahuin hanggang sa ito ay matapos: $ git checkout -b hotfix Switched to a new branch 'hotfix' $ vim index.html $ git commit -a -m 'fixed the broken email address' [hotfix 1fb7853] fixed the broken email address 1 file changed, 2 insertions(+) Figure 21. Ang Hotfix na branch ay nakabatay sa master Maaari mong patakbuhin ang iyong mga test, siguraduhing ang hotfix ay kung ano ang iyong gusto, at sa wakas i-merge ang hotfix na branch pabalik sa iyong master na branch upang i-deploy sa produksyon. Gawin mo ito gamit ang git merge na utos: $ git checkout master $ git merge hotfix Updating f42c576..3a0874c Fast-forward index.html | 2 ++ 1 file changed, 2 insertions(+) Mapapansin mo ang pariral na “fast-forward” sa merge na iyon. Dahil ang commit na C4 na itinuro ng hotfix na branch na iyong na-merge in ay direktang nauuna sa C2 na commit kung saan nandoon ka, ang Git ay simpleng ililipat ang pointer nang pasulong. Upang ipahayag iyon sa ibang paraan, kapag sinubukan mong i-merge ang isang commit sa isang pang commit na maaaring maabot sa pamamagitan ng pagsunod sa kasaysayan ng unang commit, ang Git ay pinapasimple ang mga bagay sa pamamagitan ng paglipat ng pointer nang pasulong dahil walang magkakaibang trabaho na sama-samang i-merge — ito ay tinatawag na isang “fast-forward.” Ang iyong pagbabago ay nasa snapshot na ngayon ng commit na itinuro ng master na branch, at maaari mong i-deploy ang fix. Figure 22. Ang master ay na-fast-forward sa hotfix Pagkatapos ma-deploy ang iyong sobrang importanteng pag-ayos, handa ka nang lumipat pabalik sa trabahong ginagawa mo dati bago ka naabala. Ngunit, una ay burahin mo ang hotfix na branch, dahil hindi mo na kailangan ito — ang master na branch ay nakaturo sa parehong lugar. Maaari mong burahin ito gamit ang -d na opsyon sa git branch : $ git branch -d hotfix Deleted branch hotfix (3a0874c). Ngayon maaari ka nang lumipat pabalik sa iyong work-in-progress na branch sa isyu #53 at magpatuloy sa pagtrabaho nito. $ git checkout iss53 Switched to branch "iss53" $ vim index.html $ git commit -a -m 'finished the new footer [issue 53]' [iss53 ad82d7a] finished the new footer [issue 53] 1 file changed, 1 insertion(+) Figure 23. Ang trabaho ay magpapatuloy sa iss53 Mahalagang tandaan dito na ang trabaho na iyong ginawa sa iyong hotfix na branch ay hindi nilalaman sa mga file sa iyong iss53 na branch. Kung kailangan mong i-pull ito, maaari mong i-merge ang iyong master na branch sa iyong iss53 na branch sa pagpapatakbo ng git merge master , o maaari kang maghintay na pagsamahin ang mga pagbabagong iyon hanggang ikaw ay makapagpasya na i-pull ang iss53 na branch pabalik sa master mamaya. Batayan ng Pag-merge Mangyaring ikaw ay nakapagpasya na ang iyong isyu #53 na trabaho ay natapos at handa nang i-merge sa iyong master na branch. Upang magawa iyon, ime-merge mo ang iyong iss53 na branch sa master , masyadong katulad ng pag-merge mo sa iyong hotfix na branch kamakailan lamang. Ang kailangan mo lamang gawin ay i-check out ang branch na gusto mong i-merge at pagkatapos ay patakbuhin ang git merge na utos: $ git checkout master Switched to branch 'master' $ git merge iss53 Merge made by the 'recursive' strategy. index.html | 1 + 1 file changed, 1 insertion(+) Ito ay mukhang medyo iba sa hotfix na merge na ginawa mo kamakailan lamang. Sa kasong ito, ang kasaysayan ng iyong pag-develop ay humiwalay mula sa ilang mas matandang punto. Dahil ang commit sa branch kung saan nandoon ka ay hindi isang direktang ninuno ng branch na iyong mini-merge, ang Git ay dapat gumawa ng ilang trabaho. Sa kasong ito, ang Git ay gagawa ng isang simpleng three-way na merge, gamit ang dalawang snapshot na itinuro ng mga dulo ng branch at ang karaniwang ninuno ng dalawa. Figure 24. Tatlong mga snapshot na ginamit sa isang tipikal na merge Sa halip na ililipat lamang ang pointer ng branch nang pasulong, ang Git ay gagawa ng isang panibagong snapshot na nagreresulta mula sa three-way na merge na ito at awtomatikong bubuo ng isang panibagong commit na nakaturo nito. Ito ay tinutukoy bilang isang merge na commit, at ang espesyal nito ay mayroon itong higit pa sa isang magulang. Figure 25. Isang merge na commmit Mahalagang pagtuunan ng pansin na tinutukoy ng Git ang pinakamabuti na karaniwang ninuno para gamitin sa merge base nito; ito ay iba sa mas matandang mga kasangkapan katulad ng CVS o Subversion (bago ang bersyon 1.5), kung saan ang developer na gumagawa ng merge ay kailangang malaman ang pinakamainam na merge base para sa sarili nila. Ginagawa nitong mas madali ang pag-merge sa Git kaysa sa mga ibang sistemang ito. Ngayong ang iyong trabaho ay naka-merge na, wala ka nang higit pang kailangan para sa iss53 na branch. Maaari mo nang isara ang tiket sa iyong ticket-tracking na sistema, at burahin ang branch: $ git branch -d iss53 Mga Pangunahing Salungatan sa Pag-Merge Paminsan-minsan, ang prosesong ito ay hindi dadaloy ng maaayos. Kung binago mo ang parehong parte ng parehong file na nagkakaiba sa dalawang branch na iyong ime-merge pareho, ang Git ay hindi makakayang i-merge ang mga ito nang malinis. Kung ang iyong pag-ayos para sa isyu #53 ay nagbago ng parehong parte ng isang file bilang hotfix na branch, magkakaroon ka ng isang merge na salungatan na magmumukha katulad nito: $ git merge iss53 Auto-merging index.html CONFLICT (content): Merge conflict in index.html Automatic merge failed; fix conflicts and then commit the result. Ang Git ay hindi awtomatikong gumawa ng isang bagong merge na commmit. Ito ay sandaling tinigil ang proseso habang ikaw ay naglulutas ng mga salungatan. Kung gusto mong tingnan kung ano ang mga file an naka-unmerge sa anumang punto pagkatapos ng isang salungatan sa pag-merge, maaari mong patakbuhin ang git status : $ git status On branch master You have unmerged paths. (fix conflicts and run "git commit") Unmerged paths: (use "git add <file>..." to mark resolution) both modified: index.html no changes added to commit (use "git add" and/or "git commit -a") Anuman ang mayroong mga salungatan sa pag-merge at hindi nalutas ay nakalista bilang naka-unmerge. Ang Git ay nagdaragdag ng pamantayan na mga marker para sa conflict-resolution sa mga file na mayroong mga salungatan, upang maaari mong manu-manong buksan ang mga ito at lutasin ang mga salungatang iyon. Ang iyong file ay naglalamang ng isang bahagi na nagmumukha katulad nito: <<<<<<< HEAD:index.html <div id="footer">contact : email.support@github.com</div> ======= <div id="footer"> please contact us at support@github.com </div> >>>>>>> iss53:index.html Ang kahulugan nito ay ang bersyon sa HEAD (iyong master na branch, dahil iyon ang na-check out mo kapag nagpatakbo ka ng iyong merge na utos) ay ang tuktok na parte ng blokeng iyon (anuman na nasa itaas ng ======= ), habang ang bersyon sa iyong iss53 na branch ay nagmumukhang katulad sa lahat sa ibaba na parte. Upang malutas ang salungatan, kailangan mong alinmang pumili ng isang gilid o ang iba o sariling i-merge ang mga nilalaman. Halimbawa, ikaw ay maaaring maglutas ng salungatang ito sa pamamagitan ng pagpapalit ng buong bloke gamit nito: <div id="footer"> please contact us at email.support@github.com </div> Ang resolusyong ito ay may maliliit na seksyon, at ang <<<<<<< , ======= , at >>>>>>> na mga linya ay ganap na natanggal. Pagkatapos mong malutas ang bawat seksyon na mga ito sa bawat salungatang file, patakbuhin ang git add sa bawat file upang markahan bilang nalutas na. Ang pag-stage ng file ay nagmamarka nito bilang nalutas na sa Git. Kung gusto mong gumamit ng isang grapikal na kasangkapan para sa paglutas ng mga isyu, maaari mong patakbuhin ang git mergetool , na nagpapagana ng isang angkop na biswal na merge na kasangkapan at ilalakad ka sa mga salungatan: $ git mergetool This message is displayed because 'merge.tool' is not configured. See 'git mergetool --tool-help' or 'git help config' for more details. 'git mergetool' will now attempt to use one of the following tools: opendiff kdiff3 tkdiff xxdiff meld tortoisemerge gvimdiff diffuse diffmerge ecmerge p4merge araxis bc3 codecompare vimdiff emerge Merging: index.html Normal merge conflict for 'index.html': {local}: modified file {remote}: modified file Hit return to start merge resolution tool (opendiff): Kung gusto mong gumamit ng isang merge na kasangkapan maliban sa default (ang Git ay pumili ng opendiff sa kasong ito dahil ang utos ay napatakbo sa isang Mac), maaari mong tingnan lahat ang mga suportadong mga kasangkapan na nakalista sa tuktok pagkatapos ng “isa sa mga sumusunod na mga kasangkapan.” I-type lamang ang pangalan ng kasangkapan na mas gugustuhin mong gamitin. Kung kailangan mo ng mas advance na mga kasangkapan para sa paglulutas ng nakakalitong mga salungatan sa pag-merge, nasasakop pa namin ang higit pa sa pag-merge sa Advanced na Pag-merge . Pagkatapos mong lumabas sa merge na kasangkapan, ang Git ay tatanungin ka kung matagumpay ba ang pag-merge. Kung sasabihan mo ang iskrip na matagumpay, ito ay isi-stage ang file upang markahan ito bilang nalutas na para sa iyo. Maaari mong patakbuhin ang git status ulit para mapatunayan na ang lahat ng mga salungatan ay nalutas na: $ git status On branch master All conflicts fixed but you are still merging. (use "git commit" to conclude merge) Changes to be committed: modified: index.html Kung masaya ka na sa iyon, at mapatunayan mo na ang lahat ng may mga salungatan ay na-stage na, maaari mong i-type ang git commmit upang tapusin ang merge na commit. Ang mensahe ng commit na default ay magmumukha katulad nito: Merge branch 'iss53' Conflicts: index.html # # It looks like you may be committing a merge. # If this is not correct, please remove the file # .git/MERGE_HEAD # and try again. # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # All conflicts fixed but you are still merging. # # Changes to be committed: # modified: index.html # Kung sa tingin mong ito ay makakatulong sa iba na titingin sa merge na ito sa hinaharap, maaari mong baguhin ang mensahe ng commit na ito gamit ang mga detalye tungkol sa kung papaano mo nalutas ang merge at paliwanag kung bakit mo ginawa ang mga pagbabagong ginawa mo kung hindi halata ang mga ito. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_419 | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상�� | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=en_GB | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Pla | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=fil | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 �� | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=hy | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 � | 2026-01-13T09:29:23 |
https://git-scm.com/book/zh/v2/Git-%e5%88%86%e6%94%af-%e5%88%86%e6%94%af%e7%ae%80%e4%bb%8b | Git - 分支简介 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 起步 1.1 关于版本控制 1.2 Git 简史 1.3 Git 是什么？ 1.4 命令行 1.5 安装 Git 1.6 初次运行 Git 前的配置 1.7 获取帮助 1.8 总结 2. Git 基础 2.1 获取 Git 仓库 2.2 记录每次更新到仓库 2.3 查看提交历史 2.4 撤消操作 2.5 远程仓库的使用 2.6 打标签 2.7 Git 别名 2.8 总结 3. Git 分支 3.1 分支简介 3.2 分支的新建与合并 3.3 分支管理 3.4 分支开发工作流 3.5 远程分支 3.6 变基 3.7 总结 4. 服务器上的 Git 4.1 协议 4.2 在服务器上搭建 Git 4.3 生成 SSH 公钥 4.4 配置服务器 4.5 Git 守护进程 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第三方托管的选择 4.10 总结 5. 分布式 Git 5.1 分布式工作流程 5.2 向一个项目贡献 5.3 维护项目 5.4 总结 6. GitHub 6.1 账户的创建和配置 6.2 对项目做出贡献 6.3 维护项目 6.4 管理组织 6.5 脚本 GitHub 6.6 总结 7. Git 工具 7.1 选择修订版本 7.2 交互式暂存 7.3 贮藏与清理 7.4 签署工作 7.5 搜索 7.6 重写历史 7.7 重置揭密 7.8 高级合并 7.9 Rerere 7.10 使用 Git 调试 7.11 子模块 7.12 打包 7.13 替换 7.14 凭证存储 7.15 总结 8. 自定义 Git 8.1 配置 Git 8.2 Git 属性 8.3 Git 钩子 8.4 使用强制策略的一个例子 8.5 总结 9. Git 与其他系统 9.1 作为客户端的 Git 9.2 迁移到 Git 9.3 总结 10. Git 内部原理 10.1 底层命令与上层命令 10.2 Git 对象 10.3 Git 引用 10.4 包文件 10.5 引用规范 10.6 传输协议 10.7 维护与数据恢复 10.8 环境变量 10.9 总结 A1. 附录 A: 在其它环境中使用 Git A1.1 图形界面 A1.2 Visual Studio 中的 Git A1.3 Visual Studio Code 中的 Git A1.4 IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 中的 Git A1.5 Sublime Text 中的 Git A1.6 Bash 中的 Git A1.7 Zsh 中的 Git A1.8 PowerShell 中的 Git A1.9 总结 A2. 附录 B: 在你的应用中嵌入 Git A2.1 命令行 Git 方式 A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. 附录 C: Git 命令 A3.1 设置与配置 A3.2 获取与创建项目 A3.3 快照基础 A3.4 分支与合并 A3.5 项目分享与更新 A3.6 检查与比较 A3.7 调试 A3.8 补丁 A3.9 邮件 A3.10 外部系统 A3.11 管理 A3.12 底层命令 2nd Edition 3.1 Git 分支 - 分支简介 几乎所有的版本控制系统都以某种形式支持分支。 使用分支意味着你可以把你的工作从开发主线上分离开来，以免影响开发主线。 在很多版本控制系统中，这是一个略微低效的过程——常常需要完全创建一个源代码目录的副本。对于大项目来说，这样的过程会耗费很多时间。 有人把 Git 的分支模型称为它的“必杀技特性”，也正因为这一特性，使得 Git 从众多版本控制系统中脱颖而出。 为何 Git 的分支模型如此出众呢？ Git 处理分支的方式可谓是难以置信的轻量，创建新分支这一操作几乎能在瞬间完成，并且在不同分支之间的切换操作也是一样便捷。 与许多其它版本控制系统不同，Git 鼓励在工作流程中频繁地使用分支与合并，哪怕一天之内进行许多次。 理解和精通这一特性，你便会意识到 Git 是如此的强大而又独特，并且从此真正改变你的开发方式。 分支简介 为了真正理解 Git 处理分支的方式，我们需要回顾一下 Git 是如何保存数据的。 或许你还记得 起步 的内容， Git 保存的不是文件的变化或者差异，而是一系列不同时刻的 快照 。 在进行提交操作时，Git 会保存一个提交对象（commit object）。 知道了 Git 保存数据的方式，我们可以很自然的想到——该提交对象会包含一个指向暂存内容快照的指针。 但不仅仅是这样，该提交对象还包含了作者的姓名和邮箱、提交时输入的信息以及指向它的父对象的指针。 首次提交产生的提交对象没有父对象，普通提交操作产生的提交对象有一个父对象， 而由多个分支合并产生的提交对象有多个父对象， 为了更加形象地说明，我们假设现在有一个工作目录，里面包含了三个将要被暂存和提交的文件。 暂存操作会为每一个文件计算校验和（使用我们在 起步 中提到的 SHA-1 哈希算法），然后会把当前版本的文件快照保存到 Git 仓库中 （Git 使用 blob 对象来保存它们），最终将校验和加入到暂存区域等待提交： $ git add README test.rb LICENSE $ git commit -m 'The initial commit of my project' 当使用 git commit 进行提交操作时，Git 会先计算每一个子目录（本例中只有项目根目录）的校验和， 然后在 Git 仓库中这些校验和保存为树对象。随后，Git 便会创建一个提交对象， 它除了包含上面提到的那些信息外，还包含指向这个树对象（项目根目录）的指针。 如此一来，Git 就可以在需要的时候重现此次保存的快照。 现在，Git 仓库中有五个对象：三个 blob 对象（保存着文件快照）、一个 树 对象 （记录着目录结构和 blob 对象索引）以及一个 提交 对象（包含着指向前述树对象的指针和所有提交信息）。 Figure 9. 首次提交对象及其树结构 做些修改后再次提交，那么这次产生的提交对象会包含一个指向上次提交对象（父对象）的指针。 Figure 10. 提交对象及其父对象 Git 的分支，其实本质上仅仅是指向提交对象的可变指针。 Git 的默认分支名字是 master 。 在多次提交操作之后，你其实已经有一个指向最后那个提交对象的 master 分支。 master 分支会在每次提交时自动向前移动。 Note Git 的 master 分支并不是一个特殊分支。 它就跟其它分支完全没有区别。 之所以几乎每一个仓库都有 master 分支，是因为 git init 命令默认创建它，并且大多数人都懒得去改动它。 Figure 11. 分支及其提交历史 分支创建 Git 是怎么创建新分支的呢？ 很简单，它只是为你创建了一个可以移动的新的指针。 比如，创建一个 testing 分支， 你需要使用 git branch 命令： $ git branch testing 这会在当前所在的提交对象上创建一个指针。 Figure 12. 两个指向相同提交历史的分支 那么，Git 又是怎么知道当前在哪一个分支上呢？ 也很简单，它有一个名为 HEAD 的特殊指针。 请注意它和许多其它版本控制系统（如 Subversion 或 CVS）里的 HEAD 概念完全不同。 在 Git 中，它是一个指针，指向当前所在的本地分支（译注：将 HEAD 想象为当前分支的别名）。 在本例中，你仍然在 master 分支上。 因为 git branch 命令仅仅 创建 一个新分支，并不会自动切换到新分支中去。 Figure 13. HEAD 指向当前所在的分支 你可以简单地使用 git log 命令查看各个分支当前所指的对象。 提供这一功能的参数是 --decorate 。 $ git log --oneline --decorate f30ab (HEAD -> master, testing) add feature #32 - ability to add new formats to the central interface 34ac2 Fixed bug #1328 - stack overflow under certain conditions 98ca9 The initial commit of my project 正如你所见，当前 master 和 testing 分支均指向校验和以 f30ab 开头的提交对象。 分支切换 要切换到一个已存在的分支，你需要使用 git checkout 命令。 我们现在切换到新创建的 testing 分支去： $ git checkout testing 这样 HEAD 就指向 testing 分支了。 Figure 14. HEAD 指向当前所在的分支 那么，这样的实现方式会给我们带来什么好处呢？ 现在不妨再提交一次： $ vim test.rb $ git commit -a -m 'made a change' Figure 15. HEAD 分支随着提交操作自动向前移动 如图所示，你的 testing 分支向前移动了，但是 master 分支却没有，它仍然指向运行 git checkout 时所指的对象。 这就有意思了，现在我们切换回 master 分支看看： $ git checkout master Figure 16. 检出时 HEAD 随之移动 这条命令做了两件事。 一是使 HEAD 指回 master 分支，二是将工作目录恢复成 master 分支所指向的快照内容。 也就是说，你现在做修改的话，项目将始于一个较旧的版本。 本质上来讲，这就是忽略 testing 分支所做的修改，以便于向另一个方向进行开发。 Note 分支切换会改变你工作目录中的文件 在切换分支时，一定要注意你工作目录里的文件会被改变。 如果是切换到一个较旧的分支，你的工作目录会恢复到该分支最后一次提交时的样子。 如果 Git 不能干净利落地完成这个任务，它将禁止切换分支。 我们不妨再稍微做些修改并提交： $ vim test.rb $ git commit -a -m 'made other changes' 现在，这个项目的提交历史已经产生了分叉（参见 项目分叉历史 ）。 因为刚才你创建了一个新分支，并切换过去进行了一些工作，随后又切换回 master 分支进行了另外一些工作。 上述两次改动针对的是不同分支：你可以在不同分支间不断地来回切换和工作，并在时机成熟时将它们合并起来。 而所有这些工作，你需要的命令只有 branch 、 checkout 和 commit 。 Figure 17. 项目分叉历史 你可以简单地使用 git log 命令查看分叉历史。 运行 git log --oneline --decorate --graph --all ，它会输出你的提交历史、各个分支的指向以及项目的分支分叉情况。 $ git log --oneline --decorate --graph --all * c2b9e (HEAD, master) made other changes | * 87ab2 (testing) made a change |/ * f30ab add feature #32 - ability to add new formats to the * 34ac2 fixed bug #1328 - stack overflow under certain conditions * 98ca9 initial commit of my project 由于 Git 的分支实质上仅是包含所指对象校验和（长度为 40 的 SHA-1 值字符串）的文件，所以它的创建和销毁都异常高效。 创建一个新分支就相当于往一个文件中写入 41 个字节（40 个字符和 1 个换行符），如此的简单能不快吗？ 这与过去大多数版本控制系统形成了鲜明的对比，它们在创建分支时，将所有的项目文件都复制一遍，并保存到一个特定的目录。 完成这样繁琐的过程通常需要好几秒钟，有时甚至需要好几分钟。所需时间的长短，完全取决于项目的规模。 而在 Git 中，任何规模的项目都能在瞬间创建新分支。 同时，由于每次提交都会记录父对象，所以寻找恰当的合并基础（译注：即共同祖先）也是同样的简单和高效。 这些高效的特性使得 Git 鼓励开发人员频繁地创建和使用分支。 接下来，让我们看看你为什么应该这样做。 Note 创建新分支的同时切换过去 通常我们会在创建一个新分支后立即切换过去，这可以用 git checkout -b <newbranchname> 一条命令搞定。 prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/fa/v2/%da%af%db%8c%d8%aa-%d8%b1%d9%88%db%8c-%d8%b3%d8%b1%d9%88%d8%b1-Git-on-the-server-%da%af%db%8c%d8%aa%e2%80%8c%d9%88%d8%a8-GitWeb | Git - گیتوب (GitWeb) About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. شروع به کار (getting started) 1.1 درباره ورژن کنترل (About Version Control) 1.2 تاریخچه کوتاهی از گیت (A Short History of Git) 1.3 گیت چیست؟ (What is Git) 1.4 نصب گیت (Installing Git) 1.5 ستاپ اولیه گیت (First-Time Git Setup) 1.6 دریافت کمک (Getting Help) 1.7 خلاصه (summary) 2. مقدمات گیت (git basics chapter) 2.1 گرفتن یک مخزن گیت (Getting a Git Repository) 2.2 ثبت تغییرات در مخزن (Recording Changes to the Repository) 2.3 مشاهده تاریخچه کامیتها (Viewing the Commit History) 2.4 بازگرداندن تغییرات (Undoing Things) 2.5 کار کردن با ریموت ها (Working with Remotes) 2.6 تگ کردن (Tagging) 2.7 نام مستعار گیت (Git Aliases) 2.8 خلاصه (summary) 3. انشعابگیری در گیت (Git Branching) 3.1 شاخهها در یک نگاه (Branches in a Nutshell) 3.2 شاخهبندی و ادغام پایهای (Basic Branching and Merging) 3.3 مدیریت شاخهها (Branch Management) 3.4 روندهای کاری شاخهها (Branching Workflows) 3.5 شاخههای راه دور (Remote Branches) 3.6 بازپایهگذاری (Rebasing) 3.7 خلاصه (Summary) 4. گیت روی سرور (Git on the server) 4.1 پروتکلها (The Protocols) 4.2 راهاندازی گیت روی یک سرور (Getting Git on a Server) 4.3 ایجاد کلید عمومی SSH شما (Generating Your SSH Public Key) 4.4 نصب و راهاندازی سرور (Setting up server) 4.5 سرویسدهنده گیت (Git Daemon) 4.6 HTTP هوشمند (Smart HTTP) 4.7 گیتوب (GitWeb) 4.8 گیتلب (GitLab) 4.9 گزینههای میزبانی شخص ثالث (Third Party Hosted Options) 4.10 خلاصه (Summary) 5. گیت توزیعشده (Distributed git) 5.1 جریانهای کاری توزیعشده (Distributed Workflows) 5.2 مشارکت در یک پروژه (Contributing to a Project) 5.3 نگهداری یک پروژه (Maintaining a Project) 5.4 خلاصه (Summary) 6. گیت هاب (GitHub) 6.1 راهاندازی و پیکربندی حساب کاربری (Account Setup and Configuration) 6.2 مشارکت در یک پروژه (Contributing to a Project) 6.3 نگهداری یک پروژه (Maintaining a Project) 6.4 مدیریت یک سازمان (Managing an organization) 6.5 اسکریپتنویسی در گیتهاب (Scripting GitHub) 6.6 خلاصه (Summary) 7. ابزارهای گیت (Git Tools) 7.1 انتخاب بازبینی (Revision Selection) 7.2 مرحلهبندی تعاملی (Interactive Staging) 7.3 ذخیره موقت و پاکسازی (Stashing and Cleaning) 7.4 امضای کارهای شما (Signing Your Work) 7.5 جستجو (Searching) 7.6 بازنویسی تاریخچه (Rewriting History) 7.7 بازنشانی به زبان ساده (Reset Demystified) 7.8 ادغام پیشرفته (Advanced Merging) 7.9 بازاستفاده خودکار از حل تضادها (Rerere) 7.10 اشکالزدایی با گیت (Debugging with Git) 7.11 سابماژول ها (Submodules) 7.12 بستهبندی (Bundling) 7.13 جایگزینی (Replace) 7.14 ذخیرهسازی اطلاعات ورود (Credential Storage) 7.15 خلاصه (Summary) 8. سفارشیسازی Git (Customizing Git) 8.1 پیکربندی گیت (Git Configuration) 8.2 ویژگیهای گیت (Git Attributes) 8.3 هوکهای گیت (Git Hooks) 8.4 یک نمونه سیاست اعمال شده توسط گیت (An Example Git-Enforced Policy) 8.5 خلاصه (Summary) 9. گیت و سیستمهای دیگر (Git and Other Systems) 9.1 گیت بهعنوان کلاینت (Git as a Client) 9.2 مهاجرت به گیت (Migrating to Git) 9.3 خلاصه (Summary) 10. مباحث درونی گیت (Git Internals) 10.1 ابزارها و دستورات سطح پایین (Plumbing and Porcelain) 10.2 اشیا گیت (Git Objects) 10.3 مراجع گیت (Git References) 10.4 فایلهای بسته (Packfiles) 10.5 نگاشت (The Refspec) 10.6 پروتکلهای انتقال (Transfer Protocols) 10.7 نگهداری و بازیابی دادهها (Maintenance and Data Recovery) 10.8 متغیرهای محیطی (Environment Variables) 10.9 خلاصه (Summary) A1. پیوست A: گیت در محیطهای دیگر (Git in Other Environments) A1.1 رابط های گرافیکی (Graphical Interfaces) A1.2 گیت در ویژوال استودیو (Git in Visual Studio) A1.3 گیت در Visual Studio Code (Git in Visual Studio Code) A1.4 گیت در IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine (Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine) A1.5 گیت در Sublime Text (Git in Sublime Text) A1.6 گیت در بش (Git in Bash) A1.7 گیت در Zsh (Git in Zsh) A1.8 گیت در PowerShell (Git in PowerShell) A1.9 خلاصه (Summary) A2. پیوست B: گنجاندن گیت در برنامههای شما (Embedding Git in your Applications) A2.1 خط فرمان گیت (Command-line Git) A2.2 کتابخانهٔ گیت به زبان سی (Libgit2) A2.3 کتابخانه گیت برای زبان جاوا (JGit) A2.4 کتابخانه گیت برای زبان گو (go-git) A2.5 کتابخانه گیت پایتون (Dulwich) A3. پیوست C: دستورات گیت (Git Commands) A3.1 تنظیم و پیکربندی (Setup and Config) A3.2 گرفتن و ایجاد پروژهها (Getting and Creating Projects) A3.3 نمونهبرداری پایهای (Basic Snapshotting) A3.4 انشعابگیری و ادغام (Branching and Merging) A3.5 بهاشتراکگذاری و بهروزرسانی پروژهها (Sharing and Updating Projects) A3.6 بازرسی و مقایسه (Inspection and Comparison) A3.7 عیبیابی (Debugging) A3.8 اعمال تغییرات به صورت پچ (Patching) A3.9 ایمیل (Email) A3.10 سیستمهای خارجی (External Systems) A3.11 مدیریت (Administration) A3.12 دستورات سطح پایین گیت (Plumbing Commands) 2nd Edition 4.7 گیت روی سرور (Git on the server) - گیتوب (GitWeb) گیتوب (GitWeb) حال که به پروژهتان دسترسی پایهای خواندن/نوشتن و فقط خواندنی دارید، ممکن است بخواهید یک نمایشگر ساده مبتنی بر وب راهاندازی کنید. گیت همراه با یک اسکریپت CGI به نام GitWeb عرضه میشود که گاهی برای این منظور استفاده میشود. نمودار 49. The GitWeb web-based user interface اگر میخواهید ببینید GitWeb برای پروژهتان چگونه خواهد بود، گیت دستوری دارد که میتواند یک نمونه موقت راهاندازی کند، البته به شرطی که وبسرور سبکی مانند lighttpd یا webrick روی سیستمتان نصب باشد. در سیستمهای لینوکس، معمولاً lighttpd نصب است، پس ممکن است با تایپ کردن git instaweb در پوشه پروژهتان بتوانید آن را اجرا کنید. اگر از macOS استفاده میکنید، نسخه Leopard به صورت پیشفرض Ruby دارد، پس احتمالاً webrick بهترین گزینه برای شماست. برای راهاندازی instaweb با یک وبسرور غیر از lighttpd میتوانید از گزینه --httpd استفاده کنید. $ git instaweb --httpd=webrick [2009-02-21 10:02:21] INFO WEBrick 1.3.1 [2009-02-21 10:02:21] INFO ruby 1.8.6 (2008-03-03) [universal-darwin9.0] این دستور یک سرور HTTPD روی پورت ۱۲۳۴ راهاندازی میکند و به طور خودکار یک مرورگر وب را باز میکند که صفحه مربوطه را نمایش میدهد. کار سادهای است. وقتی کارتان تمام شد و میخواهید سرور را خاموش کنید، میتوانید همان دستور را با گزینه --stop اجرا کنید. $ git instaweb --httpd=webrick --stop اگر میخواهید رابط وب را دائماً روی یک سرور برای تیمتان یا پروژه متنباز میزبانیشده راهاندازی کنید، باید اسکریپت CGI را طوری تنظیم کنید که توسط وبسرور معمولی شما سرو شود. برخی توزیعهای لینوکس بستهای به نام gitweb دارند که ممکن است بتوانید با apt یا dnf آن را نصب کنید، پس بهتر است ابتدا این روش را امتحان کنید. ما به سرعت نصب دستی GitWeb را مرور میکنیم. ابتدا باید کد منبع گیت را دریافت کنید که GitWeb همراه آن است و سپس اسکریپت CGI سفارشی را بسازید: $ git clone https://git.kernel.org/pub/scm/git/git.git $ cd git/ $ make GITWEB_PROJECTROOT="/srv/git" prefix=/usr gitweb SUBDIR gitweb SUBDIR ../ make[2]: `GIT-VERSION-FILE' is up to date. GEN gitweb.cgi GEN static/gitweb.js $ sudo cp -Rf gitweb /var/www/ توجه کنید که باید به دستور بگویید مخازن گیت شما کجا قرار دارند، با استفاده از متغیر GITWEB_PROJECTROOT . حالا باید به آپاچی بگویید که از CGI برای این اسکریپت استفاده کند، برای این کار میتوانید یک VirtualHost اضافه کنید: <VirtualHost *:80> ServerName gitserver DocumentRoot /var/www/gitweb <Directory /var/www/gitweb> Options +ExecCGI +FollowSymLinks +SymLinksIfOwnerMatch AllowOverride All order allow,deny Allow from all AddHandler cgi-script cgi DirectoryIndex gitweb.cgi </Directory> </VirtualHost> دوباره تأکید میکنیم که GitWeb را میتوان با هر وبسرور دارای قابلیت CGI یا Perl سرو کرد؛ اگر ترجیح میدهید از چیز دیگری استفاده کنید، راهاندازی آن دشوار نخواهد بود. در این مرحله باید بتوانید با مراجعه به آدرس http://gitserver/ مخازن خود را به صورت آنلاین مشاهده کنید. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/Pagsisimula-Buod | Git - Buod About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 1.8 Pagsisimula - Buod Buod Dapat mayroon kanang pangunahing pag-uunawa kung ano ang Git at paano ito kakaiba mula sa kahit na anong sentralisadong mga sistema ng taga-kontrol ng bersyon na maaaring nagamit mo na sa nakaaraan. Ngayon, dapat ka na rin magkaroon ng gumagana na bersyon ng Git sa iyong sistema na ini-setup gamit ang iyong personal na pagkakakilanlan. Oras na para matuto ka ng iilang pangunahing kaalaman sa Git. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/uk/v2/%d0%9e%d1%81%d0%bd%d0%be%d0%b2%d0%b8-Git-%d0%97%d0%b0%d0%bf%d0%b8%d1%81-%d0%b7%d0%bc%d1%96%d0%bd-%d0%b4%d0%be-%d1%80%d0%b5%d0%bf%d0%be%d0%b7%d0%b8%d1%82%d0%be%d1%80%d1%96%d1%8f | Git - Запис змін до репозиторія About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Вступ 1.1 Про систему контролю версій 1.2 Коротка історія Git 1.3 Основи Git 1.4 Git, зазвичай, тільки додає дані 1.5 Три стани 1.6 Командний рядок 1.7 Інсталяція Git 1.8 Початкове налаштування Git 1.9 Отримання допомоги 1.10 Підсумок 2. Основи Git 2.1 Створення Git-сховища 2.2 Запис змін до репозиторія 2.3 Перегляд історії комітів 2.4 Скасування речей 2.5 Взаємодія з віддаленими сховищами 2.6 Теґування 2.7 Псевдоніми Git 2.8 Підсумок 3. Галуження в git 3.1 Гілки у кількох словах 3.2 Основи галуження та зливання 3.3 Управління гілками 3.4 Процеси роботи з гілками 3.5 Віддалені гілки 3.6 Перебазовування 3.7 Підсумок 4. Git на сервері 4.1 Протоколи 4.2 Отримання Git на сервері 4.3 Генерація вашого публічного ключа SSH 4.4 Налаштування Серверу 4.5 Демон Git 4.6 Розумний HTTP 4.7 GitWeb 4.8 GitLab 4.9 Варіанти стороннього хостингу 4.10 Підсумок 5. Розподілений Git 5.1 Розподілені процеси роботи 5.2 Внесення змін до проекту 5.3 Супроводжування проекту 5.4 Підсумок 6. GitHub 6.1 Створення та налаштування облікового запису 6.2 Як зробити внесок до проекту 6.3 Супроводжування проєкту 6.4 Керування організацією 6.5 Скриптування GitHub 6.6 Підсумок 7. Інструменти Git 7.1 Вибір ревізій 7.2 Інтерактивне індексування 7.3 Ховання та чищення 7.4 Підписання праці 7.5 Пошук 7.6 Переписування історії 7.7 Усвідомлення скидання (reset) 7.8 Складне злиття 7.9 Rerere 7.10 Зневадження з Git 7.11 Підмодулі 7.12 Пакування 7.13 Заміна 7.14 Збереження посвідчення (credential) 7.15 Підсумок 8. Налаштування Git 8.1 Конфігурація Git 8.2 Атрибути Git 8.3 Гаки (hooks) Git 8.4 Приклад політики користування виконуваної Git-ом 8.5 Підсумок 9. Git and Other Systems 9.1 Git як клієнт 9.2 Міграція на Git 9.3 Підсумок 10. Git зсередини 10.1 Кухонні та парадні команди 10.2 Об’єкти Git 10.3 Посилання Git 10.4 Файли пакунки 10.5 Специфікація посилань (refspec) 10.6 Протоколи передачі 10.7 Супроводження та відновлення даних 10.8 Змінні середовища 10.9 Підсумок A1. Додаток A: Git в інших середовищах A1.1 Графічні інтерфейси A1.2 Git у Visual Studio A1.3 Git в Eclipse A1.4 Git у Bash A1.5 Git у Zsh A1.6 Git у Powershell A1.7 Підсумок A2. Додаток B: Вбудовування Git у ваші застосунки A2.1 Git з командного рядка A2.2 Libgit2 A2.3 JGit A2.4 go-git A3. Додаток C: Команди Git A3.1 Налаштування та конфігурація A3.2 Отримання та створення проектів A3.3 Базове збереження відбитків A3.4 Галуження та зливання A3.5 Поширення й оновлення проектів A3.6 Огляд та порівняння A3.7 Зневаджування A3.8 Латання (patching) A3.9 Електронна пошта A3.10 Зовнішні системи A3.11 Адміністрування A3.12 Кухонні команди 2nd Edition 2.2 Основи Git - Запис змін до репозиторія Запис змін до репозиторія Тепер у вас на локальній машині має бути справжній Git репозиторій та робоча тека з усіма файлами цього проекту. Зазвичай, ви хочете зробити деякі зміни та записати їх у вашому репозиторії кожного разу, коли ваш проект набуває стану, що ви бажаєте зберегти. Пам’ятайте, що кожен файл вашої робочої директорії може бути в одному з двох станів: контрольований (tracked) чи неконтрольований (untracked). Контрольовані файли — це файли, що були в останньому знімку. Вони можуть бути не зміненими, зміненими або індексованими. Якщо стисло, контрольовані файли — це файли, про які Git щось знає. Неконтрольовані файли — це все інше, будь-які файли у вашій робочій директорії, що не були у вашому останньому знімку та не існують у вашому індексі. Якщо ви щойно зробили клон репозиторія, усі ваші файли контрольовані та не змінені, адже Git щойно їх отримав, а ви нічого не редагували. По мірі редагування файлів, Git бачить, що вони змінені, адже ви їх змінили після останнього коміту. Впродовж роботи ви вибірково індексуєте ці змінені файли та потім зберігаєте всі індексовані зміни, та цей цикл повторюється. Рисунок 8. Цикл життя статусу ваших файлів. Перевірка статусу ваших файлів Щоб дізнатись, в якому стані ваші файли, варто скористатись командою git status . Якщо ви виконаєте цю команду відразу після клонування, ви маєте побачити таке: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean Це означає, що ваша робоча директорія чиста — іншими словами, жоден з контрольованих файлів не змінено. Git також не бачить неконтрольованих файлів, інакше він би їх тут вказав. Нарешті, ця команда показує вам, в якій ви зараз гілці та інформує вас про те, що вона не розбіглася з такою ж гілкою на сервері. Поки що, ця гілка завжди буде ``master'', така гілка створюється автоматично. Це нас не обходить у цьому розділі. Галуження в git розповідає про гілки та посилання докладно. Припустімо, ви додали новий файл до вашого проекту, простий файл README . Якщо файл раніше не існував, і ви виконаєте git status , ви побачите ваш неконтрольований файл так: $ echo 'My Project' > README $ git status On branch master Your branch is up-to-date with 'origin/master'. Untracked files: (use "git add <file>..." to include in what will be committed) README nothing added to commit but untracked files present (use "git add" to track) Ви можете бачити, що ваш новий файл README неконтрольований, адже він під заголовком `Untracked files'' у статусі. Неконтрольований (untracked) означає, що Git бачить файл, якого нема у попередньому знімку (коміті). Git не почне включати його до ваших комітів доки ви явно не скажете йому це зробити. Так зроблено щоб ви випадково не почали включати генеровані бінарні файли чи інші файли, які ви не збирались включати. Ви все ж таки хочете почати включати `README , отже почнімо контролювати файл. Контролювання нових файлів Щоб почати контролювати новий файл, вам треба використати команду git add . Почати контролювати файл README можна так: $ git add README Якщо ви знову виконаєте команду status, ви побачите, що ваш файл README тепер контролюється та готовий до включення до коміту: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Ви можете зрозуміти, що цей файл доданий, бо він під заголовком `Changes to be committed''. Якщо ви створите коміт зміни зараз, версія файлу на момент коли ви виконали `git add буде збережена в знімку в історії. Ви можете пригадати, що коли ви виконали git init раніше, ви потім виконали git add <файли> — це було зроблено щоб розпочати контролювати файли у вашій директорії. Команда git add приймає шлях файлу або директорії. Якщо це директорія, команда додає усі файли в цій директорії рекурсивно. Індексування змінених файлів Змінімо файл, що вже контролюється. Якщо ви зміните файл CONTRIBUTING.md , що вже контролюється, та потім виконаєте команду git status знову, ви отримаєте щось на кшталт: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Файл CONTRIBUTING.md з’явився під секцією названою Changes not staged for commit'' — це означає, що контрольований файл був редагований у робочій директорії проте його не індексували. Щоб проіндексувати його, виконайте команду git add . git add багатоцільова команда — її слід використовувати щоб почати контролювати нові файли, щоб додавати файли, та для інших речей, наприклад позначання конфліктних файлів як розв’язаних. Про неї краще думати Додай саме цей зміст до наступного коміту'' а не `додай цей файл до проекту''. Виконаймо `git add зараз для індексації файлу CONTRIBUTING.md , а потім знову виконаємо git status : $ git add CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Обидва файли індексовані та будуть включені до наступного коміту. Припустімо, що саме зараз ви пригадали маленьку зміну, яку ви хочете зробити в CONTRIBUTING.md до того, як зробити коміт з ним. Ви знову його відкриваєте та редагуєте, і ви готові зробити коміт. Втім, виконаймо git status ще раз: $ vim CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Якого біса? Тепер CONTRIBUTING.md є як в індексованих, так і в неіндексованих. Як таке можливо? Виявляється, що Git індексує файл саме таким, яким він був, коли ви виконали команду git add . Якщо ви зараз створите коміт, в історії збережеться версія CONTRIBUTING.md , яка була коли ви востаннє викликали git add , а не поточна версія файлу з вашої робочої директорії, коли ви виконаєте git commit . Якщо ви зміните файл після того, як виконаєте git add , вам треба знову виконати git add щоб проіндексувати останню версію файлу: $ git add CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Короткий статус Хоча вивід git status доволі вичерпний, він також дещо довгий. Git також пропонує опцію короткого перегляду статусу, щоб ви могли побачити свої зміни в більш компактному вигляді. Якщо ви виконаєте git status -s або git status --short , ви отримаєте набагато простіший вивід: $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt Нові неконтрольовані файли позначаються ?? , нові індексовані файли позначаються A , змінені файли позначаються M тощо. Результат має дві колонки – ліва містить статус індексу, а права містить статус робочої теки. Наприклад у цьому виводі, файл README змінений у робочій директорії, проте не індексований, а файл lib/simplegit.rb змінений та індексований. Rakefile був змінений, індексований та знову змінений, тому є зміни в обох колонках. Ігнорування файлів Буває, що у вас є клас файлів, що ви не хочете щоб Git їх автоматично індексував чи навіть відображав як неконтрольовані. Зазвичай це автоматично згенеровані файли, наприклад файли лоґів або файли вироблені вашою системою збірки. У таких випадках, ви можете створити файл .gitignore , що містить взірці, яким відповідають ці файли. Ось приклад файлу .gitignore : $ cat .gitignore *.[oa] *~ Перший рядок каже Git ігнорувати файли, що закінчуються на .o'' або .a'' — об’єктні та архівні файли, що можуть бути продуктами компіляції вашого коду. Другий рядок каже Git ігнорувати всі файли, що їхні назви закінчуються на тильду ( ~ ), яка використовується багатьма текстовими редакторами (такими як Emacs) щоб позначати тимчасові файли. Ви також можете додати директорії log, tmp та pid, автоматично згенеровану документацію, тощо. Заповнення файлу .gitignore вашого нового сховища до початку праці зазвичай гарна думка, адже це допоможе вам випадково не додати файли, які ви не хочете додавати до репозиторія Git. Правила для взірців, які ви можете додати до файлу .gitignore : Порожні рядки та рядки, що починаються з # , ігноруються. Стандартні ґлоб взірці працюють, і будуть застосовані для всього робочого дерева рекурсивно.. Ви можете почати взірець з прямої похилої риски ( / ) щоб уникнути рекурсії. Ви можете завершити взірець похилою рискою ( / ) щоб позначити директорію. Ви можете відкинути взірець, якщо почнете його зі знаку оклику ( ! ). Ґлоб (glob) взірці – це ніби спрощені регулярні вирази, що їх використовують оболонки. Зірочка ( ) відповідає нулю або більше символам. [абв] відповідає будь-якому з символів всередині квадратних дужок (у цьому випадку а, б або в). Знак питання ( ? ) відповідає одному символу. Квадратні дужки з символами, що розділені дефісом ( [0-9] ) відповідають будь-якому символу між ними (у даному випадку від 0 до 9). Ви можете використовувати дві зірочки щоб позначити вкладені директорії: a/*/z відповідає a/z , a/b/z , a/b/c/z тощо. Ось ще один приклад файлу .gitignore : # ігнорувати всі файли .a *.a # Проте відстежувати lib.a, хоч ми й ігноруємо .a файли вище !lib.a # Ігнорувати файл TODO тільки в поточній теці, не в інших теках subdir/TODO /TODO # Ігнорувати усі файли в теці build/ build/ # Ігнорувати doc/notes.txt, проте не doc/server/arch.txt doc/*.txt # Ігнорувати усі .pdf файли в теці doc/ та всіх її підтеках doc/**/*.pdf Підказка GitHub підтримує доволі вичерпний список гарних прикладів файлів .gitignore для десятків проектів та мов за адресою https://github.com/github/gitignore , якщо ви бажаєте мати зразок для свого проекту. Зауваження In the simple case, a repository might have a single .gitignore file in its root directory, which applies recursively to the entire repository. However, it is also possible to have additional .gitignore files in subdirectories. The rules in these nested .gitignore files apply only to the files under the directory where they are located. (The Linux kernel source repository has 206 .gitignore files.) It is beyond the scope of this book to get into the details of multiple .gitignore files; see man gitignore for the details. Перегляд ваших доданих та недоданих змін Якщо команда git status занадто зверхня для вас — ви хочете знати що саме ви змінили, а не просто які файли ви змінили — ви можете використати команду git diff . Ми докладніше розглянемо git diff пізніше, проте напевно найчастіше ви її будете використовувати для того щоб дізнатись дві речі: Що ви змінили, проте ще не індексували? Та що ви індексували та збираєтесь зберегти? Хоч git status відповідає на ці питання дуже загально — тільки показує список файлів, git diff показує вам усі індексовані та видалені рядки — латку, як вона є. Припустімо, що ви внесли та проіндексували зміни до файлу README знову, а потім змінили файл CONTRIBUTING.md але не індексували його. Якщо ви виконаєте команду git status , ви знову побачите щось на кшталт: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Щоб побачити зміни, які ви ще не індексували, наберіть git diff без параметрів: $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,8 @@ branch directly, things can get messy. Please include a nice description of your changes when you submit your PR; if we have to read the whole diff to figure out why you're contributing in the first place, you're less likely to get feedback and have your change -merged in. +merged in. Also, split your changes into comprehensive chunks if your patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's Ця команда порівнює вашу робочу директорію з індексом. Результат показує вам зміни, котрі ви зробили проте не індексували. Якщо ви хочете побачити, що ви індексували та ввійде до вашого наступного коміту, ви можете скористатись git diff --staged . Ця команда порівнює індексовані зміни з вашим останнім знімком: $ git diff --staged diff --git a/README b/README new file mode 100644 index 0000000..03902a1 --- /dev/null +++ b/README @@ -0,0 +1 @@ +My Project Важливо пам’ятати, що команда git diff без опцій не відображає всіх змін з останнього коміту — тільки неіндексовані зміни. Якщо ви проіндексували всі свої зміни, вивід git diff буде порожнім. Наведемо інший приклад, припустимо, що ви проіндексували файл CONTRIBUTING.md та знову його відредагували, ви можете скористатись git diff щоб побачити індексовані та неіндексовані зміни. Якщо наше середовище виглядає наступним чином: $ git add CONTRIBUTING.md $ echo '# test line' >> CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Тепер ви можете використати git diff щоб побачити неіндексовані зміни: $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 643e24f..87f08c8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -119,3 +119,4 @@ at the ## Starter Projects See our [projects list](https://github.com/libgit2/libgit2/blob/development/PROJECTS.md). +test line і git diff --cached щоб побачити наразі індексовані зміни ( --staged і --cached мають однакове значення): $ git diff --cached diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,8 @@ branch directly, things can get messy. Please include a nice description of your changes when you submit your PR; if we have to read the whole diff to figure out why you're contributing in the first place, you're less likely to get feedback and have your change -merged in. +merged in. Also, split your changes into comprehensive chunks if your patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's Зауваження Git Diff у зовнішній утиліті. Ми продовжимо використати команду git diff різноманітними шляхами в решті книги. Є інший шлях подивитись на різницю між файлами, якщо вам більш до смаку графічна чи зовнішня програма для відображення різниці. Якщо ви виконаєте git difftool замість git diff , ви зможете використати будь-яку з програм на кшталт emerge, vimdiff і багато інших (включно з комерційними програмами). Виконайте git difftool --tool-help щоб дізнатись, що доступно на вашій системі. Збереження ваших змін у комітах Припустімо, що ваш індекс саме в стані, який ви бажаєте, та тепер ви можете створити коміт з ваших зміни. Пам’ятайте, що будь-які неіндексовані зміни — будь-які файли, що ви їх створили чи змінили, але ви не виконали git add після їх редагування — не потраплять до цього коміту. Вони так і залишаться зміненими файлами на вашому диску. У цьому випадку, припустімо, що останнього разу, коли ви виконали git status , ви побачили, що всі зміни індексовані, отже ви готові зберегти ваші зміни. Найпростіший спосіб створити коміт — набрати git commit : $ git commit Це запустить ваш редактор. (Це редактор, який встановлено в змінній середовища EDITOR вашої оболонки — зазвичай vim або emacs, хоча ви можете налаштувати його як завгодно за допомогою команди git config --global core.editor , яку ви бачили в Вступ ). Редактор покаже вам наступний текст (це приклад екрану Vim): # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # new file: README # modified: CONTRIBUTING.md # ~ ~ ~ ".git/COMMIT_EDITMSG" 9L, 283C Ви бачите, згенероване повідомлення коміту містить закоментований останній вивід команди git status та один пустий рядок нагорі. Ви можете видалити ці коментарі на написати своє повідомлення коміту, або можете залишити їх, щоб вони допомогли вам пригадати що ви зберігаєте. (Для навіть більш докладного нагадування про ваші зміни, ви можете передати опцію -v до git commit . Це призведе то того, що у вашому редакторі також будуть відображені всі зміни, що ввійдуть до коміту.) Коли ви виходите з редактору, Git створює коміт з цим повідомленням коміту (після видалення коментарів та змін до файлів). Іншим чином, ви можете набрати повідомлення коміту прямо в команді commit , якщо напишете її після опції -m , ось так: $ git commit -m "Story 182: Fix benchmarks for speed" [master 463dc4f] Story 182: Fix benchmarks for speed 2 files changed, 2 insertions(+) create mode 100644 README Тепер ви створили свій перший коміт! Ви можете бачити, що команда commit розповіла вам дещо про коміт: до якої гілки ви зберегли зміни ( master ), який SHA-1 хеш отримав коміт ( 463dc4f ), скільки файлів було змінено, та статистику щодо індексованих та видалених рядків у коміті. Пам’ятайте, що коміт записує знімок, який ви створили в індексі. Усе, що ви не проіндексували, залишиться зміненим. Ви можете зробити інший коміт, щоб додати ці зміни до історії. Щоразу ви створюєте коміт, ви записуєте знімок вашого проекту, до якого ви можете повернутися або порівняти щось пізніше. Обходимо індекс Хоч індекс може бути неперевершено корисним для підготовки комітів саме до потрібного вам вигляду, іноді він може буди надто складним для ваших потреб. Якщо ви бажаєте обійти індекс, Git надає вам простий короткий шлях. Додавання опції -a до команди git commit , змушує Git автоматично додати кожен файл, що вже контролюється, до коміту, що дозволяє вам пропустити команди git add : $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md no changes added to commit (use "git add" and/or "git commit -a") $ git commit -a -m 'added new benchmarks' [master 83e38c7] added new benchmarks 1 file changed, 5 insertions(+), 0 deletions(-) Зауважте, що вам не довелося виконувати git add до файлу CONTRIBUTING.md у цьому випадку до того, як ви створили коміт. Це тому що опція -a включає всі змінені файли. Це зручно, проте будьте обережні; інколи ця опція є причиною додавання небажаних змін. Видаляємо файли Щоб видалити файл з Git, вам треба прибрати його з контрольованих файлів (вірніше, видалити його з вашого індексу) та створити коміт. Команда git rm це робить, а також видаляє файл з вашої робочої директорії, щоб наступного разу він не відображався неконтрольованим. Якщо ви просто видалите файл з вашої робочої директорії, він з’явиться під заголовком `Changes not staged for commit'' (тобто, неіндексованим ) виводу команди `git status : $ rm PROJECTS.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add/rm <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) deleted: PROJECTS.md no changes added to commit (use "git add" and/or "git commit -a") Потім, якщо ви виконаєте git rm , файл буде індексованим на видалення: $ git rm PROJECTS.md rm 'PROJECTS.md' $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) deleted: PROJECTS.md Наступного разу, коли ви створите коміт, файл зникне та більше не буде контрольованим. Якщо ви редагували файл та вже додали його до індексу, ви маєте примусово видалити його за допомогою опції -f . Це захід безпеки, щоб завадити випадковому видаленню даних, які ви не записали до знімку, і тому вони не можуть бути відновлені Git. Інша корисна річ, яку ви можливо захочете зробити, це зберегти файл у робочій директорії, проте видалити його з індексу. Іншими словами, ви можете забажати зберегти файл на диску, проте більше не контролювати його Git. Це може бути корисним, якщо ви забули щось додати до свого файлу .gitignore та випадково проіндексували, наприклад великий файл журнал чи купу скомпільованих файлів .a . Щоб це зробити, скористайтеся опцією --cached : $ git rm --cached README Ви можете передавати команді git rm файли, директорії або файлові ґлоб шаблони. Це означає, що ви можете зробити щось таке: $ git rm log/\*.log Зверніть увагу на зворотну похилу ( \ ) попереду * . Вона необхідна адже Git має власне розкриття шаблону на додаток до розкриття шаблону вашої оболонки. Ця команда видаляє всі файли, що мають .log розширення та знаходяться в директорії log/ . Або, ви можете зробити щось таке: $ git rm \*~ Ця команда видаляє всі файли, чиї назви закінчуються на ~ . Пересування файлів На відміну від багатьох інших СКВ, Git явно не стежить за пересуванням файлів. Якщо ви перейменуєте файл у Git, ніяких метаданих про це не буде збережено. Втім, Git доволі кмітливий, та може сам зрозуміти, що перейменування відбулося вже після нього — ми повернемося до виявлення пересування файлів трохи пізніше. Тому присутність команди mv у Git трохи спантеличує. Якщо ви бажаєте перейменувати файл у Git, ви можете виконати щось таке: $ git mv стара_назва нова_назва і це зробить що вам треба. Насправді, якщо ви виконаєте щось таке і подивитесь на статус, ви побачите, що Git вважає, що перейменував файл: $ git mv README.md README $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Втім, це рівнозначно виконанню таких команд: $ mv README.md README $ git rm README.md $ git add README Git без підказок розуміє, що це перейменування файлу, тому неважливо, чи ви перейменували файл так, або за допомогою команди mv . Єдина дійсна різниця в тому, що git mv це одна команда замість трьох — ця команда існує тільки для зручності. Більш важливо, що ви можете використати будь-яку утиліту для перейменування файлу та зробити add/rm пізніше, до збереження коміту. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=pa | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등�� | 2026-01-13T09:29:23 |
https://git-scm.com/book/ru/v2/%d0%9e%d1%81%d0%bd%d0%be%d0%b2%d1%8b-Git-%d0%9e%d0%bf%d0%b5%d1%80%d0%b0%d1%86%d0%b8%d0%b8-%d0%be%d1%82%d0%bc%d0%b5%d0%bd%d1%8b | Git - Операции отмены About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Введение 1.1 О системе контроля версий 1.2 Краткая история Git 1.3 Что такое Git? 1.4 Командная строка 1.5 Установка Git 1.6 Первоначальная настройка Git 1.7 Как получить помощь? 1.8 Заключение 2. Основы Git 2.1 Создание Git-репозитория 2.2 Запись изменений в репозиторий 2.3 Просмотр истории коммитов 2.4 Операции отмены 2.5 Работа с удалёнными репозиториями 2.6 Работа с тегами 2.7 Псевдонимы в Git 2.8 Заключение 3. Ветвление в Git 3.1 О ветвлении в двух словах 3.2 Основы ветвления и слияния 3.3 Управление ветками 3.4 Работа с ветками 3.5 Удалённые ветки 3.6 Перебазирование 3.7 Заключение 4. Git на сервере 4.1 Протоколы 4.2 Установка Git на сервер 4.3 Генерация открытого SSH ключа 4.4 Настраиваем сервер 4.5 Git-демон 4.6 Умный HTTP 4.7 GitWeb 4.8 GitLab 4.9 Git-хостинг 4.10 Заключение 5. Распределённый Git 5.1 Распределённый рабочий процесс 5.2 Участие в проекте 5.3 Сопровождение проекта 5.4 Заключение 6. GitHub 6.1 Настройка и конфигурация учётной записи 6.2 Внесение собственного вклада в проекты 6.3 Сопровождение проекта 6.4 Управление организацией 6.5 Создание сценариев GitHub 6.6 Заключение 7. Инструменты Git 7.1 Выбор ревизии 7.2 Интерактивное индексирование 7.3 Припрятывание и очистка 7.4 Подпись 7.5 Поиск 7.6 Перезапись истории 7.7 Раскрытие тайн reset 7.8 Продвинутое слияние 7.9 Rerere 7.10 Обнаружение ошибок с помощью Git 7.11 Подмодули 7.12 Создание пакетов 7.13 Замена 7.14 Хранилище учётных данных 7.15 Заключение 8. Настройка Git 8.1 Конфигурация Git 8.2 Атрибуты Git 8.3 Хуки в Git 8.4 Пример принудительной политики Git 8.5 Заключение 9. Git и другие системы контроля версий 9.1 Git как клиент 9.2 Переход на Git 9.3 Заключение 10. Git изнутри 10.1 Сантехника и Фарфор 10.2 Объекты Git 10.3 Ссылки в Git 10.4 Pack-файлы 10.5 Спецификации ссылок 10.6 Протоколы передачи данных 10.7 Обслуживание репозитория и восстановление данных 10.8 Переменные окружения 10.9 Заключение A1. Приложение A: Git в других окружениях A1.1 Графические интерфейсы A1.2 Git в Visual Studio A1.3 Git в Visual Studio Code A1.4 Git в Eclipse A1.5 Git в IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.6 Git в Sublime Text A1.7 Git в Bash A1.8 Git в Zsh A1.9 Git в PowerShell A1.10 Заключение A2. Приложение B: Встраивание Git в ваши приложения A2.1 Git из командной строки A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Приложение C: Команды Git A3.1 Настройка и конфигурация A3.2 Клонирование и создание репозиториев A3.3 Основные команды A3.4 Ветвление и слияния A3.5 Совместная работа и обновление проектов A3.6 Осмотр и сравнение A3.7 Отладка A3.8 Внесение исправлений A3.9 Работа с помощью электронной почты A3.10 Внешние системы A3.11 Администрирование A3.12 Низкоуровневые команды 2nd Edition 2.4 Основы Git - Операции отмены Операции отмены В любой момент вам может потребоваться что-либо отменить. Здесь мы рассмотрим несколько основных способов отмены сделанных изменений. Будьте осторожны, не все операции отмены в свою очередь можно отменить! Это одна из редких областей Git, где неверными действиями можно необратимо удалить результаты своей работы. Отмена может потребоваться, если вы сделали коммит слишком рано, например, забыв добавить какие-то файлы или комментарий к коммиту. Если вы хотите переделать коммит — внесите необходимые изменения, добавьте их в индекс и сделайте коммит ещё раз, указав параметр --amend : $ git commit --amend Эта команда использует область подготовки (индекс) для внесения правок в коммит. Если вы ничего не меняли с момента последнего коммита (например, команда запущена сразу после предыдущего коммита), то снимок состояния останется в точности таким же, а всё что вы сможете изменить — это ваше сообщение к коммиту. Запустится тот же редактор, только он уже будет содержать сообщение предыдущего коммита. Вы можете редактировать сообщение как обычно, однако, оно заменит сообщение предыдущего коммита. Например, если вы сделали коммит и поняли, что забыли проиндексировать изменения в файле, который хотели добавить в коммит, то можно сделать следующее: $ git commit -m 'Initial commit' $ git add forgotten_file $ git commit --amend В итоге получится единый коммит — второй коммит заменит результаты первого. Примечание Очень важно понимать, что когда вы вносите правки в последний коммит, вы не столько исправляете его, сколько заменяете новым, который полностью его перезаписывает. В результате всё выглядит так, будто первоначальный коммит никогда не существовал, а так же он больше не появится в истории вашего репозитория. Очевидно, смысл изменения коммитов в добавлении незначительных правок в последние коммиты и, при этом, в избежании засорения истории сообщениями вида «Ой, забыл добавить файл» или «Исправление грамматической ошибки». Отмена индексации файла Следующие два раздела демонстрируют как работать с индексом и изменениями в рабочем каталоге. Радует, что команда, которой вы определяете состояние этих областей, также подсказывает вам как отменять изменения в них. Например, вы изменили два файла и хотите добавить их в разные коммиты, но случайно выполнили команду git add * и добавили в индекс оба. Как исключить из индекса один из них? Команда git status напомнит вам: $ git add * $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README modified: CONTRIBUTING.md Прямо под текстом «Changes to be committed» говорится: используйте git reset HEAD <file>… для исключения из индекса. Давайте последуем этому совету и отменим индексирование файла CONTRIBUTING.md : $ git reset HEAD CONTRIBUTING.md Unstaged changes after reset: M CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Команда выглядит несколько странно, но — работает! Файл CONTRIBUTING.md изменен, но больше не добавлен в индекс. Примечание Команда git reset может быть опасной если вызвать её с параметром --hard . В приведённом примере файл не был затронут, следовательно команда относительно безопасна. На текущий момент этот магический вызов — всё, что вам нужно знать о команде git reset . Мы рассмотрим в деталях что именно делает reset и как с её помощью делать действительно интересные вещи в разделе Раскрытие тайн reset главы 7. Отмена изменений в файле Что делать, если вы поняли, что не хотите сохранять свои изменения файла CONTRIBUTING.md ? Как можно просто отменить изменения в нём — вернуть к тому состоянию, которое было в последнем коммите (или к начальному после клонирования, или ещё как-то полученному)? Нам повезло, что git status подсказывает и это тоже. В выводе команды из последнего примера список изменений выглядит примерно так: Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Здесь явно сказано как отменить существующие изменения. Давайте так и сделаем: $ git checkout -- CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Как видите, откат изменений выполнен. Важно Важно понимать, что git checkout -- <file> — опасная команда. Все локальные изменения в файле пропадут — Git просто заменит его версией из последнего коммита. Ни в коем случае не используйте эту команду, если вы не уверены, что изменения в файле вам не нужны. Если вы хотите сохранить изменения в файле, но прямо сейчас их нужно отменить, то есть способы получше, такие как ветвление и припрятывание — мы рассмотрим их в главе Ветвление в Git . Помните, всё что попало в коммит почти всегда Git может восстановить. Можно восстановить даже коммиты из веток, которые были удалены, или коммиты, перезаписанные параметром --amend (см. Восстановление данных ). Но всё, что не было включено в коммит и потеряно — скорее всего, потеряно навсегда. Отмена действий с помощью git restore Git версии 2.23.0 представил новую команду: git restore . По сути, это альтернатива git reset, которую мы только что рассмотрели. Начиная с версии 2.23.0, Git будет использовать git restore вместо git reset для многих операций отмены. Давайте проследим наши шаги и отменим действия с помощью git restore вместо git reset . Отмена индексации файла с помощью git restore В следующих двух разделах показано, как работать с индексом и изменениями рабочей копии с помощью git restore . Приятно то, что команда, которую вы используете для определения состояния этих двух областей, также напоминает вам, как отменить изменения в них. Например, предположим, что вы изменили два файла и хотите зафиксировать их как два отдельных изменения, но случайно набираете git add * и индексируете их оба. Как вы можете убрать из индекса один из двух? Команда git status напоминает вам: $ git add * $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) modified: CONTRIBUTING.md renamed: README.md -> README Прямо под текстом «Changes to be committed», написано использовать git restore --staged <file> … для отмены индексации файла. Итак, давайте воспользуемся этим советом, чтобы убрать из индекса файл CONTRIBUTING.md : $ git restore --staged CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) renamed: README.md -> README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Файл CONTRIBUTING.md изменен, но снова не индексирован. Откат изменённого файла с помощью git restore Что, если вы поймёте, что не хотите сохранять изменения в файле CONTRIBUTING.md ? Как легко его откатить — вернуть обратно к тому, как он выглядел при последнем коммите (или изначально клонирован, или каким-либо образом помещён в рабочий каталог)? К счастью, git status тоже говорит, как это сделать. В выводе последнего примера, неиндексированная область выглядит следующим образом: Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Он довольно недвусмысленно говорит, как отменить сделанные вами изменения. Давайте сделаем то, что написано: $ git restore CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) renamed: README.md -> README Важно Важно понимать, что git restore <file> — опасная команда. Любые локальные изменения, внесённые в этот файл, исчезнут — Git просто заменит файл последней зафиксированной версией. Никогда не используйте эту команду, если точно не знаете, нужны ли вам эти несохранённые локальные изменения. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=da | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상품 및 | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_DO | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play�� | 2026-01-13T09:29:23 |
https://git-scm.com/book/zh/v2/Git-%e5%9f%ba%e7%a1%80-%e8%ae%b0%e5%bd%95%e6%af%8f%e6%ac%a1%e6%9b%b4%e6%96%b0%e5%88%b0%e4%bb%93%e5%ba%93 | Git - 记录每次更新到仓库 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 起步 1.1 关于版本控制 1.2 Git 简史 1.3 Git 是什么？ 1.4 命令行 1.5 安装 Git 1.6 初次运行 Git 前的配置 1.7 获取帮助 1.8 总结 2. Git 基础 2.1 获取 Git 仓库 2.2 记录每次更新到仓库 2.3 查看提交历史 2.4 撤消操作 2.5 远程仓库的使用 2.6 打标签 2.7 Git 别名 2.8 总结 3. Git 分支 3.1 分支简介 3.2 分支的新建与合并 3.3 分支管理 3.4 分支开发工作流 3.5 远程分支 3.6 变基 3.7 总结 4. 服务器上的 Git 4.1 协议 4.2 在服务器上搭建 Git 4.3 生成 SSH 公钥 4.4 配置服务器 4.5 Git 守护进程 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第三方托管的选择 4.10 总结 5. 分布式 Git 5.1 分布式工作流程 5.2 向一个项目贡献 5.3 维护项目 5.4 总结 6. GitHub 6.1 账户的创建和配置 6.2 对项目做出贡献 6.3 维护项目 6.4 管理组织 6.5 脚本 GitHub 6.6 总结 7. Git 工具 7.1 选择修订版本 7.2 交互式暂存 7.3 贮藏与清理 7.4 签署工作 7.5 搜索 7.6 重写历史 7.7 重置揭密 7.8 高级合并 7.9 Rerere 7.10 使用 Git 调试 7.11 子模块 7.12 打包 7.13 替换 7.14 凭证存储 7.15 总结 8. 自定义 Git 8.1 配置 Git 8.2 Git 属性 8.3 Git 钩子 8.4 使用强制策略的一个例子 8.5 总结 9. Git 与其他系统 9.1 作为客户端的 Git 9.2 迁移到 Git 9.3 总结 10. Git 内部原理 10.1 底层命令与上层命令 10.2 Git 对象 10.3 Git 引用 10.4 包文件 10.5 引用规范 10.6 传输协议 10.7 维护与数据恢复 10.8 环境变量 10.9 总结 A1. 附录 A: 在其它环境中使用 Git A1.1 图形界面 A1.2 Visual Studio 中的 Git A1.3 Visual Studio Code 中的 Git A1.4 IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 中的 Git A1.5 Sublime Text 中的 Git A1.6 Bash 中的 Git A1.7 Zsh 中的 Git A1.8 PowerShell 中的 Git A1.9 总结 A2. 附录 B: 在你的应用中嵌入 Git A2.1 命令行 Git 方式 A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. 附录 C: Git 命令 A3.1 设置与配置 A3.2 获取与创建项目 A3.3 快照基础 A3.4 分支与合并 A3.5 项目分享与更新 A3.6 检查与比较 A3.7 调试 A3.8 补丁 A3.9 邮件 A3.10 外部系统 A3.11 管理 A3.12 底层命令 2nd Edition 2.2 Git 基础 - 记录每次更新到仓库 记录每次更新到仓库 现在我们的机器上有了一个 真实项目 的 Git 仓库，并从这个仓库中检出了所有文件的 工作副本 。 通常，你会对这些文件做些修改，每当完成了一个阶段的目标，想要将记录下它时，就将它提交到仓库。 请记住，你工作目录下的每一个文件都不外乎这两种状态： 已跟踪 或 未跟踪 。 已跟踪的文件是指那些被纳入了版本控制的文件，在上一次快照中有它们的记录，在工作一段时间后， 它们的状态可能是未修改，已修改或已放入暂存区。简而言之，已跟踪的文件就是 Git 已经知道的文件。 工作目录中除已跟踪文件外的其它所有文件都属于未跟踪文件，它们既不存在于上次快照的记录中，也没有被放入暂存区。 初次克隆某个仓库的时候，工作目录中的所有文件都属于已跟踪文件，并处于未修改状态，因为 Git 刚刚检出了它们， 而你尚未编辑过它们。 编辑过某些文件之后，由于自上次提交后你对它们做了修改，Git 将它们标记为已修改文件。 在工作时，你可以选择性地将这些修改过的文件放入暂存区，然后提交所有已暂存的修改，如此反复。 Figure 8. 文件的状态变化周期 检查当前文件状态 可以用 git status 命令查看哪些文件处于什么状态。 如果在克隆仓库后立即使用此命令，会看到类似这样的输出： $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean 这说明你现在的工作目录相当干净。换句话说，所有已跟踪文件在上次提交后都未被更改过。 此外，上面的信息还表明，当前目录下没有出现任何处于未跟踪状态的新文件，否则 Git 会在这里列出来。 最后，该命令还显示了当前所在分支，并告诉你这个分支同远程服务器上对应的分支没有偏离。 现在，分支名是“master”，这是默认的分支名。 我们在 Git 分支 中会详细讨论分支和引用。 现在，让我们在项目下创建一个新的 README 文件。 如果之前并不存在这个文件，使用 git status 命令，你将看到一个新的未跟踪文件： $ echo 'My Project' > README $ git status On branch master Your branch is up-to-date with 'origin/master'. Untracked files: (use "git add <file>..." to include in what will be committed) README nothing added to commit but untracked files present (use "git add" to track) 在状态报告中可以看到新建的 README 文件出现在 Untracked files 下面。 未跟踪的文件意味着 Git 在之前的快照（提交）中没有这些文件；Git 不会自动将之纳入跟踪范围，除非你明明白白地告诉它“我需要跟踪该文件”。 这样的处理让你不必担心将生成的二进制文件或其它不想被跟踪的文件包含进来。 不过现在的例子中，我们确实想要跟踪管理 README 这个文件。 跟踪新文件 使用命令 git add 开始跟踪一个文件。 所以，要跟踪 README 文件，运行： $ git add README 此时再运行 git status 命令，会看到 README 文件已被跟踪，并处于暂存状态： $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git restore --staged <file>..." to unstage) new file: README 只要在 Changes to be committed 这行下面的，就说明是已暂存状态。 如果此时提交，那么该文件在你运行 git add 时的版本将被留存在后续的历史记录中。 你可能会想起之前我们使用 git init 后就运行了 git add <files> 命令，开始跟踪当前目录下的文件。 git add 命令使用文件或目录的路径作为参数；如果参数是目录的路径，该命令将递归地跟踪该目录下的所有文件。 暂存已修改的文件 现在我们来修改一个已被跟踪的文件。 如果你修改了一个名为 CONTRIBUTING.md 的已被跟踪的文件，然后运行 git status 命令，会看到下面内容： $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md 文件 CONTRIBUTING.md 出现在 Changes not staged for commit 这行下面，说明已跟踪文件的内容发生了变化，但还没有放到暂存区。 要暂存这次更新，需要运行 git add 命令。 这是个多功能命令：可以用它开始跟踪新文件，或者把已跟踪的文件放到暂存区，还能用于合并时把有冲突的文件标记为已解决状态等。 将这个命令理解为“精确地将内容添加到下一次提交中”而不是“将一个文件添加到项目中”要更加合适。 现在让我们运行 git add 将“CONTRIBUTING.md”放到暂存区，然后再看看 git status 的输出： $ git add CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md 现在两个文件都已暂存，下次提交时就会一并记录到仓库。 假设此时，你想要在 CONTRIBUTING.md 里再加条注释。 重新编辑存盘后，准备好提交。 不过且慢，再运行 git status 看看： $ vim CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md 怎么回事？ 现在 CONTRIBUTING.md 文件同时出现在暂存区和非暂存区。 这怎么可能呢？ 好吧，实际上 Git 只不过暂存了你运行 git add 命令时的版本。 如果你现在提交， CONTRIBUTING.md 的版本是你最后一次运行 git add 命令时的那个版本，而不是你运行 git commit 时，在工作目录中的当前版本。 所以，运行了 git add 之后又作了修订的文件，需要重新运行 git add 把最新版本重新暂存起来： $ git add CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md 状态简览 git status 命令的输出十分详细，但其用语有些繁琐。 Git 有一个选项可以帮你缩短状态命令的输出，这样可以以简洁的方式查看更改。 如果你使用 git status -s 命令或 git status --short 命令，你将得到一种格式更为紧凑的输出。 $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt 新添加的未跟踪文件前面有 ?? 标记，新添加到暂存区中的文件前面有 A 标记，修改过的文件前面有 M 标记。 输出中有两栏，左栏指明了暂存区的状态，右栏指明了工作区的状态。例如，上面的状态报告显示： README 文件在工作区已修改但尚未暂存，而 lib/simplegit.rb 文件已修改且已暂存。 Rakefile 文件已修改，暂存后又作了修改，因此该文件的修改中既有已暂存的部分，又有未暂存的部分。 忽略文件 一般我们总会有些文件无需纳入 Git 的管理，也不希望它们总出现在未跟踪文件列表。 通常都是些自动生成的文件，比如日志文件，或者编译过程中创建的临时文件等。 在这种情况下，我们可以创建一个名为 .gitignore 的文件，列出要忽略的文件的模式。 来看一个实际的 .gitignore 例子： $ cat .gitignore *.[oa] *~ 第一行告诉 Git 忽略所有以 .o 或 .a 结尾的文件。一般这类对象文件和存档文件都是编译过程中出现的。 第二行告诉 Git 忽略所有名字以波浪符（~）结尾的文件，许多文本编辑软件（比如 Emacs）都用这样的文件名保存副本。 此外，你可能还需要忽略 log，tmp 或者 pid 目录，以及自动生成的文档等等。 要养成一开始就为你的新仓库设置好 .gitignore 文件的习惯，以免将来误提交这类无用的文件。 文件 .gitignore 的格式规范如下： 所有空行或者以 # 开头的行都会被 Git 忽略。 可以使用标准的 glob 模式匹配，它会递归地应用在整个工作区中。 匹配模式可以以（ / ）开头防止递归。 匹配模式可以以（ / ）结尾指定目录。 要忽略指定模式以外的文件或目录，可以在模式前加上叹号（ ! ）取反。 所谓的 glob 模式是指 shell 所使用的简化了的正则表达式。 星号（ * ）匹配零个或多个任意字符； [abc] 匹配任何一个列在方括号中的字符 （这个例子要么匹配一个 a，要么匹配一个 b，要么匹配一个 c）； 问号（ ? ）只匹配一个任意字符；如果在方括号中使用短划线分隔两个字符， 表示所有在这两个字符范围内的都可以匹配（比如 [0-9] 表示匹配所有 0 到 9 的数字）。 使用两个星号（ ** ）表示匹配任意中间目录，比如 a/**/z 可以匹配 a/z 、 a/b/z 或 a/b/c/z 等。 我们再看一个 .gitignore 文件的例子： # 忽略所有的 .a 文件 *.a # 但跟踪所有的 lib.a，即便你在前面忽略了 .a 文件 !lib.a # 只忽略当前目录下的 TODO 文件，而不忽略 subdir/TODO /TODO # 忽略任何目录下名为 build 的文件夹 build/ # 忽略 doc/notes.txt，但不忽略 doc/server/arch.txt doc/*.txt # 忽略 doc/ 目录及其所有子目录下的 .pdf 文件 doc/**/*.pdf Tip GitHub 有一个十分详细的针对数十种项目及语言的 .gitignore 文件列表， 你可以在 https://github.com/github/gitignore 找到它。 Note 在最简单的情况下，一个仓库可能只根目录下有一个 .gitignore 文件，它递归地应用到整个仓库中。 然而，子目录下也可以有额外的 .gitignore 文件。子目录中的 .gitignore 文件中的规则只作用于它所在的目录中。 （Linux 内核的源码库拥有 206 个 .gitignore 文件。） 多个 .gitignore 文件的具体细节超出了本书的范围，更多详情见 man gitignore 。 查看已暂存和未暂存的修改 如果 git status 命令的输出对于你来说过于简略，而你想知道具体修改了什么地方，可以用 git diff 命令。 稍后我们会详细介绍 git diff ，你通常可能会用它来回答这两个问题：当前做的哪些更新尚未暂存？ 有哪些更新已暂存并准备好下次提交？ 虽然 git status 已经通过在相应栏下列出文件名的方式回答了这个问题，但 git diff 能通过文件补丁的格式更加具体地显示哪些行发生了改变。 假如再次修改 README 文件后暂存，然后编辑 CONTRIBUTING.md 文件后先不暂存， 运行 status 命令将会看到： $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md 要查看尚未暂存的文件更新了哪些部分，不加参数直接输入 git diff ： $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,8 @@ branch directly, things can get messy. Please include a nice description of your changes when you submit your PR; if we have to read the whole diff to figure out why you're contributing in the first place, you're less likely to get feedback and have your change -merged in. +merged in. Also, split your changes into comprehensive chunks if your patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's 此命令比较的是工作目录中当前文件和暂存区域快照之间的差异。 也就是修改之后还没有暂存起来的变化内容。 若要查看已暂存的将要添加到下次提交里的内容，可以用 git diff --staged 命令。 这条命令将比对已暂存文件与最后一次提交的文件差异： $ git diff --staged diff --git a/README b/README new file mode 100644 index 0000000..03902a1 --- /dev/null +++ b/README @@ -0,0 +1 @@ +My Project 请注意，git diff 本身只显示尚未暂存的改动，而不是自上次提交以来所做的所有改动。 所以有时候你一下子暂存了所有更新过的文件，运行 git diff 后却什么也没有，就是这个原因。 像之前说的，暂存 CONTRIBUTING.md 后再编辑，可以使用 git status 查看已被暂存的修改或未被暂存的修改。 如果我们的环境（终端输出）看起来如下： $ git add CONTRIBUTING.md $ echo '# test line' >> CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md 现在运行 git diff 看暂存前后的变化： $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 643e24f..87f08c8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -119,3 +119,4 @@ at the ## Starter Projects See our [projects list](https://github.com/libgit2/libgit2/blob/development/PROJECTS.md). +# test line 然后用 git diff --cached 查看已经暂存起来的变化（ --staged 和 --cached 是同义词）： $ git diff --cached diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,8 @@ branch directly, things can get messy. Please include a nice description of your changes when you submit your PR; if we have to read the whole diff to figure out why you're contributing in the first place, you're less likely to get feedback and have your change -merged in. +merged in. Also, split your changes into comprehensive chunks if your patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's Note Git Diff 的插件版本 在本书中，我们使用 git diff 来分析文件差异。 但是你也可以使用图形化的工具或外部 diff 工具来比较差异。 可以使用 git difftool 命令来调用 emerge 或 vimdiff 等软件（包括商业软件）输出 diff 的分析结果。 使用 git difftool --tool-help 命令来看你的系统支持哪些 Git Diff 插件。 提交更新 现在的暂存区已经准备就绪，可以提交了。 在此之前，请务必确认还有什么已修改或新建的文件还没有 git add 过， 否则提交的时候不会记录这些尚未暂存的变化。 这些已修改但未暂存的文件只会保留在本地磁盘。 所以，每次准备提交前，先用 git status 看下，你所需要的文件是不是都已暂存起来了， 然后再运行提交命令 git commit ： $ git commit 这样会启动你选择的文本编辑器来输入提交说明。 Note 启动的编辑器是通过 Shell 的环境变量 EDITOR 指定的，一般为 vim 或 emacs。 当然也可以按照 起步 介绍的方式， 使用 git config --global core.editor 命令设置你喜欢的编辑器。 编辑器会显示类似下面的文本信息（本例选用 Vim 的屏显方式展示）： # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # new file: README # modified: CONTRIBUTING.md # ~ ~ ~ ".git/COMMIT_EDITMSG" 9L, 283C 可以看到，默认的提交消息包含最后一次运行 git status 的输出，放在注释行里，另外开头还有一个空行，供你输入提交说明。 你完全可以去掉这些注释行，不过留着也没关系，多少能帮你回想起这次更新的内容有哪些。 Note 更详细的内容修改提示可以用 -v 选项查看，这会将你所作的更改的 diff 输出呈现在编辑器中，以便让你知道本次提交具体作出哪些修改。 退出编辑器时，Git 会丢弃注释行，用你输入的提交说明生成一次提交。 另外，你也可以在 commit 命令后添加 -m 选项，将提交信息与命令放在同一行，如下所示： $ git commit -m "Story 182: Fix benchmarks for speed" [master 463dc4f] Story 182: Fix benchmarks for speed 2 files changed, 2 insertions(+) create mode 100644 README 好，现在你已经创建了第一个提交！ 可以看到，提交后它会告诉你，当前是在哪个分支（ master ）提交的，本次提交的完整 SHA-1 校验和是什么（ 463dc4f ），以及在本次提交中，有多少文件修订过，多少行添加和删改过。 请记住，提交时记录的是放在暂存区域的快照。 任何还未暂存文件的仍然保持已修改状态，可以在下次提交时纳入版本管理。 每一次运行提交操作，都是对你项目作一次快照，以后可以回到这个状态，或者进行比较。 跳过使用暂存区域 尽管使用暂存区域的方式可以精心准备要提交的细节，但有时候这么做略显繁琐。 Git 提供了一个跳过使用暂存区域的方式， 只要在提交的时候，给 git commit 加上 -a 选项，Git 就会自动把所有已经跟踪过的文件暂存起来一并提交，从而跳过 git add 步骤： $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md no changes added to commit (use "git add" and/or "git commit -a") $ git commit -a -m 'added new benchmarks' [master 83e38c7] added new benchmarks 1 file changed, 5 insertions(+), 0 deletions(-) 看到了吗？提交之前不再需要 git add 文件“CONTRIBUTING.md”了。 这是因为 -a 选项使本次提交包含了所有修改过的文件。 这很方便，但是要小心，有时这个选项会将不需要的文件添加到提交中。 移除文件 要从 Git 中移除某个文件，就必须要从已跟踪文件清单中移除（确切地说，是从暂存区域移除），然后提交。 可以用 git rm 命令完成此项工作，并连带从工作目录中删除指定的文件，这样以后就不会出现在未跟踪文件清单中了。 如果只是简单地从工作目录中手工删除文件，运行 git status 时就会在 “Changes not staged for commit” 部分（也就是 未暂存清单 ）看到： $ rm PROJECTS.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add/rm <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) deleted: PROJECTS.md no changes added to commit (use "git add" and/or "git commit -a") 然后再运行 git rm 记录此次移除文件的操作： $ git rm PROJECTS.md rm 'PROJECTS.md' $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) deleted: PROJECTS.md 下一次提交时，该文件就不再纳入版本管理了。 如果要删除之前修改过或已经放到暂存区的文件，则必须使用强制删除选项 -f （译注：即 force 的首字母）。 这是一种安全特性，用于防止误删尚未添加到快照的数据，这样的数据不能被 Git 恢复。 另外一种情况是，我们想把文件从 Git 仓库中删除（亦即从暂存区域移除），但仍然希望保留在当前工作目录中。 换句话说，你想让文件保留在磁盘，但是并不想让 Git 继续跟踪。 当你忘记添加 .gitignore 文件，不小心把一个很大的日志文件或一堆 .a 这样的编译生成文件添加到暂存区时，这一做法尤其有用。 为达到这一目的，使用 --cached 选项： $ git rm --cached README git rm 命令后面可以列出文件或者目录的名字，也可以使用 glob 模式。比如： $ git rm log/\*.log 注意到星号 * 之前的反斜杠 \ ， 因为 Git 有它自己的文件模式扩展匹配方式，所以我们不用 shell 来帮忙展开。 此命令删除 log/ 目录下扩展名为 .log 的所有文件。 类似的比如： $ git rm \*~ 该命令会删除所有名字以 ~ 结尾的文件。 移动文件 不像其它的 VCS 系统，Git 并不显式跟踪文件移动操作。 如果在 Git 中重命名了某个文件，仓库中存储的元数据并不会体现出这是一次改名操作。 不过 Git 非常聪明，它会推断出究竟发生了什么，至于具体是如何做到的，我们稍后再谈。 既然如此，当你看到 Git 的 mv 命令时一定会困惑不已。 要在 Git 中对文件改名，可以这么做： $ git mv file_from file_to 它会恰如预期般正常工作。 实际上，即便此时查看状态信息，也会明白无误地看到关于重命名操作的说明： $ git mv README.md README $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README 其实，运行 git mv 就相当于运行了下面三条命令： $ mv README.md README $ git rm README.md $ git add README 如此分开操作，Git 也会意识到这是一次重命名，所以不管何种方式结果都一样。 两者唯一的区别在于， git mv 是一条命令而非三条命令，直接使用 git mv 方便得多。 不过在使用其他工具重命名文件时，记得在提交前 git rm 删除旧文件名，再 git add 添加新文件名。 prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/cs/v2/Git-na-serveru-Shrnut%c3%ad | Git - Shrnutí About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Úvod 1.1 Správa verzí 1.2 Stručná historie systému Git 1.3 Základy systému Git 1.4 Příkazový řádek 1.5 Instalace systému Git 1.6 První nastavení systému Git 1.7 Získání nápovědy 1.8 Shrnutí 2. Základy práce se systémem Git 2.1 Získání repozitáře Git 2.2 Nahrávání změn do repozitáře 2.3 Zobrazení historie revizí 2.4 Návrat do předchozího stavu 2.5 Práce se vzdálenými repozitáři 2.6 Používání značek 2.7 Aliasy v Gitu 2.8 Shrnutí 3. Větve v systému Git 3.1 Větve v kostce 3.2 Základy větvení a slučování 3.3 Správa větví 3.4 Postupy při práci s větvemi 3.5 Vzdálené větve 3.6 Přeskládání 3.7 Shrnutí 4. Git na serveru 4.1 Protokoly 4.2 Zprovoznění Gitu na serveru 4.3 Generování veřejného klíče SSH 4.4 Nastavení serveru 4.5 Démon Git 4.6 Chytrý HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti hostování u třetí strany 4.10 Shrnutí 5. Distribuovaný Git 5.1 Distribuované pracovní postupy 5.2 Přispívání do projektu 5.3 Správa projektu 5.4 Shrnutí 6. GitHub 6.1 Zřízení účtu a úprava konfigurace 6.2 Přispívání do projektu 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Shrnutí 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Ladění v systému Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Shrnutí 8. Customizing Git 8.1 Git Configuration 8.2 Atributy Git 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Shrnutí 9. Git a ostatní systémy 9.1 Git as a Client 9.2 Migrating to Git 9.3 Shrnutí 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Balíčkové soubory 10.5 The Refspec 10.6 Přenosové protokoly 10.7 Správa a obnova dat 10.8 Environment Variables 10.9 Shrnutí A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Shrnutí A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.10 Git na serveru - Shrnutí Shrnutí Existuje několik možností, jak vytvořit a zprovoznit vzdálený gitový repozitář tak, abyste mohli spolupracovat s ostatními uživateli nebo sdílet svou práci. Provoz vlastního serveru vám dává celou řadu možností řízení a umožňuje provozovat server za vaším firewallem. Nastavení a správa takového serveru však obecně bývají časově náročné. Umístíte-li data na hostovaný server, bude nastavení a správa jednoduchá. Svůj zdrojový kód však v takovém případě ukládáte na cizím serveru, což některé organizace nedovolují. Teď už byste se měli umět rozhodnout, které řešení nebo jaká kombinace řešení se pro vás a pro vaši organizaci hodí. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_PY | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 P | 2026-01-13T09:29:23 |
https://git-scm.com/book/be/v2/Git-Basics-Recording-Changes-to-the-Repository | Git - Recording Changes to the Repository About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Першыя крокі 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Падсумаваньне 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Дадатак A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Дадатак B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Дадатак C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.2 Git Basics - Recording Changes to the Repository Recording Changes to the Repository At this point, you should have a bona fide Git repository on your local machine, and a checkout or working copy of all of its files in front of you. Typically, you’ll want to start making changes and committing snapshots of those changes into your repository each time the project reaches a state you want to record. Remember that each file in your working directory can be in one of two states: tracked or untracked . Tracked files are files that were in the last snapshot; they can be unmodified, modified, or staged. In short, tracked files are files that Git knows about. Untracked files are everything else — any files in your working directory that were not in your last snapshot and are not in your staging area. When you first clone a repository, all of your files will be tracked and unmodified because Git just checked them out and you haven’t edited anything. As you edit files, Git sees them as modified, because you’ve changed them since your last commit. As you work, you selectively stage these modified files and then commit all those staged changes, and the cycle repeats. Малюнак 8. The lifecycle of the status of your files Checking the Status of Your Files The main tool you use to determine which files are in which state is the git status command. If you run this command directly after a clone, you should see something like this: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working tree clean This means you have a clean working directory; in other words, none of your tracked files are modified. Git also doesn’t see any untracked files, or they would be listed here. Finally, the command tells you which branch you’re on and informs you that it has not diverged from the same branch on the server. For now, that branch is always master , which is the default; you won’t worry about it here. Git Branching will go over branches and references in detail. Let’s say you add a new file to your project, a simple README file. If the file didn’t exist before, and you run git status , you see your untracked file like so: $ echo 'My Project' > README $ git status On branch master Your branch is up-to-date with 'origin/master'. Untracked files: (use "git add <file>..." to include in what will be committed) README nothing added to commit but untracked files present (use "git add" to track) You can see that your new README file is untracked, because it’s under the “Untracked files” heading in your status output. Untracked basically means that Git sees a file you didn’t have in the previous snapshot (commit); Git won’t start including it in your commit snapshots until you explicitly tell it to do so. It does this so you don’t accidentally begin including generated binary files or other files that you did not mean to include. You do want to start including README , so let’s start tracking the file. Tracking New Files In order to begin tracking a new file, you use the command git add . To begin tracking the README file, you can run this: $ git add README If you run your status command again, you can see that your README file is now tracked and staged to be committed: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git restore --staged <file>..." to unstage) new file: README You can tell that it’s staged because it’s under the “Changes to be committed” heading. If you commit at this point, the version of the file at the time you ran git add is what will be in the subsequent historical snapshot. You may recall that when you ran git init earlier, you then ran git add <files> — that was to begin tracking files in your directory. The git add command takes a path name for either a file or a directory; if it’s a directory, the command adds all the files in that directory recursively. Staging Modified Files Let’s change a file that was already tracked. If you change a previously tracked file called CONTRIBUTING.md and then run your git status command again, you get something that looks like this: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md The CONTRIBUTING.md file appears under a section named “Changes not staged for commit” — which means that a file that is tracked has been modified in the working directory but not yet staged. To stage it, you run the git add command. git add is a multipurpose command — you use it to begin tracking new files, to stage files, and to do other things like marking merge-conflicted files as resolved. It may be helpful to think of it more as “add precisely this content to the next commit” rather than “add this file to the project”. Let’s run git add now to stage the CONTRIBUTING.md file, and then run git status again: $ git add CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Both files are staged and will go into your next commit. At this point, suppose you remember one little change that you want to make in CONTRIBUTING.md before you commit it. You open it again and make that change, and you’re ready to commit. However, let’s run git status one more time: $ vim CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md What the heck? Now CONTRIBUTING.md is listed as both staged and unstaged. How is that possible? It turns out that Git stages a file exactly as it is when you run the git add command. If you commit now, the version of CONTRIBUTING.md as it was when you last ran the git add command is how it will go into the commit, not the version of the file as it looks in your working directory when you run git commit . If you modify a file after you run git add , you have to run git add again to stage the latest version of the file: $ git add CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Short Status While the git status output is pretty comprehensive, it’s also quite wordy. Git also has a short status flag so you can see your changes in a more compact way. If you run git status -s or git status --short you get a far more simplified output from the command: $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt New files that aren’t tracked have a ?? next to them, new files that have been added to the staging area have an A , modified files have an M and so on. There are two columns to the output — the left-hand column indicates the status of the staging area and the right-hand column indicates the status of the working tree. So for example in that output, the README file is modified in the working directory but not yet staged, while the lib/simplegit.rb file is modified and staged. The Rakefile was modified, staged and then modified again, so there are changes to it that are both staged and unstaged. Ignoring Files Often, you’ll have a class of files that you don’t want Git to automatically add or even show you as being untracked. These are generally automatically generated files such as log files or files produced by your build system. In such cases, you can create a file listing patterns to match them named .gitignore . Here is an example .gitignore file: $ cat .gitignore *.[oa] *~ The first line tells Git to ignore any files ending in “.o” or “.a” — object and archive files that may be the product of building your code. The second line tells Git to ignore all files whose names end with a tilde ( ~ ), which is used by many text editors such as Emacs to mark temporary files. You may also include a log, tmp, or pid directory; automatically generated documentation; and so on. Setting up a .gitignore file for your new repository before you get going is generally a good idea so you don’t accidentally commit files that you really don’t want in your Git repository. The rules for the patterns you can put in the .gitignore file are as follows: Blank lines or lines starting with # are ignored. Standard glob patterns work, and will be applied recursively throughout the entire working tree. You can start patterns with a forward slash ( / ) to avoid recursivity. You can end patterns with a forward slash ( / ) to specify a directory. You can negate a pattern by starting it with an exclamation point ( ! ). Glob patterns are like simplified regular expressions that shells use. An asterisk ( * ) matches zero or more characters; [abc] matches any character inside the brackets (in this case a, b, or c); a question mark ( ? ) matches a single character; and brackets enclosing characters separated by a hyphen ( [0-9] ) matches any character between them (in this case 0 through 9). You can also use two asterisks to match nested directories; a/**/z would match a/z , a/b/z , a/b/c/z , and so on. Here is another example .gitignore file: # ignore all .a files *.a # but do track lib.a, even though you're ignoring .a files above !lib.a # only ignore the TODO file in the current directory, not subdir/TODO /TODO # ignore all files in any directory named build build/ # ignore doc/notes.txt, but not doc/server/arch.txt doc/*.txt # ignore all .pdf files in the doc/ directory and any of its subdirectories doc/**/*.pdf Падказка GitHub maintains a fairly comprehensive list of good .gitignore file examples for dozens of projects and languages at https://github.com/github/gitignore if you want a starting point for your project. Заўвага In the simple case, a repository might have a single .gitignore file in its root directory, which applies recursively to the entire repository. However, it is also possible to have additional .gitignore files in subdirectories. The rules in these nested .gitignore files apply only to the files under the directory where they are located. The Linux kernel source repository has 206 .gitignore files. It is beyond the scope of this book to get into the details of multiple .gitignore files; see man gitignore for the details. Viewing Your Staged and Unstaged Changes If the git status command is too vague for you — you want to know exactly what you changed, not just which files were changed — you can use the git diff command. We’ll cover git diff in more detail later, but you’ll probably use it most often to answer these two questions: What have you changed but not yet staged? And what have you staged that you are about to commit? Although git status answers those questions very generally by listing the file names, git diff shows you the exact lines added and removed — the patch, as it were. Let’s say you edit and stage the README file again and then edit the CONTRIBUTING.md file without staging it. If you run your git status command, you once again see something like this: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md To see what you’ve changed but not yet staged, type git diff with no other arguments: $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,8 @@ branch directly, things can get messy. Please include a nice description of your changes when you submit your PR; if we have to read the whole diff to figure out why you're contributing in the first place, you're less likely to get feedback and have your change -merged in. +merged in. Also, split your changes into comprehensive chunks if your patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's That command compares what is in your working directory with what is in your staging area. The result tells you the changes you’ve made that you haven’t yet staged. If you want to see what you’ve staged that will go into your next commit, you can use git diff --staged . This command compares your staged changes to your last commit: $ git diff --staged diff --git a/README b/README new file mode 100644 index 0000000..03902a1 --- /dev/null +++ b/README @@ -0,0 +1 @@ +My Project It’s important to note that git diff by itself doesn’t show all changes made since your last commit — only changes that are still unstaged. If you’ve staged all of your changes, git diff will give you no output. For another example, if you stage the CONTRIBUTING.md file and then edit it, you can use git diff to see the changes in the file that are staged and the changes that are unstaged. If our environment looks like this: $ git add CONTRIBUTING.md $ echo '# test line' >> CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Now you can use git diff to see what is still unstaged: $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 643e24f..87f08c8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -119,3 +119,4 @@ at the ## Starter Projects See our [projects list](https://github.com/libgit2/libgit2/blob/development/PROJECTS.md). +# test line and git diff --cached to see what you’ve staged so far ( --staged and --cached are synonyms): $ git diff --cached diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,8 @@ branch directly, things can get messy. Please include a nice description of your changes when you submit your PR; if we have to read the whole diff to figure out why you're contributing in the first place, you're less likely to get feedback and have your change -merged in. +merged in. Also, split your changes into comprehensive chunks if your patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's Заўвага Git Diff in an External Tool We will continue to use the git diff command in various ways throughout the rest of the book. There is another way to look at these diffs if you prefer a graphical or external diff viewing program instead. If you run git difftool instead of git diff , you can view any of these diffs in software like emerge, vimdiff and many more (including commercial products). Run git difftool --tool-help to see what is available on your system. Committing Your Changes Now that your staging area is set up the way you want it, you can commit your changes. Remember that anything that is still unstaged — any files you have created or modified that you haven’t run git add on since you edited them — won’t go into this commit. They will stay as modified files on your disk. In this case, let’s say that the last time you ran git status , you saw that everything was staged, so you’re ready to commit your changes. The simplest way to commit is to type git commit : $ git commit Doing so launches your editor of choice. Заўвага This is set by your shell’s EDITOR environment variable — usually vim or emacs, although you can configure it with whatever you want using the git config --global core.editor command as you saw in Першыя крокі . The editor displays the following text (this example is a Vim screen): # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # new file: README # modified: CONTRIBUTING.md # ~ ~ ~ ".git/COMMIT_EDITMSG" 9L, 283C You can see that the default commit message contains the latest output of the git status command commented out and one empty line on top. You can remove these comments and type your commit message, or you can leave them there to help you remember what you’re committing. Заўвага For an even more explicit reminder of what you’ve modified, you can pass the -v option to git commit . Doing so also puts the diff of your change in the editor so you can see exactly what changes you’re committing. When you exit the editor, Git creates your commit with that commit message (with the comments and diff stripped out). Alternatively, you can type your commit message inline with the commit command by specifying it after a -m flag, like this: $ git commit -m "Story 182: fix benchmarks for speed" [master 463dc4f] Story 182: fix benchmarks for speed 2 files changed, 2 insertions(+) create mode 100644 README Now you’ve created your first commit! You can see that the commit has given you some output about itself: which branch you committed to ( master ), what SHA-1 checksum the commit has ( 463dc4f ), how many files were changed, and statistics about lines added and removed in the commit. Remember that the commit records the snapshot you set up in your staging area. Anything you didn’t stage is still sitting there modified; you can do another commit to add it to your history. Every time you perform a commit, you’re recording a snapshot of your project that you can revert to or compare to later. Skipping the Staging Area Although it can be amazingly useful for crafting commits exactly how you want them, the staging area is sometimes a bit more complex than you need in your workflow. If you want to skip the staging area, Git provides a simple shortcut. Adding the -a option to the git commit command makes Git automatically stage every file that is already tracked before doing the commit, letting you skip the git add part: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md no changes added to commit (use "git add" and/or "git commit -a") $ git commit -a -m 'Add new benchmarks' [master 83e38c7] Add new benchmarks 1 file changed, 5 insertions(+), 0 deletions(-) Notice how you don’t have to run git add on the CONTRIBUTING.md file in this case before you commit. That’s because the -a flag includes all changed files. This is convenient, but be careful; sometimes this flag will cause you to include unwanted changes. Removing Files To remove a file from Git, you have to remove it from your tracked files (more accurately, remove it from your staging area) and then commit. The git rm command does that, and also removes the file from your working directory so you don’t see it as an untracked file the next time around. If you simply remove the file from your working directory, it shows up under the “Changes not staged for commit” (that is, unstaged ) area of your git status output: $ rm PROJECTS.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add/rm <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) deleted: PROJECTS.md no changes added to commit (use "git add" and/or "git commit -a") Then, if you run git rm , it stages the file’s removal: $ git rm PROJECTS.md rm 'PROJECTS.md' $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) deleted: PROJECTS.md The next time you commit, the file will be gone and no longer tracked. If you modified the file or had already added it to the staging area, you must force the removal with the -f option. This is a safety feature to prevent accidental removal of data that hasn’t yet been recorded in a snapshot and that can’t be recovered from Git. Another useful thing you may want to do is to keep the file in your working tree but remove it from your staging area. In other words, you may want to keep the file on your hard drive but not have Git track it anymore. This is particularly useful if you forgot to add something to your .gitignore file and accidentally staged it, like a large log file or a bunch of .a compiled files. To do this, use the --cached option: $ git rm --cached README You can pass files, directories, and file-glob patterns to the git rm command. That means you can do things such as: $ git rm log/\*.log Note the backslash ( \ ) in front of the * . This is necessary because Git does its own filename expansion in addition to your shell’s filename expansion. This command removes all files that have the .log extension in the log/ directory. Or, you can do something like this: $ git rm \*~ This command removes all files whose names end with a ~ . Moving Files Unlike many other VCSs, Git doesn’t explicitly track file movement. If you rename a file in Git, no metadata is stored in Git that tells it you renamed the file. However, Git is pretty smart about figuring that out after the fact — we’ll deal with detecting file movement a bit later. Thus it’s a bit confusing that Git has a mv command. If you want to rename a file in Git, you can run something like: $ git mv file_from file_to and it works fine. In fact, if you run something like this and look at the status, you’ll see that Git considers it a renamed file: $ git mv README.md README $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README However, this is equivalent to running something like this: $ mv README.md README $ git rm README.md $ git add README Git figures out that it’s a rename implicitly, so it doesn’t matter if you rename a file that way or with the mv command. The only real difference is that git mv is one command instead of three — it’s a convenience function. More importantly, you can use any tool you like to rename a file, and address the add/rm later, before you commit. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=ln | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상품 및 | 2026-01-13T09:29:23 |
https://git-scm.com/book/de/v2/GitHub-Ein-Projekt-betreuen | Git - Ein Projekt betreuen About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Erste Schritte 1.1 Was ist Versionsverwaltung? 1.2 Kurzer Überblick über die Historie von Git 1.3 Was ist Git? 1.4 Die Kommandozeile 1.5 Git installieren 1.6 Git Basis-Konfiguration 1.7 Hilfe finden 1.8 Zusammenfassung 2. Git Grundlagen 2.1 Ein Git-Repository anlegen 2.2 Änderungen nachverfolgen und im Repository speichern 2.3 Anzeigen der Commit-Historie 2.4 Ungewollte Änderungen rückgängig machen 2.5 Mit Remotes arbeiten 2.6 Taggen 2.7 Git Aliases 2.8 Zusammenfassung 3. Git Branching 3.1 Branches auf einen Blick 3.2 Einfaches Branching und Merging 3.3 Branch-Management 3.4 Branching-Workflows 3.5 Remote-Branches 3.6 Rebasing 3.7 Zusammenfassung 4. Git auf dem Server 4.1 Die Protokolle 4.2 Git auf einem Server einrichten 4.3 Erstellung eines SSH-Public-Keys 4.4 Einrichten des Servers 4.5 Git-Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Von Drittanbietern gehostete Optionen 4.10 Zusammenfassung 5. Verteiltes Git 5.1 Verteilter Arbeitsablauf 5.2 An einem Projekt mitwirken 5.3 Ein Projekt verwalten 5.4 Zusammenfassung 6. GitHub 6.1 Einrichten und Konfigurieren eines Kontos 6.2 Mitwirken an einem Projekt 6.3 Ein Projekt betreuen 6.4 Verwalten einer Organisation 6.5 Skripte mit GitHub 6.6 Zusammenfassung 7. Git Tools 7.1 Revisions-Auswahl 7.2 Interaktives Stagen 7.3 Stashen und Bereinigen 7.4 Deine Arbeit signieren 7.5 Suchen 7.6 Den Verlauf umschreiben 7.7 Reset entzaubert 7.8 Fortgeschrittenes Merging 7.9 Rerere 7.10 Debuggen mit Git 7.11 Submodule 7.12 Bundling 7.13 Replace (Ersetzen) 7.14 Anmeldeinformationen speichern 7.15 Zusammenfassung 8. Git einrichten 8.1 Git Konfiguration 8.2 Git-Attribute 8.3 Git Hooks 8.4 Beispiel für Git-forcierte Regeln 8.5 Zusammenfassung 9. Git und andere VCS-Systeme 9.1 Git als Client 9.2 Migration zu Git 9.3 Zusammenfassung 10. Git Interna 10.1 Basisbefehle und Standardbefehle (Plumbing and Porcelain) 10.2 Git Objekte 10.3 Git Referenzen 10.4 Packdateien (engl. Packfiles) 10.5 Die Referenzspezifikation (engl. Refspec) 10.6 Transfer Protokolle 10.7 Wartung und Datenwiederherstellung 10.8 Umgebungsvariablen 10.9 Zusammenfassung A1. Anhang A: Git in anderen Umgebungen A1.1 Grafische Schnittstellen A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Zusammenfassung A2. Anhang B: Git in deine Anwendungen einbetten A2.1 Die Git-Kommandozeile A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Anhang C: Git Kommandos A3.1 Setup und Konfiguration A3.2 Projekte importieren und erstellen A3.3 Einfache Snapshot-Funktionen A3.4 Branching und Merging A3.5 Projekte gemeinsam nutzen und aktualisieren A3.6 Kontrollieren und Vergleichen A3.7 Debugging A3.8 Patchen bzw. Fehlerkorrektur A3.9 E-mails A3.10 Externe Systeme A3.11 Administration A3.12 Basisbefehle 2nd Edition 6.3 GitHub - Ein Projekt betreuen Ein Projekt betreuen Nachdem wir nun zu einem Projekt beitragen können, schauen wir uns die andere Seite an: die Erstellung, Wartung und Verwaltung deines eigenen Projekts. Ein neues Repository erstellen Erstellen wir ein neues Repository, in dem wir unseren Projekt-Code freigeben können. Klicke zunächst auf die Schaltfläche „New repository“ auf der rechten Seite des Dashboards oder auf die Schaltfläche + in der oberen Symbolleiste neben deinem Benutzernamen, wie in Das Dropdown-Menü „New repository“ zu sehen. Abbildung 109. Der Bereich „Your repositories“ Abbildung 110. Das Dropdown-Menü „New repository“ Du wirst zum Formular „new repository“ weitergeleitet: Abbildung 111. Das Formular „new repository“ Alles, was du hier wirklich tun musst, ist, einen Projektnamen anzugeben. Die restlichen Felder sind optional. Fürs Erste klicke einfach auf die Schaltfläche „Create Repository“, und bäm — du verfügst über ein neues Repository auf GitHub mit dem Namen <User>/<Projekt_Name> . Da du dort noch keinen Code vorfindest, zeigt dir GitHub Anleitungen an, wie du ein brandneues Git-Repository einrichten oder es zu einem bestehenden Git-Projekt verbinden kannst. Wir werden das hier nicht weiter vertiefen. Wenn du eine Auffrischung benötigst, schaue dir noch einmal Kapitel 2, Git Grundlagen an. Da dein Projekt jetzt auf GitHub gehostet wird, kannst du die URL an jeden weitergeben, mit dem du dein Projekt teilen möchtest. Jedes Projekt auf GitHub ist über HTTPS als https://github.com/<User>/<Projekt_Name> und über SSH als git@github.com:<User>/<Projekt_Name> erreichbar. Git kann von diesen beiden URLs abholen/fetchen und auf sie hochladen/pushen. Auf Basis der Anmeldedaten des Benutzers, der sich verbindet, werden die Zugriffsrechte entsprechend beschränkt. Anmerkung Häufig ist es sinnvoll, die HTTPS-basierte URL für ein öffentliches Projekt zu verwenden, da der Anwender zum Klonen kein GitHub-Konto haben muss. Wenn User per SSH-URL auf dein Projekt zugreifen wollen, müssen sie über ein GitHub-Konto und einen hochgeladenen SSH-Schlüssel verfügen. Die HTTPS-Adresse ist genau die gleiche URL, die du in einen Browser einfügen würdest, um das Projekt dort anzuzeigen. Hinzufügen von Mitwirkenden Wenn du mit anderen Personen zusammenarbeitest, denen du die Erlaubnis zum Committen gewähren möchtest, musst du diese als „collaborators“ (dt. Mitwirkende) eintragen. Ben, Jeff und Louise besitzen ein GitHub-Konto. Wenn du ihnen Push-Zugriff auf dein Repository gewähren möchtest, kannst du sie deinem Projekt hinzufügen. Dadurch erhalten sie „Push“-Zugriff, d.h. sie haben sowohl Lese- als auch Schreibzugriff auf das Projekt und das Git-Repository. Klicke auf den Link „Settings“ unten rechts in der Seitenleise. Abbildung 112. Der Settings-Link des Repositorys Wähle aus dem Menü auf der linken Seite „Collaborators“. Gib dann einfach einen Benutzernamen in das Feld ein und klicke auf „Add Collaborator“. Du kannst diese Prozedur beliebig oft wiederholen, um so jedem Zugriff zu gewähren. Wenn du die Zugangsberechtigung widerrufen möchtest, klicke einfach auf das "X" auf der rechten Seite der entsprechenden Zeile. Abbildung 113. Mitwirkende im Repository Pull-Requests verwalten Da es jetzt ein Projekt mit einigem Code und vielleicht sogar ein paar Mitwirkenden gibt, die auch Push-Zugriff haben, lass uns noch einmal darüber nachdenken, was zu tun ist, wenn du einen Pull Request erhältst. Pull-Requests können entweder von einem Branch in einem Fork deines Repositorys kommen oder von einem anderen Branch im selben Repository. Der einzige Unterschied besteht darin, dass Fork-Pill-Requests oft von Personen stammen, auf deren Branch du nicht pushen kannst und sie nicht auf deinen.Bei internen Pull-Requests haben im Allgemeinen beide Parteien Zugriff auf alle Branches. Für diese Beispiele nehmen wir an, du bist „tonychacon“ und hast ein neues Arduino-Code-Projekt mit der Bezeichnung „fade“ erstellt. E-Mail Benachrichtigungen Irgendjemand bearbeitet deinen Code und sendet dir einen Pull-Request. In diesem Fall solltest du eine E-Mail erhalten, in der du über den neuen Pull-Request informiert wirst. Dieser sollte etwa so aussehen wie in E-Mail Benachrichtigung über einen neuen Pull-Request . Abbildung 114. E-Mail Benachrichtigung über einen neuen Pull-Request Es gibt ein paar Punkte, die man bei dieser E-Mail beachten sollte. Es gibt ein kleines diffstat – eine Liste von Dateien, die sich im Pull Request geändert haben und um wie sehr sie sich geändert haben. Du erhältst einen Link zum Pull Request auf GitHub. Du erhältst auch ein paar URLs, die du von der Kommandozeile aus verwenden kannst. Wenn du die Zeile siehst, die git pull <url> patch-1 lautet, ist das eine einfache Möglichkeit, aus einer entfernten Branch zu mergen, ohne einen Remote hinzufügen zu müssen. Wir haben das in Kapitel 5, Remote-Branches auschecken kurz besprochen. Wenn du möchtest, kannst du einen Feature-Branch erstellen und in diesen wechseln (engl. checkout). Anschließend kannst du diesen Befehl ausführen, um die Änderungen in dem Pull-Request zu mergen. Die anderen interessanten URLs sind die .diff und .patch URLs, die, wie du vielleicht vermutest, vereinheitlichte Diff- und Patch-Versionen des Pull Requests bereitstellen. Technisch gesehen kannst du die Arbeit im Pull-Request mit einem Befehl wie diesem zusammenführen: $ curl https://github.com/tonychacon/fade/pull/1.patch | git am Mitwirkung beim Pull Request Wie in Github Workflow beschrieben, kannst du nun eine Diskussion mit der Person führen, die den Pull Request geöffnet hat. Du kannst bestimmte Code-Zeilen kommentieren, ganze Commits kommentieren oder den gesamten Pull-Request selbst kommentieren, indem du „GitHub Flavored Markdown“ an beliebiger Stelle verwendest. Jedes Mal, wenn jemand den Pull-Request kommentiert, erhältst du weitere E-Mail-Benachrichtigungen, damit du weißt, dass Aktivitäten stattfinden. Du wirst jeweils einen Link zum Pull Request erhalten, in dem die Aktivität stattfindet. Auf die E-Mails kannst du auch direkt antworten, um den Pull-Request-Thread zu kommentieren. Abbildung 115. Antworten auf E-Mails sind in den Thread integriert Sobald der Quellcode soweit korrekt ist und du ihn zusammenführen möchtest, kannst du ihn mit der Anweisung git pull <url> <branch> (wie zuvor gesehen) pullen und lokal mergen. Oder du fügst den Fork als Remote hinzu, fetchst den Patch und mergst ihn anschließend. Wenn das Zusammenführen trivial ist, kannst du auch einfach auf der GitHub-Seite auf die Schaltfläche „Merge“ klicken. Dadurch wird ein „non-fast-forward“ Merge durchgeführt, wodurch ein Merge-Commit erstellt wird, auch wenn ein „fast-forward“ Merge möglich gewesen wäre. Das bedeutet, dass unabhängig davon, was du tust, jedes Mal, wenn du auf die Schaltfläche Merge klickst, ein Merge-Commit erstellt wird. Wie du in Merge-Button und Anweisungen zum manuellen Zusammenführen eines Pull-Requests sehen kannst, gibt dir GitHub all diese Informationen, wenn du auf den Hinweis-Link klickst. Abbildung 116. Merge-Button und Anweisungen zum manuellen Zusammenführen eines Pull-Requests Wenn du dich entscheidest, dass du ihn nicht zusammenführen möchtest, kannst du auch einfach den Pull-Request schließen und die Person, die ihn geöffnet hat, wird benachrichtigt. Pull Request Refs (Referenzen) Wenn du m< viele Pull-Requests erhältst und nicht jedes Mal einen ganzen Batzen Remotes hinzufügen oder einmalige Pulls durchführen willst, gibt es einen tollen Kniff in GitHub. Es handelt sich um einen fortgeschrittenen Trick, den wir in Kapitel 10, Refspecs ausführlicher durchgehen werden. Er kann jedoch recht nützlich sein. GitHub beschreibt die Pull-Request-Branches für ein Repository als eine Art Pseudo-Branch auf dem Server. Normalerweise werden sie beim Klonen nicht angezeigt- Sie sind jedoch verdeckt vorhanden und man kann recht einfach darauf zugreifen. Um das zu verdeutlichen, werden wir den Low-Level-Befehl ls-remote verwenden, der oft als Git-Basisbefehl (engl. plumbing) bezeichnet wird und über den wir in Basisbefehle und Standardbefehle (Plumbing and Porcelain) mehr lesen werden. Dieses Kommando wird im Regelfall nicht im täglichen Gebrauch von Git verwendet, aber es ist zweckmäßig, um uns zu zeigen, welche Referenzen auf dem Server vorhanden sind. Wenn wir diesen Befehl gegen das „blink“ Repository ausführen, das wir vorhin benutzt haben, erhalten wir eine Liste aller Branches und Tags, sowie anderer Referenzen im Repository. $ git ls-remote https://github.com/schacon/blink 10d539600d86723087810ec636870a504f4fee4d HEAD 10d539600d86723087810ec636870a504f4fee4d refs/heads/master 6a83107c62950be9453aac297bb0193fd743cd6e refs/pull/1/head afe83c2d1a70674c9505cc1d8b7d380d5e076ed3 refs/pull/1/merge 3c8d735ee16296c242be7a9742ebfbc2665adec1 refs/pull/2/head 15c9f4f80973a2758462ab2066b6ad9fe8dcf03d refs/pull/2/merge a5a7751a33b7e86c5e9bb07b26001bb17d775d1a refs/pull/4/head 31a45fc257e8433c8d8804e3e848cf61c9d3166c refs/pull/4/merge Wenn du dich in deinem Repository befindest und git ls-remote origin ausführst (oder auch einen beliebigen anderen Remote, den du überprüfen möchtest), dann sieht die Ausgabe ähnlich aus. Wenn sich das Repository auf GitHub befindet und es offnee Pull-Requests gibt, werden diese Referenzen mit vorangestelltem refs/pull/ angezeigt. Das sind im Prinzip Branches, die aber nicht unter refs/heads/ stehen. Sie werden normalerweise nicht angezeigt, wenn du klonst oder vom Server fetchst – der Fetching-Prozess ignoriert sie normalerweise. Es gibt zwei Referenzen pro Pull-Request – eine endet mit /head . Sie zeigt auf genau den gleichen Commit wie der letzte Commit im Pull-Request-Branch. Wenn also jemand einen Pull-Request in unserem Repository öffnet und sein Branch bug-fix heißt, der auf a5a775 zeigt, dann haben wir in unserem Repository keinen bug-fix Branch (weil der in seinem Fork liegt). Wir haben jedoch pull/\<pr#>/head , der auf a5a775 zeigt. Das heißt, wir können jeden Pull-Request-Branch herunterladen, ohne lokal einen Menge Remotes hinzufügen zu müssen. Jetzt kannst du das Fetchen dieser Referenz direkt durchführen. $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD Damit sagt man Git: „Verbinde dich mit dem origin Remote und laden die Referenz refs/pull/958/head herunter.“ Git macht das mit Vergnügen und lädt alles herunter, was du brauchst, um diesen Ref zu erstellen. Es setzt einen Zeiger auf den Commit, den du unter .git/FETCH_HEAD haben willst. Du kannst die Bearbeitung mit git merge FETCH_HEAD in einen Branch fortsetzen. In diesem könntest du die Änderung testen. Die Merge-Commit-Nachricht sieht jedoch ein wenig merkwürdig aus. Wenn du viele Pull-Requests überprüfen musst, wird das etwas umständlich. Es gibt auch eine Möglichkeit wie du alle Pull-Requests abrufen und aktuell halten kannst, wann immer du dich mit dem Remote verbindest. Öffne .git/config in deinem bevorzugten Editor und suche nach dem origin Remote. Es sollte etwa so aussehen: [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* Die Zeile, die mit fetch = beginnt, ist eine „refspec.“ Es ist eine Möglichkeit, Namen auf dem Remote auf Namen in deinem lokalen .git Verzeichnis zuzuordnen. Dieser hier sagt git: „die Sachen auf dem Remote, die unter refs/heads liegen, sollten in meinem lokalen Repository unter refs/remotes/origin abgelegt werden.“ Du kannst diesen Teil ändern, um eine weitere Referenz (refspec) hinzuzufügen: [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* Diese letzte Zeile sagt Git: „Alle Referenzen, die wie refs/pull/123/head aussehen, sollten lokal als refs/remotes/origin/pr/123 gespeichert werden.“ Wenn du diese Änderung speicherst und ein git fetch ausführst, passiert folgendes: $ git fetch # … * [new ref] refs/pull/1/head -> origin/pr/1 * [new ref] refs/pull/2/head -> origin/pr/2 * [new ref] refs/pull/4/head -> origin/pr/4 # … Nun werden alle Remote-Pull-Requests lokal mit Referenzen (refs) abgebildet, die sich ähnlich wie das Tracken von Branches verhalten. Sie sind schreibgeschützt und werden aktualisiert, wenn du ein Fetch durchführst. Dadurch ist es besonders einfach, den Code aus einer Pull-Anforderung lokal auszuprobieren: $ git checkout pr/2 Checking out files: 100% (3769/3769), done. Branch pr/2 set up to track remote branch pr/2 from origin. Switched to a new branch 'pr/2' Diejenigen mit Adleraugen unter euch werden das head am Ende des Remote-Abschnitts der refspec bemerkt haben. Es gibt auch ein refs/pull/\<num>/merge ref auf der GitHub-Seite, der den Commit darstellt, der sich ergeben würde, wenn du auf die Schaltfläche „merge" klickst. Auf diese Weise kannst du das Ergebnis des Pull-Requests testen, bevor du überhaupt auf die Schaltfläche geklickt hast. Pull-Requests auf Pull-Requests Du kannst nicht nur Pull-Requests öffnen, die auf den Haupt- oder master Branch zeigen. Du kannst Pull-Request, gegen jeden beliebigen Branch im Netzwerk stellen. Du kannst sogar einen anderen Pull-Request als Ziel wählen. Wenn du einen Pull-Request siehst, der dir gefällt und du eine Idee für eine Änderung hast, die von ihm abhängt; oder du dir nicht sicher bist, ob dieser Pull-Request überhaupt eine gute Idee ist; oder du keine Push-Berechtigung zum Zie-Branch hast – kannst du einen Pull-Request auf diesen anderen Pull-Request öffnen. Wenn du einen Pull-Request öffnest, befindet sich oben auf der Seite ein Feld, das angibt, von welchem Branch du pullen und in welchen du den Pull-Vorgang ausführen möchtest. Wenn du auf die Schaltfläche „Edit“ (Bearbeiten), rechts neben diesem Feld, klickst, kannst du nicht nur die Branches, sondern auch den Fork ändern. Abbildung 117. Manuelles Ändern der Pull-Request Ziel-Fork und der Branch Hier kannst du relativ einfach angeben, ob dein neuer Branch in einen anderen Pull-Request oder in einen anderen Fork des Projekts zusammengeführt werden soll. Erwähnen und Benachrichtigen GitHub hat auch ein ziemlich praktisches Benachrichtigungssystem integriert, das bei Fragen oder Rückmeldungen von einzelnen Personen oder Teams eine große Hilfe sein kann. In jedem Kommentar kannst du mit der Eingabe eines @ -Zeichens beginnen und es wird automatisch mit den Namen und Benutzernamen von Personen vervollständigt, die Mitstreiter oder Beitragende des Projektes sind. Abbildung 118. Mit der Eingabe von @ anfangen, um jemanden zu erwähnen Du kannst auch einen Benutzer angeben, der sich nicht in diesem Dropdown-Menü befindet, aber oft ist der Auto-Komplettierer schneller. Sobald du einen Kommentar mit einer Benutzererwähnung postest, wird dieser Benutzer benachrichtigt. Damit ist es möglich, Andere effektiv in Gespräche einbinden, anstatt sie einfach nur zu befragen. Häufig werden bei Pull-Requests auf GitHub andere Personen in Teams oder Unternehmen einbezogen, um ein Issue oder Pull-Requests zu überprüfen. Wenn jemand in einem Pull-Request oder Issue erwähnt wird, wird er darauf „abonniert“ (engl. subscribed) und erhält immer dann weitere Benachrichtigungen, wenn eine Aktivität dort stattfindet. Du wirst auch subskribiert, wenn der Pull-Request von dir geöffnet wurde, wenn du das Repository beobachten oder wenn du etwas kommentierst. Wenn du keine weiteren Benachrichtigungen mehr erhalten möchtest, kannst du auf die Schaltfläche “Unsubscribe” klicken, um dich von den Benachrichtigungen abzumelden. Abbildung 119. Von einer Issue- oder Pull-Request-Benachrichtigung abmelden Die Benachrichtigungs-Seite Wenn wir hier „Benachrichtigungen“ (engl. notifications) erwähnen, meinen wir wie GitHub versucht dich zu informieren, falls ein Ereignis eintritt. Es gibt ein paar Einstellungen, die du konfigurieren kannst. Wenn du von der Settings-Seite aus auf die Registerkarte "Notifications" gehst, siehst du einige der verfügbaren Optionen. Abbildung 120. Benachrichtigungs-Optionen Die beiden Möglichkeiten sind: über „E-Mail“ oder „Web“ benachrichtigen. Du kannst entweder eine, keine oder beide Optionen wählen, wenn du dich an den Aktivitäten in Repositorys beteiligst, die du gerade beobachtest. Web Benachrichtigungen Web-Benachrichtigungen landen nur auf GitHub und du kannst sie nur auf GitHub überprüfen. Wenn du diese Option in deinen Einstellungen ausgewählt hast und eine Benachrichtigung für dich ausgelöst wird, siehst du oben auf deinem Bildschirm einen kleinen blauen Punkt über deinem Benachrichtigungssymbol, wie in Benachrichtigungen zu sehen ist. Abbildung 121. Benachrichtigungen Wenn du darauf klickst, siehst du eine Liste aller Elemente, über die du informiert wurdest, gruppiert nach Projekten. Du kannst nach den Benachrichtigungen eines bestimmten Projekts filtern, indem du auf dessen Namen in der linken Seitenleiste klickst. Du kannst deine Benachrichtigung als Gelesen markieren indem du das Häkchens neben einer Meldung anklickst oder alle Benachrichtigungen in einem Projekt bestätigen indem du das Häkchens oben in der Gruppe anklickst. Es gibt auch eine Mute-Taste neben jedem Häkchen, die du anklicken kannst, um keine weiteren Mitteilungen zu diesem Thema zu erhalten. Diese Tools sind alle sehr praktisch für die Organisation vieler Benachrichtigungen in GitHub. Viele GitHub Power-User schalten E-Mail-Benachrichtigungen einfach komplett aus und verwalten ihre gesamten Benachrichtigungen über die Web-Oberfläche. E-Mail Benachrichtigungen E-Mail-Benachrichtigungen sind die zweite Variante, mit der du Benachrichtigungen über GitHub erhalten kannst. Wenn du diese Option aktiviert hast, erhältst du E-Mails für jede Mitteilung. Wir haben Beispiele dafür in E-Mail Benachrichtigungen und E-Mail Benachrichtigung über einen neuen Pull-Request gesehen. Die E-Mails werden auch nach Thema sortiert, was sehr hilfreich ist, wenn dein E-Mail-Client entsprechend konfiguriert ist. In den Headern der E-Mails, die GitHub dir sendet, sind auch eine ganze Reihe von Metadaten eingebettet, was bei der Einrichtung angepasster Filter und Regeln sehr nützlich sein kann. Wenn wir uns zum Beispiel die aktuellen E-Mail-Header ansehen, der in E-Mail Benachrichtigung über einen neuen Pull-Request angezeigten E-Mail, die an Tony gesendet wurde, werden wir unter den gesendeten Informationen Folgendes sehen: To: tonychacon/fade <fade@noreply.github.com> Message-ID: <tonychacon/fade/pull/1@github.com> Subject: [fade] Wait longer to see the dimming effect better (#1) X-GitHub-Recipient: tonychacon List-ID: tonychacon/fade <fade.tonychacon.github.com> List-Archive: https://github.com/tonychacon/fade List-Post: <mailto:reply+i-4XXX@reply.github.com> List-Unsubscribe: <mailto:unsub+i-XXX@reply.github.com>,... X-GitHub-Recipient-Address: tchacon@example.com Es gibt hier noch ein paar interessante Kleinigkeiten. Möchtest du E-Mails zu einem Projekt oder Pull Request hervorheben oder umleiten, erhältst du alle notwendige Daten in Message-ID im <user>/<project>/<type>/<id> Format. Wenn das, zum Beispiel, ein Issue wäre, dann wäre das Feld <type> eher „Issues“ als „Pull“ gewesen. Die List-Post und List-Unsubscribe Felder bedeuten, dass du, wenn du einen Mail-Client haben, der das versteht, ganz einfach in die Liste posten oder dich vom Thread „abmelden“ (engl. unsubscribe) kannst. Das wäre im Wesentlichen dasselbe wie das Anklicken des „Mute“ Buttons in Web-Benachrichtigungen oder „Unsubscribe“ auf der Issue- oder Pull-Request-Seite selbst. Es ist auch wichtig zu wissen, dass, wenn du sowohl E-Mail- als auch Web-Benachrichtigungen aktiviert hast und du die E-Mail-Version der Benachrichtigung liest, die Web-Version auch als gelesen markiert wird, falls du in deinem Mail-Client Bilder erlaubt hast. Besondere Dateien Es gibt ein paar besondere Dateien, die GitHub erkennt, wenn sie in deinem Repository vorhanden sind. README Zuerst ist da die README Datei, die in nahezu jedem Dateiformat vorliegen kann, das GitHub als Text erkennt. Zum Beispiel könnte es sich um README , README.md , README.asciidoc usw. handeln. Wenn GitHub eine README-Datei in deinem Projekt findet, wird sie auf der Startseite des Projekts angezeigt. Viele Teams verwenden diese Datei, um alle relevanten Projektinformationen für Personen zu sammeln, die neu im Repository oder Projekt sind. Dazu gehören in der Regel Sachen wie: Wofür ist das Projekt vorgesehen Wie wird es konfiguriert und installiert Ein Beispiel, wie man es anwendet oder zum Laufen bringt Die Lizenz, unter der das Projekt zur Verfügung steht Wie man dazu beitragen kann Da GitHub diese Datei rendert, kannst du Bilder oder Links in sie einbetten, um sie besser verständlich zu machen. CONTRIBUTING Die andere von GitHub erkannte, spezielle Datei ist die Datei CONTRIBUTING . Wenn du eine CONTRIBUTING Datei mit einer beliebigen Dateiendung verwendest, zeigt GitHub sie wie in Einen Pull-Request starten, wenn eine CONTRIBUTING-Datei existiert gezeigt an, wenn irgend jemand einen Pull-Request öffnet. Abbildung 122. Einen Pull-Request starten, wenn eine CONTRIBUTING-Datei existiert Die Absicht dabei ist, dass du bestimmte Punkte spezifizieren kannst, die du benötigst oder nicht wünschst, für Pull-Requests, die an deinem Projekt gesendet werden. Auf diese Weise kann ein Benutzer die Leitlinien auch wirklich lesen, bevor er den Pull-Request eröffnet. Projekt-Administration Generell gibt es nur wenige administrative Aufgaben, die du mit einem einzelnen Projekt durchführen kannst, aber ein paar Punkte könnten interessant sein. Ändern des Standard-Branchs Wenn du einen anderen Branch als „master“ als Standard-Branch verwenden willst, auf den die Teilnehmer Pull-Requests öffnen oder ihn standardmäßig sehen sollen, dann kannst du das auf der Settings-Seite deines Repositorys unter der Registerkarte „Optionen“ ändern. Abbildung 123. Ändern des Standard-Branchs eines Projekts Ändere einfach den Standard-Branch in der Dropdown-Liste und das ist dann der Vorgabewert für alle wichtigen Operationen, einschließlich des Branchs, der standardmäßig ausgecheckt wird, wenn jemand das Repository klont. Übertragen eines Projektes Wenn du ein Projekt auf einen anderen Benutzer oder eine Organisation in GitHub übertragen möchtest, gibt es unten auf der gleichen Registerkarte „Optionen“ deiner Repository-Einstellungen eine Option „Eigentum übertragen“ (engl. Transfer ownership), die das ermöglicht. Abbildung 124. Übertragen eines Projekts auf einen anderen GitHub-User oder eine andere Organisation Diese Option ist sinnvoll, wenn du ein Projekt aufgibst und es von jemandem übernommen werden soll oder wenn dein Projekt größer wird und du es in eine andere Organisation verlagern möchtest. Dadurch wird nicht nur das Repository zusammen mit all seinen Beobachtern und Sternen an einen anderen Ort verschoben, sondern es wird auch ein Redirect von deiner URL an den neuen Ort eingerichtet. Es wird auch die Klone und Fetches von Git umleiten, nicht nur die Web-Anfragen. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/Git-sa-Server-Git-Daemon | Git - Git Daemon About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 4.5 Git sa Server - Git Daemon Git Daemon Susunod ay magse-set up tayo ng isang naglilingkod na repositoryo ng daemon gamit ang protokol ng “Git”. Ito ay isang karaniwang pagpili para sa mabilis, unauthenticated na access sa iyong datos sa Git. Tandaan na dahil ito ay isang unauthenticated na serbisyo, anumang bagay na ihahatid mo sa protokol na ito ay pampubliko sa network nito. Kapag pinapatakbo mo ito sa isang server sa labas ng iyong firewall, ito ay dapat ginagamit lamang sa mga proyekto na makikita ng publiko sa mundo. Kapag ang server na pinapatakbo mo ay sa loob ng iyong firewall, maaari mo itong gamitin sa mga proyekto na mayroong malaking bilang ng tao o mga kompyuter (tuloy-tuloy na pagsasama o mga build server) ay mayroong read-only na access, kapag ayaw mong magdagdag ng SSH key para sa bawat isa. Sa anumang kaso, ang protokol ng Git ay medyo madaling gamitin. Kailangan mo patakbuhin ang utos na ito sa isang daemonized na paraan: $ git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Ang --reuseaddr na opsyon ay nagpapahintulot sa server na mag-restart nang hindi naghihintay na mag-timeout ang mga lumang mga koneksyon na mag time out, habang ang --base-path na opsyon ay nagpapahintulot sa mga tao na mag-clone ng mga proyekto na hindi tinutukoy ang buong landas, at ang landas sa dulo ay sinasabihan ang Git daemon kung saan tumingin para sa mga repositoryo na i-export. Kapag ikaw ay nagpapatakbo ng isang firewall, kakailanganin mo ring butasan ito sa port 9418 sa kahon kung asan ka nagse-set up. Maaari mong i-daemonize ang prosesong ito sa iilang paraan, depende sa operating system na pinapatakbo mo. Dahil ang systemd ang pinakakaraniwan na init na sistema sa mga modernong distribusyon ng Linux, maaari mong gamitin ito para sa layunin na iyon. Maglagay lamang ng isang file sa /etc/systemd/system/git-daemon.service na may ganitong nilalaman: [Unit] Description=Start Git Daemon [Service] ExecStart=/usr/bin/git daemon --reuseaddr --base-path=/srv/git/ /srv/git/ Restart=always RestartSec=500ms StandardOutput=syslog StandardError=syslog SyslogIdentifier=git-daemon User=git Group=git [Install] WantedBy=multi-user.target Maaaring napansin mo na ang Git daemon ay nagsimula dito kasama ang git bilang parehong grupo at user. Baguhin ito upang magkasya sa iyong pangangailangan at siguraduhin ang ibinigay na user ay umiiral sa sistema. Gayundin, tiyakin na ang Git binary ay matatagpuan sa /usr/bin/git at baguhin ang landas kung kailangan man. Sa wakas, ipatakbo ang systemctl enable git-daemon para awtomatikong simulan ang serbisyo sa pag-boot, at maaaring simulan o itigil ang serbisyo gamit ang, ayon sa pagkakabanggit systemctl start git-daemon at systemctl stop git-daemon . Hanggang LTS 14.04, ginamit ng Ubuntu ang kompigurasyon ng upstart na unit ng serbisyo. Sa gayon, sa Ubuntu ⇐ 14.04 magagamit mo ang Upstart na iskrip. Kaya, sa mga sumusunod na file /etc/init/local-git-daemon.conf Ilagay mo ang iskrip na ito: start on startup stop on shutdown exec /usr/bin/git daemon \ --user=git --group=git \ --reuseaddr \ --base-path=/srv/git/ \ /srv/git/ respawn Para sa dahilan ng seguridad, malakas na hinihikayat na ipatakbo ang daemon na ito bilang isang user na mayroong read-only na mga pahintulot sa mga repositoryo — madali mo itong magagawa sa pamamagitan ng paglikha ng isang bagong user git-ro at pagpapatakbo ng daemon bilang sila. Para sa kapanan ng pagiging simple, ipapatakbo lang natin ito pareho sa git na user na pinapatakbo ng git-shell . Kapag na-restart mo na iyong makina, ang iyong Git daemon ay awtomatikong magsisimula at mag-respawn kapag bumaba ito. Upang mapatakbo ito na hindi kailangan mag-reboot, maaari mong ipatakbo ito: $ initctl start local-git-daemon Sa mga ibang sistema, maaaring nais mong gamitin ang xinetd , isang iskrip sa iyong sysvinit na sistema, o ibang bagay — hangga’t makahanap ka ng paraan na makakuha ng utos na daemonized at pinapanood. Sunod, dapat mong sabihan ang Git kung anong repository ang papayagan na magkaroon ng unauthenticated na pagpasok ayon sa server. Maaari mo itong gawin sa bawat repositoryo sa pamamagitan ng paglikha ng isang file na may pangalang git-daemon-export-ok . $ cd /path/to/project.git $ touch git-daemon-export-ok Ang presensya ng file na iyon ay nagsasabi sa Git na OK na paglingkuran ang proyektong ito na walang pagpapatunay. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/ru/v2/%d0%9e%d1%81%d0%bd%d0%be%d0%b2%d1%8b-Git-%d0%97%d0%b0%d0%ba%d0%bb%d1%8e%d1%87%d0%b5%d0%bd%d0%b8%d0%b5 | Git - Заключение About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Введение 1.1 О системе контроля версий 1.2 Краткая история Git 1.3 Что такое Git? 1.4 Командная строка 1.5 Установка Git 1.6 Первоначальная настройка Git 1.7 Как получить помощь? 1.8 Заключение 2. Основы Git 2.1 Создание Git-репозитория 2.2 Запись изменений в репозиторий 2.3 Просмотр истории коммитов 2.4 Операции отмены 2.5 Работа с удалёнными репозиториями 2.6 Работа с тегами 2.7 Псевдонимы в Git 2.8 Заключение 3. Ветвление в Git 3.1 О ветвлении в двух словах 3.2 Основы ветвления и слияния 3.3 Управление ветками 3.4 Работа с ветками 3.5 Удалённые ветки 3.6 Перебазирование 3.7 Заключение 4. Git на сервере 4.1 Протоколы 4.2 Установка Git на сервер 4.3 Генерация открытого SSH ключа 4.4 Настраиваем сервер 4.5 Git-демон 4.6 Умный HTTP 4.7 GitWeb 4.8 GitLab 4.9 Git-хостинг 4.10 Заключение 5. Распределённый Git 5.1 Распределённый рабочий процесс 5.2 Участие в проекте 5.3 Сопровождение проекта 5.4 Заключение 6. GitHub 6.1 Настройка и конфигурация учётной записи 6.2 Внесение собственного вклада в проекты 6.3 Сопровождение проекта 6.4 Управление организацией 6.5 Создание сценариев GitHub 6.6 Заключение 7. Инструменты Git 7.1 Выбор ревизии 7.2 Интерактивное индексирование 7.3 Припрятывание и очистка 7.4 Подпись 7.5 Поиск 7.6 Перезапись истории 7.7 Раскрытие тайн reset 7.8 Продвинутое слияние 7.9 Rerere 7.10 Обнаружение ошибок с помощью Git 7.11 Подмодули 7.12 Создание пакетов 7.13 Замена 7.14 Хранилище учётных данных 7.15 Заключение 8. Настройка Git 8.1 Конфигурация Git 8.2 Атрибуты Git 8.3 Хуки в Git 8.4 Пример принудительной политики Git 8.5 Заключение 9. Git и другие системы контроля версий 9.1 Git как клиент 9.2 Переход на Git 9.3 Заключение 10. Git изнутри 10.1 Сантехника и Фарфор 10.2 Объекты Git 10.3 Ссылки в Git 10.4 Pack-файлы 10.5 Спецификации ссылок 10.6 Протоколы передачи данных 10.7 Обслуживание репозитория и восстановление данных 10.8 Переменные окружения 10.9 Заключение A1. Приложение A: Git в других окружениях A1.1 Графические интерфейсы A1.2 Git в Visual Studio A1.3 Git в Visual Studio Code A1.4 Git в Eclipse A1.5 Git в IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.6 Git в Sublime Text A1.7 Git в Bash A1.8 Git в Zsh A1.9 Git в PowerShell A1.10 Заключение A2. Приложение B: Встраивание Git в ваши приложения A2.1 Git из командной строки A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Приложение C: Команды Git A3.1 Настройка и конфигурация A3.2 Клонирование и создание репозиториев A3.3 Основные команды A3.4 Ветвление и слияния A3.5 Совместная работа и обновление проектов A3.6 Осмотр и сравнение A3.7 Отладка A3.8 Внесение исправлений A3.9 Работа с помощью электронной почты A3.10 Внешние системы A3.11 Администрирование A3.12 Низкоуровневые команды 2nd Edition 2.8 Основы Git - Заключение Заключение Теперь вы умеете выполнять все базовые локальные операции с Git: создавать или клонировать репозиторий, вносить изменения, индексировать и фиксировать эти изменения, а также просматривать историю всех изменений в репозитории. Дальше мы рассмотрим киллер-фичу Git — его модель ветвления. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_CO | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상� | 2026-01-13T09:29:23 |
https://zh-cn.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Frootstock.io | Facebook Facebook 邮箱或手机号 密码 忘记账户了？ 创建新账户 你暂时被禁止使用此功能 你暂时被禁止使用此功能 似乎你过度使用了此功能，因此暂时被阻止，不能继续使用。 Back 中文(简体) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 日本語 Português (Brasil) Français (France) Deutsch 注册 登录 Messenger Facebook Lite 视频 Meta Pay Meta 商店 Meta Quest Ray-Ban Meta Meta AI Meta AI 更多内容 Instagram Threads 选民信息中心 隐私政策 隐私中心 关于 创建广告 创建公共主页 开发者 招聘信息 Cookie Ad Choices 条款 帮助 联系人上传和非用户 设置 动态记录 Meta © 2026 | 2026-01-13T09:29:23 |
https://fr-fr.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Frootstock.io | Facebook Facebook Adresse e-mail ou téléphone Mot de passe Informations de compte oubliées ? Créer un compte Cette fonction est temporairement bloquée Cette fonction est temporairement bloquée Il semble que vous ayez abusé de cette fonctionnalité en l’utilisant trop vite. Vous n’êtes plus autorisé à l’utiliser. Back Français (France) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Deutsch S’inscrire Se connecter Messenger Facebook Lite Vidéo Meta Pay Boutique Meta Meta Quest Ray-Ban Meta Meta AI Plus de contenu Meta AI Instagram Threads Centre d’information sur les élections Politique de confidentialité Centre de confidentialité À propos Créer une publicité Créer une Page Développeurs Emplois Cookies Choisir sa publicité Conditions générales Aide Importation des contacts et non-utilisateurs Paramètres Historique d’activité Meta © 2026 | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/GitHub-Pamamahala-ng-isang-organisasyon | Git - Pamamahala ng isang organisasyon About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 6.4 GitHub - Pamamahala ng isang organisasyon Pamamahala ng isang organisasyon Bukod sa mga single-user account, ang GitHub ay may tinatawag na mga Organisasyon. Tulad ng mga personal na account, ang mga account ng Organisasyon ay may namespace kung saan umiiral ang lahat ng kanilang mga proyekto, ngunit maraming iba pang mga bagay ay naiiba. Ang mga account na ito ay kumakatawan sa isang grupo ng mga tao na may ibinahaging pagmamay-ari ng mga proyekto, at mayroong maraming mga kasangkapan upang pamahalaan ang mga subgroup ng mga tao. Karaniwan ang mga account na ito ay ginagamit para sa mga grupo ng Open Source (tulad ng “perl” o “rails”) o mga kompanya (tulad ng “google” o “twitter”). Mga Pangunahing Kaalaman sa Organisasyon Ang organisasyon ay medyo madali malikha; i-click lamang ang icon na “+” na nasa itaas na kanan ng anumang pahina ng GitHub, at piliin ang “Bagong Organisasyon” mula sa menu. Figure 126. Ang aytem ng menu na “Bagong organisasyon”. Una kinakailangan mong pangalanan ang iyong organisasyon at magbigay ng isang email address para sa isang pangunahing punto ng contact para sa grupo. Pagkatapos ay maaari kang mag-imbita ng iba pang mga gumagamit na maging mga may-ari rin ng account kung gusto mo. Sundin ang mga hakbang na ito at ikaw ay magiging may-ari ng isang bagong organisasyon. Tulad ng mga personal na account, ang mga organisasyon ay libre kung ang lahat na iyong pinaplano na iimbak doon ay magiging open source. Bilang isang may-ari ng isang organisasyon, kapag ikaw ay nag-fork ng isang repositoryo, magkakaroon ka ng pagpipilian sa pag-fork nito sa namespace ng iyong organisasyon. Kapag lumikha ka ng mga bagong repositoryo maaari mong ilikha ang mga ito alinman sa iyong personal na account o sa ilalim ng anumang mga organisasyon na iyong pagmamay-ari. Awtomatiko mo ring “mapanood” ang anumang bagong repositoryo na iyong nalikha sa ilalim ng mga organisasyong ito. Katulad ng sa Ang iyong Avatar , maaari kang mag-upload ng isang avatar sa iyong organisasyon upang gawing pansarili ito nang kaunti. Tulad din ng mga personal na account, mayroon kang isang pahina sa paglapag para sa isang organisasyon na naglilista sa lahat ng iyong mga repositoryo at maaari matingnan ng ibang mga tao. Ngayon tatalakayin natin ang ilan sa mga bagay na may kaunting pagkakaiba sa isang account ng organisasyon. Mga Koponan Ang organisasyon ay nauugnay sa mga indibidwal na tao sa pamamaraan ng koponan, na kung saan ay isang grupo lamang ng mga indibidwal na account ng gumagamit at mga repositoryo sa loob ng organisasyon at kung anong uri ng pag-access mayroon ang mga taong iyon sa mga repositoryo. Halimbawa, sabihin ang iyong kumpanya ay may tatlong repositoryo: frontend , backend , at deployscripts . Gugustuhin mo na ang iyong mga developer ng HTML/CSS/JavaScript na magkaroon ng access sa frontend at marahil sa backend , at ang iyong mga tao sa Operasyon na magkaroon ng access sa backend at deployscripts . Ginagawang madali ito ng koponan, nang hindi kinakailangang pamahalaan ang mga tagatulong para sa bawat indibidwal na repositoryo. Ipinapakita sa iyo ng pahina ng Organisasyon ang isang simpleng dashboard sa lahat ng mga repositoryo, gumagamit at koponan na nasa ilalim ng organisasyon na ito. Figure 127. Ang pahina ng Organisasyon. Upang mapamahalaan ang iyong mga Koponan, maaari mong i-click ang sidebar na Koponan sa kanang bahagi ng pahina sa Ang pahina ng Organisasyon. . Ito ay magdadala sa iyo sa isang pahina na maaari mong magamit upang magdagdag ng mga miyembro sa koponan, magdagdag ng mga repositoryo sa koponan o pamahalaan ang settings at kontrol sa mga antas ng pag-access para sa koponan. Ang bawat koponan ay maaaring magkaroon ng pagbasa lamang, pagbasa/pagsulat o access na administratibo sa mga repositoryo. Maaari mong baguhin ang antas na iyon sa pamamagitan ng pag-click sa pindutan na “Settings” sa Ang pahina ng Koponan. . Figure 128. Ang pahina ng Koponan. Kapag inaanyayahan mo ang isang tao sa isang koponan, makakakuha sila ng email na nagpapaalam sa kanila na sila ay inanyayahan. Bukod pa rito, ang @mentions ng koponan (tulad ng @acmecorp/frontend ) ay gumagana nang kapareho katulad ng ginagawa nila sa mga indibidwal na gumagamit, maliban na ang lahat ng mga miyembro ng koponan ay naka-subscribe sa thread. Ito ay kapaki-pakinabang kung nais mo ang atensiyon mula sa isang tao sa isang koponan, ngunit hindi mo eksaktong alam kung sino ang tatanungin. Ang gumagamit ay maaari nabibilang sa anumang bilang ng mga koponan, kaya huwag limitahan ang iyong sarili para lamang sa mga koponan ng kontrol ng pag-access. Mga koponan na interes na Espesyal kagaya ng ux , css , o pag-refactor ay kapaki-pakinabang para sa ilang mga uri ng mga tanong, at iba pa tulad ng legal at colorblind para sa isang ganap na ibang uri. Log ng Audit Binibigyan din ng mga orgnasisasyon ang mga may-ari ng access sa lahat ng impormasyon tungkol sa kung ano ang naganap sa ilalim ng organisasyon. Maaari kang magpunta sa tab na Log ng Audit at makita kung ano ang mga kaganapan na nangyari sa antas ng organisasyon, sino ang gumawa ng mga ito at saan sila natapos. Figure 129. Ang log ng Audit. Maaari mo ring i-filter pababa sa mga partikular na uri ng mga kaganapan, partikular na lugar o partikular na tao. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://th-th.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Frootstock.io | Facebook Facebook อีเมลหรือโทรศัพท์ รหัสผ่าน ลืมบัญชีใช่หรือไม่ สร้างบัญชีใหม่ คุณถูกบล็อกชั่วคราว คุณถูกบล็อกชั่วคราว ดูเหมือนว่าคุณจะใช้คุณสมบัตินี้ในทางที่ผิดโดยการใช้เร็วเกินไป คุณถูกบล็อกจากการใช้โดยชั่วคราว Back ภาษาไทย 한국어 English (US) Tiếng Việt Bahasa Indonesia Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch สมัคร เข้าสู่ระบบ Messenger Facebook Lite วิดีโอ Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI เนื้อหาเพิ่มเติมจาก Meta AI Instagram Threads ศูนย์ข้อมูลการลงคะแนนเสียง นโยบายความเป็นส่วนตัว ศูนย์ความเป็นส่วนตัว เกี่ยวกับ สร้างโฆษณา สร้างเพจ ผู้พัฒนา ร่วมงานกับ Facebook คุกกี้ ตัวเลือกโฆษณา เงื่อนไข ความช่วยเหลือ การอัพโหลดผู้ติดต่อและผู้ที่ไม่ได้ใช้บริการ การตั้งค่า บันทึกกิจกรรม Meta © 2026 | 2026-01-13T09:29:23 |
https://git-scm.com/book/cs/v2/Distribuovan%c3%bd-Git-P%c5%99isp%c3%adv%c3%a1n%c3%ad-do-projektu | Git - Přispívání do projektu About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Úvod 1.1 Správa verzí 1.2 Stručná historie systému Git 1.3 Základy systému Git 1.4 Příkazový řádek 1.5 Instalace systému Git 1.6 První nastavení systému Git 1.7 Získání nápovědy 1.8 Shrnutí 2. Základy práce se systémem Git 2.1 Získání repozitáře Git 2.2 Nahrávání změn do repozitáře 2.3 Zobrazení historie revizí 2.4 Návrat do předchozího stavu 2.5 Práce se vzdálenými repozitáři 2.6 Používání značek 2.7 Aliasy v Gitu 2.8 Shrnutí 3. Větve v systému Git 3.1 Větve v kostce 3.2 Základy větvení a slučování 3.3 Správa větví 3.4 Postupy při práci s větvemi 3.5 Vzdálené větve 3.6 Přeskládání 3.7 Shrnutí 4. Git na serveru 4.1 Protokoly 4.2 Zprovoznění Gitu na serveru 4.3 Generování veřejného klíče SSH 4.4 Nastavení serveru 4.5 Démon Git 4.6 Chytrý HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti hostování u třetí strany 4.10 Shrnutí 5. Distribuovaný Git 5.1 Distribuované pracovní postupy 5.2 Přispívání do projektu 5.3 Správa projektu 5.4 Shrnutí 6. GitHub 6.1 Zřízení účtu a úprava konfigurace 6.2 Přispívání do projektu 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Shrnutí 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Ladění v systému Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Shrnutí 8. Customizing Git 8.1 Git Configuration 8.2 Atributy Git 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Shrnutí 9. Git a ostatní systémy 9.1 Git as a Client 9.2 Migrating to Git 9.3 Shrnutí 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Balíčkové soubory 10.5 The Refspec 10.6 Přenosové protokoly 10.7 Správa a obnova dat 10.8 Environment Variables 10.9 Shrnutí A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Shrnutí A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 5.2 Distribuovaný Git - Přispívání do projektu Přispívání do projektu Hlavní potíž při popisu způsobu přispívání do projektu spočívá v tom, že existuje obrovské množství variací, jak se to dá udělat. Git je velmi pružný, lidé mohou spolupracovat různými způsoby (a taky to tak dělají), takže není snadné popsat, jakým způsobem byste měli přispívat. Každý projekt je trochu jiný. Mezi proměnné v tomto procesu patří počet aktivních přispěvatelů, zvolený pracovní postup, vaše oprávnění pro odesílání revizí a případně i metoda externího přispívání. První proměnnou je počet aktivních přispěvatelů. Kolik uživatelů aktivně přispívá svým kódem do projektu a jak často? V mnoha případech budete mít dva nebo tři vývojáře přispívající několika málo revizemi denně. U spících projektů to bude i méně. U větších společností nebo u větších projektů může počet vývojářů dosahovat tisíců — při stovkách nebo tisících zápisů revizí (commit) denně. Počet přispěvatelů je důležitý, protože s rostoucím počtem vývojářů narůstají i potíže se zajištěním toho, aby byl váš kód aplikován čistě, nebo aby ho bylo možné snadno začlenit (merge). Vámi odeslané změny se mohou ukázat jako zastaralé nebo vážně narušené pracemi, které byly do projektu začleněny během vaší práce, nebo v době, kdy vaše změny čekaly na schválení či aplikaci. Jak lze dosáhnout neustálé aktuálnosti vašeho kódu a platnosti vašich revizí? Další proměnnou je pracovní postup, který se u projektu využívá. Probíhá vývoj centralizovaně s tím, že každý vývojář má stejné oprávnění pro zápis do hlavní linie kódu? Má projekt svého správce nebo integračního manažera, který kontroluje všechny záplaty? Jsou všechny záplaty odborně posuzovány a schvalovány? Jste součástí tohoto procesu? Jsou součástí systému poručíci a musíte všechnu svou práci odesílat nejprve jim? Další otázkou je vaše oprávnění k zapisování revizí. Pracovní postup při přispívání do projektu se velmi liší podle toho, zda máte, či nemáte oprávnění k zápisu do projektu. Pokud oprávnění k zápisu nemáte, jaké metodě se dává přednost při přijímání příspěvků? Je nějaká strategie vůbec určena? Kolik práce představuje jeden váš příspěvek? A jak často přispíváte? Všechny tyto otázky mohou mít vliv na efektivní přispívání do projektu a určují, jaký pracovní postup je vůbec možný a který bude upřednostněn. Každou z těchto otázek si probereme na sérii praktických případů, postupně od jednodušších po složitější. Z uvedených příkladů byste si měli být schopni odvodit vlastní pracovní postup, který budete v praxi využívat. Pravidla pro zápis revizí Než se podíváme na konkrétní případy, uveďme rychlou poznámku o zprávách k revizím. Pokud stanovíte dobrá pravidla pro vytváření revizí (commit) a pokud se jich budete držet, bude práce s Gitem a spolupráce s ostatními mnohem jednodušší. Samotný projekt Git obsahuje dokument, v němž je navržena celá řada dobrých tipů pro vytváření revizí, z kterých se vytvářejí záplaty. Najdete ho ve zdrojovém kódu systému Git, v souboru Documentation/SubmittingPatches . Především nechcete odesílat chybně použité prázdné znaky (whitespace). Git nabízí snadný způsob, jak tyto chyby zkontrolovat. Před zapsáním revize spusťte git diff --check , který zkontroluje prázdné znaky a zobrazí vám je. Figure 57. Výstup příkazu git diff --check . Spustíte-li tento příkaz před zapsáním revize, můžete zjistit, zda se budou zapisovat i problematické prázdné znaky, které by mohly ostatní vývojáře obtěžovat. Dále se snažte zapisovat každou revizi (commit) jako logicky oddělený soubor změn. Pokud je to možné, snažte se, aby byly vaše změny stravitelné. Není právě ideální pracovat celý víkend na pěti různých problémech a v pondělí je všechny najednou odeslat formou jedné velké revize. Když už během víkendu nebudete zapisovat revize, využijte v pondělí oblasti připravených změn pro rozdělení práce alespoň do stejného počtu revizí, kolik je řešených problémů, a přidejte k nim vysvětlující zprávy. Pokud některé změny upravují stejný soubor, zkuste použít příkaz git add --patch a připravit soubory k zapsání po částech (podrobnosti jsou popsány v kapitole Interactive Staging ). Snímek projektu na vrcholu větve bude stejný, ať zapíšete jednu revizi, nebo pět (za předpokladu, že vložíte všechny změny). Snažte se proto usnadnit práci svým kolegům, kteří možná někdy budou vaše změny revidovat. Takový přístup současně usnadňuje stahování změn (pull) nebo vracení jedné sady změn do původního stavu — bude-li to později třeba. Podkapitola Rewriting History popisuje několik užitečných triků, jak v systému Git přepsat historii a jak interaktivně připravovat soubory k zapsání. Než svou práci odešlete ostatním, použijte tyto nástroje k udržení čisté a srozumitelné historie. Poslední věcí, na kterou byste měli myslet, jsou zprávy k revizím. Pokud si zvyknete připisovat k revizím kvalitní zprávy, bude pro vás práce s Gitem a spolupráce s ostatními mnohem jednodušší. Základním pravidlem je, že by vaše zprávy měly začínat jedním řádkem, který nemá víc než asi 50 znaků a který popisuje sadu provedených změn. Za ním následuje prázdný řádek a potom podrobnější vysvětlení. Projekt Git vyžaduje, aby podrobnější popis revize zahrnoval i vaši motivaci ke změnám a aby uvedl srovnání nové implementace s původním chováním. Tuto zásadu je dobré dodržovat. Doporučuje se také, aby se pro zápis zpráv používal rozkazovací způsob. Jinými slovy, formulujte je jako příkazy. Místo „Přidal jsem testy pro“ nebo „Přidány testy pro“ použijte „Přidej testy pro“. Zde je originální (přeložená) šablona, kterou napsal Tim Pope: Krátké shrnutí změn (do 50 znaků) Podrobnější vysvětlující text, pokud je třeba. Zalamujte řádky přibližně na 72 znaků. Někdy se první řádek používá jako předmět emailu a zbytek textu jako tělo dopisu. Prázdný řádek, který odděluje shrnutí od těla je nezbytně nutný (pokud tělo nevynecháte úplně); nástroje jako rebase mohou být zmatené, pokud tyto části neoddělíte. Další odstavce se oddělují prázdným řádkem. - Můžete používat i odrážky. - Pro odrážku se typicky používá pomlčka nebo hvězdička, před kterou se uvádí jedna mezera. Mezi odrážky se vkládají prázdné řádky, ale tady se zvyklosti mohou lišit. Pokud budou všechny vaše zprávy k revizím vypadat takto, usnadníte tím práci sobě i svým spolupracovníkům. Projekt Git obsahuje kvalitně naformátované zprávy k revizím. Zkuste spustit git log --no-merges , abyste se podívali, jak vypadá pěkně naformátovaná historie revizí projektu. V následujících příkladech — a ve většině ukázek v knize — se takto pěkně naformátované zprávy nepoužívají kvůli stručnosti. Místo toho budeme používat volbu -m za příkazem git commit . Dělejte to, jak říkám, a ne jak to dělám. Malý soukromý tým Nejjednodušší situaci, s kterou se asi setkáte, představuje soukromý projekt s jedním nebo pár dalšími vývojáři. „Soukromý“ v této souvislosti znamená s uzavřeným zdrojovým kódem — okolní svět k němu nemá přístup. Vy a vaši ostatní vývojáři máte všichni oprávnění odesílat změny do repozitáře (push). V takovém prostředí můžete uplatnit podobný pracovní postup, na jaký jste možná zvyklí ze systému Subversion nebo z jiného centralizovaného systému. Přesto získáte výhody v takových ohledech, jako je zapisování revizí offline a podstatně snazší větvení a slučování. Pracovní postup však bude velmi podobný. Hlavním rozdílem je to, že slučování probíhá na straně klienta, a ne během zapisování revize na straně serveru. Podívejme se, jak to může vypadat, když dva vývojáři začnou spolupracovat na projektu se sdíleným repozitářem. První vývojář, John, naklonuje repozitář, provede změny a zapíše lokální revizi. (V následujících příkladech byly zprávy protokolů nahrazeny třemi tečkami, abych je trochu zkrátil.) # Johnův počítač $ git clone john@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim lib/simplegit.rb $ git commit -am 'removed invalid default value' [master 738ee87] removed invalid default value 1 files changed, 1 insertions(+), 1 deletions(-) Druhá vývojářka, Jessica, učiní totéž — naklonuje repozitář a zapíše provedenou změnu: # Jessičin počítač $ git clone jessica@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim TODO $ git commit -am 'add reset task' [master fbff5bc] add reset task 1 files changed, 1 insertions(+), 0 deletions(-) Jessica teď odešle (push) svou práci na server: # Jessičin počítač $ git push origin master ... To jessica@githost:simplegit.git 1edee6b..fbff5bc master -> master Také John se pokusí odeslat své změny na server: # Johnův počítač $ git push origin master To john@githost:simplegit.git ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'john@githost:simplegit.git' John nemá povoleno odeslat změny, protože mezitím odeslala své změny Jessica. Pochopit to je obzvlášť důležité v případě, kdy jste zvyklí na Subversion. Můžete si totiž všimnout, že oba vývojáři neupravovali stejný soubor. Pokud byly upraveny různé soubory, provádí Subversion takové sloučení na serveru automaticky. Ale v Gitu musíte provést sloučení revizí (merge) lokálně. John musí vyzvednout (fetch) změny, které provedla Jessica, a začlenit je (merge) do své práce. Teprve potom mu bude umožněno je odeslat (push): $ git fetch origin ... From john@githost:simplegit + 049d078...fbff5bc master -> origin/master V tomto okamžiku vypadá Johnův lokální repozitář nějak takto: Figure 58. Johnova odchylující se historie. John má k dispozici odkaz na změny, které odeslala Jessica, ale než bude moci sám odeslat svá data, bude muset začlenit její práci: $ git merge origin/master Merge made by recursive. TODO | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) Sloučení probíhá hladce — Johnova historie revizí teď vypadá takto: Figure 59. Johnův repozitář po začlenění origin/master . Teď může John svůj kód otestovat, aby se ujistil, že stále pracuje správně, a pak může odeslat svou novou sloučenou práci na server: $ git push origin master ... To john@githost:simplegit.git fbff5bc..72bbc59 master -> master Johnova historie revizí nakonec vypadá takto: Figure 60. Johnova historie po odeslání revize na server origin . Jessica mezitím pracovala na tématické větvi. Vytvořila tématickou větev s názvem issue54 a zapsala do ní tři revize. Zatím ještě nevyzvedla Johnovy změny, takže její historie revizí vypadá nějak takto: Figure 61. Jessičina tématická větev. Jessica chce synchronizovat svou práci s Johnem, a proto vyzvedne jeho data: # Jessičin počítač $ git fetch origin ... From jessica@githost:simplegit fbff5bc..72bbc59 master -> origin/master Tím stáhne práci, kterou mezitím odeslal John. Historie revizí Jessicy teď vypadá takto: Figure 62. Historie Jessicy po vyzvednutí Johnových změn. Jessica považuje svou tématickou větev za dokončenou, ale chce zjistit, co by měla do své práce začlenit, aby ji mohla odeslat. Spustí proto příkaz git log : $ git log --no-merges issue54..origin/master commit 738ee872852dfaa9d6634e0dea7a324040193016 Author: John Smith <jsmith@example.com> Date: Fri May 29 16:01:27 2009 -0700 removed invalid default value Zápis issue54..origin/master představuje filtr příkazu, kterým se Gitu říká, aby zobrazil seznam jen těch objektů revize, které se nacházejí v druhé z větví (zde origin/master ), ale které se nenacházejí v první větvi (zde issue54 ). Podrobně se budeme touto syntaxí zabývat v části Commit Ranges . Z výstupu vidíme, že existuje jediná revize, kterou zapsal John a kterou Jessica nesloučila se svou prací. Pokud začlení origin/master , bude to jediná revize, která změní její lokální práci. Teď může Jessica začlenit svou tématickou větev do své větve master (merge), pak začlenit Johnovu práci ( origin/master ) rovněž do své větve master a potom může vše znovu odeslat na server (push). Nejdříve se přepne zpět na svou větev master , aby do ní mohla vše integrovat: $ git checkout master Switched to branch 'master' Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded. Buď může nejdříve začlenit origin/master nebo issue54 . Obě revize jsou následníky té aktuální, takže na pořadí nezáleží. Konečný snímek bude stejný, ať zvolí jakékoli pořadí. Trochu se bude lišit jen historie revizí. Jessica se rozhodne začlenit nejdříve issue54 : $ git merge issue54 Updating fbff5bc..4af4298 Fast forward README | 1 + lib/simplegit.rb | 6 +++++- 2 files changed, 6 insertions(+), 1 deletions(-) Nevyskytly se žádné problémy. Jak vidíte, šlo o jednoduchý posun „rychle vpřed“. Nyní Jessica začlení Johnovu práci ( origin/master ): $ git merge origin/master Auto-merging lib/simplegit.rb Merge made by recursive. lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Začlenění proběhne čistě a Jessičina historie bude vypadat následovně: Figure 63. Jessičina historie po začlenění Johnových změn. Větev origin/master je dosažitelná z Jessičiny větve master , takže by měla být schopná práci úspěšně odeslat (za předpokladu, že John mezitím neodeslal další revizi): $ git push origin master ... To jessica@githost:simplegit.git 72bbc59..8059c15 master -> master Každý z nich provedl několik zápisů (commit) a úspěšně začlenil práci toho druhého (merge). Figure 64. Jessičina historie po odeslání všech změn zpět na server. Toto je jeden z nejjednodušších pracovních postupů. Po určitou dobu pracujete, obvykle na nějaké tématické větvi, a když je připravena k integraci, začleníte ji do své větve master . Chcete-li tuto práci sdílet, pak vyzvednete (fetch) a začleníte (merge) případné změny z origin/master do vaší větve master . Nakonec odešlete všechna data do větve master na serveru (push). Obvyklá posloupnost událostí vypadá takto: Figure 65. Obecná posloupnost událostí pro jednoduchý pracovní postup s více vývojáři. Soukromý řízený tým V následujícím scénáři se podíváme na role přispěvatelů ve větší soukromé skupině. Naučíte se, jak pracovat v prostředí, v němž na jednotlivých úkolech spolupracují malé skupiny a tyto týmové příspěvky jsou poté integrovány jinou skupinou. Řekněme, že John a Jessica spolupracují na jednom úkolu, zatímco Jessica a Josie pracují na jiném. Společnost v tomto případě používá typ pracovního postupu s integračním manažerem, kdy práci jednotlivých skupin integrují pouze někteří inženýři a větev master hlavního repozitáře mohou aktualizovat pouze oni. V tomto scénáři se veškerá práce provádí ve větvích jednotlivých týmů a později je spojována integrátory. Sledujme pracovní postup Jessicy pracující na dvou úkolech a spolupracující v tomto prostředí paralelně s dvěma různými vývojáři. Protože už má naklonovaný repozitář, rozhodne se pracovat nejprve na úkolu featureA . Vytvoří si pro něj novou větev a udělá v ní kus práce: # Jessičin počítač $ git checkout -b featureA Switched to a new branch 'featureA' $ vim lib/simplegit.rb $ git commit -am 'add limit to log function' [featureA 3300904] add limit to log function 1 files changed, 1 insertions(+), 1 deletions(-) V tomto okamžiku potřebuje sdílet svou práci s Johnem, a tak odešle revize své větve featureA na server. Jessica nemá oprávnění pro odesílání dat do větve master (ten mají pouze integrátoři), takže aby mohla s Johnem spolupracovat, musí své revize odeslat do jiné větve: $ git push -u origin featureA ... To jessica@githost:simplegit.git * [new branch] featureA -> featureA Jessica e-mailem Johnovi sdělí, že odeslala svou práci do větve pojmenované featureA a že se na ni může podívat. Zatímco čeká na zpětnou vazbu od Johna, rozhodne se, že začne pracovat spolu s Josie na úkolu featureB . Začne tím, že založí novou větev, která vychází ze serverové větve master : # Jessičin počítač $ git fetch origin $ git checkout -b featureB origin/master Switched to a new branch 'featureB' Jessica nyní vytvoří několik revizí ve větvi featureB : $ vim lib/simplegit.rb $ git commit -am 'made the ls-tree function recursive' [featureB e5b0fdc] made the ls-tree function recursive 1 files changed, 1 insertions(+), 1 deletions(-) $ vim lib/simplegit.rb $ git commit -am 'add ls-files' [featureB 8512791] add ls-files 1 files changed, 5 insertions(+), 0 deletions(-) Jessičin repozitář vypadá nějak takto: Figure 66. Jessičina výchozí historie revizí. Je připravena odeslat svou práci, ale dostane e-mail od Josie, že již na server odeslala větev featureBee , v níž už je část práce hotová. Než bude Jessica moci odeslat svou práci na server, musí do ní nejprve začlenit práci Josie. Změny, které Josie provedla, vyzvedne příkazem git fetch : $ git fetch origin ... From jessica@githost:simplegit * [new branch] featureBee -> origin/featureBee Nyní může Jessica začlenit tyto změny do své práce příkazem git merge : $ git merge origin/featureBee Auto-merging lib/simplegit.rb Merge made by recursive. lib/simplegit.rb | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) Tady nastává drobný problém. Musí odeslat sloučenou práci ze své větve featureB do větve featureBee na serveru. Může tak učinit příkazem git push s určením lokální větve, za níž bude následovat dvojtečka (:) a za ní vzdálená větev: $ git push -u origin featureB:featureBee ... To jessica@githost:simplegit.git fba9af8..cd685d1 featureB -> featureBee Říká se tomu refspec . Podrobnější diskusi o specifikaci gitových referencí a o různých možnostech práce s nimi najdete v kapitole The Refspec . Všimněte si též příznaku -u . Jde o zkratku pro volbu --set-upstream , která se používá k nastavení větví pro pozdější zjednodušené odesílání (push) a stahování (pull). John poté pošle Jessice e-mail, aby jí sdělil, že odeslal několik změn do větve featureA , a poprosí ji, aby je ověřila. Jessica je stáhne spuštěním příkazu git fetch : $ git fetch origin ... From jessica@githost:simplegit 3300904..aad881d featureA -> origin/featureA Poté si může příkazem git log prohlédnout, co všechno bylo změněno: $ git log featureA..origin/featureA commit aad881d154acdaeb2b6b18ea0e827ed8a6d671e6 Author: John Smith <jsmith@example.com> Date: Fri May 29 19:57:33 2009 -0700 changed log output to 30 from 25 Nakonec začlení Johnovu práci do své vlastní větve featureA : $ git checkout featureA Switched to branch 'featureA' $ git merge origin/featureA Updating 3300904..aad881d Fast forward lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) Jessica by ráda něco vylepšila, a proto vytvoří novou revizi a odešle ji zpět na server: $ git commit -am 'small tweak' [featureA 774b3ed] small tweak 1 files changed, 1 insertions(+), 1 deletions(-) $ git push ... To jessica@githost:simplegit.git 3300904..774b3ed featureA -> featureA Historie revizí Jessicy bude nyní vypadat takto: Figure 67. Jessičina historie po zapsání revizí do větve s úkolem. Jessica, Josie a John pošlou zprávu integrátorům, že větve featureA a featureBee jsou na serveru připraveny k integraci do hlavní linie. Poté, co integrátoři uvedené větve začlení do hlavní linie, bude možné vyzvednout (fetch) nový bod sloučení (merge commit) a historie revizí bude vypadat takto: Figure 68. Historie Jessicy po začlenění obou jejích tématických větví. Mnoho skupin přechází na Git právě kvůli této možnosti paralelní spolupráce několika týmů a možnosti slučování různých linií práce až v pozdějších fázích procesu. Možnost spolupráce menších podskupin týmu prostřednictvím vzdálených větví — aniž by si práce vyžádala účast celého týmu nebo aby bránila ostatním v jiné práci — patří k obrovským výhodám Gitu. Posloupnost událostí ve zde popsaném pracovním postupu vypadá takto: Figure 69. Základní posloupnost událostí pracovního postupu řízeného týmu. Odštěpený veřejný projekt Přispívání do veřejných projektů je trochu odlišné. Protože nemáte oprávnění k tomu, abyste mohli aktualizovat větve projektu přímo, musíte svou práci správcům doručit nějakým jiným způsobem. První příklad popisuje, jak se přispívá s využitím odštěpení (fork) na gitovských hostitelských serverech, které podporují snadné vytváření odštěpených projektů. Tento mechanismus podporuje řada hostitelských serverů (včetně GitHub, BitBucket, Google Code, repo.or.cz a dalších) a řada správců projektů takový styl přispívání očekává. Další část pojednává o projektech, které upřednostňují přijímání záplat posílaných e-mailem. Nejdříve pravděpodobně naklonujete hlavní repozitář, vytvoříte tématickou větev — pro záplatu nebo pro posloupnost záplat, kterými chcete přispět — a zde vaši práci zrealizujete. Posloupnost příkazů vypadá v podstatě takto: $ git clone (url) $ cd project $ git checkout -b featureA # (něco uděláte) $ git commit # (něco uděláte) $ git commit Note Možná budete chtít použít rebase -i , abyste svou práci stlačili do jediného zápisu revize, nebo budete chtít práci přeuspořádat do posloupnosti revizí, která správci usnadní zkoumání záplat. Další informace o interaktivním přeskládání najdete v části Rewriting History . Až budete s prací ve větvi hotovi a budete ji chtít poslat zpět správcům, přejděte na původní stránku projektu a klikněte na tlačítko „Fork“, čímž vytvoříte vlastní odštěpený projekt, do kterého budete moci zapisovat. Poté musíte URL adresu tohoto nového repozitáře přidat jako druhý vzdálený repozitář, v tomto případě pojmenovaný myfork : $ git remote add myfork (url) Do něj teď musíte odeslat svou práci (push). Lepší bude, když do repozitáře odešlete svou tématickou větev (v které pracujete) než abyste výsledek začlenili do své větve master (merge) a odesílali tuto větev. Důvod je ten, že pokud nebude vaše práce přijata, nebo pokud z ní budou převzaty jen některé revize, nebudete muset svou větev master vracet zpět. Pokud správci provedou sloučení (merge), přeskládání (rebase) nebo částečné převzetí vaší práce (cherry-pick), budete stejně muset stáhnout změny z jejich repozitáře (pull): $ git push -u myfork featureA Pokud jste práci odeslali do odštěpeného repozitáře, musíte to správci oznámit. Často se tomu říká „pull request“, čili požadavek na stažení. Můžete ho vytvořit prostřednictvím webové stránky — GitHub má svůj vlastní mechanismus Pull Request, kterým se budeme zabývat v kapitole GitHub — nebo můžete spustit příkaz git request-pull a správci projektu ručně zaslat výstup příkazu e-mailem. Příkazu request-pull se zadává základní větev, do které chcete nechat vaši tématickou větev vtáhnout, a URL adresa gitového repozitáře, z kterého se má změna stahovat. Příkaz vypíše shrnutí všech změn, které by měly být vtaženy. Pokud chce například Jessica poslat Johnovi požadavek na stažení a vytvořila předtím dvě revize v tématické větvi, kterou právě odeslala, může zadat tento příkaz: $ git request-pull origin/master myfork The following changes since commit 1edee6b1d61823a2de3b09c160d7080b8d1b3a40: John Smith (1): added a new function are available in the git repository at: git://githost/simplegit.git featureA Jessica Smith (2): add limit to log function change log output to 30 from 25 lib/simplegit.rb | 10 +++++++++- 1 files changed, 9 insertions(+), 1 deletions(-) Výstup příkazu lze odeslat správci. Říká mu, odkud daná větev vychází, podá mu přehled o revizích a řekne mu, odkud lze práci stáhnout. U projektů, kde nevystupujete jako správce, je většinou jednodušší, aby vaše větev master stále sledovala větev origin/master a abyste práci prováděli v tématických větvích, které můžete v případě odmítnutí snadno odstranit. Izolováním tématických úkolů do tématických větví si také usnadníte přeskládání vaší práce v případě, kdy se vrchol v hlavním repozitáři mezi tím posunul a vaše revize se už nedají čistě aplikovat. Pokud například chcete do projektu odeslat druhé pracovní téma, nepokračujte v práci v tématické větvi, kterou jste právě odeslali. Začněte znovu od začátku z větve master hlavního repozitáře: $ git checkout -b featureB origin/master # (nějaká práce) $ git commit $ git push myfork featureB # (odeslání e-mailu správci) $ git fetch origin Teď je každé z vašich témat obsaženo v samostatném zásobníku — podobá se frontě záplat — a můžete je přepsat, přeskládat a upravit, aniž by se obě témata navzájem ovlivňovala nebo aby se mezi nimi vytvářela vzájemná závislost, viz obrázek: Figure 70. Počáteční historie revizí s prací na featureB . Řekněme, že správce projektu vtáhl do projektu několik jiných záplat a vyzkoušel vaši první větev, ale ta už se nedá začlenit čistě. V takovém případě můžete zkusit přeskládat tuto větev na vrchol větve origin/master , vyřešit za správce vzniklé konflikty a poté své změny ještě jednou odeslat: $ git checkout featureA $ git rebase origin/master $ git push -f myfork featureA Tím se vaše historie přepíše a bude vypadat jako na obrázku Historie revizí po přeskládání práce z featureA . . Figure 71. Historie revizí po přeskládání práce z featureA . Protože jste větev přeskládali, musíte u příkazu pro odesílání (push) přidat -f , abyste mohli serverové větvi featureA podsunout revizi, která není jejím potomkem. Druhou možností by bylo odeslání nové práce na server do jiné větve (nazvané třeba featureAv2 ). Podívejme se ještě na jeden možný scénář: Správce se podíval na práci ve vaší druhé větvi a tento koncept se mu líbí, ale rád by, abyste změnili jeden implementační detail. Této příležitosti využijete i k tomu, abyste za základ své práce vzali aktuální stav projektu ve větvi master . Začnete vytvořením nové větve z aktuální větve origin/master , nacpete (squash) do ní změny z featureB , vyřešíte případné konflikty, provedete požadovanou úpravu implementace a vše odešlete jako novou větev: $ git checkout -b featureBv2 origin/master $ git merge --squash featureB # (změníte implementaci) $ git commit $ git push myfork featureBv2 Volba --squash (stlačit) zajistí převzetí všech změn ze začleňované větve a stlačí je do podoby jedné sady změn, která vede ke stejnému stavu repozitáře, jako kdyby se provedlo opravdové sloučení (merge), ale nevytvoří se při tom bod sloučení [ 16 ] (merge commit). To znamená, že váš budoucí objekt revize bude mít jen jednoho rodiče a přitom vám umožní vnést všechny změny z jiné větve a poté provést další úpravy ještě před tím, než se nová revize zapíše. V případě základního procesu slučování (merge) může být užitečná i volba --no-commit , která oddálí vytvoření bodu sloučení. Teď už můžete správci zaslat zprávu, že jste provedli požadované změny a že je najde ve vaší větvi featureBv2 . Figure 72. Historie revizí po práci ve větvi featureBv2 . Veřejný projekt využívající elektronickou poštu Mnoho projektů si vytvořilo vlastní procedury pro přijímání záplat. Konkrétní pravidla si u každého projektu budete muset zjistit, protože budou odlišná. Protože existuje několik starších, větších projektů, kde se záplaty přijímají prostřednictvím vývojářské poštovní konference [ 17 ] , projdeme si teď podobný příklad. Pracovní postup je podobný jako v předchozím případě. Pro každou sérii záplat, na níž pracujete, vytvoříte samostatnou tématickou větev. Odlišnost spočívá ve způsobu doručování změn do projektu. Místo vytváření odštěpeného projektu a odesílání změn (push) do vlastní zapisovatelné verze, vygenerujete e-mailovou verzi každé série revizí a pošlete je e-mailem do poštovní konference vývojářů: $ git checkout -b topicA # (práce) $ git commit # (práce) $ git commit Teď máte dvě revize, které chcete odeslat do poštovní konference. Pro vygenerování souborů v podobě vhodné pro zaslání poštou použijete příkaz git format-patch . Každá revize se tím přetransformuje na e-mailovou zprávu, jejíž předmět bude tvořit první řádek zprávy k revizi a tělo e-mailu bude tvořeno zbytkem zprávy a samotnou záplatou. Výhodou tohoto postupu je, že se při aplikaci záplaty z e-mailu, který byl vygenerován příkazem format-patch , korektně převezmou všechny informace o revizi. $ git format-patch -M origin/master 0001-add-limit-to-log-function.patch 0002-changed-log-output-to-30-from-25.patch Příkaz format-patch vypíše názvy souborů záplaty, kterou vytváří. Přepínač -M řekne systému Git, aby zkontroloval případné přejmenování. Soubory nakonec vypadají takto: $ cat 0001-add-limit-to-log-function.patch From 330090432754092d704da8e76ca5c05c198e71a8 Mon Sep 17 00:00:00 2001 From: Jessica Smith <jessica@example.com> Date: Sun, 6 Apr 2008 10:17:23 -0700 Subject: [PATCH 1/2] add limit to log function Limit log functionality to the first 20 --- lib/simplegit.rb | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/simplegit.rb b/lib/simplegit.rb index 76f47bc..f9815f1 100644 --- a/lib/simplegit.rb +++ b/lib/simplegit.rb @@ -14,7 +14,7 @@ class SimpleGit end def log(treeish = 'master') - command("git log #{treeish}") + command("git log -n 20 #{treeish}") end def ls_tree(treeish = 'master') -- 2.1.0 Do souborů se záplatami můžete dodatečně připsat další informace, které jsou určeny pro poštovní konferenci, ale které nechcete vkládat do zprávy k revizi. Pokud mezi řádek --- a začátek záplaty (řádek lib/simplegit.rb ) přidáte nějaký text, mohou si ho vývojáři přečíst; ale při aplikaci záplaty se nepoužije. Při odesílání souboru do poštovní konference můžete soubor buď vložit do svého poštovního programu, nebo ho můžete odeslat z příkazového řádku. Vkládání textu často způsobuje problémy s formátováním, zvlášť v případě některých „chytřejších“ klientů, kteří správně nezachovávají zalamování řádků a prázdné znaky (whitespace). Git naštěstí nabízí nástroj, který vám pomůže odeslat správně formátované záplaty protokolem IMAP, což pro vás může být jednodušší. Ukážeme si, jak se dá záplata odeslat přes Gmail, což je nástroj pro poštu, který známe nejlépe. Podrobné pokyny pro používání celé řady poštovních programů najdete na konci dříve zmíněného souboru Documentation/SubmittingPatches ve zdrojovém kódu systému Git. Nejdříve si musíte ve vašem souboru ~/.gitconfig nastavit sekci „imap“. Každou hodnotu můžete nastavit zvlášť pomocí série příkazů git config , nebo můžete vložit hodnoty ručně. Na závěr by ale měl váš konfigurační soubor vypadat nějak takto: [imap] folder = "[Gmail]/Drafts" host = imaps://imap.gmail.com user = user@gmail.com pass = p4ssw0rd port = 993 sslverify = false Pokud váš server IMAP nepoužívá SSL, nebudou zřejmě dva poslední řádky vůbec třeba a hodnota hostitele bude imap:// , a nikoli imaps:// . Až toto nastavení dokončíte, můžete použít příkaz git imap-send , jímž umístíte sérii záplat (patch) do složky Drafts zadaného serveru IMAP: $ cat *.patch |git imap-send Resolving imap.gmail.com... ok Connecting to [74.125.142.109]:993... ok Logging in... sending 2 messages 100% (2/2) done V tomto okamžiku byste měli být schopni přejít do své složky Drafts, změnit pole To na adresu poštovní konference, do které záplatu posíláte, případně pole CC na správce nebo na osobu odpovědnou za tuto část, a odeslat. Záplaty můžete odesílat i přes SMTP server. Můžete rovněž nastavit každou hodnotu zvlášť sérií příkazů git config , nebo je můžete vložit ručně do sekce sendemail vašeho souboru ~/.gitconfig : [sendemail] smtpencryption = tls smtpserver = smtp.gmail.com smtpuser = user@gmail.com smtpserverport = 587 Jakmile je to hotové, můžete záplaty odeslat příkazem git send-email : $ git send-email *.patch 0001-added-limit-to-log-function.patch 0002-changed-log-output-to-30-from-25.patch Who should the emails appear to be from? [Jessica Smith <jessica@example.com>] Emails will be sent from: Jessica Smith <jessica@example.com> Who should the emails be sent to? jessica@example.com Message-ID to be used as In-Reply-To for the first email? y Git poté vytvoří log s určitými informacemi, který bude pro každou odesílanou záplatu vypadat asi takto: (mbox) Adding cc: Jessica Smith <jessica@example.com> from \line 'From: Jessica Smith <jessica@example.com>' OK. Log says: Sendmail: /usr/sbin/sendmail -i jessica@example.com From: Jessica Smith <jessica@example.com> To: jessica@example.com Subject: [PATCH 1/2] added limit to log function Date: Sat, 30 May 2009 13:29:15 -0700 Message-Id: <1243715356-61726-1-git-send-email-jessica@example.com> X-Mailer: git-send-email 1.6.2.rc1.20.g8c5b.dirty In-Reply-To: <y> References: <y> Result: OK Shrnutí Tato část se zabývala obvyklými pracovními postupy, které týkají několika velmi odlišných typů gitových projektů, s kterými se asi setkáte. Uvedla pár nových nástrojů, které vám pomohou celý proces zvládnout. V další části uvidíte, jak se pracuje na druhé straně — jak se spravuje gitový projekt. Dozvíte se, jak být benevolentním diktátorem nebo integračním manažerem. 16 . Pozn. překl.: Nezapíše se tedy revize. Jinými slovy, nevytvoří se žádný objekt revize. Změny budou promítnuté jen to pracovního stromu. 17 . mailing list prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=kn | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상 | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=lo | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_US | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상품 | 2026-01-13T09:29:23 |
https://telegram.org/dl?tme=86e65db19b2cc6c8aa_12848882232352970832 | Telegram Applications English Bahasa Indonesia Bahasa Melayu Deutsch Español Français Italiano Nederlands O‘zbek Polski Português (Brasil) Türkçe Беларуская Русский Українська Қазақша العربية فارسی 한국어 Twitter Home FAQ Apps API Moderation Telegram Applications Telegram apps are open source and support reproducible builds . Anyone can independently verify that Telegram apps you download from App Store or Google Play were built using the exact same code that we publish. Mobile apps Telegram for Android Telegram for iPhone and iPad Desktop apps Telegram for Windows/Mac/Linux Telegram for macOS Web apps Telegram WebK Telegram WebA Telegram Database Library (TDLib) TDLib – a cross-platform client designed to facilitate creating custom apps on the Telegram platform. Telegram X for Android – a slick experimental Telegram client based on TDLib. Unofficial apps Unigram, a client optimized for Windows (based on TDLib ) Telegram CLI for Linux MadelineProto Source code This code allows security researchers to fully evaluate our end-to-end encryption implementation . It is also possible to independently verify that Telegram apps available on Google Play and App Store are built using the same code that we publish on GitHub. Telegram Database Library Cross-platform library for building custom Telegram apps, see TDLib for details. Licensed under Boost 1.0 . GitHub » Telegram for Android Official Android App, see Google Play Market page for full description. Licensed under GNU GPL v. 2 or later . GitHub » Download APK File » Telegram for iOS Licensed under GNU GPL v. 2 or later . GitHub » Telegram for macOS Native macOS client. Licensed under GNU GPL v. 2 . GitHub » Telegram for Web browsers Telegram Web, Version K . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Telegram Web, Version A . Mac, Windows, Linux, Mobile. Licensed under GNU GPL v. 3 . GitHub » Legacy JavaScript client . Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram React JavaScript client for browsers. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram Desktop Qt-based desktop client. Mac, Windows, Linux. Licensed under GNU GPL v. 3 . GitHub » Telegram for WP Licensed under GNU GPL v. 2 or later . GitHub » Telegram X for Android Alternative Telegram client for Android based on TDLib. Licensed under GPL v.3.0 GitHub » Unofficial apps Telegram CLI (Unofficial) Linux Command-line interface for Telegram. Licensed under GNU GPL v. 2 . GitHub » Unigram (Unofficial) A Telegram client optimized for Windows. Licensed under GNU GPL v. 3 or later . GitHub » MadelineProto (Unofficial) A PHP MTProto Telegram client. Licensed under GNU AGPL v. 3 . GitHub » Bug Bounty Program Telegram welcomes developers and the security research community to audit its services, code and protocol seeking vulnerabilities or security-related issues. Learn more about our Bug Bounty Program here . Telegram Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed. About FAQ Privacy Press Mobile Apps iPhone/iPad Android Mobile Web Desktop Apps PC/Mac/Linux macOS Web-browser Platform API Translations Instant View About Blog Press Moderation | 2026-01-13T09:29:23 |
http://dig.ccmixter.org/ccplus | Available under Royalty-Free License. Click for details on how to use. Toggle navigation donate to keep this library available! licenses tag search featured music for film music for games free for commercial use royalty free licensed 1 - 40 of 1,774 display 10 20 40 Available under Royalty-Free License. Click for details on how to use. Our artists count on you returning their generosity. It Really Helps when you filters × all licenses free for commercial use royalty free ccPlus license all time magic sort recent latest instrumental only reset filters I J U S T W A N N A SO SHA Tags: alternative , music_for_film , guitar , drums , female_vocals , electronic , synthesizer , piano , spoken_word , remix , ccplus Phone Neck ft. reiswerk Apoxode Tags: remix Sense SackJo22 Tags: downtempo , ballad , electronic , female_vocals , ambient , remix Kung-Fu Glitch cdk Tags: experimental , chill , remix , CBR Collective Relief Carosone Tags: keyboards , bass , remix , non_commercial , CBR I Saw the Future Ivan Chew Tags: future , remix , ccplus , VBR , VBR pushoutfromyourshore martinsea Tags: remix Changey - changed Beluga Ten Tags: chill , music_for_film , rock , guitar , drums , downtempo , ambient , multiple_formats , laid_back , casual , atmospheric , remix Retrospective Man Mr_Yesterday Tags: autumn , sunday , perspective , male_vocals , guitar , synthesizer , remix , CBR A Channel Snowflake Tags: magic , rock , alternative , female_vocals , guitar , bass , drums , synthesizer , remix , non_commercial Alchemist Apprentice Snowflake Tags: female_vocals , guitar , bass , piano , downtempo , remix , ccplus , non_commercial It's Love ft. Vidian Apoxode Tags: techno , rave , remix BinOut Admiral Bob Tags: experimental , remix Tracing My Steps Stefan Kartenberg Tags: folk , remix , VBR It's Deep SackJo22 Tags: female_vocals , guitar , harmonies , remix , ccplus lightSoy airtone Tags: synthesizer , music_for_film , remix , in_web , non_commercial Ascending (Hexagram 46) SackJo22 Tags: spoken_word , female_vocals , poem , iching , downtempo , contemplative , jazz , experimental , remix Parallel Pathways Snowflake Tags: music_for_film , anxiety , spiraling , duality , remix , non_commercial Electric Feelings Apoxode Tags: techno , rave , remix , non_commercial , CBR You and I Admiral Bob Tags: chill , mellow , remix , ccplus The Grave Gambol (Dead Bones Dance) PorchCat Tags: bop , death , dead , samhain , hip_hop , groove , horror , memento_mori , danse_macabre , remix , ccplus I Breathe Snowflake Tags: music_for_film , chill , downtempo , percussion , female_vocals , bass , synthesizer , piano , dreamy , meditation , yoga , tantra , string_theory , dawn , embodiment , consciousness , mother reflect ft airtone Apoxode Tags: instrumental , chill , remix , non_commercial , CBR Heading out with MJ ScOmBer Tags: purple , funky , edm , club , synthesizer , bass , drums , remix , non_commercial Viewing (Hexagram 20) SackJo22 Tags: spoken_word , female_vocals , chorus , upbeat , iching , remix She Will Bounce Back ft. Radioontheshelf Apoxode Tags: hip_hop , breaks , remix , CBR Life Is But A Dream J.Lang Tags: female_vocals , drums , bass , experimental , chill , hip_hop , funky , remix , non_commercial brokencloud airtone Tags: synthesizer , piano , remix , mixup , non_commercial , your Dove SackJo22 Tags: ambient , jazz , spoken_word , poem , bass , downtempo , remix , mixup Delays Delays Delays J.Lang Tags: female_vocals , bass , synthesizer , instrumental , loops , downtempo , remix , mixup Love is the Power ScOmBer Tags: electro , lo_fi , rock , synthesizer , bass , beats , toy_piano , remix , ccplus Not Yet Crossing SackJo22 Tags: soul , jazz , spoken_word , female_vocals , poem , harmonies , guitar , singing_bowls , remix , non_commercial I Wanna Move Apoxode Tags: techno , rave , remix , CBR , Bob What Really Is? spinningmerkaba Tags: remix , CBR , mono Pollinators Snowflake Tags: drums , bass , downtempo , hope , death_and_birth , evolve , extinction , climate_change , remix , mixup , non_commercial Hurricane ft. Admiral Bob Apoxode Tags: blues , downtempo , remix , CBR Imagining Imaginal SackJo22 Tags: downbeat , groove , meditative , spoken_word , somatic_regulation , remix , mixup , solidarity_songs , non_commercial Old Friend Admiral Bob Tags: acoustic , remix , mixup , non_commercial , nostalgic , this bluenotes airtone Tags: guitar , instrumental , bass , piano , jazz , music_for_film , music_for_video , remix , pell Can't Stand Still Apoxode Tags: techno , rave , remix , ccplus , CBR , mwic Here Licenses Privacy Terms Donate(!) Credits There Everywhere Twitter YouTube Vimeo Facebook Instagram Resources GitHub Query API Forums Contact | 2026-01-13T09:29:23 |
https://git-scm.com/book/id/v2/Git-di-Server-GitWeb | Git - GitWeb About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Memulai 1.1 Tentang Version Control 1.2 Sejarah Singkat Git 1.3 Dasar-dasar Git 1.4 Command Line 1.5 Memasang Git 1.6 Pengaturan Awal Git 1.7 Mendapatkan Bantuan 1.8 Kesimpulan 2. Git Basics 2.1 Mendapatkan Repository Git 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Alias Git 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git di Server 4.1 Protokol 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Ringkasan 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pengaturan dan Konfigurasi Akun 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Mengelola Organization 6.5 Scripting GitHub 6.6 Ringkasan 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Kostumisasi Git 8.1 Konfigurasi Git 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Ringkasan 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.7 Git di Server - GitWeb GitWeb Now that you have basic read/write and read-only access to your project, you may want to set up a simple web-based visualizer. Git comes with a CGI script called GitWeb that is sometimes used for this. Figure 49. The GitWeb web-based user interface. If you want to check out what GitWeb would look like for your project, Git comes with a command to fire up a temporary instance if you have a lightweight server on your system like lighttpd or webrick . On Linux machines, lighttpd is often installed, so you may be able to get it to run by typing git instaweb in your project directory. If you’re running a Mac, Leopard comes preinstalled with Ruby, so webrick may be your best bet. To start instaweb with a non-lighttpd handler, you can run it with the --httpd option. $ git instaweb --httpd=webrick [2009-02-21 10:02:21] INFO WEBrick 1.3.1 [2009-02-21 10:02:21] INFO ruby 1.8.6 (2008-03-03) [universal-darwin9.0] That starts up an HTTPD server on port 1234 and then automatically starts a web browser that opens on that page. It’s pretty easy on your part. When you’re done and want to shut down the server, you can run the same command with the --stop option: $ git instaweb --httpd=webrick --stop If you want to run the web interface on a server all the time for your team or for an open source project you’re hosting, you’ll need to set up the CGI script to be served by your normal web server. Some Linux distributions have a gitweb package that you may be able to install via apt or yum , so you may want to try that first. We’ll walk though installing GitWeb manually very quickly. First, you need to get the Git source code, which GitWeb comes with, and generate the custom CGI script: $ git clone git://git.kernel.org/pub/scm/git/git.git $ cd git/ $ make GITWEB_PROJECTROOT="/opt/git" prefix=/usr gitweb SUBDIR gitweb SUBDIR ../ make[2]: `GIT-VERSION-FILE' is up to date. GEN gitweb.cgi GEN static/gitweb.js $ sudo cp -Rf gitweb /var/www/ Notice that you have to tell the command where to find your Git repositories with the GITWEB_PROJECTROOT variable. Now, you need to make Apache use CGI for that script, for which you can add a VirtualHost: <VirtualHost *:80> ServerName gitserver DocumentRoot /var/www/gitweb <Directory /var/www/gitweb> Options ExecCGI +FollowSymLinks +SymLinksIfOwnerMatch AllowOverride All order allow,deny Allow from all AddHandler cgi-script cgi DirectoryIndex gitweb.cgi </Directory> </VirtualHost> Again, GitWeb can be served with any CGI or Perl capable web server; if you prefer to use something else, it shouldn’t be difficult to set up. At this point, you should be able to visit http://gitserver/ to view your repositories online. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://es-la.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Frootstock.io | Facebook Facebook Correo o teléfono Contraseña ¿Olvidaste tu cuenta? Crear cuenta nueva Se te bloqueó temporalmente Se te bloqueó temporalmente Parece que hiciste un uso indebido de esta función al ir muy rápido. Se te bloqueó su uso temporalmente. Back Español 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Registrarte Iniciar sesión Messenger Facebook Lite Video Meta Pay Tienda de Meta Meta Quest Ray-Ban Meta Meta AI Más contenido de Meta AI Instagram Threads Centro de información de votación Política de privacidad Centro de privacidad Información Crear anuncio Crear página Desarrolladores Empleo Cookies Opciones de anuncios Condiciones Ayuda Importación de contactos y no usuarios Configuración Registro de actividad Meta © 2026 | 2026-01-13T09:29:23 |
https://ja-jp.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Frootstock.io | Facebook Facebook メールアドレスまたは電話番号 パスワード アカウントを忘れた場合 新しいアカウントを作成 機能の一時停止 機能の一時停止 この機能の使用ペースが早過ぎるため、機能の使用が一時的にブロックされました。 Back 日本語 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) Português (Brasil) Français (France) Deutsch アカウント登録 ログイン Messenger Facebook Lite 動画 Meta Pay Metaストア Meta Quest Ray-Ban Meta Meta AI Meta AIのコンテンツをもっと見る Instagram Threads 投票情報センター プライバシーポリシー プライバシーセンター Facebookについて 広告を作成 ページを作成 開発者 採用情報 Cookie AdChoices 規約 ヘルプ 連絡先のアップロードと非ユーザー 設定 アクティビティログ Meta © 2026 | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=fr_CA | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상품 | 2026-01-13T09:29:23 |
https://googleonlinesecurity.blogspot.com/2007/07/automating-web-application-security.html | Google Online Security Blog: Automating web application security testing Security Blog The latest news and insights from Google on security and safety on the Internet Automating web application security testing July 16, 2007 Posted by Srinath Anantharaju, Security Team Cross-site scripting (aka XSS) is the term used to describe a class of security vulnerabilities in web applications. An attacker can inject malicious scripts to perform unauthorized actions in the context of the victim's web session. Any web application that serves documents that include data from untrusted sources could be vulnerable to XSS if the untrusted data is not appropriately sanitized. A web application that is vulnerable to XSS can be exploited in two major ways: Stored XSS - Commonly exploited in a web application where one user enters information that's viewed by another user. An attacker can inject malicious scripts that are executed in the context of the victim's session. The exploit is triggered when a victim visits the website at some point in the future, such as through improperly sanitized blog comments and guestbook entries, which facilitates stored XSS. Reflected XSS - An application that echoes improperly sanitized user input received as query parameters is vulnerable to reflected XSS. With a vulnerable application, an attacker can craft a malicious URL and send it to the victim via email or any other mode of communication. When the victim visits the tampered link, the page is loaded along with the injected script that is executed in the context of the victim's session. The general principle behind preventing XSS is the proper sanitization (via, for instance, escaping or filtering) of all untrusted data that is output by a web application. If untrusted data is output within an HTML document, the appropriate sanitization depends on the specific context in which the data is inserted into the HTML document. The context could be in the regular HTML body, tag attributes, URL attributes, URL query string attributes, style attributes, inside JavaScript, HTTP response headers, etc. The following are some (by no means complete) examples of XSS vulnerabilities. Let's assume there is a web application that accepts user input as the 'q' parameter. Untrusted data coming from the attacker is marked in red. Injection in regular HTML body - angled brackets not filtered or escaped <b>Your query ' <script>evil_script()</script> ' returned xxx results</b> Injection inside tag attributes - double quote not filtered or escaped <form ... <input name="q" value=" blah"><script>evil_script()</script> "> </form> Injection inside URL attributes - non-http(s) URL <img src=" javascript:evil_script() ">...</img> In JavaScript context - single quote not filtered or escaped <script> var msg = ' blah'; evil_script(); // ' ; // do something with msg variable </script> In the cases where XSS arises from meta characters being inserted from untrusted sources into an HTML document, the issue can be avoided either by filtering/disallowing the meta characters, or by escaping them appropriately for the given HTML context. For example, the HTML meta characters <, >, &, " and ' must be replaced with their corresponding HTML entity references &lt;, &gt;, &amp;, &quot; and &#39 respectively. In a JavaScript-literal context, inserting a backslash in front of \, ', " and converting the carriage returns, line-feeds and tabs into \r, \n and \t respectively should avoid untrusted meta characters being interpreted as code. How about an automated tool for finding XSS problems in web applications? Our security team has been developing a black box fuzzing tool called Lemon (deriving from the commonly-recognized name for a defective product). Fuzz testing (also referred to as fault-injection testing) is an automated testing approach based on supplying inputs that are designed to trigger and expose flaws in the application. Our vulnerability testing tool enumerates a web application's URLs and corresponding input parameters. It then iteratively supplies fault strings designed to expose XSS and other vulnerabilities to each input, and analyzes the resulting responses for evidence of such vulnerabilities. Although it started out as an experimental tool, it has proved to be quite effective in finding XSS problems. Besides XSS, it finds other security problems such as response splitting attacks, cookie poisoning problems, stacktrace leaks, encoding issues and charset bugs. Since the tool is homegrown it is easy to integrate into our automated test environment and to extend based on specific needs. We are constantly in the process of adding new attack vectors to improve the tool against known security problems. Update: I wanted to respond to a few questions that seem to be common among readers. I've listed them below. Thanks for the feedback. Please keep the questions and comments coming. Q. Does Google plan to market it at some point? A. Lemon is highly customized for Google apps and we have no plans of releasing it in near future. Q. Did Google's security team check out any commercially available fuzzers? Is the ability to keep improving the fuzzer the main draw of a homegrown tool? A. We did evaluate commercially available fuzzers but felt that our specialized needs could be served best by developing our own tools. Google 23 comments : Philipp Lenssen said... Thanks for the explanations. In a future post, can you explain how you limit the damage an XSS exploit cookie stealer on *.Google.com can do? E.g. if an XSS hole is found at groups.google.com (these things have been found in the past), how do you ensure it can't easily spread to mail.google.com -- if that's even possible if you want to keep a single sign on via Google Account? July 16, 2007 at 4:45 PM Alex said... Is Lemon going to be available to the public? July 16, 2007 at 5:21 PM Akuma said... If you talk about XSS you rearly should have mentioned the "XSS Cheat Sheet". You can pull it up with a Google search for that term, since i did not want to post the URL here ;-) It shows a lot more attack vectors. July 16, 2007 at 5:25 PM .mario said... Automated scanning will never be able to replace manual testing but it's a good and fast approcach to catch "low hanging fruits". If you are looking for more advanced vectors I recommend the xssDB hosted on GNUCITIZEN. The vectors from the XSS Cheat Sheet will find their way in the next days as well as some XSS injection verctors of mine. http://www.gnucitizen.org/xssdb/ Also we will add SQL injection vectors later. I am very interested in contributing to the Lemon project so if you need some manpower just drop me a line. Greetings, .mario July 16, 2007 at 5:48 PM pdp said... What about DOM-based XSS. This type of vector is quite common and extremely hard to detect. I don't think that there is a tool that can handle it at the moment. The XSSDB can be used in many different ways. Since it is community driven I guess you might be interested in consuming the feed into your Lemon tool to provide finner results. July 16, 2007 at 6:03 PM Javier Mendoza said... Just a question, after reading this I understand that Lemon is a testing box, with some scripts, programs and so to test the pages weakness to a XSS attack. I think this is great, but what about, apart from this, using a layer 7 firewall in front of the servers? At least here in Spain, these kind of boxes are not very common, although they filter HTTP request pretty well... Just my 2 cents, and sorry for my English! July 16, 2007 at 9:01 PM Pogo said... I'd like to know if Lemon is ever going to be released to the public. Any chance of this happening? July 17, 2007 at 2:02 PM Unknown said... > What about DOM-based XSS. This type > of vector is quite common and > extremely hard to detect. I don't > think that there is a tool that can > handle it at the moment. As long as they will not do javascript static/functional analysis, tool will not be able to test for this. And I don't think it will come by tomorrow.. :/ July 17, 2007 at 6:13 PM Andres Riancho said... Shameless plug! I have been working on a web application attack and audit framework for some time, maybe you guys would like to see it . Many things make w3af a great project: gpl, coded in python, extended using plugins and much much more!. The site is: http://w3af.sf.net July 18, 2007 at 9:04 PM Unknown said... I don't think your suggestion for preventing XSS can avoid the "Injection inside URL attributes - non-http(s) URL" XSS vlun. Hong July 22, 2007 at 4:09 AM Unknown said... While I recognize you have to start somewhere, there is little to no support from Google when your account has been compromised. You fill out a plain and simple Google form with no reccord or confirmation number issued. No promise of a response in 5 business days, etc., just soon as possible. With the billions you make, maybe next Google should try to buy a company who knows how to offer good customer service, and offer a tinely response to customers who don't know what to do, or where to turn and are anxious because thousands have been taken out of their accounts. Maybe they will get it back, but really its rather disappointing you can't even send a confirmation email to let us know you really did get the email and that its not "crawling" around somewhere in cyberspace. July 23, 2007 at 5:28 PM Mastishka said... This comment has been removed by the author. July 27, 2007 at 1:20 PM Mastishka said... I own a website and had a Google AdSense account. In the early days when I was getting information about earning money via my website, I came to know about Google AdSense. As an analyst I am always curious about what is happening behind the scenes, so I went through the AdSense ad generator code which can be easily download from Google's server, which they used to generate Ads. To know more about PPC model of advertisement I had gone through number of articles/reports on Pay Per Click mechanism including the report of Dr. Tuzhilin (Professor of Information Systems at the Stern School of Business at New York University), who evaluated Google’s invalid click detection efforts (Find PDF Report [Source: http://ebiquity.umbc.edu/blogger/2006/07/25/revealed-how-google-manages-click-fraud/]). After going through all those articles and analyzing Google’s code I found a way to simulate human behavior in click generation and page impressions in proper (acceptable) ratio from different geographic location (IP address) and was able to credit thousands of dollars in my AdSense account (By not a single human being generated click). So, do you realy think they are really having good things with them??? Contact me at lalit.arora@mgoos.com if you like to know more... July 27, 2007 at 1:21 PM antispam96 said... This comment has been removed by a blog administrator. August 21, 2007 at 11:09 PM Unknown said... This comment has been removed by a blog administrator. September 30, 2007 at 11:13 AM Unknown said... I am posting this message on behalf of Ishita Gureck who has profile on Orkut ,But facing problem because some intrudder,mischief people has create her two more profile with same name and details also has joined illegal communities from her fake profile. Her original profile has more than 100 scraps. but the fake two has 50 and 3 scraps respectively..when you search using ISHITA GURECK search option...there may be few political resons...We have well verified with details..I request to delete the same to avoid any further infeltration....Please help urgent..Is there any way to avoid any else to do such illegal act...Its major concern. September 30, 2007 at 11:21 AM ae said... @mario -- re: Human analysis -- it's interesting you say this. As we refine tests at WhiteHat, I get to measure percentages of vulnerability. e.g.- many classes of our XSS detection have a 99.9something% accuracy rate, and require almost no human validation. Others can drop as low as 40% accuracy, but as we learn with time we can streamline what to look for, variances, and document them, and the net results is that finding locations weak to XSS in over 600 hosts better than any "scanner" isn't that hard. @pdp -- DOM-based XSS: Um, we do this fairly well with WhiteHat Sentinel. We, like all the scanners, have a "DOM-based parser" as well as static analysis, but we have some tricks in automation, with humans added, that allow us to find this. @hong -- Attribute-based XSS. Done. Solved. Sentinel scanner, above. Took a while though. @GOS blog -- You realize the whole XSS problem isn't just a "javascript injection problem"? There's many other ways to find this, not to mention you have livescript, actionscript, mocha, vbscript, and good old HTML that presents issues. Take the image source tag -- the majority of modern browsers will not execute js directly in the src= tag, nor using the js embedded-as-an-image trick. Older IE, Opera, and some moz versions. Here's a handful of simple examples: http://www.anachronic.com/xss/ I'm curious if Google has a "protect our top browsers" or "protect all browsers" stance? October 1, 2007 at 3:39 PM ae said... @GOS blog -- re: recommendations, also one more BIG thing: Converting CRLF to \r\n can be really dangerous depending on when, where, and how it's done. In many, many applicatons folks do this wrong and you wind up with exploitable applications because \r\n lands somewhere in the headers, most commonly URI data, like a name-value pair, passed in the Location Header on a 302 redirect, but sometimes in a cookie with user-supplied value as well. This can give you full control of the HTTP Response, in addition to opening up some dangerous cache-poisoning attacks that are very hard to detect and measure. -ae October 1, 2007 at 3:58 PM Unknown said... what about url encoded attacks? u have not covered tht :-p November 11, 2007 at 1:14 AM COYOTE said... excuse me...... but am i the only one who is ennoyed from this eye test every time i want to search something on google?? anyway if the way stays like this, i'm sure not only me, a lot of google users would transfer to yahoo or others. Because it is ennoying March 12, 2008 at 6:37 AM Anonymous said... This comment has been removed by a blog administrator. March 23, 2008 at 10:25 AM Unknown said... To make automatic test for WEB site vulnerabilities I use CyD NET Utilities. The latest version has a new testing engine. Sometimes the program make mistakes but work fine and fast. September 4, 2009 at 9:45 AM Priti said... Is Lemon open for contribution from the Open Source Community? July 27, 2014 at 10:19 PM Post a Comment    Labels  #sharethemicincyber #supplychain #security #opensource AI Security android android security android tr app security big data biometrics blackhat C++ chrome chrome enterprise chrome security connected devices CTF diversity encryption federated learning fuzzing Gboard google play google play protect hacking interoperability iot security kubernetes linux kernel memory safety Open Source pha family highlights pixel privacy private compute core Rowhammer rust Security security rewards program sigstore spyware supply chain targeted spyware tensor Titan M2 VDP vulnerabilities workshop  Archive      2025 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2024 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2023 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2022 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2021 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2020 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2019 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2018 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2017 Dec Nov Oct Sep Jul Jun May Apr Mar Feb Jan     2016 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2015 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb Jan     2014 Dec Nov Oct Sep Aug Jul Jun Apr Mar Feb Jan     2013 Dec Nov Oct Aug Jun May Apr Mar Feb Jan     2012 Dec Sep Aug Jun May Apr Mar Feb Jan     2011 Dec Nov Oct Sep Aug Jul Jun May Apr Mar Feb     2010 Nov Oct Sep Aug Jul May Apr Mar     2009 Nov Oct Aug Jul Jun Mar     2008 Dec Nov Oct Aug Jul May Feb     2007 Nov Oct Sep Jul Jun May Feed Follow @google Follow Give us feedback in our Product Forums . Google Privacy Terms | 2026-01-13T09:29:23 |
https://git-scm.com/book/cs/v2/GitHub-P%c5%99isp%c3%adv%c3%a1n%c3%ad-do-projektu | Git - Přispívání do projektu About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Úvod 1.1 Správa verzí 1.2 Stručná historie systému Git 1.3 Základy systému Git 1.4 Příkazový řádek 1.5 Instalace systému Git 1.6 První nastavení systému Git 1.7 Získání nápovědy 1.8 Shrnutí 2. Základy práce se systémem Git 2.1 Získání repozitáře Git 2.2 Nahrávání změn do repozitáře 2.3 Zobrazení historie revizí 2.4 Návrat do předchozího stavu 2.5 Práce se vzdálenými repozitáři 2.6 Používání značek 2.7 Aliasy v Gitu 2.8 Shrnutí 3. Větve v systému Git 3.1 Větve v kostce 3.2 Základy větvení a slučování 3.3 Správa větví 3.4 Postupy při práci s větvemi 3.5 Vzdálené větve 3.6 Přeskládání 3.7 Shrnutí 4. Git na serveru 4.1 Protokoly 4.2 Zprovoznění Gitu na serveru 4.3 Generování veřejného klíče SSH 4.4 Nastavení serveru 4.5 Démon Git 4.6 Chytrý HTTP 4.7 GitWeb 4.8 GitLab 4.9 Možnosti hostování u třetí strany 4.10 Shrnutí 5. Distribuovaný Git 5.1 Distribuované pracovní postupy 5.2 Přispívání do projektu 5.3 Správa projektu 5.4 Shrnutí 6. GitHub 6.1 Zřízení účtu a úprava konfigurace 6.2 Přispívání do projektu 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Shrnutí 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Ladění v systému Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Shrnutí 8. Customizing Git 8.1 Git Configuration 8.2 Atributy Git 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Shrnutí 9. Git a ostatní systémy 9.1 Git as a Client 9.2 Migrating to Git 9.3 Shrnutí 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Balíčkové soubory 10.5 The Refspec 10.6 Přenosové protokoly 10.7 Správa a obnova dat 10.8 Environment Variables 10.9 Shrnutí A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Shrnutí A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 6.2 GitHub - Přispívání do projektu Přispívání do projektu Now that our account is set up, let’s walk through some details that could be useful in helping you contribute to an existing project. Odštěpení projektů If you want to contribute to an existing project to which you don’t have push access, you can “fork” the project. What this means is that GitHub will make a copy of the project that is entirely yours; it lives in your user’s namespace, and you can push to it. Note Historically, the term “fork” has been somewhat negative in context, meaning that someone took an open source project in a different direction, sometimes creating a competing project and splitting the contributors. In GitHub, a “fork” is simply the same project in your own namespace, allowing you to make changes to a project publicly as a way to contribute in a more open manner. Díky tomu se projekty nemusí starat o přidávání uživatelů do role spolupracovníků, kteří by měli právo zápisu. People can fork a project, push to it, and contribute their changes back to the original repository by creating what’s called a Pull Request, which we’ll cover next. This opens up a discussion thread with code review, and the owner and the contributor can then communicate about the change until the owner is happy with it, at which point the owner can merge it in. To fork a project, visit the project page and click the “Fork” button at the top-right of the page. Figure 89. The “Fork” button. After a few seconds, you’ll be taken to your new project page, with your own writeable copy of the code. The GitHub Flow GitHub is designed around a particular collaboration workflow, centered on Pull Requests. This flow works whether you’re collaborating with a tightly-knit team in a single shared repository, or a globally-distributed company or network of strangers contributing to a project through dozens of forks. It is centered on the Tématické větve workflow covered in Větve v systému Git . Here’s how it generally works: Create a topic branch from master . Make some commits to improve the project. Push this branch to your GitHub project. Open a Pull Request on GitHub. Discuss, and optionally continue committing. The project owner merges or closes the Pull Request. This is basically the Integration Manager workflow covered in Pracovní postup s integračním manažerem , but instead of using email to communicate and review changes, teams use GitHub’s web based tools. Let’s walk through an example of proposing a change to an open source project hosted on GitHub using this flow. Creating a Pull Request Tony is looking for code to run on his Arduino programmable microcontroller and has found a great program file on GitHub at https://github.com/schacon/blink . Figure 90. The project we want to contribute to. The only problem is that the blinking rate is too fast, we think it’s much nicer to wait 3 seconds instead of 1 in between each state change. So let’s improve the program and submit it back to the project as a proposed change. First, we click the Fork button as mentioned earlier to get our own copy of the project. Our user name here is “tonychacon” so our copy of this project is at https://github.com/tonychacon/blink and that’s where we can edit it. We will clone it locally, create a topic branch, make the code change and finally push that change back up to GitHub. $ git clone https://github.com/tonychacon/blink (1) Cloning into 'blink'... $ cd blink $ git checkout -b slow-blink (2) Switched to a new branch 'slow-blink' $ sed -i '' 's/1000/3000/' blink.ino (3) $ git diff --word-diff (4) diff --git a/blink.ino b/blink.ino index 15b9911..a6cc5a5 100644 --- a/blink.ino +++ b/blink.ino @@ -18,7 +18,7 @@ void setup() { // the loop routine runs over and over again forever: void loop() { digitalWrite(led, HIGH); // turn the LED on (HIGH is the voltage level) [-delay(1000);-]{+delay(3000);+} // wait for a second digitalWrite(led, LOW); // turn the LED off by making the voltage LOW [-delay(1000);-]{+delay(3000);+} // wait for a second } $ git commit -a -m 'three seconds is better' (5) [slow-blink 5ca509d] three seconds is better 1 file changed, 2 insertions(+), 2 deletions(-) $ git push origin slow-blink (6) Username for 'https://github.com': tonychacon Password for 'https://tonychacon@github.com': Counting objects: 5, done. Delta compression using up to 8 threads. Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 340 bytes | 0 bytes/s, done. Total 3 (delta 1), reused 0 (delta 0) To https://github.com/tonychacon/blink * [new branch] slow-blink -> slow-blink Clone our fork of the project locally Create a descriptive topic branch Make our change to the code Check that the change is good Commit our change to the topic branch Push our new topic branch back up to our GitHub fork Now if we go back to our fork on GitHub, we can see that GitHub noticed that we pushed a new topic branch up and present us with a big green button to check out our changes and open a Pull Request to the original project. You can alternatively go to the “Branches” page at https://github.com/<user>/<project>/branches to locate your branch and open a new Pull Request from there. Figure 91. Pull Request button If we click that green button, we’ll see a screen that asks us to give our Pull Request a title and description. It is almost always worthwhile to put some effort into this, since a good description helps the owner of the original project determine what you were trying to do, whether your proposed changes are correct, and whether accepting the changes would improve the original project. We also see a list of the commits in our topic branch that are “ahead” of the master branch (in this case, just the one) and a unified diff of all the changes that will be made should this branch get merged by the project owner. Figure 92. Pull Request creation page When you hit the Create pull request button on this screen, the owner of the project you forked will get a notification that someone is suggesting a change and will link to a page that has all of this information on it. Note Though Pull Requests are used commonly for public projects like this when the contributor has a complete change ready to be made, it’s also often used in internal projects at the beginning of the development cycle. Since you can keep pushing to the topic branch even after the Pull Request is opened, it’s often opened early and used as a way to iterate on work as a team within a context, rather than opened at the very end of the process. Iterating on a Pull Request At this point, the project owner can look at the suggested change and merge it, reject it or comment on it. Let’s say that he likes the idea, but would prefer a slightly longer time for the light to be off than on. Where this conversation may take place over email in the workflows presented in Distribuovaný Git , on GitHub this happens online. The project owner can review the unified diff and leave a comment by clicking on any of the lines. Figure 93. Comment on a specific line of code in a Pull Request Once the maintainer makes this comment, the person who opened the Pull Request (and indeed, anyone else watching the repository) will get a notification. We’ll go over customizing this later, but if he had email notifications turned on, Tony would get an email like this: Figure 94. Comments sent as email notifications Anyone can also leave general comments on the Pull Request. In Pull Request discussion page we can see an example of the project owner both commenting on a line of code and then leaving a general comment in the discussion section. You can see that the code comments are brought into the conversation as well. Figure 95. Pull Request discussion page Now the contributor can see what they need to do in order to get their change accepted. Luckily this is very straightforward. Where over email you may have to re-roll your series and resubmit it to the mailing list, with GitHub you simply commit to the topic branch again and push, which will automatically update the Pull Request. In Pull Request final you can also see that the old code comment has been collapsed in the updated Pull Request, since it was made on a line that has since been changed. Adding commits to an existing Pull Request doesn’t trigger a notification, so once Tony has pushed his corrections he decides to leave a comment to inform the project owner that he made the requested change. Figure 96. Pull Request final An interesting thing to notice is that if you click on the “Files Changed” tab on this Pull Request, you’ll get the “unified” diff — that is, the total aggregate difference that would be introduced to your main branch if this topic branch was merged in. In git diff terms, it basically automatically shows you git diff master...<branch> for the branch this Pull Request is based on. See Jak zjistit provedené změny for more about this type of diff. The other thing you’ll notice is that GitHub checks to see if the Pull Request merges cleanly and provides a button to do the merge for you on the server. This button only shows up if you have write access to the repository and a trivial merge is possible. If you click it GitHub will perform a “non-fast-forward” merge, meaning that even if the merge could be a fast-forward, it will still create a merge commit. If you would prefer, you can simply pull the branch down and merge it locally. If you merge this branch into the master branch and push it to GitHub, the Pull Request will automatically be closed. This is the basic workflow that most GitHub projects use. Topic branches are created, Pull Requests are opened on them, a discussion ensues, possibly more work is done on the branch and eventually the request is either closed or merged. Note Not Only Forks It’s important to note that you can also open a Pull Request between two branches in the same repository. If you’re working on a feature with someone and you both have write access to the project, you can push a topic branch to the repository and open a Pull Request on it to the master branch of that same project to initiate the code review and discussion process. No forking necessary. Advanced Pull Requests Now that we’ve covered the basics of contributing to a project on GitHub, let’s cover a few interesting tips and tricks about Pull Requests so you can be more effective in using them. Pull Requests as Patches It’s important to understand that many projects don’t really think of Pull Requests as queues of perfect patches that should apply cleanly in order, as most mailing list-based projects think of patch series contributions. Most GitHub projects think about Pull Request branches as iterative conversations around a proposed change, culminating in a unified diff that is applied by merging. This is an important distinction, because generally the change is suggested before the code is thought to be perfect, which is far more rare with mailing list based patch series contributions. This enables an earlier conversation with the maintainers so that arriving at the proper solution is more of a community effort. When code is proposed with a Pull Request and the maintainers or community suggest a change, the patch series is generally not re-rolled, but instead the difference is pushed as a new commit to the branch, moving the conversation forward with the context of the previous work intact. For instance, if you go back and look again at Pull Request final , you’ll notice that the contributor did not rebase his commit and send another Pull Request. Instead they added new commits and pushed them to the existing branch. This way if you go back and look at this Pull Request in the future, you can easily find all of the context of why decisions were made. Pushing the “Merge” button on the site purposefully creates a merge commit that references the Pull Request so that it’s easy to go back and research the original conversation if necessary. Keeping up with Upstream If your Pull Request becomes out of date or otherwise doesn’t merge cleanly, you will want to fix it so the maintainer can easily merge it. GitHub will test this for you and let you know at the bottom of every Pull Request if the merge is trivial or not. Figure 97. Pull Request does not merge cleanly If you see something like Pull Request does not merge cleanly , you’ll want to fix your branch so that it turns green and the maintainer doesn’t have to do extra work. You have two main options in order to do this. You can either rebase your branch on top of whatever the target branch is (normally the master branch of the repository you forked), or you can merge the target branch into your branch. Most developers on GitHub will choose to do the latter, for the same reasons we just went over in the previous section. What matters is the history and the final merge, so rebasing isn’t getting you much other than a slightly cleaner history and in return is far more difficult and error prone. If you want to merge in the target branch to make your Pull Request mergeable, you would add the original repository as a new remote, fetch from it, merge the main branch of that repository into your topic branch, fix any issues and finally push it back up to the same branch you opened the Pull Request on. For example, let’s say that in the “tonychacon” example we were using before, the original author made a change that would create a conflict in the Pull Request. Let’s go through those steps. $ git remote add upstream https://github.com/schacon/blink (1) $ git fetch upstream (2) remote: Counting objects: 3, done. remote: Compressing objects: 100% (3/3), done. Unpacking objects: 100% (3/3), done. remote: Total 3 (delta 0), reused 0 (delta 0) From https://github.com/schacon/blink * [new branch] master -> upstream/master $ git merge upstream/master (3) Auto-merging blink.ino CONFLICT (content): Merge conflict in blink.ino Automatic merge failed; fix conflicts and then commit the result. $ vim blink.ino (4) $ git add blink.ino $ git commit [slow-blink 3c8d735] Merge remote-tracking branch 'upstream/master' \ into slower-blink $ git push origin slow-blink (5) Counting objects: 6, done. Delta compression using up to 8 threads. Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 682 bytes | 0 bytes/s, done. Total 6 (delta 2), reused 0 (delta 0) To https://github.com/tonychacon/blink ef4725c..3c8d735 slower-blink -> slow-blink Add the original repository as a remote named “upstream” Fetch the newest work from that remote Merge the main branch into your topic branch Fix the conflict that occurred Push back up to the same topic branch Once you do that, the Pull Request will be automatically updated and re-checked to see if it merges cleanly. Figure 98. Pull Request now merges cleanly One of the great things about Git is that you can do that continuously. If you have a very long-running project, you can easily merge from the target branch over and over again and only have to deal with conflicts that have arisen since the last time that you merged, making the process very manageable. If you absolutely wish to rebase the branch to clean it up, you can certainly do so, but it is highly encouraged to not force push over the branch that the Pull Request is already opened on. If other people have pulled it down and done more work on it, you run into all of the issues outlined in Rizika spojená s přeskládáním . Instead, push the rebased branch to a new branch on GitHub and open a brand new Pull Request referencing the old one, then close the original. References Your next question may be “How do I reference the old Pull Request?”. It turns out there are many, many ways to reference other things almost anywhere you can write in GitHub. Let’s start with how to cross-reference another Pull Request or an Issue. All Pull Requests and Issues are assigned numbers and they are unique within the project. For example, you can’t have Pull Request #3 and Issue #3. If you want to reference any Pull Request or Issue from any other one, you can simply put #<num> in any comment or description. You can also be more specific if the Issue or Pull request lives somewhere else; write username#<num> if you’re referring to an Issue or Pull Request in a fork of the repository you’re in, or username/repo#<num> to reference something in another repository. Let’s look at an example. Say we rebased the branch in the previous example, created a new pull request for it, and now we want to reference the old pull request from the new one. We also want to reference an issue in the fork of the repository and an issue in a completely different project. We can fill out the description just like Cross references in a Pull Request. . Figure 99. Cross references in a Pull Request. When we submit this pull request, we’ll see all of that rendered like Cross references rendered in a Pull Request. . Figure 100. Cross references rendered in a Pull Request. Notice that the full GitHub URL we put in there was shortened to just the information needed. Now if Tony goes back and closes out the original Pull Request, we can see that by mentioning it in the new one, GitHub has automatically created a trackback event in the Pull Request timeline. This means that anyone who visits this Pull Request and sees that it is closed can easily link back to the one that superseded it. The link will look something like Cross references rendered in a Pull Request. . Figure 101. Cross references rendered in a Pull Request. In addition to issue numbers, you can also reference a specific commit by SHA-1. You have to specify a full 40 character SHA-1, but if GitHub sees that in a comment, it will link directly to the commit. Again, you can reference commits in forks or other repositories in the same way you did with issues. Markdown Linking to other Issues is just the beginning of interesting things you can do with almost any text box on GitHub. In Issue and Pull Request descriptions, comments, code comments and more, you can use what is called “GitHub Flavored Markdown”. Markdown is like writing in plain text but which is rendered richly. See An example of Markdown as written and as rendered. for an example of how comments or text can be written and then rendered using Markdown. Figure 102. An example of Markdown as written and as rendered. GitHub Flavored Markdown The GitHub flavor of Markdown adds more things you can do beyond the basic Markdown syntax. These can all be really useful when creating useful Pull Request or Issue comments or descriptions. Task Lists The first really useful GitHub specific Markdown feature, especially for use in Pull Requests, is the Task List. A task list is a list of checkboxes of things you want to get done. Putting them into an Issue or Pull Request normally indicates things that you want to get done before you consider the item complete. You can create a task list like this: - [X] Write the code - [ ] Write all the tests - [ ] Document the code If we include this in the description of our Pull Request or Issue, we’ll see it rendered like Task Lists Figure 103. Task lists rendered in a Markdown comment. This is often used in Pull Requests to indicate what all you would like to get done on the branch before the Pull Request will be ready to merge. The really cool part is that you can simply click the checkboxes to update the comment — you don’t have to edit the Markdown directly to check tasks off. What’s more, GitHub will look for task lists in your Issues and Pull Requests and show them as metadata on the pages that list them out. For example, if you have a Pull Request with tasks and you look at the overview page of all Pull Requests, you can see how far done it is. This helps people break down Pull Requests into subtasks and helps other people track the progress of the branch. You can see an example of this in Task list summary in the Pull Request list. . Figure 104. Task list summary in the Pull Request list. These are incredibly useful when you open a Pull Request early and use it to track your progress through the implementation of the feature. Code Snippets You can also add code snippets to comments. This is especially useful if you want to present something that you could try to do before actually implementing it as a commit on your branch. This is also often used to add example code of what is not working or what this Pull Request could implement. To add a snippet of code you have to “fence” it in backticks. ```java for(int i=0 ; i < 5 ; i++) { System.out.println("i is : " + i); } ``` If you add a language name like we did there with java , GitHub will also try to syntax highlight the snippet. In the case of the above example, it would end up rendering like Rendered fenced code example. . Figure 105. Rendered fenced code example. Quoting If you’re responding to a small part of a long comment, you can selectively quote out of the other comment by preceding the lines with the > character. In fact, this is so common and so useful that there is a keyboard shortcut for it. If you highlight text in a comment that you want to directly reply to and hit the r key, it will quote that text in the comment box for you. The quotes look something like this: > Whether 'tis Nobler in the mind to suffer > The Slings and Arrows of outrageous Fortune, How big are these slings and in particular, these arrows? Once rendered, the comment will look like Rendered quoting example. . Figure 106. Rendered quoting example. Emoji Finally, you can also use emoji in your comments. This is actually used quite extensively in comments you see on many GitHub Issues and Pull Requests. There is even an emoji helper in GitHub. If you are typing a comment and you start with a : character, an autocompleter will help you find what you’re looking for. Figure 107. Emoji autocompleter in action. Emojis take the form of :<name>: anywhere in the comment. For instance, you could write something like this: I :eyes: that :bug: and I :cold_sweat:. :trophy: for :microscope: it. :+1: and :sparkles: on this :ship:, it's :fire::poop:! :clap::tada::panda_face: When rendered, it would look something like Heavy emoji commenting. . Figure 108. Heavy emoji commenting. Not that this is incredibly useful, but it does add an element of fun and emotion to a medium that is otherwise hard to convey emotion in. Note There are actually quite a number of web services that make use of emoji characters these days. A great cheat sheet to reference to find emoji that expresses what you want to say can be found at: http://www.emoji-cheat-sheet.com Images This isn’t technically GitHub Flavored Markdown, but it is incredibly useful. In addition to adding Markdown image links to comments, which can be difficult to find and embed URLs for, GitHub allows you to drag and drop images into text areas to embed them. Figure 109. Drag and drop images to upload them and auto-embed them. If you look back at Cross references in a Pull Request. , you can see a small “Parsed as Markdown” hint above the text area. Clicking on that will give you a full cheat sheet of everything you can do with Markdown on GitHub. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://www.fuse.io/fr/fusebox | Fusebox Fuse Turns Six: Future-Proofing the Entire Network Network Intro to Fuse EVM-compatible, Layer-2 Blockchain Get Fuse Explore the ways to get the native Fuse Network token Ecosystem Web3 Tools for Business Ignite Apply for Funding & Grants Tools Staking Stake FUSE for Rewards Bridge Bridge Assets To & From Fuse Safe Leading Platform to Manage Digital Assets Products Fuse Ember Integrate Web3 in Minutes Edison AI Agent Integrate Web3 in Minutes Gaming Coming soon... FuseBox Integrate Web3 in Minutes Case Studies Real World Case Studies Mystic Valley Freedom Wallet Sanduk Zneakrz Developers Documentation Build on Fuse RPC Providers Build crypto apps that scale Fuse Explorer Query Transactions & Activity Network Status Network performance and status Developers Documentation Build on Fuse RPC Providers Build crypto apps that scale Fuse Explorer Query Transactions & Activity Network Status Network performance and status Tools Ecosystem Web3 Tools for Business NFTs Mint Digital Collectibles on Artrific Community Support & Contribute Telegram Youtube LinkedIn Twitter Github Discord Governance Shape the Future of Fuse About Fuse Blog Latest news and updates Brand Kit Brand assets Jobs Explore opportunities Network Products Developers Ecosystem About Intro to Fuse EVM-compatible, Layer-2 Blockchain Ignite Apply for Funding & Grants Staking Stake FUSE for Rewards Bridge Bridge Assets To & From Fuse Safe Leading Platform to Manage Digital Assets Edison AI Agent Integrate Web3 in Minutes FuseBox Integrate Web3 in Minutes Case studies Real World Case Studies Real world case studies Mystic Valley Ticketing and Event Payments Freedom Wallet Bridging RWAs for Businesses Sanduk Send and receive digital dollars Zneakrz Frictionless e-commerce Documentation Learn about Fuse and get started with guides and tools for building on Fuse RPC Providers Build crypto apps that scale Fuse Explorer Query Transactions & Activity Network Status Network performance and status Get Started Quick Start Fuse Basics FuseBox Tutorials Explore our APIs Smart Wallets API Trade API Notifications API GraphQL API Ecosystem Web3 Tools for Business Community Support & Contribute Governance Shape the Future of Fuse Telegram Youtube LinkedIn Github Twitter Discord Get Fuse Explore the ways to get the native Fuse Network token Fuse Blog Latest news and updates Brand Kit Brand assets Jobs Explore opportunities EN FR JP CN Docs Ember Points Fuse Console FuseBox Connect your Business to Web3 Make blockchain accessible to all with our Account Abstraction Infrastructure. Start Now View Docs Client and mobile SDKs to connect users to web3 Edison AI is a powerful AI-driven business agent designed to simplify Web3 adoption for businesses and onboard customers with very little coding knowledge Wallet Account abstraction Flutter SDK ERC4337 Dedicated RPCs Webhooks Subgraphs Start with FuseBox Deploy contracts Abstract away complexity Simplify user onboarding and transactions Branded stablecoins Index and query blockchain data Build powerful dApp experiences Wallet as a service Deploy smart contracts with ease Monitor and manage deployments Online commerce Private nodes for your dApp Fast and reliable connectivity Loyalty programs Launch your own stablecoin Full control over token operations Composable yield Account abstraction standard Better UX for web3 users Automations Design token distributions Execute airdrops at scale Security & Cost cutting Track on-chain events Get real-time notifications FuseBox is powered by Account abstraction A robust Open Source Wallet-as-a-Service breaking down the remaining barriers for non-technical users and democratizing access to blockchain technology. Learn about AA Externally Owned Accounts Require private key Controlled by anyone with the private key Can initiate transactions and trigger contract accounts Transactions between such accounts can only be token transactions Smart Contract Wallet No private keys required Controlled by code Can trigger other contract accounts Transactions from an EOA to a Contract Account can trigger code that can do different things, such as transferring tokens or even creating a new contract Plans & Pricing Free plan Start receiving crypto payments in just a few clicks $0 Per month Up to 1000 monthly transactions 50 Edison AI prompts 10K RPC calls 10K API calls 10K Webhook calls Get Started Basic plan Popular Robust service. Low price. $50 Per month 1M transactions Up to 1000 Edison AI prompts 1M RPC calls 1M API calls 1M Webhook calls Access to all services on Fuse Reliable and fast support Get Started Premium Plan Get more. Maximize your business potential $500 Per month Everything in the Basic plan + Unlimited transactions Unlimited Edison AI agent Unlimited RPC calls Unlimited API calls Unlimited Webhook calls Individual support approach Coming soon Ready to start building for Web3? Start using Edison today Get started YouTube Github Twitter Telegram Discord Docs Getting started Fuse Network Mobile Stack Voltage Finance Web3 Glossary Charge Under the hood Explorer Documentation Fuse Staking Governance Service Status General Brand Kits Jobs Ambassador Program FAQ Subscribe to our newsletter © 2024 Fuse. All Rights Reserved | 2026-01-13T09:29:23 |
https://git-scm.com/book/zh-tw/v2/Git-%e5%9f%ba%e7%a4%8e-Git-Aliases | Git - Git Aliases About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 開始 1.1 關於版本控制 1.2 Git 的簡史 1.3 Git 基礎要點 1.4 命令列 1.5 Git 安裝教學 1.6 初次設定 Git 1.7 取得說明文件 1.8 摘要 2. Git 基礎 2.1 取得一個 Git 倉儲 2.2 紀錄變更到版本庫中 2.3 檢視提交的歷史記錄 2.4 復原 2.5 與遠端協同工作 2.6 標籤 2.7 Git Aliases 2.8 總結 3. 使用 Git 分支 3.1 簡述分支 3.2 分支和合併的基本用法 3.3 分支管理 3.4 分支工作流程 3.5 遠端分支 3.6 衍合 3.7 總結 4. 伺服器上的 Git 4.1 通訊協定 4.2 在伺服器上佈署 Git 4.3 產生你的 SSH 公鑰 4.4 設定伺服器 4.5 Git 常駐程式 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第3方 Git 託管方案 4.10 總結 5. 分散式的 Git 5.1 分散式工作流程 5.2 對專案進行貢獻 5.3 維護一個專案 5.4 Summary 6. GitHub 6.1 建立帳戶及設定 6.2 參與一個專案 6.3 維護專案 6.4 Managing an organization 6.5 Scripting GitHub 6.6 總結 7. Git 工具 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 總結 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. 附錄 A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. 附錄 B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. 附錄 C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.7 Git 基礎 - Git Aliases Git Aliases 在結束「Git 基礎」這個章節以前，在此想和你分享一些使用 Git 的技巧，讓你能夠更簡易且友善的使用 Git——別名（alias）。 在本書的後面章節，我們不會再提到，也不會假設你有使用別名的技巧。 但是你可能會需要知道如何使用它。 如果你只打了某個指令的一部份，Git 並不會自動推測出你想要的指令。 如果你懶得輸入完整的 Git 指令，你可以輕易的使用 git config 來替指令設定別名。 下面有一些你可能會想要設定別名的範例： $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status 舉其中一個例子來說，這樣的設定意味著你可以只打 git ci 而不需要打 git commit 。 隨著你深入使用 Git，你將會發現某些指令用的很頻繁，不要猶豫，馬上建立新的指令別名。 這個非常有用的技術還能用來創造一些你覺得應該存在的指令。 舉例來說，為了提高 unstage 檔案的方便性，你可以加入你自己的 unstage 別名： $ git config --global alias.unstage 'reset HEAD --' 而且這個 unstage 別名會讓以下兩個指令有相同的功用： $ git unstage fileA $ git reset HEAD -- fileA 這樣看起來更加簡單明瞭了。 此外，大家通常還會新增一個 last 指令如下： $ git config --global alias.last 'log -1 HEAD' 如此一來，你可以更簡易的看到最後的提交訊息： $ git last commit 66938dae3329c7aebe598c2246a8e6af90d04646 Author: Josh Goebel <dreamer3@example.com> Date: Tue Aug 26 19:48:51 2008 +0800 test for current head Signed-off-by: Scott Chacon <schacon@example.com> 如你所見，Git 會將別名直接取代成你別名內設定的指令。 然而，你可能會想要執行一個外部指令，而非 git 下的子指令。 在這個情況下，你需要在指令的開頭加個 ! 字元。 這個技巧在你如果想為 Git 倉儲撰寫自製工具時很有用。 我們可以用以下的範例設定 git visual 執行 gitk ： $ git config --global alias.visual '!gitk' prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/bg/v2/%d0%9d%d0%b0%d1%81%d1%82%d1%80%d0%be%d0%b9%d0%b2%d0%b0%d0%bd%d0%b5-%d0%bd%d0%b0-Git-Git-Hooks | Git - Git Hooks About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За Version Control системите 1.2 Кратка история на Git 1.3 Какво е Git 1.4 Конзолата на Git 1.5 Инсталиране на Git 1.6 Първоначална настройка на Git 1.7 Помощна информация в Git 1.8 Обобщение 2. Основи на Git 2.1 Създаване на Git хранилище 2.2 Запис на промени в хранилището 2.3 Преглед на историята на действията 2.4 Възстановяване на направени действия 2.5 Работа с отдалечени хранилища 2.6 Тагове в Git 2.7 Псевдоними в Git 2.8 Обобщение 3. Клонове в Git 3.1 Накратко за разклоненията 3.2 Основи на клоновете код и сливането 3.3 Управление на клонове 3.4 Стратегии за работа с клонове код 3.5 Отдалечени клонове 3.6 Управление на проект 3.7 Обобщение 4. GitHub 4.1 Създаване и настройка на акаунт 4.2 Как да сътрудничим в проект 4.3 Управление на проект 4.4 Управление на организация 4.5 Автоматизиране с GitHub 4.6 Обобщение 5. Git инструменти 5.1 Избор на къмити 5.2 Интерактивно индексиране 5.3 Stashing и Cleaning 5.4 Подписване на вашата работа 5.5 Търсене 5.6 Манипулация на историята 5.7 Мистерията на командата Reset 5.8 Сливане за напреднали 5.9 Rerere 5.10 Дебъгване с Git 5.11 Подмодули 5.12 Пакети в Git (Bundling) 5.13 Заместване 5.14 Credential Storage система 5.15 Обобщение 6. Настройване на Git 6.1 Git конфигурации 6.2 Git атрибути 6.3 Git Hooks 6.4 Примерна Git-Enforced политика 6.5 Обобщение 7. Git и други системи 7.1 Git като клиент 7.2 Миграция към Git 7.3 Обобщение 8. Git на ниско ниво 8.1 Plumbing и Porcelain команди 8.2 Git обекти 8.3 Git референции 8.4 Packfiles 8.5 Refspec спецификации 8.6 Транспортни протоколи 8.7 Поддръжка и възстановяване на данни 8.8 Environment променливи 8.9 Обобщение 9. Приложение A: Git в други среди 9.1 Графични интерфейси 9.2 Git във Visual Studio 9.3 Git във Visual Studio Code 9.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 9.5 Git в Sublime Text 9.6 Git в Bash 9.7 Git в Zsh 9.8 Git в PowerShell 9.9 Обобщение 10. Приложение B: Вграждане на Git в приложения 10.1 Git от команден ред 10.2 Libgit2 10.3 JGit 10.4 go-git 10.5 Dulwich A1. Приложение C: Git команди A1.1 Настройки и конфигурация A1.2 Издърпване и създаване на проекти A1.3 Snapshotting A1.4 Клонове и сливане A1.5 Споделяне и обновяване на проекти A1.6 Инспекция и сравнение A1.7 Дебъгване A1.8 Patching A1.9 Email команди A1.10 Външни системи A1.11 Административни команди A1.12 Plumbing команди 2nd Edition 6.3 Настройване на Git - Git Hooks Git Hooks Както повечето VCS системи, Git разполага с механизъм да изпълнява потребителски скриптове при възникване на определни събития. Тези скриптове са известни като Hooks (обработчици на събития) и се разделят на две групи: client-side и server-side. Клиентските hooks се пускат при операции като къмитване или сливане, докато сървърните отразяват събития от мрежови операции като например получаване на публикувани къмити. Можете да използвате hooks за всякакви неща. Инсталиране на Hook Всички hooks се съхраняват в hooks поддиректория в Git директорията. В повечето проекти това е .git/hooks . Когато инициализирате ново хранилище с git init , Git попълва въпросната директория с множество примерни скриптове, които освен че са полезни сами по себе си, също така и документират входните стойности за всеки скрипт. Всички примери са написани като шел скриптове с малко Perl, но всъщност кои да е коректно именувани и изпълними скриптове ще работят добре — можете да ги пишете на Ruby или Python или който език предпочитате. Ако искате да използвате фабрично доставените с Git скриптове, ще трябва да преименувате файловете, те завършват на .sample . За да разрешите hook скрипт, поставете коректно именуван (без разширение) и изпълним файл в hooks поддиректорията на .git. От този момент натам, той би трябвало да се изпълнява. Ще разгледаме няколко от основните имена за hooks файлове. Клиентски Hooks Налични са много client-side hooks. Тази секция ги разделя в категориите committing-workflow hooks, email-workflow скриптове и всичко останало. Забележка Важно е да споменем, че клиентските hooks не се копират , когато клонирате хранилище. Ако целта на скриптовете ви е да наложите дадена политика на работа, вероятно ще искате да правите това на сървъра, вижте примера в Примерна Git-Enforced политика . Committing-Workflow Hooks Първите четири hooks се занимават с процеса на къмитване. Скриптът pre-commit се пуска първи, още преди да напишете къмит съобщението. Той се използва за проверка на snapshot-а, който ще бъде къмитнат и следи дали не сте забравили нещо, дали се изпълняват тестове и т.н. Ако изходният код от този hook не е нулев (успешно завършен), то къмитът ще бъде отказан, въпреки че това е преодолимо с git commit --no-verify . Можете да правите неща като проверка на стила на писане на код (чрез изпълнение на lint или нещо от рода), проверка за празни символи в края на редовете (подразбиращият се hook върши именно това), или проверка за подходяща документация на нови методи в кода. Следва prepare-commit-msg hook-ът, който се стартира преди текстовия редактор, но след създаването на къмит съобщението по подразбиране. Това ви позволява да редактирате съобщението преди автора на къмита да го види на екрана. Този hook има няколко аргумента: пътя на файла, който съхранява къмит съобщението, типа на къмита и SHA-1 стойността, ако това е amended къмит. Това не е кой знае колко полезен Hook за нормални къмити, вместо това е приложим за такива, в които съобщението по подразбиране се генерира автоматично — като templated къмит съобщенията, сливащите къмити, а също и squashed и amended къмитите. Можете да го използвате в комбинация с commit template за да вмъквате информация програмно. Hook-ът commit-msg приема един параметър, който отново е път към временен файл, съдържащ къмит съобщението от разработчика. Ако скриптът завърши неуспешно Git отказва къмит процеса, така че можете да го използвате за валидиране на статуса на проекта или на самото къмит съобщение преди да позволите на къмита да мине. В последната част от главата ще видим как да ползваме този hook за да проверим дали подадено къмит съобщение отговаря на определени правила. След като целият къмит процес завърши се стартира post-commit hook-а. Той не приема параметри, но можете лесно да видите последния къмит с git log -1 HEAD . Общо взето, този hook се използва за нотификации или подобни процеси. Email Workflow Hooks Можете да настроите три client-side hooks за имейл базирани работни процеси. Всички те се стартират през командата git am , така че ако не я използвате, може да прескочите направо към следващата част в главата. Ако обаче получавате пачове през имейл, изготвени с git format-patch , тогава някой от тези скриптове може да ви е от полза. Първият изпълнен е applypatch-msg . Той приема един аргумент: името на временния файл с къмит съобщението. Git отказва пача, ако скриптът завърши с код за неуспех. Бихте могли да го използвате за да се уверите, че къмит съобщението е правилно форматирано или да го нормализирате с допълнителна редакция. Следващият hook, който се изпълнява при прилагане на пачове с git am е pre-applypatch . Противно на очакваното предвид името му, той се изпълнява след прилагането на пача, но преди да е направен къмит, така че би могъл да се използва за инспектиране на snapshot-а преди къмитване. С този скрипт можете да пускате тестове в работната директория. Ако нещо липсва или тестовете не минават, кодът за неуспех прекратява git am и пачът не се прилага. Последният hook касаещ git am операцията е post-applypatch , който се пуска след къмитване. Можете да го използвате за да нотифицирате група хора или автора на пача, че сте го приложили. С този скрипт не можете да спрете patching процеса. Други Client Hooks pre-rebase hook-ът се изпълнява преди пребазирането на каквото и да било и може да прекрати процеса при код за неуспех. Може да се използва например за забрана на пребазиране на публикувани в отдалечени хранилища къмити. Примерният pre-rebase hook, който Git инсталира прави това, въпреки че използва някои презумпции, които може да не отговарят на конкретния ви работен процес. Hook-ът post-rewrite се изпълнява от команди, които заместват къмити като git commit --amend и git rebase (макар и не от git filter-branch ). Единичният параметър, който получава, е командата направила заместването ведно със списък от промените на stdin . Този hook може да се ползва за повечето неща, за които могат и post-checkout и post-merge . След успешно изпълнение на команда git checkout , post-checkout hook-ът се стартира и бихте могли да го използвате за настройка на работната директория за специфичните изисквания на проекта например. Това може да означава преместване на големи двоични файлове, които не искате да проследявате, автоматично генериране на документация и т.н. Hook-ът post-merge се пуска след успешна merge команда. Може да се използва за възстановяване на информация, която Git не проследява — като например права върху файлове. Също така би могъл да се използва за проверка за наличето на външни за Git файлове, които бихте желали да се копират в проекта, когато работната директория се промени. Hook-ът pre-push работи по време на git push , след като отдалечените референции се обновят, но преди трансфера на каквито и да било обекти. Той получава в параметри името и адреса на отдалечените хранилища и списъка на референциите, които ще бъдат обновени през stdin . Може да се използва за валидация на набор от промени преди push операцията (код за неуспех на скрипта отменя публикуването). Git редовно извършва garbage collection действия като част от нормалната си работа извиквайки git gc --auto . Съответно, hook-ът pre-auto-gc се изпълнява преди процеса по почистването и може да ви известява, че то предстои да се направи или пък да го отмени, ако моментът не е подходящ за това. Сървърни Hooks В допълнение към клиентските hooks, ако сте системен администратор, можете да използвате множество важни сървърни такива за да прилагате почти всеки вид политика за вашия проект. Тези скриптове се изпълняват преди и след публикувания на промени в сървъра. Тези, които работят преди приемане на публикуването могат да върнат код за неуспех по всяко време и да го откажат, както и да отпечатат съобщение за грешка към клиента. Така че можете да си създадете push политика колкото сложна, колкото ви е нужно. pre-receive Първият изпълняван скрипт по време на обработка на push от клиент е pre-receive . Той приема от stdin списък на референциите, които се публикуват и ако излезе с код за неуспех никоя от тях не се приема. Може да ползвате този hook за да проверявате, че никоя от променените референции не е non-fast-forward или да правите контрол на достъп за всички референции и файлове, които ще бъдат променени от публикуването. update Скриптът update е много подобен на pre-receive , разликата е, че се изпълнява по веднъж за всеки клон, който публикуващият се опитва да обнови. Ако се обновяват няколко клона, pre-receive стартира само веднъж, докато update върви за всеки клон. Вместо да чете от стандартния вход, този скрипт приема три параметъра: името на референцията (клона), SHA-1 стойността, към която референцията е сочела преди push операцията, и SHA-1 стойността, която потребителят опитва да изпрати. Ако update скриптът завърши с код за неуспех, то само текущата референция се отказва, другите все още могат да бъдат обновени. post-receive Накрая, post-receive hook-ът се изпълнява след края на целия процес и може да се използва за обновяване на други услуги или нотифициране на потребители. Той получава същите stdin данни както и pre-receive . Сред примерните негови приложения биха могли да са разпращане на имейли до потребители, нотифициране на continuous integration сървър или ъпдейт на ticket-tracking система - можете дори да парсвате къмит съобщения, за да проверявате дали дадени тикети трябва да се отворят, редактират или затворят. Скриптът не може да спре push процеса, но връзката с клиента не се прекъсва докато той не завърши, така че бъдете внимателни, ако се опитвате да правите с него неща отнемащи прекалено дълго време. Подсказка Ако пишете скрипт/hook, който останалите трябва да четат, стремете се да използвате дългите версии на флаговете за командния ред. Само половин година по-късно ще ни благодарите. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/Git-sa-Server-Pagkuha-ng-Git-sa-isang-Server | Git - Pagkuha ng Git sa isang Server About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 4.2 Git sa Server - Pagkuha ng Git sa isang Server Pagkuha ng Git sa isang Server Ngayon ay tatalakayin natin ang pag-set up ng isang serbisyo ng Git na nagpapatakbo ng mga protokol sa iyong sariling server. Dito ipapakita namin ang mga mga utos at mga hakbang na kailangan upang gawin ang batayan, pinasimple na pag-install sa isang batay sa isang Linux na server, gayunman posible rin ipatakbo ang mga serbisyong ito sa mga MAC o Windows na server. Ang pag-setup ng server para sa produksyon sa loob ng iyong imprastraktura ay tiyak na may pagkakaiba sa mga hakbang sa seguridad o mga kagamitan ng operating system, ngunit sana ito ay magbibigay ng isang pangkalahatang ideya kung ano ang kasangkot. Upang simulang ang pag-set up ng anumang server sa Git, kailangan mong mag-export ng isang umiiral na repository patungo sa isang payak na repositoryo — isang repositoryo na walang laman na gumagana na repositoryo. Ito ay sa pangkalahatan ay madaling gawin. Upang ma-clone ang iyong repositoryo upang makapaglikha ng bagong payak na repositoryo, ipapatakbo mo ang clone na utos gamit ang --bare` na opsyon. Sa pamamagitan ng kombensyon, ang mga pangalan ng payak na repositoryo ay nagtatapos sa suffix na .git , tulad nito: $ git clone --bare my_project my_project.git Cloning into bare repository 'my_project.git'... done. Dapat ngayon ay may kopya ka na sa datos ng direktoryo sa Git sa iyong my_project.git na direktoryo. Ito ay halos katumbas sa katulad nito $ cp -Rf my_project/.git my_project.git Mayroong ilang mga maliit na kaibahan sa pagsasayos na file ngunit, para sa iyong layunin, ito ay isang clone ng parehong bagay. Kinukuha ang repositoryo ng Git mismo, walang isang gumagana na direktoryo, at maglikha ng isang direktoryo partikular para sa ito lamang. Paglalagay ng Payak na Repositoryo sa isang Server Ngayon na mayroon kanang isang payak na kopya ng iyong repositoryo, ang kailangan mo lamang gawin ay ilagay sa isang server at i-set up ang iyong mga protokol. Sabihin nating nakapag-setup ka ng isang server na ang tawag ay git.example.com na kung saan mayroon kang access sa SSH, at gusto mo iimbak lahat ng iyong mga repositoryo ng Git sa ilalamin ng direktoryo na /srv/git . Sa pag-aakala na ang /srv/git ay umiiral sa server, maaari kang mag-set up ng bagong repositoryo sa pamamagitan ng pag kopya ng iyong payak na repositoryo: $ scp -r my_project.git user@git.example.com:/srv/git Sa puntong ito, ang ibang mga gumagamit na mayroong read access na batay sa SSH sa /srv/git na direktoryo sa server ay maaring ma-clone ang iyong repositoryo sa pamamagitan ng pagpapatakbo ng $ git clone user@git.example.com:/srv/git/my_project.git Kung ang isang user ay nag-SSH patungo sa isang server at mayroong access sa pagsulat sa /srv/git/my_project.git na direktoryo, sila ay awtomatikong may access sa pag-push. Ang Git ay awtomatikong magdadagdag ng pahintulot ng pagsulat sa grupo sa isang repositoryo kung ipapatakbo mo ang git init na utos kasama ang --shared na opsyon. $ ssh user@git.example.com $ cd /srv/git/my_project.git $ git init --bare --shared Nakikita mo kung gaano kadali kumuha ng isang Git na repositoryo, maglikha ng isang payak na bersyon, at ilagay ito sa isang server kung saan ikaw at iyong mga katulong ay mayroong SSH na access. Ngayon ay handa ka na mag tulungan sa parehong proyekto. Mahalagang tandaan na ito lamang ang kailangan mong gawin upang makapagpatakbo ng isang kapaki-pakinabang na Git na server na kung saan ilang mga tao ang may access — magdagdag lamang ng mga SSH-able na mga account sa isang server, at maglagay ng isang payak na repositoryo na kung saan lahat ng mga gumagamit ay mayroong access sa pagbasa at access sa pagsulat. Handa ka ng magsimula — wala ng ibang kailangan. Sa ilang susunod na mga seksyon, makikita mo kung paano palawakin ang mga setup sa mas sopistikadong paraan. Kasali sa diskusyon na ito ang hindi kinakailangang lumikha ng mga account ng gumagamit, pagdaragdag ng pampublikong access sa pag basa sa mga repositoryo, pag-set up ng mga Web UI at marami pa. Gayunpaman, tandaan upang makapagtulungan kasama ang ilang mga tao sa isang pribadong proyekto, ang kailangan lamang ay isang SSH na server at isang payak na repositoryo. Maliit na mga Setup Kung ikaw ay isang maliit na sangkap o sinusubukan lamang ang Git sa iyong organisasyon at mayroon lamang iilang mga developer, maaaring maging simple ang mga bagay para sayo. Ang isa sa pinaka-komplikadong aspeto sa pag-set up ng isang Git na server ay ang pamamahala sa mga gumagamit. Kung nais mong gawing read-only ang ibang repositoryo para sa mga ilang mga gumagamit at pagbasa/pagsulat sa iba, ang access at mga pahintulot ay maaaring maging mahirap isaayos. Access sa SSH Kung ikaw ay may server na kung saan lahat na iyong mga developer ay mayroong access sa SSH, sa pangkalahatan ay mas madali i-setup ang iyong unang repositoryo doon, kasi halos wala kang kailangan gawin (na tinalakay natin sa huling seksyon). Kung gusto mo ng mas kumplikadong pahintulot sa mga uri ng kontrol sa access sa iyong mga repositoryo, maaari mong hawakan gamit ang karaniwan na pahintulot ng filesystem ng operating system ng iyong server. Kung gusto mong ilagay ang iyong mga repositoryo sa isang server na walang mga account para sa lahat ng nasa iyong koponan na gusto mo bigyan ng access sa pagsulat, kailangan mo mag set up ng access sa SSH para sa kanila. Ipinapalagay namin na kung ikaw ay mayroong server na kung saan kayang gawin ito, mayroon ka nang SSH server na naka-install, at ganun ganiyan ang paraan mo sa pag-access sa server. Mayroong ilang paraan na makapgbibigay ka ng access sa lahat ng nasa iyong koponan. Ang una ay mag set up ng mga account para sa lahat, na kung saan ay diretsahan ngunit ay maaring maging masalimuot. Maaaring hindi mo nais ipatakbo ang adduser at magtakda ng mga pansamantala na password para sa bawat gumgamit. Ang pangalawang paraan ay paglikha ng isang solong git na user account sa makina, tanungin ang lahat ng gumagamit na dapat magkaroon ng access sa pagsulat na i-send sayo ang pampublikong susi sa SSH, at idagdag ang susi na iyon sa ~/.ssh/authorized_keys na file ng bagong account na iyon. Sa puntong iyon, maaari ng i-access ng lahat ang makina na iyon sa pamamagitan ng git na account. Hindi ito nakakaapekto sa datos ng commit sa anumang paraan — Ang SSH na gumagamit na kumukonekta ka ay hindi nakakaapekto sa mga commit na iyong naitala. Isa pang paraan ito ay ang pagpapatunay sa iyong SSH na server mula sa isang LDAP na server o sa ibang sentralisadong pagpapatunay na kung saan ay na-set up mo na. Hangga’t ang bawat gumagamit ay makakuha ng access sa shell sa makina, anumang mekanismo sa papapatunay ng SSH na maisip mo ay dapat gumana. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/Git-sa-Server-Smart-HTTP | Git - Smart HTTP About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 4.6 Git sa Server - Smart HTTP Smart HTTP Tayo ngayon ay may awtentik na pag-access sa pamamamgitan ng SSH at di awtentik na pag-access sa pamamagitan ng git:// , ngunit mayroon ding isang protokol na kung saan maaaring gawin ng sabay-sabay. Ang pag-set up ng Smart HTTP ay pawang pagpapagana lang ng isang CGI script na may kasamang Git na tinatawag na git-http-backend sa server. Babasahin ng CGI ang landas at mga header na ipinadala ng isang git fetch o git push sa anumang HTTP URL at tukuyin kung maaaring makipag-usap ang kliyente sa HTTP (na totoo para sa anumang kliyente mula noong beryson 1.6.6). Kung makikita ng CGI na matalino ang kliyente, ito ay matalinong makikipag-usap dito; kung hindi man ito ay babalik sa pag-uugali ng pipi (so ito ay backward compatible para sa pagbasa sa mga luma na kliyente). Daanan natin ang isang pangunahing pag-set up. Ise-set up natin to gamit ang Apache bilang isang CGI server. Kung wala kang Apache na naka-set up, magagawa mo ito sa isang kahon sa Linux na may ganito: $ sudo apt-get install apache2 apache2-utils $ a2enmod cgi alias env Pinapayagan din nito ang mod_cgi , mod_alias , at mod_env na mga modyul, lahat ito ay kinakailangan upang mapagana ng maayos. Kailangan mo rin i-set ang grupo ng mangagamit ng Unix ng mga direktoryo ng /srv/git sa www-data upang mayroong mabasa- at pagsulat- na access sa mga repositoryo ang iyong web server, dahil ang instansya ng Apache na tumatakbo sa mga iskrip ng CGI ay (bilang default) tumatakbo bilang user na iyon. $ chgrp -R www-data /srv/git Sunod kailangan natin magdagdag ng mga bagay sa pagsasaayos ng Apache upang mapatakbo ang git-http-backend bilang handler ng anuman na darating papasok sa /git na landas ng iyong web server. SetEnv GIT_PROJECT_ROOT /srv/git SetEnv GIT_HTTP_EXPORT_ALL ScriptAlias /git/ /usr/lib/git-core/git-http-backend/ Kung hindi mo isasali ang GIT_HTTP_EXPORT_ALL na variable ng environment, pagkatapos ay ihahain lamang ng Git sa mga hindi awtentik na mga kliyente ang mga repositoryo na may git-daemon-export-ok na file sa loob nila, pareho sa ginawa ng Git daemon. Sa wakas nais mong sabihan ang Apache na pahintulutan ang mga request patungo sa git-http-backend at maghanap ng paraan na gawing awtentik ang mga pagsulat, posible sa isang block ng Auth kagaya nito: <Files "git-http-backend"> AuthType Basic AuthName "Git Access" AuthUserFile /srv/git/.htpasswd Require expr !(%{QUERY_STRING} -strmatch '*service=git-receive-pack*' || %{REQUEST_URI} =~ m#/git-receive-pack$#) Require valid-user </Files> Kinakailangan nito na gumawa ka ng .htpasswd na file na naglalaman ng mga password ng lahat ng mga balidong user. Narito ang isang halimbawa ng pagdagdag ng isang “schacon” na user sa file: $ htpasswd -c /srv/git/.htpasswd schacon Mayroong toneladang paraan na kung saan masagawang awtenik ng Apache ang mga user, kailangan mong pumili ng isa at ipatupad ito. Ito ang pinakasimpleng halimbawa na maaari nating gawin. Makikita mo rin ang tiyak na nais na i-set up ito gamit ang SSL upang lahat ng data nito ay encrypted. Hindi natin nais na talakayin ng malalim ang mga tiyak na pagsasaayos ng Apache, dahil maaaring gumagamit ka ng ibang server o ibang pangangailangan ng pagpapatunay. Ang idea ay ang Git ay may kasamang isang CGI na ang tawag ay git-http-backend na kung tinawag ay isasagawa ang lahat ng pag-aayos upang maipadala at matanggap ang mga datos gamit ang HTTP. Wala itong pagpapatunay na isinasagawa, ngunit madali ito kontrolin sa layer ng web server na tumatawag nito. Magagawa mo ito gamit ang halos anumang may kakayahan na CGI web server, so gamitin mo ang pinaka alam mo. Para sa karagdagang impormasyon sa pagsasaayos ng pagpapatunay sa Apache, tingnan ang mga doc ng Apache dito: http://httpd.apache.org/docs/current/howto/auth.html prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/tr/v2/GitHub-Kurumsal-Y%c3%b6netim | Git - Kurumsal Yönetim About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Başlangıç 1.1 Sürüm Denetimi 1.2 Git’in Kısa Tarihçesi 1.3 Git Nedir? 1.4 Komut Satırı 1.5 Git’i Yüklemek 1.6 Git’i İlk Defa Kurmak 1.7 Yardım Almak 1.8 Özet 2. Git Temelleri 2.1 Bir Git Reposu Oluşturma/Kopyalama 2.2 Değişikliklerin Repoya Kaydedilmesi 2.3 Katkı Geçmişini Görüntüleme 2.4 Değişiklikleri Geri Alma 2.5 Uzak Repo ile Çalışmak 2.6 Etiketleme 2.7 Komut Kısayolu (Alias) Ayarlama 2.8 Özet 3. Git Dalları 3.1 Dallar 3.2 Kısaca Dallandırma ve Birleştirme Temelleri 3.3 Dal Yönetimi 3.4 İş Akışı Dallandırması 3.5 Uzak Dallar 3.6 Yeniden Temelleme (rebase) 3.7 Özet 4. Bir Sunucuda Git Kurma 4.1 İletişim Kuralları (Protocols) 4.2 Bir Sunucuda Git Kurma 4.3 SSH Ortak Anahtarınızı Oluşturma 4.4 Sunucu Kurma 4.5 Git Cini (Daemon) 4.6 Akıllı HTTP 4.7 GitWeb 4.8 GitLab 4.9 Üçüncü Taraf Barındırma (Hosting) Seçenekleri 4.10 Özet 5. Dağıtık Git 5.1 Dağıtık İş Akışları 5.2 Projenin Gelişiminde Rol Almak 5.3 Bir Projeyi Yürütme 5.4 Özet 6. GitHub 6.1 Bir Projeye Katkıda Bulunmak 6.2 Proje Bakımı 6.3 Kurumsal Yönetim 6.4 GitHub’ı otomatikleştirme 6.5 Özet 7. Git Araçları 7.1 Düzeltme Seçimi 7.2 Etkileşimli İzlemleme (Staging) 7.3 Saklama ve Silme 7.4 Çalışmanızı İmzalama 7.5 Arama 7.6 Geçmişi Yeniden Yazma 7.7 Reset Komutunun Gizemleri 7.8 İleri Seviye Birleştirme 7.9 Rerere 7.10 Git’le Hata Ayıklama 7.11 Alt Modüller 7.12 Demetleme (Bundling) 7.13 Git Nesnesini Değiştirme 7.14 Kimlik Bilgisi Depolama 7.15 Özet 8. Git’i Özelleştirmek 8.1 Git Yapılandırması 8.2 Git Nitelikleri 8.3 Git Kancaları (Hooks) 8.4 Bir Örnek: Mecburi Git Politikası 8.5 Özet 9. Git ve Diğer Sistemler 9.1 İstemci Olarak Git 9.2 Git’e Geçiş 9.3 Özet 10. Dahili Git Ögeleri 10.1 Tesisat ve Döşeme (Plumbing ve Porcelain) 10.2 Git Nesneleri 10.3 Git Referansları 10.4 Packfiles 10.5 Refspec 10.6 Transfer Protokolleri 10.7 Bakım ve Veri Kurtarma 10.8 Ortam Değişkenleri 10.9 Özet A1. Ek bölüm A: Diğer Ortamlarda Git A1.1 Görsel Arayüzler A1.2 Visual Studio ile Git A1.3 Visual Studio Code ile Git A1.4 Eclipse ile Git A1.5 Sublime Text ile Git A1.6 Bash ile Git A1.7 Zsh ile Git A1.8 PowerShell ile Git A1.9 Özet A2. Ek bölüm B: Git’i Uygulamalarınıza Gömmek A2.1 Git Komut Satırı A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Ek bölüm C: Git Komutları A3.1 Kurulum ve Yapılandırma Komutları A3.2 Proje Oluşturma Komutları A3.3 Kısaca Poz (Snapshot) Alma A3.4 Dallandırma ve Birleştirme Komutları A3.5 Projeleri Paylaşma ve Güncelleme Komutları A3.6 İnceleme ve Karşılaştırma Komutları A3.7 Hata Ayıklama (Debugging) Komutları A3.8 Yamalama (Patching) A3.9 E-Posta Komutları A3.10 Harici Sistemler A3.11 Yönetim A3.12 Tesisat (Plumbing) Komutları 2nd Edition 6.3 GitHub - Kurumsal Yönetim Kurumsal Yönetim Tek kullanıcı hesaplarına ek olarak, GitHub’ın "kuruluşlar" ad altında kurumsal hesapları da bulunmaktadır. Kişisel hesaplar gibi, Kurumsal hesaplar da tüm projelerinin bulunduğu bir isim alanına sahiptir, ancak birçok farklı özelliğe de sahiptirler. Bu hesaplar, projelerin ortak sahipliğini paylaşan bir grup insanı temsil eder ve bu insanların alt gruplarını yönetmek için birçok araç sunmaktadır. Normalde, bu hesaplar Açık Kaynak grupları (örneğin ``perl`` veya ``rails``) veya şirketler (örneğin ``google`` veya ``twitter``) için kullanılır. Kısaca Kurumsal Hesap Kurumsal hesap oluşturmak oldukça kolaydır; herhangi bir GitHub sayfasının sağ üst köşesindeki ``+`` simgesine tıklayın ve menüden ``New organization`` (Yeni kuruluş) seçeneğini belirtin. Görsel 125. "Yeni kuruluş" ögesi. İlk olarak, kuruluşunuzu adlandırmanız ve grup için bir ana iletişim noktası olarak bir e-posta adresi girmeniz gerekecektir. Daha sonra, isterseniz, diğer kullanıcıları hesabın ortakları olarak davet edebilirsiniz. Bu adımları izlerseniz, çok yakında yepyeni bir kuruluşun sahibi olacaksınız. Orada saklayacağınız her şeyin açık kaynak olması durumunda, kişisel hesaplar gibi kurumsal hesaplar da ücretsizdir. Bir kuruluşun sahibi olarak bir repoyu çatalladığınızda, onu kuruluşunuzun ad alanına çatallamak üzere seçim yapabilirsiniz. Yeni repolar oluşturduğunuzda, bunları kişisel hesabınızın altında veya sahip olduğunuz herhangi bir kuruluşun altında oluşturabilirsiniz. Ayrıca, bu kuruluşlar altında oluşturulan her yeni repoyu, otomatik olarak "izlersiniz". Avatarınız "kişisel avatar"da olduğu gibi, kuruluşunuz için bir avatar yükleyerek, onu biraz kişiselleştirebilirsiniz. Ayrıca kişisel hesaplar gibi, tüm repolarınızı listeleyen ve diğer insanlar tarafından görülebilen kurumsal bir açılış sayfasına sahipsiniz. Şimdi de kurumsal hesaplarda biraz daha farklı olan bazı konuları ele alalım. Takımlar Kuruluşlar, bireysel kişilerle; bir nevi kuruluş içerisindeki bireysel kullanıcı hesapları ve bunların kurumsal repolara erişim türü grupları olan "takımlar" aracılığıyla ilişkilendirilir. Örnekle açıklamak gerekirse: diyelim ki şirketinizin üç reposu var: frontend , backend ve deployscripts . HTML/CSS/JavaScript geliştiricilerinizin frontend ve belki de backend repolarına, Operasyon ekibinizin ise backend ve deployscripts repolarına erişimi olmasını istersiniz. Takımlar özelliği, her bir repo için ayrı ayrı katılımcıları yönetmek zorunda kalmadan, bu işi kolaylaştırır. Kuruluş sayfası, bu kuruluşun altındaki tüm repoları, kullanıcıları ve takımları içeren basit bir gösterge paneline sahiptir. Görsel 126. Kuruluş sayfası. Takımlarınızı yönetmek için, Kuruluş sayfası. (kuruluş) sayfasının sağ tarafında bulunan "Teams" (Takımlar) kenar çubuğuna tıklayabilirsiniz. Bu sizi takımlara üye veya repo ekleyebileceğiniz, veya takımın ayarlarını ve erişim kontrol seviyelerini yönetebileceğiniz bir sayfaya götürecektir. Her takım, bu repolara salt okunur, okuma/yazma veya yönetici erişimli olarak ulaşabilir. Bu erişim seviyelerini Takım sayfası. (takım) sayfasındaki ``Settings`` (Ayarlar) düğmesine tıklayarak değiştirebilirsiniz. Görsel 127. Takım sayfası. Birini bir takıma davet ettiğinizde, davet edildiklerini bildiren bir e-posta alacaklardır. Ek olarak, takım @mentions (etiketlemeleri) (ör. @acmecorp/frontend ), bireysel kullanıcılarla aynı şekilde çalışır; ancak takımın tüm üyeleri o konuya abone olur. Bu özellik, bir takımdan birinin dikkatini çekmek istiyor ancak tam olarak kime soracağınızı bilmiyorsanız, çok kullanışlıdır. Bir kullanıcı birden fazla takıma üye olabilir, yani kendinizi sadece "access-control" (erişim kontrolü) takımlarıyla sınırlamayın. ux , css veya refactoring (yeniden düzenleme) gibi özel ilgi takımları, belirli türdeki sorular için çok faydalıdır. Aslında bu hukuk , renk körlüğü vs gibi tamamen farklı türde olanlar için de öyledir. Denetim Kaydı Kurumsal hesaplar sahiplerine ayrıca kuruluş altında neler olduğuyla ilgili tüm bilgilere erişim de sağlar. Audit Log (denetim kaydı) sekmesine giderek, kurumsal seviyede neler olduğunu, bunları kimin yaptığını ve dünyanın neresinde yapıldığını görebilirsiniz. Görsel 128. Denetim kaydı. Ayrıca belirli türdeki etkinliklere, belirli yerlere veya belirli kişilere göre filtreleme yapabilirsiniz. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=pt | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상�� | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=fa | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록�� | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=pt_BR | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상 | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_MX | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 �� | 2026-01-13T09:29:23 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.