Split (1)

train · ~858k rows (showing the first 350k)

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://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#discover-by-url-2	Instagram API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Instagram API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Posts API Collect by URL Discover by URL Comments API Collect by URL Reels API Collect by URL Discover by URL Social Media APIs Instagram API Scrapers Copy page Copy page Overview The Instagram API Suite offers multiple types of APIs, each designed for specific data collection needs from Instagram. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : N/A Interesting Columns : followers , post_count , post_hashtags , profile_name . Posts API This API allows users to collect multiple posts based on a single input URL (such as an Instagram reels URL, search URL or profile URL). Discovery functionality : - Direct URL of the Instagram reel - Direct URL of the search - Direct URL of the profile Interesting Columns : url , followers , hashtags , engagement_score_view . Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : comment_user , comment , likes_number , replies_number . The suite of APIs is designed to offer flexibility for targeted data collection, where users can input specific URLs to gather detailed post and comment data, either in bulk or with precise filtering options. Profiles API Collect by URL This API allows users to collect detailed data about an Instagram profile by providing the profile URL. It provides a comprehensive overview of an Instagram profile, including business and engagement information, posts, and user details. Input Parameters URL string required The Instagram profile URL. Output Structure Includes comprehensive data points: Page/Profile Details : account , id , followers , posts_count , is_business_account , is_professional_account , is_verified , avg_engagement , profile_name , profile_url , profile_image_link , and more. For all data points, click here . Posts API Collect by URL This API enables users to collect detailed data from Instagram posts by providing a post URL. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Post Details : post_id , description , hashtags , date_posted , num_comments , likes , content_type , video_view_count , video_play_count , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : photos , videos , thumbnail , display_url (link only, not the file itself), audio. Discover by URL This API allows users to discover recent Instagram posts from a public profile by providing the profile URL and specifying additional parameters. Input Parameters URL string required The Instagram profile URL. num_of_posts number The number of recent posts to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date). post_type string Specify the type of posts to collect (e.g., post, reel). Output Structure Includes comprehensive data points: Post Details: post_id , description , hashtags , date_posted , num_comments , likes , video_view_count , video_play_count ,and more. For all data points, click here . Page/Profile Details: user_posted , followers , posts_count , profile_image_link , is_verified , profile_url , is_paid_partnership , partnership_details , user_posted_id Attachments and Media: photos , videos , thumbnail , audio , display_url , content_type , product_type , coauthor_producers , tagged_users . This API is designed to allow for filtering, exclusion of specific posts, and collecting posts by type (regular post or reel) within a defined time frame. It provides detailed post and profile information, making it ideal for data collection and analytics. Comments API Collect by URL This API allows users to collect the latest comments from a specific Instagram post by providing the post URL. This API retrieves the most recent 10 comments along with associated metadata. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Comment Details : comment_id , comment_user , comment_user_url , comment_date , comment , likes_number , replies_number , replies , hashtag_comment , tagged_users_in_comment , and more. For all data points, click here . User Details : user_name , user_id , user_url We provide a limited set of data points about the profile. Post Metadata : post_url , post_user , post_id . Reels API Collect by URL This API allows users to collect detailed data about Instagram reels from public profiles by providing the reel URL. Input Parameters URL string required The Instagram reel URL. Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , tagged_users , num_comments , likes , views , video_play_count , length , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : video_url , thumbnail , audio_url . Discover by URL This API allows users to discover Instagram Reels videos from a profile URL or direct search URL. Input Parameters URL string required The Instagram profile or direct search URL. num_of_posts number The number of recent reels to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering reels in MM-DD-YYYY format. end_date string End date for filtering reels in MM-DD-YYYY format (should be later than start_date ). Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , num_comments , likes , views , video_play_count , top_comments , length , video_url , audio_url , content_id , and more. For all data points, click here . Profile Details : user_posted , followers , posts_count , following . Attachments and Media : video_url , thumbnail , audio_url (link only, not the file itself). This API provides detailed information about Instagram Reels, with filtering options by date range, exclusion of specific posts, and a limit on the number of reels collected. Was this page helpful? Yes No Facebook LinkedIn ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:24
https://git-scm.com/book/sl/v2/Osnove-Git-Snemanje-sprememb-v-repozitorij	Git - Snemanje sprememb v repozitorij 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.2 Osnove Git - Snemanje sprememb v repozitorij Snemanje sprememb v repozitorij Na tej točki bi morali v najboljšem primeru imeti pred seboj na vaši lokalni napravi repozitorij Git in izvlek (angl. checkout ) ali delovno kopijo vseh njegovih datotek. Običajno boste želeli začeti delati spremembe in potrditi posnetke teh sprememb v vaš repozitorij vsakič, ko projekt doseže stanje, ki ga želite posneti. Pomnite, da je lahko vsaka datoteka v vašem delovnem direktoriju v dveh stanjih: sledena ali nesledena . Sledene datoteke so datoteke, ki so bile v zadnjem posnetku, kot tudi katerekoli na novo pripravljene datoteke; lahko so nespremenjene, spremenjene, ali dane v področje priprave. Na kratko, sledene datoteke so datoteke, za katere Git ve. Nesledene datoteke so vse ostale — katerakoli datoteka v vašem delovnem direktoriju, ki ni bila v vašem zadnjem posnetku in ni v vašem področju priprave. Ko prvič klonirate repozitorij, bodo vse vaše datoteke sledene in nespremenjene, ker jih je Git ravnokar izvlekel in jih še niste kakorkoli urejali. Ko boste urejali datoteke, jih Git vidi kot spremenjene, ker ste jih spremenili od zadnje potrditve. Ko boste delali, izbrane spremenjene datoteke daste v pripravo in nato potrdite vse vaše spremembe v pripravi ter cikel se ponovi. Slika 8. Življenjski cikel statusa vaših datotek Preverjanje statusa vaših datotek Glavno orodje, ki ga uporabljate, da določite, katere datoteke so v kakšnem stanju, je ukaz git status . Če ta ukaz poženete neposredno po kloniranju, bi morali videti nekaj takega: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working tree clean To pomeni, da imate čisti delovni direktorij; z drugimi besedami, nobena od vaših datotek ni sledena ali spremenjena. Git tudi ne vidi kakršnihkoli nesledenih datotek, drugače bi bile tu izpisane. Na koncu vam ukaz pove, na kateri veji ste in vas obvesti, da ne izhaja iz iste veje na strežniku. Za sedaj je ta veja vedno master , kar je privzeto; to naj vas tu ne skrbi. Poglavje Veje Git bo šlo podrobno čez veje in reference. Opomba GitHub je v sredini leta 2020 spremenil privzeto ime glavne veje iz master v main , drugi gostitelji Git pa so sledili zgledu. Tako lahko opazite, da je privzeto ime veje v nekaterih novo ustvarjenih repozitorijih main in ne master . Poleg tega se lahko privzeto ime veje spremeni (kot ste videli v Vaše privzeto ime veje ), zato lahko vidite drugačno ime za privzeto vejo. Kljub temu pa Git še vedno uporablja master kot privzeto ime, zato ga bomo uporabljali v celotni knjigi. Recimo, da dodate v svoj projekt novo datoteko, kot je enostavna datoteka README . Če datoteka prej še ni obstajala in poženete git status , boste takole videli svojo nesledeno datoteko: $ 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) Vidite lahko, da vaša nova datoteka README ni sledena, ker je pod »Untracked files«, kar je v vašem izpisu statusa. Nesledeno v osnovi pomeni, da Git vidi datoteko, ki je niste imeli v prejšnjem posnetku (potrditvi) in še ni bila dana v pripravo; Git je ne bo začel vključevati v vaše potrjene posnetke, dokler mu tega eksplicitno ne naročite. To dela zato, da ne začnete po nesreči vključevati generiranih binarnih datotek ali ostalih datotek, ki jih niste mislili vključiti. Želeli boste začeti z vključevanjem README , torej začnimo s sledenjem datoteke. Sledenje novih datotek Da začnete slediti novi datoteki, uporabite ukaz git add . Da začnete slediti datoteki README , lahko poženete naslednje: $ git add README Če ponovno poženete svoj ukaz statusa, lahko vidite, da je vaša datoteka README sedaj sledena in dana v pripravo za potrjevanje: $ 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 Da je dana v pripravo, lahko veste, ker je pod naslovom »Changes to be committed«. Če na tej točki izvedete potrditev, bo različica datoteke v času, ko ste pognali git add , v naknadni zgodovini posnetka. Morda se spomnite, ko ste prej pognali git init , ste nato pognali git add <files> — to je bil začetek sledenja datotek v vašem direktoriju. Ukaz git add vzame ime poti za datoteko ali pa direktorij; če je direktorij, ukaz doda vse datoteke v tem direktoriju rekurzivno. Priprava spremenjenih datotek Spremenimo datoteko, ki je bila že sledena. Če spremenite prej sledeno datoteko imenovano CONTRIBUTING.md in nato ponovno poženete vaš ukaz git status , dobite nekaj, kar je videti takole: $ 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 Datoteka CONTRIBUTING.md se pojavi pod razdelkom imenovan »Changes not staged for commit« — kar pomeni, da je bila sledena datoteka spremenjena v delovnem direktoriju, vendar še ni bila dana v področje priprave. Za dodajanje v področje priprave, poženite ukaz git add . git add je ukaz z več pomeni — uporabite ga za začetek sledenja novih datotek, da daste datoteke v področje priprave in naredite druge stvari, kot je označevanje datotek konfliktov združevanja za rešene. Lahko je v pomoč razmišljati o tem bolj v smislu »Dodaj točno to vsebino naslednji potrditvi«, kot pa »Dodaj to datoteko projektu«. Poženimo sedaj git add , da dodamo datoteko CONTRIBUTING.md v področje priprave in nato ponovno poženimo 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 Obe datoteki sta dani v področje priprave in šli bosta v vašo naslednjo potrditev. Na tej točki predpostavimo, da se spomnite neke majhne spremembe, ki jo želite narediti v CONTRIBUTING.md , preden jo potrdite. Ponovno jo odprete in naredite to spremembo in že ste pripravljeni na potrditev. Vendar poženimo git status še enkrat: $ 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 Kaj za vraga? Sedaj je CONTRIBUTING.md izpisan tako kot v področju priprave kot tudi v področju izven le-te. Kako je to mogoče? Izkaže se, da Git da datoteko v področje priprave točno tako, kot je, ko poženete ukaz git add . Če naredite potrditev sedaj s tem, da poženete ukaz git commit , bo šla v potrditev različica CONTRIBUTING.md , kakršna je bila, ko ste nazadnje pognali ukaz git add , ne pa kot različica datoteke, kakor je videti v vašem delovnem direktoriju. Če spremenite datoteko po tem, ko poženete git add , morate ponovno pognati git add , da daste v področje priprave zadnjo različico datoteke: $ 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 Kratek status Medtem ko je izpis git status precej celovit, je tudi precej gostobeseden. Git ima tudi kratko zastavico statusa, da lahko vidite svoje spremembe na bolj kompakten način. Če poženete git status -s ali git status --short , dobite veliko bolj poenostavljen izpis iz ukaza. $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt Nove nesledene datoteke imajo zraven njih ?? , nove datoteke, ki so bile dodane v področje priprave, imajo A , spremenjene datoteke imajo M in tako dalje. Obstajata dva stolpca za izpis — levi stolpec označuje, da je bila datoteka dana v pripravo in desni stolpec označuje status v delovni drevesni strukturi. Torej na primer v tem izpisu je datoteka README spremenjena v delovnem direktoriju, vendar še ni dana v pripravo, medtem ko je datoteka lib/simplegit.rb spremenjena in dana v pripravo. Rakefile je bila spremenjena, dana v pripravo in nato ponovno spremenjena, torej so na njej spremembe, ki so dane tako v pripravo kot tudi ne. Ignoriranje datotek Pogostokrat boste imeli razred datotek, ki jih ne želite, da jih Git avtomatično doda ali celo prikazuje kot sledene. To so v splošnem avtomatsko generirane datoteke, kot so datoteke dnevnika ali datoteke proizvedene z vašim sistemom gradnje. V teh primerih lahko ustvarite vzorec seznama datotek, ki se mu prilegajo, z imenom .gitignore . Tu je primer datoteke .gitignore : $ cat .gitignore .[oa] ~ Prva vrstica pove Gitu, naj ignorira katerekoli datoteke, ki se končajo z ».o« ali ».a« — objekti in arhivske datoteke, ki so lahko produkt gradnje vaše kode. Druga vrstica pove Gitu, naj ignorira vse datoteke, ki se končajo s tildo ( ~ ), ki jo uporabljajo mnogi tekstovni urejevalniki, kot je Emacs, da označujejo začasne datoteke. Dodate lahko tudi direktorij log, tmp ali pid, avtomatsko generirano dokumentacijo itd. Nastavitev datoteke .gitignore preden začnete, je v splošnem dobra ideja, da po nesreči ne potrdite datotek, ki jih v resnici ne želite imeti v svojem repozitoriju Git. Pravila vzorcev, ki jih lahko vključite v datoteko .gitignore , so naslednja: Prazne vrstice ali vrstice, ki se začnejo z # , so ignorirane. Standardni vzorci glob delujejo in bodo uporabljeni rekurzivno skozi celotno delovno drevesno strukturo. Vzorce lahko začnete s poševnico ( / ), da se izognete rekurziji. Vzorce lahko zaključite s poševnico ( / ), da določite direktorij. Vzorec lahko negirate tako, da ga začnete s klicajem ( ! ). Vzorci glob so kot poenostavljeni splošni izrazi, ki jih uporablja lupina. Zvezdica ( * ) se prilega nič ali več znakom; [abc] se prilega katerimkoli znakom znotraj oglatih oklepajev (v tem primeru a, b, ali c); vprašaj ( ? ) se prilega enemu znaku; ter znaki oviti z oglatimi oklepaji in ločeni s pomišljaji ( [0-9] ) se prilegajo katerim koli znakom med njimi (v tem primeru od 0 do 9). Lahko uporabite tudi dve zvezdici, kar se prilega ugnezdenim direktorijem; a/*/z se prilega a/z , a/b/z a/b/c/z itd. Tu je drug primer datoteke .gitignore : # 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 Namig GitHub upravlja precej celovit seznam dobrih primerov datotek .gitignore za ducate projektov in jezikov na https://github.com/github/gitignore , če želite začetno točko za svoj projekt. Opomba V enostavnem primeru ima lahko repozitorij eno datoteko .gitignore v svojem vrhnjem direktoriju, ki velja rekurzivno za celoten repozitorij. Vendar je mogoče imeti tudi dodatne datoteke .gitignore v poddirektorijih. Pravila v teh ugnezdenih datotekah .gitignore veljajo samo za datoteke znotraj direktorija, v katerem je. Repozitorij izvorne kode jedra Linux ima 206 datotek .gitignore . Iti v podrobnosti večih datotek .gitignore je izven obsega te knjige; za več informacij poglejte man gitignore . Ogled vaših sprememb v področju priprave in izven njega Če vam ukaz git status ni preveč jasen — želite vedeti točno, kaj ste spremenili, ne samo katere datoteke so bile spremenjene — lahko uporabite ukaz git diff . git diff bomo pokrili v več podrobnostih kasneje, vendar ga boste uporabljali najpogosteje za odgovor na ti dve vprašanji: Kaj ste spremenili, vendar še ni dano v področje priprave? In kaj ste dali v področje priprave, da boste potrdili? Čeprav git status odgovori ta vprašanja zelo splošno z izpisom seznama imen datotek, vam git diff prikaže točne vrstice, ki so bile dodane in odstranjene — programski popravek, kakršne so bile. Recimo, da urejate in ponovno daste v področje priprave datoteko README ter nato uredite datoteko CONTRIBUTING.md , brez da jo daste v področje priprave. Če poženete vaš ukaz git status , vidite ponovno nekaj takega: $ 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 Da vidite, kaj ste spremenili, vendar niste še dali v področje priprave, vpišite git diff brez argumentov: $ 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 Ukaz primerja, kaj je v vašem delovnem direktoriju s tem, kar je v vašem področju priprave. Rezultat vam pove spremembe, ki ste jih naredili in ki še niso dane v pripravo. Če želite videti, kaj ste dali v področje priprave, da bo šlo v vašo naslednjo potrditev, lahko uporabite git diff --staged . Ta ukaz primerja vaše spremembe dane v področje priprave z vašo zadnjo potrditvijo: $ 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 Pomembno je omeniti, da git diff sam po sebi ne prikaže vseh sprememb, ki ste jih naredili od svoje zadnje potrditve — prikaže samo spremembe, ki še vedno niso dane področje priprave. Če ste dali v področje priprave vse svoje spremembe, vam git diff ne bo dal nobenega izpisa. Za drug primer, če daste datoteko CONTRIBUTING.md v področje priprave in jo nato uredite, lahko uporabite git diff , da vidite spremembe v datoteki, ki je dana v področje priprave in spremembe, ki še niso dane v pripravo. Če je naše okolje videti takole: $ 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 Sedaj lahko uporabite git diff , da vidite, kaj še vedno ni dano v področje priprave: $ 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 in git diff --cached , da vidite, kaj ste do sedaj dali v področje priprave ( --staged in --cached sta sinonima): $ 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 Opomba Git diff v zunanjem orodju Skozi preostanek knjige bomo nadaljevali z uporabo ukaza git diff na različne načine. Je še drug način za pogledati te spremembe, če imate namesto tega raje grafični ali zunanji pregledovalnik diff. Če poženete git difftool namesto git diff , lahko pogledate katerekoli od teh sprememb v programu, kot so emerge, vimdiff in mnogi ostali (vključno s komercialnimi produkti). Poženite git difftool --tool-help , da vidite, kaj je na voljo na vašem sistemu. Potrjevanje vaših sprememb Sedaj, ko je vaše področje priprave nastavljeno na način, kot ga želite, lahko potrdite svoje spremembe. Pomnite, da karkoli, kar še ni dano v področje priprave — katerekoli datoteke, ki jih ustvarite ali spremenite, in na njih še niste pognali git add , odkar ste jih uredili — ne bodo šle v to potrditev. Ostale bodo kot spremenjene datoteke na vašem disku. V tem primeru, recimo, da zadnjič, ko ste pognali git status , ste videli, da je vse dano v pripravo, torej ste pripravljeni, da potrdite svoje spremembe. Najenostavnejši način za potrditev je vpis git commit : $ git commit To zažene vaš urejevalnik po izbiri. Opomba To je nastavljeno v vaši spremenljivki okolja lupine $EDITOR — običajno vim ali emacs, vendar jo lahko nastavite, s čimer koli želite, z uporabo ukaza git config --global core.editor , kot ste videli v poglavju Začetek . Urejevalnik prikaže naslednje besedilo (ta primer je zaslon 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 Vidite lahko, da privzeto sporočilo potrditve vsebuje zadnji izpis ukaza git status , ki je zakomentiran in na vrhu ima eno prazno vrstico. Te komentarje lahko odstranite in vpišete svoje sporočilo potrditve, ali jih pustite tam, da vam pomagajo, se spomniti, kaj potrjujete. Opomba Za še bolj eksplicitni opomnik, kaj ste spremenili, lahko podate možnost -v ukazu git commit . To doda tudi razliko vaše spremembe v urejevalnik, da lahko točno vidite, katere spremembe potrjujete. Ko zapustite urejevalnik, Git ustvari vašo potrditev s sporočilom potrditve (z odstranjenimi komentarji in razliko). Alternativno lahko vpišete vaše sporočilo potrditve znotraj vrstice z ukazom commit , ki ga določite po zastavici -m takole: $ 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 Sedaj ste ustvarili svojo prvo potrditev! Vidite lahko, da vam je potrjevanje dalo izpis o samem sebi: v katero vejo ste dali potrditev ( master ), katera je kontrolna vsota SHA-1, ki jo ima potrditev ( 463dc4f ), koliko datotek je bilo spremenjenih in statistiko o dodanih in odstranjenih vrsticah v potrditvi. Zapomnite si, da potrditev snema posnetke, ki ste jih nastavili v svojem področju priprave. Karkoli, kar niste dali v pripravo, še vedno čaka spremenjeno; lahko naredite drugo potrditev, da to dodate v svojo zgodovino. Vsakič, ko izvedete potrditev, posnamete posnetek svojega projekta, ki ga lahko povrnete ali primerjate kasneje. Preskok področja priprave Čeprav je področje priprave posebej uporabno za izdelovanje potrditev točno takih, kakor jih želite, je včasih bolj kompleksno, kot ga potrebujete v svojem poteku dela. Če želite področje priprave preskočiti, Git ponuja enostavno bližnjico. Dodajanje možnosti -a ukazu git commit naredi, da Git avtomatično doda vsako datoteko, ki je že sledena, preden naredi potrditev in vam omogoči preskočiti del 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 'Add new benchmarks' [master 83e38c7] Add new benchmarks 1 file changed, 5 insertions(+), 0 deletions(-) Bodite pozorni, kako vam v tem primeru ni bilo potrebno pognati git add na datoteki CONTRIBUTING.md pred vašo potrditvijo. To je zato, ker zastavica -a vključuje vse spremenjene datoteke. To je priročno, vendar bodite pazljivi; včasih vam ta zastavica vključi tudi neželene spremembe. Odstranjevanje datotek Da odstranite datoteko iz Gita, jo morate odstraniti iz svojih sledenih datotek (bolj točno, odstraniti iz vašega področja priprave) in nato narediti potrditev. To naredi ukaz git rm in prav tako odstrani datoteko iz vašega delovnega direktorija, da je naslednjič ne vidite kot nesledeno datoteko. Če datoteko enostavno odstranite iz svojega delovnega direktorija, se prikaže pod »Changes not staged for commit« (to je izven področja priprave ), v področju vašega izpisa 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") Nato, če poženete git rm , doda odstranjevanje datoteke v področje priprave: $ 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 Naslednjič ko naredite potrditev, bo datoteka odstranjena in ne bo več sledena. Če ste datoteko spremenili, ali jo že dodali v področje priprave, morate prisiliti odstranjevanje z možnostjo -f . To je varnostna lastnost, da prepreči odstranjevanje podatkov po nesreči, ki še niso bili posneti v posnetku in ne morejo biti povrnjeni iz Gita. Druga uporabna stvar, ki jo morda želite narediti, je slediti datoteki v vašem delovnem drevesu, vendar jo odstraniti iz vašega področja priprave. Z drugimi besedami, morda želite slediti datoteki na svojem trdem disku, vendar ji ne več slediti v Gitu. To je posebej uporabno, če pozabite dodati nekaj v vašo datoteko .gitignore in jo po nesreči daste v pripravo, kot je velika datoteka dnevnika ali skupek prevedenih datotek .a . Da to naredite, uporabite možnost --cached : $ git rm --cached README Lahko podate datoteke, direktorije in vzorce datotek glob k ukazu git rm . To pomeni, da lahko naredite stvari, kot je: $ git rm log/\.log Bodite pozorni na levo poševnico ( \ ) pred . To je potrebno, ker Git naredi njegovo lastno razširjanje imen datotek poleg vašega razširjanja imen datotek lupine. Ta ukaz odstrani vse datoteke, ki imajo končnico .log v direktoriju log/ . Ali pa lahko naredite nekaj takega: $ git rm \*~ Ta ukaz odstrani vse datoteke, ki se končajo z ~ . Premikanje datotek Z razliko od ostalih sistemov VCS, Git eksplicitno ne sledi premikanju datotek. Če v Gitu preimenujete datoteko, ni shranjenih v Gitu nobenih metapodatkov, ki vam povejo, da ste preimenovali datoteko. Vendar je Git glede ugotavljanja precej pameten — z zaznavanjem premikanja datotek se bomo ukvarjali nekoliko kasneje. Torej je nekoliko nejasno, da ima Git ukaz mv . Če želite preimenovati datoteko v Gitu, lahko poženete nekaj takega: $ git mv file_from file_to kar deluje odlično. V bistvu, če poženete nekaj takega in pogledate status, boste videli, da ima Git to datoteko za preimenovano: $ 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 Vendar to je enakovredno pogonu nečesa takega: $ mv README.md README $ git rm README.md $ git add README Git posredno ugotovi, da gre za preimenovanje, torej ni pomembno, ali preimenujete datoteko na ta način ali z ukazom mv . Edina resnična razlika je, da je ukaz git mv en ukaz namesto treh — gre za funkcijo priročnosti. Bolj pomembno, za preimenovanje datoteke lahko uporabite katerokoli orodje želite in naslovite add/rm kasneje, preden potrjujete. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://git-scm.com/book/ko/v2/Git%ec%9d%98-%ea%b8%b0%ec%b4%88-%ec%88%98%ec%a0%95%ed%95%98%ea%b3%a0-%ec%a0%80%ec%9e%a5%ec%86%8c%ec%97%90-%ec%a0%80%ec%9e%a5%ed%95%98%ea%b8%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 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 2.2 Git의 기초 - 수정하고 저장소에 저장하기 수정하고 저장소에 저장하기 만질 수 있는 Git 저장소를 하나 만들었고 워킹 디렉토리에 Checkout도 했다. 이제는 파일을 수정하고 파일의 스냅샷을 커밋해 보자. 파일을 수정하다가 저장하고 싶으면 스냅샷을 커밋한다. 워킹 디렉토리의 모든 파일은 크게 Tracked(관리대상임)와 Untracked(관리대상이 아님)로 나눈다. Tracked 파일은 이미 스냅샷에 포함돼 있던 파일이다. Tracked 파일은 또 Unmodified(수정하지 않음)와 Modified(수정함) 그리고 Staged(커밋으로 저장소에 기록할) 상태 중 하나이다. 간단히 말하자면 Git이 알고 있는 파일이라는 것이다. 그리고 나머지 파일은 모두 Untracked 파일이다. Untracked 파일은 워킹 디렉토리에 있는 파일 중 스냅샷에도 Staging Area에도 포함되지 않은 파일이다. 처음 저장소를 Clone 하면 모든 파일은 Tracked이면서 Unmodified 상태이다. 파일을 Checkout 하고 나서 아무것도 수정하지 않았기 때문에 그렇다. 마지막 커밋 이후 아직 아무것도 수정하지 않은 상태에서 어떤 파일을 수정하면 Git은 그 파일을 Modified 상태로 인식한다. 실제로 커밋을 하기 위해서는 이 수정한 파일을 Staged 상태로 만들고, Staged 상태의 파일을 커밋한다. 이런 라이프사이클을 계속 반복한다. 그림 8. 파일의 라이프사이클. 파일의 상태 확인하기 파일의 상태를 확인하려면 보통 git status 명령을 사용한다. Clone 한 후에 바로 이 명령을 실행하면 아래과 같은 메시지를 볼 수 있다. $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean 위의 내용은 파일을 하나도 수정하지 않았다는 것을 말해준다. Tracked 파일은 하나도 수정되지 않았다는 의미다. Untracked 파일은 아직 없어서 목록에 나타나지 않는다. 그리고 현재 작업 중인 브랜치를 알려주며 서버의 같은 브랜치로부터 진행된 작업이 없는 것을 나타낸다. 기본 브랜치가 master이기 때문에 현재 브랜치 이름이 “master” 로 나온다. 브랜치 관련 내용은 차차 알아가자. Git 브랜치 에서 브랜치와 Refs에 대해 자세히 다룬다. 프로젝트에 README 파일을 만들어보자. README 파일은 새로 만든 파일이기 때문에 git status 를 실행하면 'Untracked files’에 들어 있다: $ 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” 부분에 속해 있는데 이것은 README 파일이 Untracked 상태라는 것을 말한다. Git은 Untracked 파일을 아직 스냅샷(커밋)에 넣어지지 않은 파일이라고 본다. 파일이 Tracked 상태가 되기 전까지는 Git은 절대 그 파일을 커밋하지 않는다. 그래서 일하면서 생성하는 바이너리 파일 같은 것을 커밋하는 실수는 하지 않게 된다. README 파일을 추가해서 직접 Tracked 상태로 만들어 보자. 파일을 새로 추적하기 git add 명령으로 파일을 새로 추적할 수 있다. 아래 명령을 실행하면 Git은 README 파일을 추적한다. $ git add README git status 명령을 다시 실행하면 README 파일이 Tracked 상태이면서 커밋에 추가될 Staged 상태라는 것을 확인할 수 있다. $ 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” 에 들어 있는 파일은 Staged 상태라는 것을 의미한다. 커밋하면 git add 를 실행한 시점의 파일이 커밋되어 저장소 히스토리에 남는다. 앞에서 git init 명령을 실행한 후, git add (files) 명령을 실행했던 걸 기억할 것이다. 이 명령을 통해 디렉토리에 있는 파일을 추적하고 관리하도록 한다. git add 명령은 파일 또는 디렉토리의 경로를 아규먼트로 받는다. 디렉토리면 아래에 있는 모든 파일들까지 재귀적으로 추가한다. Modified 상태의 파일을 Stage 하기 이미 Tracked 상태인 파일을 수정하는 법을 알아보자. 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” 에 있다. 이것은 수정한 파일이 Tracked 상태이지만 아직 Staged 상태는 아니라는 것이다. Staged 상태로 만들려면 git add 명령을 실행해야 한다. git add 명령은 파일을 새로 추적할 때도 사용하고 수정한 파일을 Staged 상태로 만들 때도 사용한다. Merge 할 때 충돌난 상태의 파일을 Resolve 상태로 만들때도 사용한다. add의 의미는 프로젝트에 파일을 추가한다기 보다는 다음 커밋에 추가한다고 받아들이는게 좋다. git add 명령을 실행하여 CONTRIBUTING.md 파일을 Staged 상태로 만들고 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 두 파일 모두 Staged 상태이므로 다음 커밋에 포함된다. 하지만 아직 더 수정해야 한다는 것을 알게 되어 바로 커밋하지 못하는 상황이 되었다고 생각해보자. 이 상황에서 CONTRIBUTING.md 파일을 열고 수정한다. 이제 커밋할 준비가 다 됐다고 생각할 테지만, Git은 그렇지 않다. 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 가 Staged 상태이면서 동시에 Unstaged 상태로 나온다. 어떻게 이런 일이 가능할까? git add 명령을 실행하면 Git은 파일을 바로 Staged 상태로 만든다. 지금 이 시점에서 커밋을 하면 git commit 명령을 실행하는 시점의 버전이 커밋되는 것이 아니라 마지막으로 git add 명령을 실행했을 때의 버전이 커밋된다. 그러니까 git add 명령을 실행한 후에 또 파일을 수정하면 git add 명령을 다시 실행해서 최신 버전을 Staged 상태로 만들어야 한다. $ 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 status -s 또는 git status --short 처럼 옵션을 주면 현재 변경한 상태를 짤막하게 보여준다. $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt 아직 추적하지 않는 새 파일 앞에는 ?? 표시가 붙는다. Staged 상태로 추가한 파일 중 새로 생성한 파일 앞에는 A 표시가, 수정한 파일 앞에는 M 표시가 붙는다. 위 명령의 결과에서 상태정보 컬럼에는 두 가지 정보를 보여준다. 왼쪽에는 Staging Area에서의 상태를, 오른쪽에는 Working Tree에서의 상태를 표시한다. README 파일 같은 경우 내용을 변경했지만 아직 Staged 상태로 추가하지는 않았다. lib/simplegit.rb 파일은 내용을 변경하고 Staged 상태로 추가까지 한 상태이다. 위 결과에서 차이점을 비교해보자. Rakefile 은 변경하고 Staged 상태로 추가한 후 또 내용을 변경해서 Staged 이면서 Unstaged 상태인 파일이다. 파일 무시하기 어떤 파일은 Git이 관리할 필요가 없다. 보통 로그 파일이나 빌드 시스템이 자동으로 생성한 파일이 그렇다. 그런 파일을 무시하려면 .gitignore 파일을 만들고 그 안에 무시할 파일 패턴을 적는다. 아래는 .gitignore 파일의 예이다. $ cat .gitignore .[oa] ~ 첫번째 라인은 확장자가 “.o” 나 “.a” 인 파일을 Git이 무시하라는 것이고 둘째 라인은 ~ 로 끝나는 모든 파일을 무시하라는 것이다. 보통 대부분의 텍스트 편집기에서 임시파일로 사용하는 파일 이름이기 때문이다. “.o” 와 “.a” 는 각각 빌드 시스템이 만들어내는 오브젝트와 아카이브 파일이고 ~ 로 끝나는 파일은 Emacs나 VI 같은 텍스트 편집기가 임시로 만들어내는 파일이다. 또 log, tmp, pid 같은 디렉토리나, 자동으로 생성하는 문서 같은 것들도 추가할 수 있다. .gitignore 파일은 보통 처음에 만들어 두는 것이 편리하다. 그래서 Git 저장소에 커밋하고 싶지 않은 파일을 실수로 커밋하는 일을 방지할 수 있다. .gitignore 파일에 입력하는 패턴은 아래 규칙을 따른다. 아무것도 없는 라인이나, # 로 시작하는 라인은 무시한다. 표준 Glob 패턴을 사용한다. 이는 프로젝트 전체에 적용된다. 슬래시( / )로 시작하면 하위 디렉토리에 적용되지(Recursivity) 않는다. 디렉토리는 슬래시( / )를 끝에 사용하는 것으로 표현한다. 느낌표( ! )로 시작하는 패턴의 파일은 무시하지 않는다. Glob 패턴은 정규표현식을 단순하게 만든 것으로 생각하면 되고 보통 쉘에서 많이 사용한다. 애스터리스크( * )는 문자가 하나도 없거나 하나 이상을 의미하고, [abc] 는 중괄호 안에 있는 문자 중 하나를 의미한다(그러니까 이 경우에는 a, b, c). 물음표( ? )는 문자 하나를 말하고, [0-9] 처럼 중괄호 안의 캐릭터 사이에 하이픈( - )을 사용하면 그 캐릭터 사이에 있는 문자 하나를 말한다. 애스터리스크 2개를 사용하여 디렉토리 안의 디렉토리 까지 지정할 수 있다. a/*/z 패턴은 a/z , a/b/z , a/b/c/z 디렉토리에 사용할 수 있다. 아래는 .gitignore 파일의 예이다. # 확장자가 .a인 파일 무시 .a # 윗 라인에서 확장자가 .a인 파일은 무시하게 했지만 lib.a는 무시하지 않음 !lib.a # 현재 디렉토리에 있는 TODO파일은 무시하고 subdir/TODO처럼 하위디렉토리에 있는 파일은 무시하지 않음 /TODO # build/ 디렉토리에 있는 모든 파일은 무시 build/ # doc/notes.txt 파일은 무시하고 doc/server/arch.txt 파일은 무시하지 않음 doc/.txt # doc 디렉토리 아래의 모든 .pdf 파일을 무시 doc//.pdf 힌트 GitHub은 다양한 프로젝트에서 자주 사용하는 .gitignore 예제를 관리하고 있다. 어떤 내용을 넣을지 막막하다면 https://github.com/github/gitignore 사이트에서 적당한 예제를 찾을 수 있다. 노트 .gitignore 를 사용하는 간단한 방식은 하나의 .gitignore 파일을 최상위 디렉토리에 하나 두고 모든 하위 디렉토리에까지 적용시키는 방식이다. 물론 .gitignore 파일을 하나만 두는 것이 아니라 하위 디렉토리에도 추가로 둘 수도 있다. .gitignore 정책은 현재 .gitignore 파일이 위치한 디렉토리와 그 하위 디렉토리에 적용된다. (리눅스 커널 소스 저장소에는 .gitignore 파일이 206개나 있음) 다수의 .gitignore 파일을 두고 정책을 적용하는 부분은 이 책에서 다루는 범위를 벗어난다. 자세한 내용은 man gitignore 에서 확인할 수 있다. Staged와 Unstaged 상태의 변경 내용을 보기 단순히 파일이 변경됐다는 사실이 아니라 어떤 내용이 변경됐는지 살펴보려면 git status 명령이 아니라 git diff 명령을 사용해야 한다. 보통 우리는 '수정했지만, 아직 Staged 파일이 아닌 것?'과 '어떤 파일이 Staged 상태인지?'가 궁금하기 때문에 git status 명령으로도 충분하다. 더 자세하게 볼 때는 git diff 명령을 사용하는데 Patch처럼 어떤 라인을 추가했고 삭제했는지가 궁금할 때 사용한다. git diff 는 나중에 더 자세히 다룬다. README 파일을 수정해서 Staged 상태로 만들고 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 명령을 실행하면 수정했지만 아직 staged 상태가 아닌 파일을 비교해 볼 수 있다. $ 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 이 명령은 워킹 디렉토리에 있는 것과 Staging Area에 있는 것을 비교한다. 그래서 수정하고 아직 Stage 하지 않은 것을 보여준다. 만약 커밋하려고 Staging Area에 넣은 파일의 변경 부분을 보고 싶으면 git diff --staged 옵션을 사용한다. 이 명령은 저장소에 커밋한 것과 Staging Area에 있는 것을 비교한다. $ 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 는 Unstaged 상태인 것들만 보여준다. 수정한 파일을 모두 Staging Area에 넣었다면 git diff 명령은 아무것도 출력하지 않는다. CONTRIBUTING.md 파일을 Stage 한 후에 다시 수정해도 git diff 명령을 사용할 수 있다. 이때는 Staged 상태인 것과 Unstaged 상태인 것을 비교한다. $ 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 명령으로 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 Staged 상태인 파일은 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 명령으로 여기저기서 써 먹는다. 즐겨 쓰거나 결과를 아름답게 보여주는 Diff 도구가 있으면 사용할 수 있다. git diff 대신 git difftool 명령을 사용해서 emerge, vimdiff 같은 도구로 비교할 수 있다. 상용 제품도 사용할 수 있다. git difftool --tool-help 라는 명령은 사용가능한 도구를 보여준다. 변경사항 커밋하기 수정한 것을 커밋하기 위해 Staging Area에 파일을 정리했다. Unstaged 상태의 파일은 커밋되지 않는다는 것을 기억해야 한다. Git은 생성하거나 수정하고 나서 git add 명령으로 추가하지 않은 파일은 커밋하지 않는다. 그 파일은 여전히 Modified 상태로 남아 있다. 커밋하기 전에 git status 명령으로 모든 것이 Staged 상태인지 확인할 수 있다. 그 후에 git commit 을 실행하여 커밋한다. $ git commit Git 설정에 지정된 편집기가 실행되고, 아래와 같은 텍스트가 자동으로 포함된다 (아래 예제는 Vim 편집기의 화면이다. 이 편집기는 쉘의 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 명령의 결과가 채워진다. 커밋한 내용을 쉽게 기억할 수 있도록 이 메시지를 포함할 수도 있고 메시지를 전부 지우고 새로 작성할 수 있다 (정확히 뭘 수정했는지도 보여줄 수 있는데, git commit 에 -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 이렇게 첫번째 커밋을 작성해보았다. commit 명령은 몇 가지 정보를 출력하는데 위 예제는 ( master ) 브랜치에 커밋했고 체크섬은 ( 463dc4f )이라고 알려준다. 그리고 수정한 파일이 몇 개이고 삭제됐거나 추가된 라인이 몇 라인인지 알려준다. Git은 Staging Area에 속한 스냅샷을 커밋한다는 것을 기억해야 한다. 수정은 했지만, 아직 Staging Area에 넣지 않은 것은 다음에 커밋할 수 있다. 커밋할 때마다 프로젝트의 스냅샷을 기록하기 때문에 나중에 스냅샷끼리 비교하거나 예전 스냅샷으로 되돌릴 수 있다. Staging Area 생략하기 Staging Area는 커밋할 파일을 정리한다는 점에서 매우 유용하지만 복잡하기만 하고 필요하지 않은 때도 있다. 아주 쉽게 Staging Area를 생략할 수 있다. git commit 명령을 실행할 때 -a 옵션을 추가하면 Git은 Tracked 상태의 파일을 자동으로 Staging Area에 넣는다. 그래서 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 명령으로 Tracked 상태의 파일을 삭제한 후에(정확하게는 Staging Area에서 삭제하는 것) 커밋해야 한다. 이 명령은 워킹 디렉토리에 있는 파일도 삭제하기 때문에 실제로 파일도 지워진다. Git 명령을 사용하지 않고 단순히 워킹 디렉터리에서 파일을 삭제하고 git status 명령으로 상태를 확인하면 Git은 현재 “Changes not staged for commit” (즉, Unstaged 상태)라고 표시해준다. $ 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 명령을 실행하면 삭제한 파일은 Staged 상태가 된다. $ 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 커밋하면 파일은 삭제되고 Git은 이 파일을 더는 추적하지 않는다. 이미 파일을 수정했거나 Staging Area에(역주 - Git Index라고도 부른다) 추가했다면 -f 옵션을 주어 강제로 삭제해야 한다. 이 점은 실수로 데이터를 삭제하지 못하도록 하는 안전장치다. 커밋 하지 않고 수정한 데이터는 Git으로 복구할 수 없기 때문이다. 또 Staging Area에서만 제거하고 워킹 디렉토리에 있는 파일은 지우지 않고 남겨둘 수 있다. 다시 말해서 하드디스크에 있는 파일은 그대로 두고 Git만 추적하지 않게 한다. 이것은 .gitignore 파일에 추가하는 것을 빼먹었거나 대용량 로그 파일이나 컴파일된 파일인 .a 파일 같은 것을 실수로 추가했을 때 쓴다. --cached 옵션을 사용하여 명령을 실행한다. $ git rm --cached README 여러 개의 파일이나 디렉토리를 한꺼번에 삭제할 수도 있다. 아래와 같이 git rm 명령에 file-glob 패턴을 사용한다. $ git rm log/\.log 앞에 \ 을 사용한 것을 기억하자. 파일명 확장 기능은 쉘에만 있는 것이 아니라 Git 자체에도 있기 때문에 필요하다. 이 명령은 log/ 디렉토리에 있는 .log 파일을 모두 삭제한다. 아래의 예제처럼 할 수도 있다. $ git rm \*~ 이 명령은 ~ 로 끝나는 파일을 모두 삭제한다. 파일 이름 변경하기 Git은 다른 VCS 시스템과는 달리 파일 이름의 변경이나 파일의 이동을 명시적으로 관리하지 않는다. 다시 말해서 파일 이름이 변경됐다는 별도의 정보를 저장하지 않는다. Git은 똑똑해서 굳이 파일 이름이 변경되었다는 것을 추적하지 않아도 아는 방법이 있다. 파일의 이름이 변경된 것을 Git이 어떻게 알아내는지 살펴보자. 이렇게 말하고 Git에 mv 명령이 있는 게 좀 이상하겠지만, 아래와 같이 파일 이름을 변경할 수 있다. $ git mv file_from file_to 잘 동작한다. 이 명령을 실행하고 Git의 상태를 확인해보면 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 사실 git mv 명령은 아래 명령어를 수행한 것과 완전 똑같다. $ mv README.md README $ git rm README.md $ git add README git mv 명령은 일종의 단축 명령어이다. 이 명령으로 파일 이름을 바꿔도 되고 mv 명령으로 파일 이름을 직접 바꿔도 된다. 단지 git mv 명령은 편리하게 명령을 세 번 실행해주는 것 뿐이다. 어떤 도구로 이름을 바꿔도 상관없다. 중요한 것은 이름을 변경하고 나서 꼭 rm/add 명령을 실행해야 한다는 것 뿐이다. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=or	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:24
https://git-scm.com/book/fr/v2/GitHub-Maintenance-d%e2%80%99un-projet	Git - Maintenance d’un projet 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 6.3 GitHub - Maintenance d’un projet Maintenance d’un projet Maintenant que vous êtes à l’aise sur les aspects contribution à un projet, regardons maintenant l’autre côté : la création, la maintenance et l’administration de vos propres projets. Création d’un nouveau dépôt Créons un nouveau dépôt pour permettre le partage du code de notre projet avec d’autres. Commencez par cliquer sur le bouton « New repository » (nouveau dépôt) sur le côté droit de votre tableau de bord ou sur le bouton + dans la barre d’outils du haut à côté de votre nom d’utilisateur comme sur la figure La liste déroulante « New repository » (nouveau dépôt) . Figure 109. La zone « Your repositories » (vos dépôts) Figure 110. La liste déroulante « New repository » (nouveau dépôt) Vous êtes redirigé vers le formulaire pour la création de nouveau dépôt : Figure 111. Le formulaire « new repository » (nouveau dépôt) Tout ce que vous avez à faire, c’est de fournir un nom de projet, les autres champs sont facultatifs. Pour l’instant, cliquez juste sur le bouton « Create Repository » (créer un dépôt) et paf, vous obtenez un nouveau dépôt sur GitHub nommé <utilisateur>/<nom_du_projet> . Puisque vous n’avez pas encore de code, GitHub vous affiche des instructions sur la façon de créer un tout nouveau dépôt Git ou de se connecter à un projet Git existant. Nous ne détaillerons pas cela ici ; si vous avez besoin d’un rappel, vérifiez Les bases de Git . Maintenant que votre projet est hébergé sur GitHub, vous pouvez donner l’URL à toutes les personnes avec lesquelles vous voulez partager votre projet. Chaque projet est accessible via HTTP par https://github.com/<utilisateur>/<nom_du_projet> et via SSH par git@github.com:<utilisateur>/<nom_du_projet> . Git peut récupérer et pousser en utilisant les deux URL mais l’accès est contrôlé sur la base des paramètres d’authentification de l’utilisateur qui s’y connecte. Note Il est souvent mieux de partager l’URL basé sur HTTP pour un projet public puisque l’utilisateur n’a pas besoin d’avoir un compte GitHub pour y accéder et pour le cloner. Les utilisateurs devront posséder un compte et avoir déposé une clé SSH pour accéder à votre projet si vous leur donnez l’URL SSH. L’URL HTTP est également exactement le même que celui que vous colleriez dans votre navigateur pour y afficher le projet. Ajout de collaborateurs Si vous travaillez avec d’autres personnes à qui vous voulez donner l’accès en poussée, vous devez les ajouter en tant que « collaborateurs ». Si Ben, Jeff et Louise possèdent tous un compte GitHub et que vous voulez qu’ils puissent pousser sur votre dépôt, vous pouvez les ajouter à votre projet. En faisant cela, vous leur donnez un accès en poussée ce qui signifie qu’ils possèdent un accès en lecture et en écriture au projet et au dépôt Git. Cliquez sur le lien « Settings » (paramètres) en bas de la barre latérale de droite. Figure 112. Le lien des paramètres (Settings) du dépôt. Ensuite sélectionnez « Collaborators » dans le menu de gauche, saisissez un nom d’utilisateur dans la boîte et cliquez sur « Add collaborator » (ajouter un collaborateur). Vous pouvez répéter cette action autant de fois que vous le voulez pour permettre l’accès à toutes les personnes que vous souhaitez. Si vous devez révoquer leur accès, il suffit de cliquer sur le « X » à droite de leur nom. Figure 113. Les collaborateurs du dépôt. Gestion des requêtes de tirage Maintenant que vous possédez un projet contenant un peu de code et peut-être même quelques collaborateurs qui possèdent un accès en poussée, voyons ce que vous devez faire lorsque vous recevez vous-même une requête de tirage. Les requêtes de tirage peuvent provenir soit d’une branche d’un clone de votre dépôt ou d’une autre branche du même dépôt. La seule différence est que celles d’un clone proviennent souvent de personnes vers lesquelles vous ne pouvez pas pousser sur leurs branches et qui ne peuvent pas pousser vers les vôtres alors qu’avec des requêtes de tirage internes, les deux parties peuvent généralement accéder à la branche. Pour ces exemples, supposons que vous êtes « tonychacon » et que vous avez créé un nouveau projet de code Arduino qui s’appelle « fade ». Notifications par courriel Quelqu’un se connecte et fait une modification à votre programme et vous envoie une requête de tirage. Vous devriez recevoir un courriel vous informant de cette nouvelle requête de tirage et ressemblant à celui sur la figure Notification par courriel d’une nouvelle requête de tirage. . Figure 114. Notification par courriel d’une nouvelle requête de tirage. Faisons quelques remarques à propos de ce courriel. Celui-ci vous fournit quelques statistiques : une liste de fichiers modifiés par la requête de tirage et le nombre de modifications. Il vous donne un lien vers la requête de tirage sur GitHub et il vous fournit également quelques URL que vous pouvez utiliser en ligne de commande. Remarquez la ligne git pull <url> patch-1 , il s’agit d’une manière simple de fusionner une branche distante sans avoir à ajouter un dépôt distant. Nous avons déjà vu rapidement cela dans Vérification des branches distantes . Si vous voulez, vous pouvez créer une branche thématique et basculer vers celle-ci puis lancer cette commande pour fusionner les modifications de cette requête de tirage. Les autres URL intéressantes sont les URL .diff et .patch , qui, comme vous l’avez certainement deviné, vous fournissent des versions au format différence unifiée et patch de la requête de tirage. Vous pourriez techniquement fusionner le travail contenu dans la requête de tirage de la manière suivante : $ curl https://github.com/tonychacon/fade/pull/1.patch \| git am Collaboration à une requête de tirage Comme déjà traité dans la section Processus GitHub , vous pouvez maintenant commencer une conversation avec la personne qui a ouvert la requête de tirage. Vous pouvez commenter certaines lignes de code, commenter des soumissions complètes ou commenter la requête de tirage elle-même en utilisant les outils Markdown, saveur GitHub un peu partout. À chaque fois que quelqu’un d’autre commente la requête de tirage, vous recevrez des notifications par courriel afin d’être au courant de chaque activité. Celles-ci possèdent un lien vers la requête de tirage dans laquelle l’activité s’est produite et vous pouvez également répondre directement au courriel pour commenter le fil de discussion de la requête de tirage. Figure 115. Les réponses aux courriels sont incorporées dans le fil de discussion. Une fois que le code est dans un état satisfaisant et que vous voulez le fusionner, vous pouvez soit tirer le code et le fusionner localement, soit utiliser la syntaxe décrite précédemment git pull <url> <branch> , soit ajouter le clone comme dépôt distant, le récupérer et le fusionner. Si la fusion est triviale, vous pouvez également cliquer sur le bouton « Merge » (fusionner) sur le site GitHub. Une fusion sans avance rapide (non-fast-forward) sera réalisée ce qui créera une soumission de fusion ( merge commit ) même si une fusion en avance rapide (fast-forward) était possible. Cela signifie que dans tous les cas, à chaque fois que vous cliquez sur le bouton « Merge », un commit de fusion est créé. Comme vous pouvez le voir sur Bouton « Merge » et instructions pour la fusion manuelle d’une requête de tirage. , GitHub vous donne toutes ces informations si vous cliquez sur le lien descriptif. Figure 116. Bouton « Merge » et instructions pour la fusion manuelle d’une requête de tirage. Si vous décidez que vous ne voulez pas fusionner, vous pouvez tout simplement fermer la requête de tirage et la personne qui l’a créée en sera informée. Références aux requêtes de tirage Si vous gérez beaucoup de requêtes de tirage et que vous ne voulez pas ajouter une série de dépôts distants ou faire des tirages isolés à chaque fois, GitHub vous permet une astuce. C’est toutefois une astuce avancée et nous irons un peu plus dans les détails à la section La refspec mais cela peut être assez utile dès maintenant. GitHub traite en réalité les branches de requête de tirage d’un dépôt comme une sorte de pseudo-branches sur le serveur. Par défaut, vous ne les obtenez pas lorsque vous clonez mais elles sont présentes de façon cachée et vous pouvez y accéder assez facilement. Pour le montrer, nous allons utiliser une commande bas niveau (souvent appelée commande de « plomberie » dont nous parlerons un peu plus dans la section Plomberie et porcelaine ) qui s’appelle ls-remote . Cette commande n’est en général pas utilisée dans les opérations quotidiennes mais elle est utile pour afficher les références présentes sur le serveur. Si nous lançons cette commande sur le dépôt « blink » que nous utilisions tout à l’heure, nous obtenons la liste de toutes les branches et étiquettes ainsi que d’autres références dans le dépôt. $ 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 Bien sûr, si vous êtes dans votre dépôt et que vous lancez la commande git ls-remote origin (ou avec un autre dépôt distant), quelque chose de similaire s’affiche. Si le dépôt se trouve sur GitHub et que des requêtes de tirage ont été ouvertes, vous obtiendrez leurs références préfixées par refs/pull/ . Ce sont simplement des branches mais comme elles ne sont pas sous refs/heads/ , vous ne les obtenez généralement pas lorsque vous clonez ou récupérez à partir d’un serveur — le processus de récupération les ignore normalement. Il y a deux références par requête de tirage - l’une se termine par /head et pointe vers la même soumission que la dernière soumission dans la branche de requête de tirage. Donc si quelqu’un ouvre une requête de tirage sur notre dépôt, que leur branche s’appelle bug-fix et qu’elle pointe sur la soumission a5a775 , alors dans notre dépôt nous n’aurons pas de branche bug-fix (puisqu’elle se trouve dans leur clone) mais nous aurons une référence pull/<pr#>/head qui pointe vers a5a775 . Cela signifie que vous pouvez assez facilement tirer toute branche de requête de tirage d’un coup sans avoir à ajouter tout un tas de dépôts distants. Vous pouvez désormais récupérer la référence directement. $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD Cela dit à Git, « Connecte-toi au dépôt distant origin et télécharge la référence appelée refs/pull/958/head ». Git obéit joyeusement et télécharge tout ce dont vous avez besoin pour construire cette référence et positionne un pointeur vers la soumission souhaitée sous .git/FETCH_HEAD . Vous pouvez continuer en faisant git merge FETCH_HEAD dans une branche dans laquelle vous voulez la tester mais ce message de fusion ( merge commit ) semble un peu bizarre. De plus, si vous passez en revue beaucoup de requêtes de tirage, cela devient fastidieux. Il existe également une façon de récupérer toutes les requêtes de tirage et de les maintenir à jour à chaque fois que vous vous connectez au dépôt distant. Ouvrez le fichier .git/config dans votre éditeur favori et cherchez le dépôt origin . Cela devrait ressembler à cela : [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/:refs/remotes/origin/ La ligne qui commence par fetch = est une spécification de références (refspec). C’est une façon de faire correspondre des noms sur un dépôt distant à des noms dans votre dossier .git local. Celle-ci en particulier dit à Git, « les choses sur le dépôt distant qui se trouvent sous refs/heads doivent aller dans mon dépôt local sous refs/remotes/origin ». Vous pouvez modifier cette section pour ajouter une autre spécification de références : [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/:refs/remotes/origin/ fetch = +refs/pull//head:refs/remotes/origin/pr/ Cette dernière ligne dit à Git, « Toutes les références du type refs/pull/123/head doivent être enregistrées localement comme refs/remotes/origin/pr/123 ». Maintenant, si vous enregistrez ce fichier et faites une récupération ( 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 # … Maintenant toutes les requêtes de tirage distantes sont représentées localement par des références qui agissent un peu comme des branches de suivi : elles sont en lecture seule et elles se mettent à jour lorsque vous faites un tirage. Il est ainsi super facile d’essayer le code d’une requête de tirage localement : $ 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' Les Sherlock Holmes en herbe parmi vous auront remarqué le terme head à la fin de la partie distante de la spécification de références. Il y a également une référence refs/pull/#/merge du côté de GitHub qui représente la soumission qui serait obtenue si vous cliquiez sur le bouton « Fusionner » sur le site. Cela peut vous permettre de tester la fusion avant même de cliquer sur le bouton. Requêtes de tirage sur des requêtes de tirage Non seulement vous pouvez ouvrir des requêtes de tirage qui ciblent la branche principale ou master , mais vous pouvez en fait ouvrir une requête de tirage ciblant n’importe quelle branche du réseau. En réalité, vous pouvez même cibler une autre requête de tirage. Si vous remarquez une requête de tirage qui va dans la bonne direction et que vous avez une idée de modifications qui dépendent de celle-ci, ou vous n’êtes pas sûr que c’est une bonne idée, ou vous n’avez tout simplement pas accès en poussée vers la branche cible, vous pouvez ouvrir une requête de tirage directement sur elle. Lorsque vous ouvrez une requête de tirage, une boîte en haut de la page vous indique vers quelle branche vous voulez pousser et à partir de quelle branche vous allez tirer. Si vous cliquez sur le bouton « Edit » (modifier) à droite de cette boîte, vous pouvez modifier non seulement les branches mais aussi le clone. Figure 117. Modification manuelle du clone cible et de la branche de la requête de tirage. Vous pouvez à cet instant très facilement indiquer de fusionner votre nouvelle branche sur une autre requête de tirage ou un autre clone du projet. Mentions et notifications GitHub dispose également d’un système de notifications intégré assez sympa qui peut devenir utile lorsque vous avez des questions et besoin du retour de certaines personnes ou d’équipes. Dans tous les commentaires, si vous saisissez le caractère @ , cela commence à proposer des noms et des noms d’utilisateur de personnes qui collaborent ou contribuent au projet. Figure 118. Saisissez @ pour faire référence à quelqu’un. Vous pouvez aussi faire référence à un utilisateur qui n’apparaît pas dans cette liste, mais souvent l’auto-complétion accélère les choses. Une fois que vous avez posté un commentaire contenant une référence à un utilisateur, ce dernier reçoit une notification. Cela signifie que c’est une manière très pratique de faire entrer des gens dans une conversation plutôt que de leur demander. Très souvent dans des requêtes de tirage sur GitHub, les gens vont attirer d’autres personnes dans leurs équipes ou dans leur société pour vérifier une anomalie ou une requête de tirage. Si quelqu’un est cité dans une requête de tirage ou une anomalie, il est « inscrit » à celle-ci et continue à recevoir des notifications dès qu’une activité se produit. Vous êtes également inscrit à quelque chose si vous l’ouvrez, si vous observez ( watch ) un dépôt ou si vous faites un commentaire sur quelque chose. Si vous ne souhaitez plus recevoir de notifications, cliquez sur le bouton « Unsubscribe » (se désinscrire) de la page pour arrêter de recevoir les mises à jour. Figure 119. Désinscription d’une anomalie ou d’une requête de tirage. La page des notifications Lorsque nous parlons de « notifications » ici, par rapport à GitHub, nous voulons parler de la manière spécifique par laquelle GitHub essaye de vous joindre lorsque des événements se produisent et il existe différentes façons de la configurer. Si vous allez dans l’onglet « Notification center » (centre de notification) dans la page des paramètres, vous pouvez voir les différentes options disponibles. Figure 120. Options du centre de notification. Vous pouvez recevoir des notifications soit par « courriel », soit par le « Web » et vous pouvez sélectionner une, aucune ou les deux méthodes si vous voulez participer de manière très active ou pour une activité particulière dans les dépôts que vous surveillez. Notifications Web Les notifications Web n’existent que sur GitHub et vous ne pouvez les visionner que sur GitHub. Si vous avez sélectionné cette option dans vos préférences et qu’une notification vous est envoyée, un petit point bleu apparaît sur votre icône des notifications en haut de l’écran comme sur la figure Centre de notification. . Figure 121. Centre de notification. Si vous cliquez dessus, la liste de tous les éléments pour lesquels vous avez été notifié apparaît, regroupés par projet. Vous pouvez filtrer les notifications d’un projet particulier en cliquant sur son nom dans la barre latérale gauche. Vous pouvez aussi accepter la notification en cochant l’icône à côté de celle-ci ou accepter toutes les notifications d’un projet en cochant la case en haut du groupe. Il y a aussi un bouton « muet » à côté de chaque case que vous pouvez cliquer afin de ne plus recevoir de notifications sur cet élément. Tous ces outils sont très utiles pour gérer un grand nombre de notifications. Beaucoup d’utilisateurs de GitHub très actifs arrêtent tout simplement complètement les notifications par courriel et gèrent toutes leurs notifications à partir de cette fenêtre. Notifications par courriel Les notifications par courriel sont l’autre façon de gérer les notifications provenant de GitHub. Si vous les avez activées, vous recevrez des courriels pour chaque notification. Nous avons vu des exemples concernant cela sur les figures Commentaires notifiés par courriel et Notification par courriel d’une nouvelle requête de tirage. . Ces courriels peuvent être également suivis correctement ce qui est bien agréable si vous utilisez un client de messagerie qui suit les fils de discussion. Un assez grand nombre de métadonnées sont incluses dans les entêtes des courriels que GitHub vous envoie ce qui peut vraiment vous aider à configurer des filtres et des règles personnalisés. Par exemple si nous observons les entêtes complets du courriel envoyé à Tony dans le courriel de la figure Notification par courriel d’une nouvelle requête de tirage. , nous voyons que les informations suivantes sont envoyées : 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 Il y a quelques petites choses intéressantes ici. Si vous voulez mettre en valeur ou rediriger les courriels de ce projet ou d’une requête en tirage en particulier, l’information du champ Message-ID vous fournit toutes les données au format <utilisateur>/<projet>/<type>/<id> . Si c’était une anomalie, le champ <type> aurait été « issues » à la place de « pull ». Les champs List-Post et List-Unsubscribe signifient que si votre client de messagerie les prend en compte, vous pouvez facilement écrire ( post ) à la liste ou vous désinscrire ( unsubscribe ) du fil de discussion. Cela correspond à cliquer sur la case « muet » sur la version Web de la notification ou sur « Unsubscribe » sur la page personnelle de l’anomalie ou de la requête de tirage. Il est aussi intéressant de noter que si les notifications par courriel et par Web sont toutes deux activées et que vous lisez la version courriel de la notification, la version Web sera également marquée comme lue si vous avez autorisé l’affichage des images dans votre client de messagerie. Fichiers spéciaux Quelques fichiers spéciaux attirent l’attention de GitHub s’ils existent dans votre dépôt. README Le premier est le fichier README (LISEZ-MOI) qui peut être écrit sous n’importe quel format textuel reconnu par GitHub. Par exemple, cela pourrait être README , README.md , README.asciidoc , etc. Si GitHub trouve un fichier README dans vos sources, celui-ci sera rendu sur la page d’accueil du projet. Pour beaucoup d’équipes, ce fichier contient toutes les informations importantes du projet pour quelqu’un qui serait nouveau dans le dépôt ou le projet. Il contient habituellement des choses comme : À quoi sert le projet. Comment le configurer et l’installer. Un exemple d’utilisation et comment le lancer. La licence sous laquelle le projet est proposé. Comment y contribuer. Puisque GitHub va afficher à l’écran ce fichier, vous pouvez y incorporer des images ou des liens pour faciliter la compréhension. CONTRIBUTING L’autre fichier spécial que GitHub reconnaît est le fichier CONTRIBUTING . Si vous possédez un fichier nommé CONTRIBUTING , peu importe son extension, GitHub affichera la figure Ouverture d’une requête de tirage si un fichier CONTRIBUTING existe. lorsque quelqu’un commence à ouvrir une requête de tirage. Figure 122. Ouverture d’une requête de tirage si un fichier CONTRIBUTING existe. L’idée ici est d’expliquer les choses particulières que vous voulez ou ne voulez pas voir soumises dans une requête de tirage envoyée vers votre projet. De cette façon, les gens peuvent vraiment lire les recommandations avant d’ouvrir la requête de tirage. Administration du projet Il n’y a généralement pas beaucoup de tâches administratives à faire si vous avez un seul projet, mais ces quelques points peuvent vous intéresser. Modification de la branche par défaut Si vous utilisez une autre branche que « master » comme branche par défaut et que vous voulez que les gens ouvrent les requêtes de tirage dessus ou la voient par défaut, vous pouvez modifier cela dans la page des paramètres de votre dépôt dans l’onglet « Options ». Figure 123. Modification de la branche par défaut pour un projet. Modifiez tout simplement la branche par défaut dans la liste déroulante et celle-ci sera la branche par défaut pour toutes les opérations principales à partir de maintenant, y compris la branche qui sera extraite par défaut lorsque quelqu’un clone le dépôt. Transfert de projet Si vous voulez transférer un projet à un autre utilisateur ou une organisation dans GitHub, une option « Transfer ownership » (transférer la propriété) en bas du même onglet « Options » de la page des paramètres de votre dépôt vous permet cela. Figure 124. Transfert d’un projet vers un autre utilisateur GitHub ou une organisation. C’est bien pratique si vous abandonnez un projet et que quelqu’un souhaite le récupérer ou si votre projet devient plus gros et que vous voulez le déplacer vers une organisation. Non seulement, cela déplace le dépôt ainsi que tous ses observateurs et étoiles vers un autre endroit, mais cela met également en place une redirection de votre URL vers le nouvel emplacement. Cela redirige également les clones et les tirages à partir de Git et pas seulement les requêtes Web. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://git-scm.com/book/tl/v2/Git-sa-Server-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 4.10 Git sa Server - Buod Buod Mayroon kang iilang opsyon upang mapatakbo ang isang remote na repositoryo sa Git at nang para makapagtulungan ka sa iba o ibahagi ang iyong trabaho. Ang pagpapatakbo ng iyong sariling server ay nagbibigay sayo ng maraming kontrol at nagpapahintulot sayo na ipatakbo ang server sa loob ng sarili mong firewall, ngunit tulad ng server ay karaniwang nangangailangan ng makatarungang halaga ng iyong oras sa pag-setup at mapanatili. Kapag inilagay mo ang iyong datos sa isang naka-host na server, madali itong i-setup at mapanatili; gayunpaman, dapat mong panatilihin ang iyong code sa server ng ibang tao, at ito ay hindi pinapayagan ng ilang organisasyon. Ito ay dapat tuwiran na matukoy kung anong solusyon o kombinasyon ng mga solusyon ang angkop para sayo at organisasyon mo. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://git-scm.com/book/uz/v2/Git-%d0%b0%d1%81%d0%be%d1%81%d0%bb%d0%b0%d1%80%d0%b8-Git-%d0%b4%d0%b0-%d1%82%d0%b0%d2%b3%d0%b0%d0%bb%d0%bb%d1%83%d1%81%d0%bb%d0%b0%d1%80	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 Командалар сатри 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 2.7 Git асослари - Git да таҳаллуслар Git да таҳаллуслар Ушбу Git асослари бўлимини тугатишдан олдин Git ни ишлатишни енгиллаштирувчи, онсонлаштирувчи ва янада одатий ҳолатга айланган яна битта айёрона йўлни кўриб ўтамиз: таҳаллуслар(aliases). Биз уларга кейинчалик мурожаат этмаймиз ёки сизни китобни ўқиш давомида улардан фойдаланади деб қарамаймиз, бироқ сизни уларни қандай ишлатишни билиб қўйишингиз яхши деб ўйладик. Git сизни тўлиқ ёзмаган матнингиздан қандай команда ёзмоқчи бўлганлигингизни аниқлашга ҳаракат қилмайди. Агар сиз ҳар бир командаларни тўлиқ ёзишни истамасангиз сиз енгиллик билан ихтиёрий командалар учун git config ёрдамида таҳаллусларни (alias) созлашингиз мумкин. Мана таҳаллусларга бир қанча мисоллар, эҳтимол сиз уларни ишлатишни хоҳлаб қоларсиз: $ 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 commit ўрнига git ci ни ёзишингиз мумкин бўлади. Git ни ўзлаштириш давомида эҳтимол тез-тез бошқа командаларни ишлатишга тўғри келар. Бундай ҳолатларда ҳеч иккиланмасдан таҳаллусларни яратинг. Бундай услуб сиз бўлиши керак деб ҳисоблаган командаларни яратиш учун ҳам қўл келиши мумкин. Масалан, индексдан файлни олишда дуч келган ноқулайликни тўғрилаш учун Git га ўз unstage таҳаллусимизни қўшишимиз мумкин: $ git config --global alias.unstage 'reset HEAD --' Ушбу юқоридаги таҳаллус яратиш командаси бажарилгач қуйидаги иккита команда эквивалент бўлиб қолади: $ 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 омборлари билан ишлаш учун дастгоҳ яратаётган бўлсангиз ас қотади. Ушбу ҳолатга мисолни gitk ни ишга тушириш учун git visual таҳаллусини яратиш мисолида қараб ўтамиз.: $ 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:24
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=gu	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:24
https://git-scm.com/book/bg/v2/%d0%9e%d1%81%d0%bd%d0%be%d0%b2%d0%b8-%d0%bd%d0%b0-Git-%d0%97%d0%b0%d0%bf%d0%b8%d1%81-%d0%bd%d0%b0-%d0%bf%d1%80%d0%be%d0%bc%d0%b5%d0%bd%d0%b8-%d0%b2-%d1%85%d1%80%d0%b0%d0%bd%d0%b8%d0%bb%d0%b8%d1%89%d0%b5%d1%82%d0%be	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 За 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 2.2 Основи на Git - Запис на промени в хранилището Запис на промени в хранилището Вече имате чисто ново Git хранилище и работещо копие на файловете от проекта. Сега трябва да започнете да правите промените, които желаете и да записвате snapshot-и на промените в хранилището всеки път, когато проектът ви достигне състояние, което бихте желали да запишете на сигурно място. Помнете, че всеки файл от работната ви директория може да бъде в два статуса - проследяван или не (tracked/untracked). Tracked файловете са тези от последния snapshot, както и всички новоиндексирани файлове; те може да са непроменени, променени и индексирани (staged). Накратко, tracked файловете са тези, които Git познава. Untracked файловете са всичко останало - всички файлове в работната ви директория, които не са били в последния ви snapshot и не са в staging областта. Когато за пръв път клонирате хранилище, всички ваши файлове ще бъдат tracked и същевременно - unmodified, защото Git току що ги е извлякъл и вие все още не сте променяли нищо по тях. Когато започнете да променяте файловете, Git ги вижда вече като modified, понеже сте ги редактирали след последния къмит. Вие индексирате тези променени файлове, след това къмитвате промените им и този цикъл се повтаря в течение на работата ви. Фигура 8. Промяната в статуса на вашите файлове Проверка на статуса на файловете Основният инструмент, с който се проверява състоянието на файловете ви е командата git status . Ако я изпълните директно след клониране, когато не сте правили промени все още, ще видите следното: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working tree clean Това означава, че имате чиста работна директория - с други думи, никой от следените ви файлове не е променян. Git също така не вижда никакви непроследени файлове, иначе щеше да ги покаже тук. Накрая, командата ви казва в кой клон (branch) на проекта се намирате и че не се отклонявате от същия клон на сървъра. Засега, този клон е винаги master , както е по подразбиране, към момента това не ви интересува. Клонове в Git ще разгледа клоновете и референциите в подробности. Забележка GitHub смени името на клона по подразбиране от master на main в средата на 2020 г. и други Git хостове направиха същото. Ето защо, може да установите, че клонът по подразбиране на новосъздадените хранилища е main вместо master . Освен това, името на клона по подразбиране може да се променя (както видяхме в Име на клон по подразбиране ), така че може да видите съвсем различно име във вашия случай. Git обаче все още използва master по подразбиране, така че ще го използваме по-натам в книгата. Нека сега добавим нов файл в проекта, прост README файл. Ако файлът не е съществувал преди и изпълните git status , ще видите untracked файла си така: $ 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 вижда файл, който не е присъствал в предишния snapshot (commit) и все още не е индексиран; Git няма сам да започне да го прибавя към следващите commits докато вие не укажете това изрично. Това е умишлено поведение и ви предпазва от ситуации, в които бихте могли автоматично да добавяте файлове, които не желаете, например генерирани binary файлове. Вие обаче искате да включите README файла, така че нека го направим. Проследяване на нови файлове За да започнете да следите нов файл, използвайте командата git add . За вашия README файл, изпълнете това: $ git add README Ако след това изпълните отново статус командата, ще видите че 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”. Ако къмитнете в този момент, файлът който ще попадне в следващия snapshot-а ще e в състоянието, в което е бил, когато сте изпълнили 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 е многоцелева команда — използвате я както за да започнете да следите файлове, така и за да ги индексирате в staging областта и дори да правите по-различни неща, като например да маркирате отбелязани като конфликтни по време на сливане файлове като коректни такива. Би могло да ви е от полза да приемате значението ѝ повече като “добави това съдържание в следващия къмит” вместо като “добави този файл към проекта”. Нека сега изпълним 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 се показва едновременно като staged и unstaged. Как е възможно това? Оказва се, че Git индексира файла точно както е бил, когато сте изпълнили git add . Ако къмитнете сега, версията на CONTRIBUTING.md , която ще отиде в snapshot-а ще е тази, след която сте изпълнили 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 и т.н. Изходът е в две колони — лявата показва статуса на staging областта, а дясната статуса на работната директория. Така в горния пример, README файлът е променен в работната област, но не е индексиран, докато файлът lib/simplegit.rb е променен и индексиран. Файлът Rakefile е променен, индексиран и след това променен отново, така че по него има промени които са индексирани и такива, които не са. Игнориране на файлове Често, ще имате класове от файлове, за които няма да искате Git да ги добавя автоматично и дори да ви ги показва като непроследени. Това обикновено са автоматично генерирани файлове - лог-файлове или такива създадени от компилиращата ви система. В подобни случаи, можете да създадете файл с име .gitignore , в който да ги опишете с подходяща маска за имената им. Ето един примерен такъв файл: $ cat .gitignore .[oa] ~ Първият ред в него указва на Git да пропуска всички файлове завършващи на “.o” или “.a” — обектни и архивни файлове, които може да са създадени от компилатора. Вторият ред указва да се пропускат всички файлове, чиито имена завършват с тилда ( ~ ), които се ползват в много текстови редактори като Emacs за маркиране на временни файлове. Можете също да включвате log, tmp, или pid директории, автоматично генерирана документация и т.н. Добра идея е да си направите .gitignore файла преди да започнете работа, така че да не къмитнете без да искате нежелани файлове. Правилата за маските, които можете да включвате в .gitignore файла са както следва: Празните редове и редовете започащи с \# се игнорират. Работят стандартните глобални правила за маски и те ще бъдат приложени рекурсивно по цялото работно дърво. Можете да започвате маските с ( / ) за да избегнете рекурсия. Можете да завършвате маските с ( / ) за да указвате директория. Можете да обърнете логиката на маската като я започнете с ( ! ). Глобалните правила са подобни на опростени регулярни изрази, които шеловете използват. Звездичката ( * ) търси за нула или повече символа; [abc] търси за кой да е символ в скобите (в този случай a, b, или c); въпросителният знак ( ? ) търси единичен символ; символи в скоби с тире между тях ( [0-9] ) търсят за произволен символ в обхвата между символите (в този случай от 0 до 9). Можете да използвате две звездички за да търсите в под-директории; a/*/z ще открие a/z , a/b/z , a/b/c/z , и т.н. Ето друг примерен .gitignore файл: # без .a файлове .a # но lib.a се включва, въпреки че игнорирате всички .а файлове отгоре !lib.a # игнорирай само TODO файла в текущата директория, не и под-директориите съдържащи TODO /TODO # игнорира всички файлове в коя да е директория с име build build/ # игнорира doc/notes.txt, но не и doc/server/arch.txt doc/.txt # игнорира всички .pdf файлове в директорията doc/ и всички нейни под-директории doc//.pdf Подсказка GitHub поддържа сравнително подробен списък от добри .gitignore примери за стотици проекти и езици на адрес https://github.com/github/gitignore , ако искате отправна точка за проекта си. Забележка В общия случай, едно хранилище би могло да има единичен .gitignore файл в най-горната директория, който се прилага върху всички други рекурсивно. Обаче, възможно е да имате и допълнителни .gitignore файлове в поддиректориите. Правилата в тези вложени .gitignore файлове ще се прилагат само към файловете, намиращи се в директорията, в която се пазят. Linux kernel хранилището например има 206 .gitignore файла. Извън темата на тази книга е да се впускаме в детайли за множеството .gitignore файлове; погледнете man gitignore , ако желаете повече информация. Преглед на индексираните и неиндексирани промени Ако командата 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 difftool --tool-help за да видите какви diff инструменти са налични за вашата система. Ние ще продължим да ползваме git diff командата по различни начини в книгата. Има и друг начин за преглед на промените, ако предпочитате графичен или друг способ. Ако изпълните git difftool вместо git diff , можете да гледате всяко от сравненията в софтуери като emerge, vimdiff и много други подобни, вкл. комерсиални такива. Публикуване на промените (commit) Сега, след като индексната област е в състоянието, което искате, можете да публикувате (къмитнете) вашите промени. Помнете, че всичко, което все още не е индексирано — всякакви файлове, които сте създали или редактирали след последната git add команда — няма да отидат в това публикуване. Те ще останат като променени файлове на вашия диск. Нека кажем, че последния път когато сте пуснали git status , вие сте видели, че всичко е индексирано и сте готови да къмитнете промените. Най-простият начин да запишете е изпълнявайки командата git commit : $ git commit Правейки това, Git ще стартира вашия текстов редактор. Забележка (Това се определя от EDITOR environment променливата на вашия шел -– обикновено 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 в коментиран вид и един празен ред над него. Можете да изтриете тези коментари и да напишете собствено съобщение или да ги оставите там за да ви припомнят по-късно какво точно сте публикували. Забележка Ако искате още по-подробно напомняне за това какво сте модифицирали, можете да изпълните командата с параметър git commit -v . Това ще включи в съобщението и diff на самите промени, така че да можете точно да проследите какво сте къмитнали. Когато излезете от редактора запазвайки промените, Git ще публикува промените заедно със съобщението (коментарите и diff информацията се премахват) Вместо да пускате текстовия редактор, можете да подадете къмит съобщението директно като параметър на командата с флага -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 ), колко на брой файлове са променени и статистика за добавените и премахнати редове код. Помнете, че къмитът съдържа моментна снимка на това, което е имало в индексната област (staging area). Всичко, което не е било там няма да присъства в къмита и файловете ще си стоят като променени. За да ги добавите - трябва да направите следващ къмит. Всеки път, когато къмитвате промени, вие правите snapshot на състоянието на вашия проект и по-късно можете да го възстановите или да го ползвате за сравнение. Прескачане на Staging областта Въпреки, че може да е много полезна за фина настройка на вашите промени, понякога индексната област може да се прескочи в процеса на работа. Ако искате директно да къмитнете променени файлове без да ги добавяте в нея, 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 'Add new benchmarks' [master 83e38c7] Add new benchmarks 1 file changed, 5 insertions(+), 0 deletions(-) Забележете, че сега не беше нужно да изпълнявате git add за файла CONTRIBUTING.md преди да го къмитнете. Това е, защото -a параметърът включва всички променени файлове. Това е удобно, наистина, но бъдете внимателни, понякога този флаг може да включи в къмита нежелани промени. Изваждане на файлове За да извадите файл от Git, вие трябва да го изключите от списъка със следящи се файлове (по-прецизно казано, да го премахнете от индексната област) и след това да публикувате промяната. Командата git rm прави това и също така изтрива файла от работната директория, така че да не го виждате като непроследен файл следващия път. Ако просто изтриете файла от работната си директория, той се показва под “Changes not staged for commit” (тоест, unstaged ) секцията от изхода на 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 \*~ Тази команда премахва всички файлове, имената на които завършват със символа ~ . Преименуване на файлове За разлика от много други VCS системи, Git не следи експлицитно преименуването на файлове. Ако преименувате файл в Git, никакви мета данни няма да се съхранят в Git базата, така че да му указва, че сте преименували файла. Обаче, Git е достатъчно интелигентен за да усети това — ще се занимаем с детекцията на преименуваните файлове малко по-късно. Затова е малко смущаващо, че Git всъщност има mv команда. Ако искате да преименувате файл в Git, можете да изпълните това: $ git mv file_from file_to и то си работи. На практика, ако изпълните командата и погледнете в статуса, ще видите че 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:24
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=hi	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:24
https://git-scm.com/book/tl/v2/GitHub-Pag-setup-at-pagsasaayos-ng-Account	Git - Pag-setup at pagsasaayos ng Account 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.1 GitHub - Pag-setup at pagsasaayos ng Account Ang GitHub ay ang solong pinakamalaking host para sa mga repositoryo ng Git, at ang pangunahing punto ng pagtutulungan para sa milyun-milyong mga developer at proyekto. Isang malaking porsiyento ng lahat ng mga repositoryo ng Git ay naka-host sa GitHub, at marami sa mga proyekto na open-source ang gumagamit nito sa pag-host ng Git, pagsusubaybay ng isyu, pagsusuri sa code, at iba pang mga bagay. Kaya habang hindi ito direktang bahagi ng open-source na proyekto ng Git, may isang magandang pagkakataon na gusto mo o kailangang makipag-ugnayan sa GitHub sa ilang punto habang propesyonal na ginagamit ang Git. Ang kabantang ito ay tungkol sa epektibong paggamit ng GitHub. Ating tatalakayin ang pag-sign up para sa at pamamahala ng isang account, paglilikha at paggamit ng mga repositoryo ng Git, karaniwang mga workflow upang mag-ambag sa mga proyekto at upang tumanggap ng mga kontribusyon sa iyo, programmatic interface ng GitHub at maraming mga tip upang gawing mas madali ang iyong buhay sa pangkalahatan. Kung hindi ka interesado sa paggamit ng GitHub upang i-host ang iyong sariling mga proyekto o upang mag-ambag sa ibang mga proyekto na naka-host sa GitHub, maaari mong ligtas na lumaktaw sa Mga Git na Kasangkapan . Pag-setup at pagsasaayos ng Account Ang unang bagay na kailangan mong gawin ay mag-setup ng isang libreng account ng user. Bisitahin lamang ang https://github.com , pumili ng pangalan ng user na hindi pa nakuha, magbigay ng isang email address at password, at i-click ang malaking berdeng pindutan na “Mag-sign up sa GitHub”. Figure 82. Ang form ng pag-sign-up sa GitHub. Ang susunod na bagay na iyong makikita ay ang pahina ng pagpepresyo para sa naka-upgrade na mga plano, ngunit ito’y ligtas na balewalain muna sa ngayon. Magpapadala sa iyo ng email ang GitHub upang mapatunayan ang address na iyong ibinigay. Sige at gawin ito, ito ay mahalaga (tulad ng makikita natin kinamamayaan). Ang GitHub ay nagbibigay ng lahat ng pag-andar nito na may mga libreng account, may limitasyon na ang lahat ng iyong mga proyekto ay ganap na pampubliko (bawat isa ay may access sa pagbasa). Kasama sa mga bayad na plano ay isang hanay ng bilang ng mga pribadong proyekto, ngunit hindi natin tatalakayin sa librong ito. Pag-click sa Ocotocat na logo sa itaas sa kaliwa ng screen ay magdadala sa iyo sa pahina ng iyong dashboard. Handa ka na ngayon gumamit ng GitHub. Pag-access sa SSH Sa ngayon, ikaw ay ganap na makakonekta sa mga repositoryo ng Git gamit ang protocol na https:// , pinapatunayan ang username at password na iyo lamang na-setup. Gayunpaman, upang i-clone ang mga pampublikong proyekto, hindi mo na kailangan mag-sign up - ang account na ating nalikha ay mahalaga kapag mag-fork tayo ng mga proyekto at mag-push sa atong mga fork kinamamayaan. Kung gusto mong gumamit ng mga remote na SSH, kinakailangan mong isaayos ang isang publikong key. (Kung wala ka pa, tingnan ang Ang paglikha ng iyong Pampublikong Susi ng SSH .) Buksan ang settings ng iyong account gamit ang link na nasa itaas na kanan ng window: Figure 83. Ang link ng “settings ng Account”. Pagkatapos piliin ang seksyon na “SSH keys” sa tabi ng kaliwang bahagi. Figure 84. Ang link ng “SSH keys”. Mula doon, i-click ang pindutan na " Magdagdag ng isang SSH key ", bigyan ng pangalan ang iyong key, i-paste ang mga nilalaman ng iyong ~/.ssh/id_rsa.pub (o anuman ang iyong pinangalanan) file na public-key sa text area, at i-click ang “Magdagdag ng key”. Siguraduhin na pangalanan ang iyong SSH key ng isang bagay na maaalala mo. Maaari mong pangalanan ang bawat key mo (halimbawa "Aking Laptop" o "Account sa Trabaho") upang kung kailangan mong bawiin ang key mamaya, madali mong masabi kung alin ang iyong hinahanap. Ang iyong Avatar Susunod, kung nais mo, maaari mong palitan ang avatar na ginawa para sa iyo ng isang imahe ng iyong pagpili. Una, pumunta sa tab na “Profile” (sa taas ng tab ng SSH Keys) at i-click ang “Mag-upload ng bagong larawan”. Figure 85. Ang link ng “Profile”. Pipili tayo ng kopya ng logo ng Git na nasa ating hard drive at pagkatapos ay makakakuha tayo ng pagkakataong i-crop ito. Figure 86. I-crop ang iyong avatar Ngayon kahit saan ka makipag-ugnayan sa site, makikita ng mga tao ang iyong avatar kasunod ng iyong username. Kung mangyari mong na-upload ang isang avatar sa tanyag na serbisyo ng Gravatar (kadalasang ginamit para sa mga account ng Wordpress), ang avatar na iyon ay gagamitin bilang default at di mo kailangang gawin ang hakbang na ito. Ang iyong Email Addresses Ang paraan ng pagmapa ng GitHub ng iyong mga commit ng Git sa iyong mga user ay sa pamamagitan ng email address. Kung gagamit ka ng maramihang mga email address sa iyong commit at gusto mo iugnay nang maayos ang mga ito ng GitHub, kailangan mong idagdag ang lahat ng mga email address na iyong ginamit sa seksyon ng mga Email ng seksyon ng admin. Figure 87. Magdagdag ng mga email address Sa Magdagdag ng mga email address maaari nating makita ang ilan sa iba’t-ibang mga estado na posible. Ang pinakamataas na address ay napatunayan na at itinakda bilang pangunahing address, ibig sabihin na dito mo makukuha ang anumang mga abiso at mga pagtanggap. Ang pangalawang address ay napatunayan na at kaya maaari ng itakda bilang pangunahin kung nais mong ilipat ang mga ito. Ang panghuling address ay hindi pa napatunayan, ibig sabihin na hindi mo maaaring gawin itong pangunahing address. Kung nakikita ng GitHub ang alin man sa mga ito sa mga mensahe ng commit sa alinmang repositoryo sa site, ito ay maiuugnay na ngayon sa iyong user. Dalawang Kadahilanan ng Pagpapatunay Sa wakas, para sa dagdag na seguridad, kailangan mong mag-setup ng Dalawang-Kadahilanan ng Pagpapatunay o “2FA”. Ang Dalawang-Kadahilanan ng Pagpapatunay ay isang mekanismo ng pagpapatunay na nagiging mas at mas tanyag kumakailan lamang upang mapigilan ang panganib na makompromiso ang iyong account kung ang iyong password ay nanakaw. Ang pag-on nito ay maging dahilan ng paghihiling sa iyo ng GitHub para sa dalawang iba’t-ibang mga paraan ng pagpapatunay, upang kapag isa sa mga ito ay nakompromiso, hindi maa-access ng umaatake ang iyong account. Maaari mong mahanap ang setup ng Dalawang-Kadahilanan ng Pagpapatunay sa ilalim ng tab ng Seguridad sa settings ng iyong Account. Figure 88. 2FA sa Tab ng Seguridad Kung i-click mo ang pindutan na “Mag-setup ng dalawang-kadahilanan ng pagpapatunay”, dadalhin ka nito sa pahina ng pagsasaayos kung saan maaari kang mamili na gumamit ng isang app sa phone upang makabuo ng pangalawang code (“isang-beses na password” na batay sa oras), o maaari mong hayaan ang GitHub na magpadala sa iyo ng isang code sa pamamagitan ng SMS sa bawat oras na kailangan mong mag-login. Pagkatapos mong pumili kung anong paraan ang mas gusto mo at sundin ang mga instruksiyon sa pag-setup ng 2FA, ang iyong account ay magiging mas ligtas nang kaunti at kinakailangan mong magbigay ng isang code bilang karagdagan sa iyong password sa tuwing ikaw ay mag-login sa GitHub. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=mk	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:24
https://git-scm.com/book/ru/v2/Git-%d0%bd%d0%b0-%d1%81%d0%b5%d1%80%d0%b2%d0%b5%d1%80%d0%b5-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 Командная строка 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 4.7 Git на сервере - GitWeb GitWeb Теперь, когда к вашему проекту настроен доступ на чтение/запись и только на чтение, вероятно, вы захотите настроить простой веб-визуализатор. Для этой цели в комплекте с Git поставляется CGI-сценарий GitWeb. Рисунок 49. Веб-интерфейс GitWeb Если вы хотите посмотреть как будет выглядеть ваш проект в GitWeb, в Git есть стандартная команда для запуска временного экземпляра, однако она требует наличия установленного веб-сервера, такого как lighttpd или webrick . Как правило, на машинах с Linux lighttpd уже установлен, поэтому вы сможете его запустить, выполнив команду git instaweb в каталоге с вашим проектом. Если вы используете Mac, Leopard поставляется с предустановленным Ruby, поэтому webrick может быть лучшим выбором. Чтобы запустить instaweb не с ligttpd используйте параметр --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 на порту 1234, а затем откроет эту страницу в веб-браузере. Как видите, нет ничего сложного. Когда вы закончили и хотите остановить сервер, запустите ту же команду с параметром --stop : $ git instaweb --httpd=webrick --stop Если вы хотите иметь постоянно работающий веб-интерфейс на сервере для вашей команды или предоставлять хостинг для проекта с открытым кодом, вам необходимо подключить CGI-сценарий на вашем веб-сервере. В некоторых дистрибутивах Linux есть пакет gitweb , который вы можете установить, используя apt или dnf , так что вы можете попробовать сначала этот способ. Мы же вкратце рассмотрим ручную установку GitWeb. Для начала вам нужно скачать исходный код Git, с которым поставляется GitWeb, и сгенерировать 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/ Помните, что вы должны указать команде где расположены ваши репозитории Git с помощью переменной GITWEB_PROJECTROOT . Теперь вы должны настроить Apache на использование этого CGI-сценария, для чего вы можете добавить виртуальный хост: <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:24
https://git-scm.com/book/tl/v2/Mga-Pangunahing-Kaalaman-sa-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 2.8 Mga Pangunahing Kaalaman sa Git - Buod Buod Sa puntong ito, maaari mo nang gawin ang lahat ng mga pangunahing operasyon ng Git - paglikha o pag-clone ng repository, paggawa ng mga pagbabago, pag-stage at pag-commit sa mga pagbabagong iyon, at pagtingin sa kasaysayan para sa lahat ng mga pagbabago sa repository. Sa sunod ay ating sasaklawin ang makamatay na katangian ng Git: ang branching na modelo nito. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=pl	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:24
https://git-scm.com/book/be/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. Першыя крокі 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 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. Малюнак 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. Малюнак 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. Заўвага 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. Малюнак 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. Малюнак 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. Малюнак 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. Малюнак 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' Малюнак 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 Заўвага 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. Малюнак 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. Заўвага 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. Малюнак 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. Заўвага 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> . Заўвага 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:24
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=is	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:24
https://git-scm.com/book/ko/v2/Git-%ec%84%9c%eb%b2%84-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 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.8 Git 서버 - GitLab GitLab 간단하게 쓰기엔 GitWeb이 꽤 좋다. 그런데 좀 더 기능이 많은 Git 서버를 쓰려면 다른 서버를 찾아 설치해야 한다. GitLab은 널리 사용하는 서버 중 하나이다. 여기서 예제를 통해 설치하고 사용하는 것을 배워보자. GitLab은 기능이 많은 만큼 설정도 복잡하고 유지보수를 위해 해야 할 것도 많다. 설치 GitLab은 데이터베이스와 따로 연동해야하는 웹 애플리케이션이라 다른 Git 서버들보다 설치하기에 복잡하지만, 문서화가 잘 되어있으므로 이를 참고한다. 설치 방법은 여러 가지가 있다. 가상 머신 이미지나 원클릭 인스톨러를 내려받아 빨리 설치하고 환경에 맞게 후다닥 설정해서 사용할 수 있다. https://bitnami.com/stack/gitlab 에서 내려받을 수 있다. Bitnami의 로그인 화면은 아래와 같다(alt-→ 를 눌러서 들어간다). 로그인 화면에 설치된 GitLab의 IP와 기본 사용자이름, 암호가 써있다. 그림 50. Bitnami GitLab 가상 머신의 로그인 화면 더 많은 것이 알고 싶다면 GitLab 커뮤니티 에디션의 readme 파일을 읽어보면 된다. https://gitlab.com/gitlab-org/gitlab-ce/tree/master 에서 내려받을 수 있다. Chef의 레시피나 Digital Ocean(역주 - 호스팅 서비스)의 가상 머신, RPM, DEB 패키지 등에 관한 설치 방법들이 있다. “비공식적인” 설명서도 있다. 흔치 않은 운영체제나 데이터베이스와의 연동하는 법, 스크립트로 완전히 수동으로 설치하는 법 등 많은 주제를 다룬다. 관리자 GitLab의 관리자 도구는 웹 페이지로 되어있다. 웹 브라우저로 GitLab이 설치된 곳의 주소에 들어가면 그냥 보인다. 그리고 관리자로 로그인하자. 기본 사용자이름은 admin@local.host , 암호는 5iveL!fe 이다(이건 로그인 후에 바꿀 수 있다). 로그인하고 나서 메뉴 오른쪽 위에 있는 “Admin area” 를 클릭한다. 그림 51. GitLab 메뉴의 “Admin area” 버튼 사용자 GitLab의 사용자 계정은 한 사람당 하나씩 만든다. 사용자 계정의 내용은 복잡하지 않다. 로그인 데이터에 추가로 개인 정보가 들어있다. 각 사용자마다 네임스페이스 가 있다. 네임스페이스는 프로젝트를 묶는 단위이다. jane 사용자가 project 라는 프로젝트를 진행 중이라면 프로젝트의 URL은 http://server/jane/project 가 될 것이다. 그림 52. GitLab 사용자의 관리 화면 사용자를 삭제하는 방법은 두 가지다. 일시적으로 GitLab에 로그인하지 못하게 하는 “정지(Blocking)” 가 있다. 정지한 사용자 데이터와 네임스페이스 안의 프로젝트 데이터는 삭제되지 않고 그대로 남는다. 커밋의 이메일 주소에 대한 링크도 여전히 사용자 프로파일 페이지로 연결된다. 하지만 사용자를 “삭제(Destroying)” 하면 그 사용자와 관련된 모든 데이터가 삭제된다. 삭제한 사용자의 모든 프로젝트와 데이터가 삭제되고 해당 사용자가 소유한 그룹도 삭제된다. 영구히 삭제돼 되돌릴 수 없으므로 조심해야 한다. 그룹 GitLab 그룹은 프로젝트와 누가 어떤 프로젝트에 어떻게 접근할지에 대한 권한 데이터의 모음이다. 그룹에도 사용자처럼 프로젝트 네임스페이스가 있다. +training+라는 그룹이 +materials+라는 프로젝트를 가지고 있으면 URL은 http://server/training/materials 가 된다. 그림 53. GitLab의 그룹 관리 화면 그룹은 많은 사용자가 모인 곳이다. 그룹의 사용자의 권한은 그룹의 프로젝트에 대한 권한과 그룹 자체에 대한 권한이 따로 있다. 권한은 “Guest”(이슈 등록과 채팅만 할 수 있다.)부터 “Owner”(그룹과 멤버, 프로젝트에 대한 모든 제어가 가능하다.)까지 지정할 수 있다. 여기에서 어떤 권한이 있는지 나열하기엔 너무 많다. GitLab의 관리 화면에서 각 권한에 대한 링크를 참고하길 바란다. 프로젝트 GitLab의 프로젝트는 간단히 이야기하면 하나의 Git 저장소다. 모든 프로젝트는 한 사용자나 한 그룹에 속하게 된다. 사용자에 딸린 프로젝트는 사용자가 관리자로서 그 프로젝트를 완전히 제어한다. 그룹에 딸린 프로젝트는 해당 그룹의 사용자 권한 레벨에 따라 다르다. 프로젝트마다 공개 수준을 지정할 수 있어서 사람마다 프로젝트 페이지와 저장소가 보이거나 안 보이게 할 수 있다. 프로젝트가 Private 이면 프로젝트 소유자가 허락한 사람들만 프로젝트에 접근할 수 있다. Internal 은 로그인한 사용자에게만 보인다. 그리고 Public 프로젝트는 모든 사람이 볼 수 있다. 이런 공개 수준은 git fetch 같은 접근이나 웹 UI 접근에 다 적용된다. 훅 GitLab은 훅도 지원하는데 프로젝트 훅이나 시스템 훅을 사용할 수 있다. 훅은 어떤 이벤트가 발생하면 해당 이벤트 정보가 담긴 JSON 데이터를 HTTP POST로 보낸다. Git 저장소나 GitLab과 연동해서 CI나 채팅, 개발 도구 등으로 자동화하기에 좋다. 기본 사용법 먼저 새로운 프로젝트를 만들어보자. 툴바의 “+” 아이콘을 클릭한다. 프로젝트의 이름, 프로젝트 네임스페이스, 공개 수준을 입력한다. 지금 입력한 것은 대부분 나중에 다시 바꿀 수 있다. “Create Project” 를 클릭하면 끝난다. 프로젝트가 만들어졌으면 로컬 Git 저장소랑 연결하자. HTTPS나 SSH 프로토콜을 이용해 프로젝트를 Git 리모트로 등록한다. 저장소 URL은 프로젝트 홈페이지 위 쪽에 있다. 아래와 같이 명령어를 이용해 로컬 저장소에 gitlab 이라는 이름으로 리모트 저장소를 등록한다. $ git remote add gitlab https://server/namespace/project.git 로컬 저장소가 없으면 그냥 아래 명령어를 실행한다. $ git clone https://server/namespace/project.git 웹 UI는 꽤 유용하다. 저장소에 대한 각종 정보를 보여준다. 프로젝트 홈페이지에서는 최근 활동을 보여주고 제일 위의 링크를 클릭하면 프로젝트의 파일과 커밋 로그가 나온다. 함께 일하기 함께 일할 사람에게 그냥 Git 저장소의 Push 권한을 주는 걸로 간단하게 협업을 시작할 수 있다. 프로젝트 설정 페이지에서 “Members” 섹션에 같이 일할 사용자를 추가한다. 그리고 그 사용자가 Push 할 수 있도록 설정한다(다른 접근 수준에 대해서는 그룹 에서 볼 수 있다). “Developer” 이상의 권한을 주면 그 사용자는 우리 저장소에 Push 하거나 브랜치를 만들 수 있다. Merge 요청을 하도록 해서 통제권을 유지한 채로 협업하는 방법도 있다. 프로젝트에 접근할 수 있는 모든 사용자가 프로젝트에 기여할 수 있다. 사용자는 마음껏 브랜치를 만들고 커밋, Push 하고 나서 이 브랜치를 master 나 다른 브랜치에 Merge 해달라고 요청한다. Push 권한이 없는 사용자는 저장소를 “fork” 한 다음에 “fork” 한 자신의 저장소 에 Push 한다. 그리고는 원래 저장소에 내 저장소에 있는 브랜치를 Merge 해달라고 요청하면 된다. 소유자는 이걸로 자신의 저장소에 대한 모든 통제 권한을 가진다. 어떤 데이터가 들어올 수 있는지 언제 들어오는지 소유자가 결정할 수 있다. Merge 요청과 이슈는 대화의 기본 단위이다. 각 Merge 요청에서는 일반적인 토론뿐만 아니라 라인 단위로까지 대화가 이루어진다. 물론 코드 리뷰가 간단히 끝날 수도 있다. 요청과 이슈는 모두 사용자에게 할당되거나 마일스톤의 과제로 편입된다. 이 섹션에서는 GitLab의 Git과 맞닿은 부분만 설명했지만 이게 전부가 아니다. GitLab은 굉장히 성숙했다. 이 외에도 프로젝트 위키나 토론용 “walls”, 시스템 관리 도구 등 협업용 기능이 많다. GitLab의 장점은 일단 서버가 돌아가면 SSH로 서버에 접속할 일이 별로 없다는 것이다. 대부분 관리는 웹 브라우저로 가능하다. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://git-scm.com/book/uk/v2/%d0%9e%d1%81%d0%bd%d0%be%d0%b2%d0%b8-Git-%d0%9f%d1%81%d0%b5%d0%b2%d0%b4%d0%be%d0%bd%d1%96%d0%bc%d0%b8-Git	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 2.7 Основи Git - Псевдоніми Git Псевдоніми Git Перед тим, як перейти до наступного розділу, ми хочемо представити особливість, яка може зробити ваше користування Git простішим, легшим та більш знайомим: псевдоніми. Для ясності, ми більше не будемо використовувати їх деінде в цій книзі, але якщо ви продовжите працювати з Git регулярно, псевдоніми — це те, про що ви повинні знати. 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 commit ви можете набрати просто git ci . З часом, ви напевно почнете використовувати частіше й інші команди. Не вагайтесь створювати для них нові псевдоніми. Ця техніка також може бути дуже корисною для створення нових команд, які на вашу думку, мали б існувати. Наприклад, щоб виправити незручність, яку ми бачили при скасуванні змін до файлу, ви можете додати свою власну команду unstage (видалити з індексу) до Git: $ git config --global alias.unstage 'reset HEAD --' Після цього наступні дві команди еквівалентні: $ 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:24
https://play.google.com/store/apps/details?id=org.thunderdog.challegram&hl=de	Telegram X - 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 play_arrow Trailer Telegram X Telegram FZ-LLC 4.2 star 811K reviews 100M+ Downloads Rated for 12+ info Install Share Add to wishlist play_arrow Trailer About this app arrow_forward An alternative Telegram client based on TDLib, with higher speed, slicker animations and experimental features. Updated on Jan 7, 2026 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 Location, Personal info and 6 others Data is encrypted in transit You can request that data be deleted See details Ratings and reviews Ratings and reviews are verified info_outline arrow_forward Ratings and reviews are verified info_outline phone_android Phone laptop Chromebook tablet_android Tablet 4.2 788K reviews 5 4 3 2 1 Joshua Sharp more_vert Flag inappropriate September 8, 2025 The app works well, but their major monetization hook is: if you don't pay for premium, you have to allow any random person to message you. I generally have to block around one scammer a day. If I could only allow contacts to message me, it would be five stars. But monetizing by making people be vulnerable to scams and harassment unless they buy premium is a terrible business strategy. 1,613 people found this review helpful Did you find this helpful? Yes No Alexander Guzman more_vert Flag inappropriate Show review history July 18, 2025 Delivers the same telegram experience. But I typically find it is more stable and has never crashed on me. some features are a little more limited but it works quickly and simply. update 7-2025: still have unexplained restrictions.. cannot recommend this app at all, if for no reason your just going to get cut off and block from reaching your friends and damoly. literally useless now. 17,436 people found this review helpful Did you find this helpful? Yes <div role="button" id="279e488c-c194-	2026-01-13T09:29:24
https://git-scm.com/book/gr/v2/%ce%a4%ce%bf-Git-%cf%83%cf%84%ce%bf%ce%bd-%ce%b4%ce%b9%ce%b1%ce%ba%ce%bf%ce%bc%ce%b9%cf%83%cf%84%ce%ae-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. Ξεκινώντας με το 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 4.7 Το Git στον διακομιστή - GitWeb GitWeb Τώρα που έχουμε βασική πρόσβαση ανάγνωσης/εγγραφής και μόνο-για-ανάγνωση στο έργο μας, ίσως θελήσουμε να δημιουργήσουμε ένα απλό οπτικοκοποιητή (visualizer) ιστού. Το Git συνοδεύεται από ένα script CGI που ονομάζεται GitWeb και χρησιμοποιείται μερικές φορές για αυτό τον σκοπό. Figure 49. Η διεπαφή χρήστη του GitWeb Αν θέλουμε να δούμε πώς θα μοιάζει το GitWeb για το έργο μας, το Git παρέχει με μια εντολή που ενεργοποιεί ένα προσωρινό στιγμιότυπο (instance) αν έχουμε έναν ελαφρύ διακομιστή στο σύστημά μας όπως τον lighttpd ή τον webrick . Στα μηχανήματα Linux, ο lighttpd είναι συχνά εγκατεστημένος, οπότε ίσως μπορούμε να τον τρέξουμε εκτελώντας git instaweb στον κατάλογο του έργου. Εάν τρέχουμε Mac, το Leopard έρχεται προεγκατεστημένο με Ruby, έτσι το πιθανότερο είνα να είναι διαθέσιμος ο webrick . Για να ξεκινήσουμε το instaweb με handler που δεν είναι 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 στη θύρα 1234 και στη συνέχεια ξεκινά αυτόματα ένα πρόγραμμα περιήγησης που ανοίγει σε αυτή τη σελίδα. Είναι τόσο εύκολο. Όταν τελειώσουμε και θέλουμε να τερματίσουμε τη λειτουργία του διακομιστή, μπορούμε να εκτελέσουμε την ίδια εντολή με την επιλογή --stop : $ git instaweb --httpd=webrick --stop Εάν θέλουμε να τρέχουμε συνεχώς τη διεπαφή ιστού σε έναν διακομιστή για την ομάδα μας ή για ένα έργο ανοιχτού κώδικα που φιλοξενούμε, θα πρέπει να ρυθμίσουμε το script CGI να προσφέρεται από τον συνηθισμένο web server μας. Ορισμένες διανομές Linux έχουν ένα πακέτο gitweb που μπορούμε να εγκαταστήσουμε με apt ή dnf , επομένως ίσως είναι καλό να δοκιμάσουμε αυτό πρώτα. Θα δείξουμε τη χειροκίνητη εγκατάσταση του GitWeb πολύ συνοπτικά. Πρώτα πρέπει να πάρουμε τον πηγαίο κώδικα του Git, με τον οποίο έρχεται το GitWeb, και να δημιουργήσουμε το προσαρμοσμένο script 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/ Παρατηρούμε ότι πρέπει να πούμε στην εντολή πού να βρει τα αποθετήρια Git με τη μεταβλητή GITWEB_PROJECTROOT . Τώρα, πρέπει να κάνουμε το Apache να χρησιμοποιεί CGI για αυτό το script και για αυτόν τον σκοπό μπορούμε να προσθέσουμε ένα 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 μπορεί να εξυπηρετηθεί από οποιονδήποτε web server, CGI ή Perl· αν προτιμάμε να χρησιμοποιήσουμε κάτι άλλο, δεν θα είναι δύσκολο να το εγκαταστήσουμε. Σε αυτό το σημείο, θα πρέπει να μπορούμε να επισκεφτούμε την http://gitserver/ για να δούμε τα αποθετήριά μας online. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://git-scm.com/book/uz/v2/Git-%d0%b4%d0%b0-%d1%82%d0%b0%d1%80%d0%bc%d0%be%d2%9b%d0%bb%d0%b0%d0%bd%d0%b8%d1%88-%d0%a2%d0%b0%d1%80%d0%bc%d0%be%d2%9b%d0%bb%d0%b0%d0%bd%d0%b8%d1%88-%d2%b3%d0%b0%d2%9b%d0%b8%d0%b4%d0%b0-%d0%b8%d0%ba%d0%ba%d0%b8-%d0%be%d2%93%d0%b8%d0%b7-%d1%81%d1%9e%d0%b7	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 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 3.1 Git да тармоқланиш - Тармоқланиш ҳақида икки оғиз сўз Деярли барча талқинларни бошқариш тизимлари (ТБТлари) қайсидир шаклда бўлсада тармоқланишни қўллаб қувватлайди. Тармоқланишни қўллаган ҳолда сиз асосий яратиш чизиғидан бошқа чизиқга ўтиб асосий чизиқдаги ишга ҳалақит бермайсиз. Кўпгина ТБТ ларда тармоқни яратиш асосан каталогларни нусхалашни талаб этгани учун катта лойиҳалар учун кўп вақт олувчи жараён бўлади. Баъзи бир одамлар, Git нинг тармоқланиш модели ҳақида гапиришганида, уни бошқа ТБТ лардан орқа фонда қолдирган ҳолатда ажратиб тургани учун ``киллер-фичи`` дея аташади. Унда шунчалик муҳим бўлган нима бор? Git тармоқланиш жуда енгил вазнлидир. Тармоқни яратиш деярли ўша ондаёқ яратилади ва тармоқдан тармоққа ўтиб юришлар ҳам тез бажарилади. Кўпгина бошқа ТБТ лардан фарқли равишда Git бир кунда бир неча бор бирлаштириш ва тармоқланишлар амалга оширилиши сабабли иш жараёнини бироз кенгайтиради. Ушбу функционални тушуниш ва уни бошқара олиш сизга такрорланмас ва мустаҳкам бўлган ускуна сифатида сизга одат бўлиб қолган яратувчанлик жараёнини ўзгартириб юборади. Тармоқланиш ҳақида икки оғиз сўз Тармоқланиш механизмини тушуниш учун ортга қайтиб Git ни маълумотларни қандай сақлашини ўрганиш керак. Иш бошланиши бўлимдагилар ёдингизда бўлса, Git маълумотларни ўзгаришлар кетма-кетлиги тарзида сақламйди у суръатлар (snapshot) тўпламини ишлатади. Сиз фиксирлашни амалга ошираётган вақтингизда Git уни тайёрланган файллар суръатига (snapshot) мурожаат қиладиган кўрсаткични ўзида мужассамлаштирган объект тарзида сақлайди. Ушбу объект муаллифнинг номи, email и, ҳабари ва фиксирлашга тегишли кўрсаткич ёки ундан олдинги (унинг аждодлари) фиксирлашлар ҳақида маълумотларни ўзида мужассамлаштирган: биринчи сафарги фиксирлаш учун авлод фиксирлашлар бўлмайди, оддий фиксирлашга битта бош фиксирлаш ва тармоқларнинг бирлашишидан хосил бўлган фиксирлашда бир нечта бош фиксирлашлар. Тасаввур қилинг файллар дарахтини ўзида сақловчи каталог мавжуд бўлсин, ва сиз уларни барчасини тайёрлаябсиз ва сўнгра уларни битта фиксирлаш тарзида сақлаябсиз. Тайёрлаш жараёнида ҳар бир файлнинг Git да файлларнинг талқини (Git уларга мурожаат қилади) ҳисобланмиш назорат йиғиндиси ( Иш бошланиши дан билганимиздек у SHA-1) ҳисоблаб чиқилади сўнгра ушбу йиғиндилар тайёрланган файллар соҳасига қўшилади: $ git add README test.rb LICENSE $ git commit -m 'initial commit of my project' Қачон сиз фиксирлашни git commit командаси билан яратар экансиз, Git ҳар бир қисм каталогларни (бизнинг мисолимизда лойиҳанинг фақат бош каталогини) назорат йиғиндисини ҳисоблаб чиқади ва ушбу объектлар дарахтини омборга сақлайди. Сўнгра Git фиксирлаш объектини метамаълумот ва лойиҳанинг асосий дарахтига мурожаат қилувчи кўрсаткич билан яратади. Бундай қилинишига сабаб у зарурат туғилганда ушбу суръатни (snapshot) яратиш имконини яратишдир. Сизнинг Git омборингиз энди бешта объектни сақлайди: ҳар бир файлнинг ташкил этувчилари учун блоб (blob), сақланган файллар блобларига кўрсатувчи кўрсаткичлари билан бирга каталогнинг ташкил этувчиларини дарахтсимон кўриниш, асосий дарахтга мурожаат қилувчи кўрсаткичли фиксирлашнинг ўзи, фиксирлашнинг метамаълумотлари. Figure 9. Фиксирлаш ва унинг дарахти Агар сиз ўзгартириш киритсангиз ва яна фиксирлашни бажарсангиз у ҳолда навбатдаги фиксирлаш ўзидан олдинги фиксирлашга кўрсатувчи кўрсаткични сақлайди. Figure 10. Фиксирлаш ва унинг бошлари Git да тармоқ (branch) бу — енгилгина ана шу фиксирлашлардан бирига кўчувчи кўрсаткич. Git да асосий тармоқнинг номи одатда — master . Сиз қачон фиксирлашларни бажарар экансиз сиз охирги фиксирлашга кўрсатувчи асосий тармоқни оласиз. Ҳар бир фиксирлаш автоматик тарзда ушбу кўрсаткични олдинга томон суради. Note “master” тармоғи бу Git даги — махсус тармоқ эмас. Уни ҳамма тармоқлардан фарқли жойи йўқ. Унинг деярли ҳамма омборда мавжудлигига сабаб уни git init командаси яратади ва кўпчилик одамлар уни номини ўзгартиришмайди. Figure 11. Тармоқ ва фиксирлашлар тарихи Янги тармоқ яратиш Сиз тармоқ яратган вақтингизда айнан нима содир бўлади? Кейинчалик силжитиш учун янги кўрсаткич яратилади. Айтайлик сиз “testing” номли янги тармоқ яратмоқчисиз. Сиз буни ушбу git branch командаси орқали қилишингиз мумкин: $ git branch testing Натижада сиз турган фиксирлашга кўрсатувчи янги кўрсаткич яратилади. Figure 12. Икки тармоқ битта фиксирлашлар кетма-кетлигига кўрсатаябди Git сизни қайси тармоқдалигингизни қандай қилиб аниқлайди? У махсус HEAD номли кўрсаткични сақлайди. Шуни назарда тутингки Git да HEAD тушунчаси бошқа авваллари балки сиз ишлатган (Subversion ёки CVS) талқинларни бошқариш тизимидагиларга қараганда анчагина фарқ қилади. Git да бу сиз турган маҳаллий тармоққа кўрсатувчи кўрсаткич. Бизнинг мисолимизда биз ҳоли “master” тармоғида турибмиз. git branch командаси фақат янги тармоқ яратади . Унга щтиш бажарилмайди. Figure 13. HEAD кўрсаткичи тармоққа кўрсатаябди Сиз буни git log командаси ёрдамида онсонлик билан кўришингиз мумкин. У сизга тармоқлар кўрсаткичлари қаерга кўрсатаётганини кўрсатади. Ушшбу опция --decorate дейилади. $ git log --oneline --decorate f30ab (HEAD, master, testing) add feature #32 - ability to add new 34ac2 fixed bug #1328 - stack overflow under certain conditions 98ca9 initial commit of my project f30ab фиксирлашга кўрсатувчи “master” ва “testing” тармоқлари кўриниб турибди. Тармоқларга уланиш Мавжуд тармоққа уланиш учун 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 кўрсаткичи силжиди, сиз checkout қилдингиз Ушбу команда иккита нарсани қилди. У HEAD кўрсаткичини ортга “master” тармоғига силжитди ва ишчи каталогидаги файлларни тармоқ кўрсатаётган суръатдаги(snapshot) сақланган ҳолатга қайтарди. Бу яна бундан буёғига киритилган ўзгаришлар лойиҳанинг эски талқинига тегишли бўлишини англатади. Бошқа сўзлар билан айтганда “testing” тармоғида бажарилган барча ишлар ортга қайтарилди, бироқ сиз бошқа йўналишда давом этишингиз мумкин. Note Тармоқларга уланиш ишчи каталогидаги файлларни ўзгартиради Ёдда тутиш муҳимки, сиз Git да тармоқларга уланаётган вақтингизда ишчи каталогидаги файллар ўзгаради. Агар сиз эски тармоққа уланаётган бўлсангиз унда ишчи каталог кўриниши ана шу тармоқнинг охирги фиксирлаш ҳолатидаги кўринишида бўлади. Агар Git қайсидир сабабга кўра буни қила олмаса у сизга тармоққа уланишга қўймайди. Келинг яна бир қанча ўзгаришлар киритамиз ва навбатдаги фиксирлашни бажарамиз: $ vim test.rb $ git commit -a -m 'made other changes' Энди сизни лойиҳангиз тарихи бўлинди ( Тармоқланган тарих га қаранг). Сиз тармоқ яратдингиз, унга уландингиз, унда ишладингиз, сўнг асосий тармоққа қайтдингиз ва унда ишладингиз. Ушбу ўзгаришлар бир-биридан изоляцияланган: сиз ундан бунга бемалол ўтишингиз мумкин ва қачон тайёр бўлса уларни биргаликда бирлаштиришингиз мумкин. Ва буларнинг барчаси оддийгина командалар орқали бажарилади: 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 белги ва сатрга ўтиш). 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:24
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#reels-api	Instagram API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Instagram API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Posts API Collect by URL Discover by URL Comments API Collect by URL Reels API Collect by URL Discover by URL Social Media APIs Instagram API Scrapers Copy page Copy page Overview The Instagram API Suite offers multiple types of APIs, each designed for specific data collection needs from Instagram. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : N/A Interesting Columns : followers , post_count , post_hashtags , profile_name . Posts API This API allows users to collect multiple posts based on a single input URL (such as an Instagram reels URL, search URL or profile URL). Discovery functionality : - Direct URL of the Instagram reel - Direct URL of the search - Direct URL of the profile Interesting Columns : url , followers , hashtags , engagement_score_view . Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : comment_user , comment , likes_number , replies_number . The suite of APIs is designed to offer flexibility for targeted data collection, where users can input specific URLs to gather detailed post and comment data, either in bulk or with precise filtering options. Profiles API Collect by URL This API allows users to collect detailed data about an Instagram profile by providing the profile URL. It provides a comprehensive overview of an Instagram profile, including business and engagement information, posts, and user details. Input Parameters URL string required The Instagram profile URL. Output Structure Includes comprehensive data points: Page/Profile Details : account , id , followers , posts_count , is_business_account , is_professional_account , is_verified , avg_engagement , profile_name , profile_url , profile_image_link , and more. For all data points, click here . Posts API Collect by URL This API enables users to collect detailed data from Instagram posts by providing a post URL. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Post Details : post_id , description , hashtags , date_posted , num_comments , likes , content_type , video_view_count , video_play_count , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : photos , videos , thumbnail , display_url (link only, not the file itself), audio. Discover by URL This API allows users to discover recent Instagram posts from a public profile by providing the profile URL and specifying additional parameters. Input Parameters URL string required The Instagram profile URL. num_of_posts number The number of recent posts to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date). post_type string Specify the type of posts to collect (e.g., post, reel). Output Structure Includes comprehensive data points: Post Details: post_id , description , hashtags , date_posted , num_comments , likes , video_view_count , video_play_count ,and more. For all data points, click here . Page/Profile Details: user_posted , followers , posts_count , profile_image_link , is_verified , profile_url , is_paid_partnership , partnership_details , user_posted_id Attachments and Media: photos , videos , thumbnail , audio , display_url , content_type , product_type , coauthor_producers , tagged_users . This API is designed to allow for filtering, exclusion of specific posts, and collecting posts by type (regular post or reel) within a defined time frame. It provides detailed post and profile information, making it ideal for data collection and analytics. Comments API Collect by URL This API allows users to collect the latest comments from a specific Instagram post by providing the post URL. This API retrieves the most recent 10 comments along with associated metadata. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Comment Details : comment_id , comment_user , comment_user_url , comment_date , comment , likes_number , replies_number , replies , hashtag_comment , tagged_users_in_comment , and more. For all data points, click here . User Details : user_name , user_id , user_url We provide a limited set of data points about the profile. Post Metadata : post_url , post_user , post_id . Reels API Collect by URL This API allows users to collect detailed data about Instagram reels from public profiles by providing the reel URL. Input Parameters URL string required The Instagram reel URL. Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , tagged_users , num_comments , likes , views , video_play_count , length , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : video_url , thumbnail , audio_url . Discover by URL This API allows users to discover Instagram Reels videos from a profile URL or direct search URL. Input Parameters URL string required The Instagram profile or direct search URL. num_of_posts number The number of recent reels to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering reels in MM-DD-YYYY format. end_date string End date for filtering reels in MM-DD-YYYY format (should be later than start_date ). Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , num_comments , likes , views , video_play_count , top_comments , length , video_url , audio_url , content_id , and more. For all data points, click here . Profile Details : user_posted , followers , posts_count , following . Attachments and Media : video_url , thumbnail , audio_url (link only, not the file itself). This API provides detailed information about Instagram Reels, with filtering options by date range, exclusion of specific posts, and a limit on the number of reels collected. Was this page helpful? Yes No Facebook LinkedIn ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:24
https://git-scm.com/book/tr/v2/Git-Temelleri-De%c4%9fi%c5%9fikliklerin-Repoya-Kaydedilmesi	Git - Değişikliklerin Repoya Kaydedilmesi 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 2.2 Git Temelleri - Değişikliklerin Repoya Kaydedilmesi Değişikliklerin Repoya Kaydedilmesi Şu aşamada, yerel makinenizde bir Git reposuna ve önünüzde tüm dosyaları kullanıma hazır veya çalışmakta olan bir kopyasına sahip olmalısınız. Doğal olarak, proje kaydetmek istediğiniz duruma her ulaştığında değişiklik yapmaya ve bu değişikliklerin pozlarını (snapshot) reponuza kaydetmeye başlamak isteyeceksiniz. Çalışma dizininizdeki her dosyanın iki durumdan birinde olabileceğini unutmayın: ``tracked`` (izlenen / takip edilen) veya ``untracked`` (izlenmeyen / takip edilmeyen). İzlenen dosyalar, son pozdaki dosyalardır: bunlar ``modified`` (değiştirilmiş), ``unmodified`` (değiştirilmemiş) veya ``staged`` (izleme alınmış; indekslenmiş) olabilirler. Kısacası izlenen dosyalar Git’in haberdar olduğu ve değişikliklerini takip ettiği dosyalardır. İzlenmeyen dosyalar ise diğer her şeydir (çalışma dizininizdeki, son pozda olmayan ve izlemde olmayan dosyalardır). Bir repoyu ilk kez kopyaladığınızda, tüm dosyalarınız izlenecek ve ``unmodified`` (değiştirilmemiş) olarak işaretlenmiş olacaktır. Çünkü Git onları daha yeni teslim aldı ve siz henüz hiçbir değişiklik yapmadınız. Siz dosyaları düzenlerken Git onları ``modified`` (değiştirilmiş) olarak görür, çünkü son Git işleminizden (commit, clone, vs) sonra bu dosyalarda değişiklik yaptınız. Çalışırken, bu değiştirilmiş dosyaları seçerek izleme alırsınız (katkılamak amacıyla indekslersiniz) ve ardından izleme alınmış tüm bu değişiklikleri katkı olarak işlersiniz. Ve bu döngü her değişiklikten sonra tekrarlanır. Görsel 8. Dosyalarınızın durumunun yaşam döngüsü. Dosyalarınızın Durumunu Denetleme Hangi dosyanın hangi durumda olduğunu görmek için git status komutu kullanırız. Bu komutu bir projeyi kopyaladıktan hemen sonra çalıştırırsanız şöyle bir şey görmelisiniz: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean Bu, temiz bir çalışma dizininiz olduğu anlamına gelir. Bir başka deyişle, izlenen dosyalarınızın hiçbirinde henüz bir değişiklik yoktur. Ayrıca, Git izlenmeyen dosyaları görmez; aksi halde onlar da burada listelenirdi. Son olarak bu komut size hangi projenin hangi dalında (branch) olduğunuzu söyler ve sunucuda kopyaladığınız daldan ayrılmadığınızı bildirir. Şimdilik bu dal her zaman varsayılan olan ``master``, yani "ana dal"dır. Bunda endişelenmenizi gerektirecek bir durum yoktur. Git Dalları ünitesinde dalları (branch) ve işaretçileri (reference) ayrıntılı olarak göreceksiniz. Diyelim ki projenize yeni bir dosya, mesela basit bir README (BENİ OKU) dosyası eklediniz. Dosya daha önce mevcut değilse ve git status komutunu çalıştırırsanız izlenmeyen dosyanızı şu şekilde görürsünüz: $ 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) Yeni README dosyanızın izlenmediğini görebilirsiniz, çünkü git status komutuyla alacağınız durum çıktısında Untracked files (izlenmeyen dosyalar) başlığı altındadır. "İzlenmeyen" temel olarak Git’in önceki pozda sahip olmadığınız bir dosyayı gördüğü anlamına gelir. Siz bunu yapmasını açıkça söyleyene kadar, Git bunu pozlarınıza dahil etmeyecektir. Böyle yapmasının sebebi, sizi yanlışlıkla oluşturulan "ikili" (binary) dosyaların veya eklemek istemediğiniz diğer dosyaların gereksiz kalabalığından ve kafa karışıklığından korumak istemesidir. README 'yi katkılarınıza dahil etmek istiyorsanız, o halde dosyayı izlemeye başlayalım. Yeni Dosyaları İzleme Yeni bir dosyayı izlemeye başlamak için git add komutu kullanılır. README dosyasını izlemeye başlamak için şu komutu çalıştırın: $ git add README Durum komutunuzu (git status) tekrar çalıştırırsanız, README dosyanızın artık takip edildiğini (tracked) ve kaydedilmek üzere izleme alındığını görebilirsiniz: $ 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 başlığı altında yer aldığından izleme alındığını anlayabilirsiniz. Bu noktada bir katkı işlerseniz, dosyanın git add çalıştırdığınız andaki sürümü, katkı geçmişinize yeni bir katkı olarak kaydedilecektir. Daha önce git init komutunu çalıştırdığınızda, hemen ardından git add <files> komutunu çalıştırdınız. Bunun amacı dizininizdeki dosyaları izlemeye başlamaktı. git add komutu, bir dosya veya dizin için bir yol adı alır. Eğer bu bir dizinse, ilgili dizin ve alt dizinlerindeki tüm dosyaları izleme ekler. Değiştirilmiş Dosyaları İzleme Alma Şimdi izlenmekte (tracked) olan bir dosyayı değiştirelim. Eğer izlenmnekte olan CONTRIBUTING.md adlı dosyayı değiştirir ve ardından git status komutunu tekrar çalıştırırsanız, şöyle bir sonuç elde edersiniz: $ 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 dosyası, Changes not staged for commit adlı bir bölümün altında görünür. Bu, izlenen bir dosyanın çalışma dizininde değiştirildiği, ancak henüz izleme alınmadığı anlamına gelir. İzleme almak için git add komutunu çalıştırmalısınız. git add çok amaçlı bir komuttur: yeni dosyaları takibe başlamak, dosyaları izleme almak (katkı için indekslemek) ve birleştirme sonucunda çakışan dosyaları (merge conflict) çözümlenmiş olarak işaretlemek gibi diğer şeyler için de kullanırsınız. Bunu, "bu dosyayı projeye ekle" yerine "bu içeriği bir sonraki işleme ekle" olarak düşünmek daha faydalı olabilir. Şimdi CONTRIBUTING.md dosyasını izleme almak için git add komutunu çalıştıralım ve ardından git status komutunu bir kez daha koşalım: $ 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 Her iki dosya da izlemdedir ve bir sonraki işleminize aktarılacaktır. Bu noktada, varsayalım ki CONTRIBUTING.md dosyasında yapmak istediğiniz küçük bir değişikliği hatırladınız. Dosyayı tekrar açar ve bu değişikliği yaparsınız, artık değişikliğinizi katkı olarak işlemeye hazırsınız. Hadi git status komutunu bir kez daha çalıştıralım: $ 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 Bu da ne! Artık CONTRIBUTING.md hem staged hem de unstaged olarak listelenmiş. Peki neden böyle oldu!? Git’in bir dosyayı tam olarak git add komutunu çalıştırdığınız anda olduğu gibi izleme aldığını görüyorsunuz. Eğer şimdi git commit komutunu çalıştırırsanız, CONTRIBUTING.md nin çalışma dizininizde göründüğü şekliyle değil de git add komutunu en son çalıştırdığınız andaki sürümü kayıt işlemine girecektir. git add çalıştırdıktan sonra bir dosyayı değiştirirseniz, dosyanın en son sürümünü izleme almak için tekrar git add çalıştırmanız gerekir: $ 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 Özet-Durum Bilgisi git status çıktısı oldukça kapsamlı ve aynı zamanda da uzundur. Git’te ayrıca bir özet-durum bayrağı bulunur, böylece değişikliklerinizi daha derli toplu bir şekilde görebilirsiniz. Eğer git status -s veya git status --short komutunu çalıştırırsanız, çok daha basitleştirilmiş bir çıktı elde edersiniz: $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt İzlenmeyen yeni dosyaların yanında ?? , aşama alanına eklenen yeni dosyaların yanında A (added), değiştirilen dosyaların yanında ise M (modified) bulunur. Çıktıda iki sütun vardır: soldaki sütun izlem (stage) durumunu, sağdaki sütun ise çalışma ağacının (working tree) durumunu gösterir. Örneğin bu çıktıda, README dosyası çalışma dizininde değiştirilmiş ancak henüz izleme alınmamıştır. lib/simplegit.rb dosyası ise değiştirilmiş ve izleme alınmıştır. Rakefile değiştirildi (modified), izleme alındı (staged) ve tekrar değiştirildi (changed). Dolayısıyla üzerinde hem "staged" hem de "unstaged" değişiklikler var. Dosyaları Yoksayma (Ignore) Sıklıkla Git’in otomatik olarak eklemesini veya izlemesini istemediğiniz bazı dosyalara sahip olursunuz. Bunlar genellikle kayıt dosyaları gibi derleme sisteminiz tarafından otomatik olarak oluşturulan dosyalardır. Bu gibi durumlarda, bunlarla eşleşecek şekilde .gitignore adlı bir dosya listeleme modeli oluşturabilirsiniz. Örnek bir .gitignore dosyası: $ cat .gitignore .[oa] ~ İlk satır Git’e, çalıştırdığınız kodun bir yan çıktısı olabileceği için, uzantısı .o (object) veya .a (archive) ile biten tüm dosyaları yoksaymasını söyler. İkinci satır Git’e, adları tilde ( ~ ) ile biten tüm dosyaları yok saymasını söyler; bu, Emacs gibi birçok metin düzenleyicisi tarafından geçici dosyaları işaretlemek için kullanılır. Ayrıca otomatik olarak oluşturulan log (kayıt), tmp (geçici) veya pid (işlem kimliği) vb dizinleri de ekleyebilirsiniz. Başlamadan önce yeni reponuz için bir .gitignore dosyası oluşturmak iyi bir fikirdir. Böylece Git reponuzda görmek istemediğiniz dosyaları yanlışlıkla katkı olarak işlemezsiniz. .gitignore dosyasını yazarken göz önünde bulundurmanız gereken kurallar şunlardır: Boş satırlar veya # ile başlayan satırlar dikkate alınmaz. Standart glob desenleri işler. Yani yazdığınız kural çalışma ağacınızdaki tüm dosyalar için alt dizinleri de dahil olmak üzere geçerlidir. Bu alt dizinlere inen yinelemeyi önlemek için dosya dizinine eğik çizgi ( / ) ile başlayabilirsiniz. Kuralın geçerli olmasını istediğimiz belli bir dizini belirtmek için dosya dizinini eğik çizgiyle ( / ) sonlandırabilirsiniz. Kuralın uygulanmasını istemediğiniz bir modeli ünlem işaretiyle ( ! ) başlatarak reddedebilirsiniz. Glob desenleri, "shell"in kullandığı "RegEx" ifadelerine benzer: Yıldız işareti ( * ) sıfır veya daha fazla karakterle eşleşir, [abc] parantez içindeki herhangi bir karakterle eşleşir (bu örnekte a, b veya c), Soru işareti ( ? ) tek bir karakterle eşleşir, Ve kısa çizgiyle ( [0-9] ) ayrılmış karakterleri çevreleyen parantezler bu aralıkta yer alan herhangi bir karakterle (bu örnekte 0’dan 9’a kadar rakamlarla) eşleşir, İç içe geçmiş dizinleri eşleştirmek için iki yıldız işareti de kullanabilirsiniz; a/*/z ifadesi, a/z , a/b/z , a/b/c/z , vb. ile eşleşir. İşte size örnek bir .gitignore dosyası: # .a uzantılı tüm dosyaları yoksay .a # .a uzantılı tüm dosyaları yoksaysan da, lib.a dosyası bu kuralın istisnasıdır. lib.a dosyasındaki değişiklikleri izle !lib.a # Sadece bu dizindeki TODO dosyasını yoksay. Diğer dizinlerdeki TODO dosyalarını değil. (ör: subdir/TODO) /TODO # build dizinindeki ve onun alt dizinlerindeki tüm dosyaları yoksay build/ # doc/notes.txt dosyasını yoksay ama doc/server/arch.txt dosyasını değil doc/.txt # doc/ klasörü ve alt klasörlerinde yer alan tüm .pdf dosyalarını yoksay doc//.pdf İpucu Eğer projeniz için bir başlangıç noktasına ihtiyaç duyuyorsanız GitHub, https://github.com/github/gitignore adresinde pekçok farklı proje ve dilde ``.gitignore`` dosya örneklerinin kapsamlı bir listesini tutmaktadır. Not Basit projelerde, bir proje kök dizininde, tüm alt dizinler için geçerli olmak üzere tek bir ".gitignore" dosyası bulunur. Yine de alt dizinlerde ek .gitignore dosyalarının bulunması da mümkündür. Bu iç içe geçmiş .gitignore dosyalarındaki kurallar yalnızca bulundukları dizinin alt klasörlerinde bulunan dosyalar için geçerlidir. (Örneğin Linux çekirdeği kaynak reposunda 206 adet .gitignore dosyası bulunmaktadır.) Birden fazla ".gitignore" dosyası bulunduğu durumlar bu kitabın kapsamı dışındadır. Bu konuda daha detaylı bilgiye konsol ekranınıza man gitignore komutu yazarak ulaşabilirsiniz. İzleme Alınmış (Staged) ve Alınmamış (Unstaged) Değişiklikleri Görme git status komutu sizin için yeterince bilgi içermiyorsa (sadece hangi dosyaların değiştirildiğini değil, tam olarak neyi değiştirdiğinizi de bilmek istiyorsanız), bunun yerine git diff komutunu kullanabilirsiniz. git diff komutunu daha sonra ayrıntılı olarak ele alacağız, ancak muhtemelen onu en çok şu iki soruya cevap bulmak için kullanacaksınız: 1. Neyi değiştirdiniz ama henüz izleme almadınız? 2. Neyi izleme aldınız fakat henüz katkı olarak işlemediniz? Her ne kadar git status bu soruları genel olarak dosya adlarını listeleyerek cevaplasa da git diff size; eklenen ve kaldırılan satırları, değiştirilen her bir kod parçasıyla birlikte, detaylıca gösterir. Diyelim ki README dosyasını tekrar değiştirip izleme alıyorsunuz ve ardından CONTRIBUTING.md dosyasını izleme almadan düzenliyorsunuz. git status komutunuzu çalıştırırsanız bir kez daha şöyle bir şey görürsünüz: $ 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 Neyi değiştirdiğinizi ancak henüz izleme almadığınızı görmek için herhangi bir bayrak (parametre) kullanmadan ‘git diff’ yazın: $ 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 Bu komut, çalışma dizininizdeki güncel kodu, izlem alanınızdaki kodla karşılaştırır. Sonuç size, henüz gerçekleştirmediğiniz değişiklikleri görme imkanı tanır. Eğer bir sonraki katkı işleminizde nelerin kaydedileceğini görmek istiyorsanız git diff --staged komutunu kullanabilirsiniz. Bu komut, izlemdeki değişikliklerinizi, en son katkı olarak işlediğiniz kodla karşılaştırır: $ 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 komutunun son katkı işleminizden bu yana yapılan tüm değişiklikleri göstermediğini, yalnızca henüz izleme alınmamış değişiklikleri gösterdiğini aklınızdan çıkarmayın. Eğer tüm değişikliklerinizi izleme aldıysanız, git diff size hiçbir çıktı vermeyecektir. Bir başka örnek olarak, CONTRIBUTING.md dosyasını izleme alır ve ardından yeniden düzenlerseniz, dosyadaki izleme alınmış ve alınmammış değişiklikleri görmek için git diff komutunu kullanabilirsiniz. Ortamımız şöyle görünüyorsa: $ 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 Artık neyin izleme alınmamış olduğunu görmek için ' git diff komutunu kullanabilirsiniz: $ 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 veya şu ana kadar neleri izleme aldığınızı görmek için git diff --cached ( --staged ve --cached eşanlamlıdır) komutunu kullanabilirsiniz: $ 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 Not Harici Araçlarda .Git Diff Kitabın geri kalanında git diff komutunu çeşitli şekillerde kullanmaya devam edeceğiz. Çalışma ortamı ve repodaki kodlar arasındaki farkları görmek için konsol ekranı yerine görsel veya harici bir arayüz programını tercih ederseniz, bu farklılıklara bakmanın başka yolları da vardır. Eğer git diff yerine git difftool komutu çalıştırırsanız, bu farklardan herhangi birini "emerge", "vimdiff" ve daha birçok farklı yazılımda (ticari yazılımlar dahil) görüntüleyebilirsiniz. Sisteminizde hangilerinin mevcut olduğunu görmek için git difftool --tool-help komutunu çalıştırabilirsiniz. Değişiklikleri Katkı Olarak İşlemek Artık izlem alanınız istediğiniz şekilde ayarlandığına göre değişikliklerinizi katkı olarak işleyebilirsiniz. "unstaged" olarak işaretli olan dosyalarınızın (oluşturduğunuz veya değiştirdiğiniz fakat hiç git add komutuyla izleme almadığınız dosyalar) bu işlemle katkı geçmişine kaydedilmeyeceğini aklınızdan çıkarmayın. Bu dosyalar diskinizde "modified" (değiştirilmiş) işaretli olarak kalacaklar. Bu durumda, eğer bir kez daha git status komutunu çalıştırırsanız ve her şeyin "staged" işaretli olduğunu görürseniz, artık değişikliklerinizi katkı olarak işlemeye hazırsınız demektir. Değişikliklerinizi işlemenin en basit yolu git commit komutunu çalıştırmaktır: $ git commit Bunu yaptığınızda seçili derleyiciniz başlatılır. (Bu sizin shell’inizin EDITOR ortam değişkeni tarafından ayarlanmıştır. (Genellikle "vim" veya "emacs"tır, ancak Başlangıç ünitesinde gördüğünüz gibi git config --global core.editor komutunu kullanarak bunu istediğiniz şekilde yapılandırabilirsiniz.). Ekranda aşağıdaki metni göreceksiniz (bu örnek bir Vim ekranıdır): # 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 Varsayılan katkı mesajının, yorumlanan git status komutunun en son çıktısını ve üstte bir boş satırı içerdiğini görebilirsiniz. Bu yorumları kaldırabilir ve katkı mesajınızı yazabilir veya neyi katkı olarak işlediğinizi hatırlamanıza yardımcı olması için orada bırakabilirsiniz. (Neyi değiştirdiğinizi daha da açık bir şekilde hatırlatmak için, git commit komutuna -v bayrağı ekleyebilirsiniz. Böylece yaptığınız değişikliği (diff) derleyicinize eklemiş olursunuz ve tam olarak hangi değişiklikleri yaptığınızı görebilirsiniz.) Derleyicinizden çıktığınızda, Git bu mesajla birlikte (yorumlar ve değişiklikler çıkarılmış olarak) katkı kaydınızı oluşturur. Alternatif olarak, -m (message) bayrağı kullanarak katkı mesajınızı commit komutuyla aynı satırda yazabilirsiniz: $ 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 Tebrikler, artık ilk katkınızı işlediniz! Bu katkı kaydının size kendisi hakkında bazı çıkarımlar verdiğini görebilirsiniz; değişiklikleri hangi dala ( master ) kaydettiğiniz, kaydın hangi SHA-1 (Secure Hash Algorithm 1) koduna (Gelecekte, geçmiş bir katkıya geri dönmek istediğinizde tam olarak hangi katkıya dönmek istediğinizi belirtebilmeniz içih her bir katkınızın kendine özel bir SHA-1 kodu bulunur. Bu bir nevi katkınızın kimlik numarası gibidir.) sahip olduğu ( 463dc4f ), kaç dosyanın değiştirildiği, eklenen ve silinen satırlarla ilgili istatistikler vb bulunmaktadır. Katkı kayıtlarınızın izleme yüklediğiniz kodun pozu (anlık görüntüsü) olduğunu unutmayın. İzleme almadığınız her şey dosya ve kod hala orada değiştirilmiş bir halde duruyor. Bunları katkı geçmişinize eklemek için başka bir katkı işleminde bulunabilirsiniz. Aslında her katkı işlediğinizde, projenizin daha sonra geri dönebileceğiniz veya karşılaştırabileceğiniz bir pozunu kaydetmiş oluyorsunuz. İzlem Alanını Atlamak İzlem alanı katkılarınızın tam olarak istediğiniz şekilde işlenmesi için oldukça faydalı olsa da bazen iş akışınız içerisinde beklenenden daha karmaşık olabilir. İzlem alanını atlamak istiyorsanız, Git bunun için basit bir kısayol sağlar. git commit komutuna -a (add) seçeneğinin eklenmesi, Git’in zaten izlenen her dosyayı katkıda bulunmadan önce otomatik olarak izleme almasını sağlar ve git add kısmını atlamanıza olanak tanır: $ 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(-) Bu durumda katkı işlemeden önce CONTRIBUTING.md dosyasında git add komutunu çalıştırmanız gerekmediğine dikkat edin. Bunun nedeni -a bayrağının değiştirilen tüm dosyaları içermesidir. Bunu yapmakta herhangi bir sorun yoktur ancak dikkatli olun; bazen bu bayrak istenmeyen değişiklikleri de katkılarınıza eklemenize neden olur. Dosyaları Silmek Git’ten bir dosyayı kaldırmak için, onu izlemden kaldırmanız ve ardından bu değişikliği kaydetmeniz (commit) gerekir. git rm komutu seçtiğiniz dosyayı hem izlem alanından hem de çalışma dizininizden kaldırır. Böylece bir dahaki sefere onu izlenmeyen bir dosya olarak görmezsiniz. Eğer dosyayı silmek yerine sadece takipten çıkarmak istiyorsanız dosya yolunu ve adını .gitignore dosyasına kaydetmelisiniz. Dosyayı sadece çalışma dizininizden kaldırırsanız, dosyanızı git status çıktınızın Changes not staged for commit (yani unstaged ) alanında görebilirsiniz: $ 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") Daha sonra, eğer git rm komutunu çalıştırırsanız, dosyanın kaldırılması işlemini izlem alanına almış olursunuz: $ 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 Bir sonraki katkı işleminizde dosya kaybolacak ve artık izlenmeyecektir. Dosyayı değiştirdiyseniz veya izleme zaten eklediyseniz, Git’i kaldırma işlemine zorlamak için -f (forced) seçeneğini kullanmalısınız. Bu, henüz poz olarak kaydedilmemiş ve Git’ten kurtarılamayan verilerin yanlışlıkla kaldırılmasını önleyen bir güvenlik özelliğidir. Yapmak isteyebileceğiniz başka bir yararlı şey, dosyayı çalışma ağacınızda tutmak ancak izlemden kaldırmaktır. Başka bir deyişle, dosyayı sabit diskinizde tutmak ancak Git’in artık onu izlememesini sağlamak isteyebilirsiniz. Eğer .gitignore dosyanıza bir şey eklemeyi unuttuysanız ve onu yanlışlıkla izleme aldıysanız (mesela büyük bir "log" dosyası veya işlenmiş .a dosyaları gibi) bu özellik oldukça işinize yarayacaktır. Bunu yapmak için --cached seçeneğini kullanın: $ git rm --cached README Dosyaları, dizinleri ve dosya glob kalıplarını git rm komutuna aktarabilirsiniz. Bu, aşağıdaki gibi şeyler yapabileceğiniz anlamına gelir: $ git rm log/\.log işaretinin önündeki ters eğik çizgiye ( \ ) dikkat edin. Bu özellikle gereklidir; çünkü Git, "shell"inizin dosya adı genişletmesine ek olarak, kendi dosya adı genişletmesini de yapar. Bu komut, log/ dizinindeki .log uzantısına sahip tüm dosyaları kaldırır. Veya şöyle bir şey de yapabilirsiniz: $ git rm \*~ Bu komut, adları ~ ile biten tüm dosyaları kaldırır. Dosyaları Taşıma Diğer birçok VCS sisteminin aksine Git, dosya hareketlerini açıkça izlemez. Bir dosyayı yeniden adlandırırsanız, Git’te dosyayı yeniden adlandırdığınızı bildiren hiçbir meta veri depolanmaz. Ancak Git bu sorunu olaydan sonra çözme konusunda oldukça akıllıdır. Dosya hareketini tespit etme konusunu birazdan ele alacağız. Bu nedenle Git’in bir mv komutuna sahip olması biraz kafa karıştırıcıdır. Git’te bir dosyayı yeniden adlandırmak istiyorsanız şöyle bir komut çalıştırabilirsiniz: $ git mv file_from file_to Bu komut gayet iyi bir şekilde çalışıyor. Aslında, böyle bir şeyi çalıştırıp duruma bakarsanız Git’in bunu yeniden adlandırılmış bir dosya olarak değerlendirdiğini görürsünüz: $ 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 Ancak bu, şunun gibi bir şeyi çalıştırmaya eşdeğerdir: $ mv README.md README $ git rm README.md $ git add README Git bunun dolaylı olarak bir yeniden adlandırma olduğunu anlar, dolayısıyla bir dosyayı bu şekilde veya mv komutuyla yeniden adlandırmanız önemli değildir. Tek dikkate değer fark, git mv komutunun üç yerine tek bir komut olmasıdır ki bu da bize kolaylık sağlar. Daha da önemlisi, bir dosyayı yeniden adlandırmak için istediğiniz herhangi bir aracı kullanabilir ve ardından add/rm ile adresleyerek dosyayı katkı olarak işlemeye uygun hale getirebiliriz. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://git-scm.com/book/it/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. 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 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 Per Iniziare , 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, 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 checksums each one (the SHA-1 hash we mentioned in Per Iniziare ), 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 of my project' When you create the commit by running git commit , Git checksums each subdirectory (in this case, just the root project directory) and stores those tree objects 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: one blob for the contents of each of your 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. Figura 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. Figura 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, it moves forward automatically. Nota 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. Figura 11. A branch and its commit history Creating a New Branch What happens if you create a new branch? Well, doing so creates a new pointer for you to move around. Let’s say you create a new branch called testing. You do this with the git branch command: $ git branch testing This creates a new pointer at the same commit you’re currently on. Figura 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. Figura 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 34ac2 fixed bug #1328 - stack overflow under certain conditions 98ca9 initial commit of my project 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. Figura 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' Figura 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 Figura 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. Nota 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. Figura 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 * 34ac2 fixed bug #1328 - stack overflow under certain conditions * 98ca9 initial commit of my project Because a branch in Git is in actuality 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. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://www.youtube.com/c/babelfishmoney	BabelFish money - YouTube 정보 보도자료 저작권 문의하기 크리에이터 광고 개발자 약관 개인정보처리방침 정책 및 안전 YouTube 작동의 원리 새로운 기능 테스트하기 © 2026 Google LLC, Sundar Pichai, 1600 Amphitheatre Parkway, Mountain View CA 94043, USA, 0807-882-594 (무료), yt-support-solutions-kr@google.com, 호스팅: Google LLC, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다.	2026-01-13T09:29:24
https://git-scm.com/book/tl/v2/Git-sa-Server-Ang-Mga-Protokol	Git - Ang Mga Protokol 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.1 Git sa Server - Ang Mga Protokol Sa puntong ito, maaari mo na dapat gawin ang mga pang-araw-araw na gawain kung saan gagamitin mo ang Git. Gayunpaman, upang makagawa ng anumang kolaborasyon sa Git, kakailanganin mong magkaroon ng remote na respositoryo ng Git. Kahit na technically maaari mong i-push ang iyong mga pagbabago at i-push ang mga pagbabago mula sa mga repositoryo ng mga indibidwal, ang paggawa nito ay hindi hinihikayat dahil madali malito sa kanilang pinagtrabuhan kapag hindi ka maingat. At saka, gusto mo ma-access ang repositoryo ng mga tagapagtulong kahit offline ang iyong kompyuter — Ang pagkakaroon ng mas maaasahang pangkaraniwang repositoryo ay kadalasan kapaki-pakinabang. Sa gayon, ang ginusto na pamamaraan sa pakikipagtulungan ng may kasama ay ang pag-set up ng isang intermediate na repositoryo na kung saan may access kayong dalawa, at mag push at mag pull mula doon. Ang pagpapatakbo ng isang Git Server ay tuwiran. Una, pipili ka kung anong mga protokol ang gusto mo gamitin ng iyong server sa pag-usap. Sinasaklaw ng unang bahagi ng kabanatang ito ang mga magagamit na mga protokol at ang mga kalamangan at kahinaan ng bawat isa. Ang mga susunod na mga bahagi ay magpapaliwanag sa ilang tipikal na mga set up na gamit ang mga protokol na iyon at kung papaano mapapatakbo ang iyong server gamit ang mga iyon. Sa wakas, tatalakayin natin ang ilang mga naka-host na opsyon, kapag wala kang pakialam na i-host ang iyong code sa server ng ibang tao at ayaw mong dumaan sa abala ng pag-set up at pagpapanatili ng sariling server. Kapag hindi ka interesado sa pagpapatakbo ng sarili mong server, maaari kang lumaktaw sa huling bahagi ng kabanata upang makita ang ilang mga opsyon sa pag-set up ng isang naka-host na akawnt at pagkatapos ay lumipat sa susunod na kabanata, kung saan ay tatalakayin natin ang iba’t ibang ins at outs sa pagtatrabaho sa isang distributed source control environment. Ang isang remote na repositoryo ay sa pangkalahatan ay isang hubad na repositoryo — isang repositoryo sa Git na walang gumagana na direktoryo. Dahil ang repositoryo ay ginagamit lamang bilang punto ng kolaborasyon, walang dahilan upang magkaroon ng snapshot na naka-check out sa disk; ito ay data ng Git lamang. Sa madaling salita, ang isang hubad na repositoryo ay naglalaman ng .git na direktoryo ng iyong proyekto at wala ng iba. Ang Mga Protokol Maaaring gamitin ng Git ang apat na magkakaibang mga protokol upang lumipat ng mga data: Lokal, HTTP, Secure Shell (SSH) at Git. Dito tatalakayin natin kung ano sila at kung saang mga pangunahing pangyayari gusto mo (o di gusto) sila gamitin. Lokal na Protokol Ang pinaka-pangunahin ay ang Lokal na protokol , na kung saan ang remote na repositoryo ay nasa ibang direktoryo sa parehong host. Madalas itong ginagamit kapag lahat kayo sa inyong koponan ay may access sa isang ibinahagi na filesystem tulad ng isang NFS mount, o sa malabong kaso na lahat ay nag-log sa parehong kompyuter. Ang huli ay hindi tamang-tama, kasi lahat ng instansya ng repositoryo ng iyong code ay naninirahan sa parehong kompyuter, mas malaki ang posibilidad ng pagkawala ng sakuna. Kapag ikaw ay may isang ibinahagi na naka-mount na filesystem, maaari kang mag clone, mag-push sa, at mag pull mula sa isang lokal na nakabatay sa file na repositoryo. Para i-clone ang isang repositoryo na tulad nito, o idagdag bilang isang remote sa umiiral na proyekto, gamitin ang landas patungo sa repositoryo bilang URL. Halimbawa, upang i-clone ang isang lokal na repositoryo, maaari kang magpagana ng ganito: $ git clone /srv/git/project.git O maaari mong gawin ito: $ git clone file:///srv/git/project.git Ang Git ay gumagana ng bahagyang maiba kapag tahasang tinukoy mo ang file:// sa simula ng URL. Kapag ang landas lamang ang tinukoy mo, Sinusubukan ng Git na gumamit ng mga hardlink o direktang kinokopya ang mga file na kailangan nito. Kapag tinukoy mo ang file:// , pinapagana ng Git ang mga proseso na karanawing ginagamit upang lumipat ng data sa isang network, na kung saan ay karaniwang mas mahina. Ang pinakarason upang tukuyin ang file:// na prefix ay kung gusto mo ng isang malinis na kopya ng repositoryo na may mga reperensiya o mga object na naiwan — Sa pangkalahatan ay pagkatapos ng pag-import mula sa ibang VCS o sa isang bagay na katulad (tingnan Mga Panloob ng GIT para sa mga gawain ng pagpapanatili). Gagamitin natin ang normal na landas dito dahil ang paggawa nito ay halos parati na mas mabilis. Upang magdagdag ng isang lokal na repositoryo sa umiiral na proyekto sa Git, maaari kang magpagana ng ganito: $ git remote add local_proj /srv/git/project.git Pagkatapos, maaaring i-push papunta o i-pull mula sa remote na iyon sa pamamagitan ng paggamit ng iyong bagong remote na pangalan local_proj parang ginagawa mo sa isang network. Ang mga Kalamangan Ang mga kalamangan ng isang repositoryo na nakabatay sa file ay ang mga ito ay simple at ginagamit ang mga umiiral na mga pahintulot ng file at access sa network. Kapag ibinahagi mo na ang isang filesystem na kung saan may-access ang lahat ng iyong team, ang pag-set up ng isang repositoryo ay napakadali. Ilalagay mo ang kopya ng hubad na repositoryo sa kung saan may access ang lahat at i-set ang pagbasa/pagsulat na mga pahintulot katulad ng kahit anong ibinahagi na direktoryo. Tatalakayin natin kung papaano mag-export ng isang kopya ng hubad na repositoryo para sa itong layunin sa Pagkuha ng Git sa isang Server . Ito rin ay isang magandang opsyon para sa mabilis na pagkuha ng trabaho mula sa gumagana na repositoryo ng iba. Kapag ikaw at ang isang katrabaho ay nagtatrabaho sa isang proyekto at gusto nila na may kunin ka, ang pagpapagana ng isang utos tulad ng git pull /home/john/project ay kadalasan mas madali kaysa mag-push sila sa isang remote na server at pagkatapos ay kukunin mo. Ang mga Kahinaan Ang mga kahinaan ng paraan na ito ay ang mga ibinahagi na access ay sa pangkalahatan mas mahirap i-set up at maabot mula sa maramihang mga lokasyon kaysa sa pangunahing network access. Kapag gusto mong mag-push mula sa iyong laptop kapag ikaw ay nasa bahay, kailangan mong i-mount ang remote dist, na maaaring maging mahirap at mahina kumpara sa batay sa network na access. Mahalagang banggitin na hindi ito ang pinakamabilis na opsyon kung ikaw ay gumagamit ng isang uri ng ibinahagi na mount. Ang isang lokal na repositoryo ay mabilis lamang kapag ikaw ay may mabilis na access sa data. Ang repositoryo na nasa NFS ay madalas mas mahina kumpara sa repositoryo na nasa SSH sa parehong server, nagpapahintulot na ipagana ang Git gamit ang lokal na mga disk sa bawat sistema. Sa wakas, hindi pinoprotektahan ng protokol na ito ang repositoryo mula sa mga hindi sinasadya na mga aksidente. Ang bawat gumagamit ay may buong access ng shell sa “remote” na direktoryo, at walang pumipigil sa kanila sa pagbago o pagtanggal ng mga Git files sa loob at pag-corrupt sa repositoryo. Ang mga Protokol ng HTTP Ang Git ay maaaring makipag-usap sa HTTP gamit ang dalawang magkaibang mga mode. Bago ang Git 1.6.6, Mayroon lamang isang paraan upang maisagawa ito na kung saan ay madali at sa pangkalahatan ay read-only. Sa bersyon 1.6.6, isang bago, mas matalinong protokol ang ipinakilala na kasangkot ang Git na magagawang mas matalino na pag-usap ng paglipat ng data sa parehong paraan ng SSH. Sa mga nakaraang mga taon, itong bago na protokol ng HTTP ay naging popular dahil ito ay mas madali para sa gumagamit at mas matalino kung papaano nakikipag-usap. Ang mas bagong bersyon ay kadalasan mas tinutukoy bilang ang Smart HTTP na protokol at ang lumang paraan ay ang Dumb HTTP. Una natin tatalakayin ang mas bago na Smart HTTP protokol. Smart HTTP Ang Smart HTTP ay gumagana katulad ng mga protokol ng SSH o Git pero gumagana sa mga standard na port ng HTTPS at makakagamit ng iba’t ibang mekanismo ng pagpapatunay ng HTTP, ibig sabihin madalas na mas madali para sa gumagamit kaysa sa katulad ng SSH, dahil ikaw ang makakagamit ng mga bagay katulad ng pagpapatunay ng username/password kumpara sa pag-set up ng mga key ng SSH. Marahil ay ito ng ang pinaka-popular na pamamaraan sa paggamit sa Git, dahil ito ay maaaring i-set up upang parehong maghatid ng hindi nagpapakilala katulad ng protokol ng git:// , at maaaring i-push kasama ang pagpapatunay at encryption katulad ng protokol ng SSH. Sa halip ng pagkakaroon ng pag-set up ng iba’t ibang mga URL para sa mga ganitong bagay, maaaring gamitin ang isang URL para sa dalawa. Kapag susubukan mong mag-push at nangangailangan ng pag-awtentik ang repositoryo (na kung saan ito ay normal), Ang server ay maaaring mag prompt para sa isang username at password. Ito ay pareho para sa access sa pagbasa. Sa katunayan, para sa mga serbisyo katulad ng GitHub,Ang URL na ginagamit mo upang tingnan ang repositoryo online (halimbawa, https://github.com/schacon/simplegit ) ay parehong URL na maaari mong gamitin upang mag-clone at, kung ikaw ay may-access, mag-push. Dumb HTTP Kapag ang server ay hindi tumugon ng isang matalinong serbisyo ng Git HTTP, Susubukan ng kliyente ng Git na bumalik sa mas madaling Dumb HTTP na protokol. Inaasahan ng Dumb na protokol ang hubad na repositoryo ng Git ang ihahatid tulad ng mga normal na mga file mula sa web server. Ang kagandahan ng Dumb HTTP ay ang madaling pag set-up nito. Sa totoo lang, ang kailangan mo lang gawin ay maglagay ng hubad na repositoryo ng Git sa ilalim ng isang HTTP na dokumento sa root at mag-set up ng isang tiyak na post-update hook, at tapos ka na (Tingnan Mga Hook ng Git ). Sa puntong iyon, sinuman na makaka-access sa web server sa ilalim na kung saan maaaring ilagay ang repositoryo ay maaaring i-clone ang iyong repositoryo. Upang payagan ang access sa pagbasa sa iyong repositoryo sa HTTP, gumawa ng katulad nito: $ cd /var/www/htdocs/ $ git clone --bare /path/to/git_project gitproject.git $ cd gitproject.git $ mv hooks/post-update.sample hooks/post-update $ chmod a+x hooks/post-update Yun Lang. Ang post-update na hook na kasama ng Git bilang default ay ipinapagana ang tamang utos ( git update-server-info ) upang mapagana ng maayos ang HTTP fetching ang pag-kopya. Ang utos na ito ay pinapagana kapag nag-push ka sa repositoryo na ito (marahil sa SSH); pagktapos, maaaring mag-clone ang ibang tao gamit ang katulad $ git clone https://example.com/gitproject.git Sa partikular na kaso na ito, ginagamit natin ang /var/www/htdocs na landas na karaniwan sa mga Apache na setup, pero makikita mo na maaaring gumamit ng anumang statik na web server — ilagay lamang ang hubad na repositoryo sa kanyang landas. Ang data ng Git ay hinahatid bilang isang statik na mga file (tingnan ang Mga Panloob ng GIT na kabanata para sa mga detalye kung papaano ito eksaktong hinahatid). Sa pangkalahatan pipili ka kung magpapagana ng pabasa/pagsulat na Smart HTTP server o ilagay na ma-access ang mga file bilang read-only sa Dumb na paraan. Bihirang magpagana ng halo ng dalawang serbisyo. Ang mga Kalamangan Tayo ay magtuon sa mga kalamangan ng Smart na bersyon ng HTTP na protokol. Ang kasimplihan ng pagkakaroon ng isang URL para sa lahat ng klase ng access at pagkakaroon ng server na mag prompt lamang kapag kailangan ang pagpapatunay ay nagpapadali para sa mga end user. Ang kakayahan ng pag pagpapatunay gamit ang username at password ay isang malaking kalamangan sa SSH, dahil ang mga gumagamit ay hindi na kailangan lumikha sa lokal ng mga susi ng SSH at mag-upload ng kanilang pampubliko na susi sa server bago makikipag-ugnayan sa mga ito. Para sa mga hindi masyadong sopistikado na mga gumagamit, o mga gumagamit sa mga sistema kung saan hindi gaano karaniwan ang SSH, ito ay isang malaking kalamangan para sa kakayahang magamit. Ito rin ay isang napakabilis at mahusay na protokol, katulad ng SSH. Maaari mo ring pagsilbihan ang iyong mga repositoryo bilang read-only sa HTTPS, ibig sabihin maaari mong i-encrypt ang paglipat ng nilalaman; o maaari mong gawin na gumamit ng mga tiyak na napirmahan na mga sertipiko ng SSL ang mga kliyente. Isa pang magandang bagay ay ang HTTPS ay karaniwan na ginagamit na mga protokol na kung saan ang mga firewall ng mga korporasyon ay madalas na naka-set up para payagan ang trapiko sa mga port na ito. Ang mga Kahinaan Ang Git sa HTTPS ay maaaring maging mas nakakalito na i-set up kumpara sa SSH sa ibang mga server. Maliban dun, napakaliit ng kalamangan ang mayroon ang ibang mga protokol sa Smart HTTP para sa pagsilbi ng mga nilalaman ng Git. Kung ikaw ny gumagamit ng HTTP para sa pagpapatunay ng pag-push, paminsan ang pagbibigay ng iyong mga kredensyal ay mas mahirap kaysa gumamit ng mga susi sa SSH. Gayunpaman, may mga iilang mga instrumento sa pag-cache ng kridensyal na maaari mong gamitin, kasali na ang Keychain access sa macOS at Tagapamahala ng Kredensyal sa Windows, upang gawin itong madali. Basahin ang Kredensyal na ImbakanCredential Storage upang makita kung papaano mag set up ng ligtas na pag-cache ng password sa iyong sistema. Ang Protokol ng SSH Ang isang karaniwang protokol ng paglilipat para sa Git kapag ang pag boto sa sarili ay nasa SSH. Ito ay dahil ang access ng SSH sa mga server ay naka-set up na sa karamihan ng mga lugar — at kapag wala pa, ito ay madaling gawin. Ang SSH ay isang protokol ng isang network na may pagpapatunay din at, dahil ito ay saanman, ito ay karaniwang madali i-set up at gamitin. Upang i-clone ang isang repository ng Git sa SSH, maaari mong tukuyin ang isang ssh:// na URL tulad nito: To clone a Git repository over SSH, you can specify an ssh:// URL like this: $ git clone ssh://[user@]server/project.git O maari mong gamitin ang mas maikli na tulad ng scp na sintaks para sa protokol ng SSH: $ git clone [user@]server:project.git Sa dalawang kaso sa itaas, kapag hindi mo tukuyin ang opsyonal na username, ipinapagpapalagay ng Git na ang user na kasalukuyang naka-log in. Ang mga Kalamangan Marami ang kalamangan ng paggamit ng SSH. Una, Ang SSH ay relatibong madali i-set up — Ang mga SSH daemon ay karaniwan, maraming mga network admin ang may karanasan gamit sila, at maraming distribusyon ng OS naka-set up kasama nila or mayroong mga kasangkapan upang pamahalaan sila. Sunod, ang pag-access sa SSH ay ligtas — lahat ng paglipat ng datos ay naka-encrypt at napatunayan. Sa wakas, katulad ng HTTPS, Git at mga lokal na protokol, ang SSH ay mabilis, ginagawang siksik ang datos bago nililipat. Ang mga Kahinaan Ang negatibong aspeto ng SSH ay ito ay hindi sumusuporta ng hindi kilalang pag-acces sa iyong Git na repositoryo. Kung ikaw ay gumagamit ng SSH, ang mga tao ay dapat may access sa SSH sa iyong makina, kahit na read-only lang ang kapasidad, na hindi gumagawa sa SSH na nakakatulong sa mga open source na proyekto para sa mga tao na gusto lamang i-clone ang iyong repositoryo at suriin ito. Kapag ginagamit mo lamang sa loob ng network ng iyong korporasyon, Maaaring ang SSH na protokol lamang ang iyong kailangan harapin. Kapag gusto mong payagan ang mga hindi kilalang read-only na access sa iyong mga proyekto at gusto rin gamitin ang SSH, kailangan mong mag-set up ng SSH para ikaw ay makaka-push pero iba pa para sa iba na mag-fetch. Ang Protokol ng Git Ang sunod ay ang protokol ng Git. Ito ay isang espesyal na daemon na nakabalot sa Git, ito ay nakikinig sa isang dedikado na port (9418) na kung saan ay nagbibigay ng isang serbisyo tulad sa protokol ng SSH, pero walang pagpapatunay. Upang ang isang repositoryo ay magsilbi sa protokol ng Git, ikaw ay dapat lumikha ng isang git-daemon-export-ok na file — ang daemon ay hindi magsisilbi ng isang repositoryo kung walang file sa loob nito — pero maliban pa dun wala ng ibang seguridad. Ang alinman ang Git ng repositoryo ay magagamit ng lahat para i-clone, o hindi. Ibig sabihin karaniwang walang pag-push sa protokol na ito. Maaari mong paganahin ang access sa pag-push pero, dahil kulang ang pagpapatunay, sino man sa internet na mahahanap ang URL ng iyong proyekto ay maaaring mag-push sa proyektong iyon. Sapat na sabihin na ito ay bihira. Ang mga Kalamangan Ang protokol ng Git ay kadalasan ang pinakamabilis na protokol sa paglipat sa network na magagamit. Kung ikaw ay naghahatid ng maraming trapiko sa isang pampublikong proyekto o naghahatid ng malaking proyekto na hindi nangangailangan ng pagpapatunay ng user para sa read na access, Malamang gugustohin mong mag set up ng isang Git daemon upang pagsilbihan ang iyong proyekto. Ito ay gumagamit ng parehong data-transfer na mekanismo sa protokol ng SSH pero walang encryption at pagpapatunay sa itaas. Ang mga Kakulangan Ang problema sa protokol ng Git ay ang kakulangan ng pagpapatunay. Ito ay sa pangkalahatan ay hindi gusto para sa protokol ng Git na maging tanging access sa iyong proyekto. Sa pangkalahatan, ipapares mo sa access ng SSH o HTTPS para sa iilang mga developer na mayroong push (sulat) na access at payagan ang iba na gamitin ang git:// para sa read-only na access. Ito rin siguro ang pinaka mahirap na i-set up na protokol. Ito ay dapat magpatakbo ng sariling daemon, na nangangailangan ng xinetd na pagsasaayos o ang katulad nito, na kung saan ay hindi palagi madaling gawin. Ito ay nangangailangan din ng access sa firewall patungo sa port 9418, na kung saan ay hindi kinikilala na port ng mga firewall ng korporasyon na parating payagan. Sa likod ng mga firewall ng korporasyon, itong nakatago na port ay karaniwang naka-block prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://dev.to/pratyush_soni_853633e1553/huginn-a-discord-bot-for-my-valheim-server-felt-too-lazy-to-click-on-bash-script-so-made-a-42l8#main-content	𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Pratyush Soni Posted on May 26, 2025           𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 # linux # discord # programming # functional Why Valheim?(●'◡'●) It’s been a while — I’ve been playing the game Valheim quite often, and I keep falling deeper in love with its gameplay, graphics, and atmosphere. This is the kind of game that captivates you with its procedurally generated , vast world, pushing you to explore, face dangers, plan ahead, and ultimately — survive. It’s already incredibly fun in single-player, but guess what? It also supports multiplayer . You can play with friends using Steam’s built-in multiplayer, host your own server, or use a dedicated server hosting service. Being broke $ , having friends across different time zones 🌏︎, and needing flexibility meant I decided to host a dedicated server on my local machine . But here’s the thing — it was so annoying to manage the server. Not because it was resource-hungry or overly complicated — it was the repetitive process of running scripts and notifying everyone that the server was up (┬┬﹏┬┬)... My Solution to the Laziness of Clicking What I Was Too Lazy To Do Manually launching the server’s .sh script Notifying friends when the server was up Responding to friend requests to start the server Providing an easy way for people to check if the server was running All this made me feel a need of automation of all this task! Hence came up with a discord bot Huginn (‾◡◝). The Rise of the Bot! (/≧▽≦)/ The bot runs on pure Node.js , executing a series of bash commands triggered by simple in-text slash commands from Discord. Here’s what happens behind the scenes: I set the bot script to autostart on system boot along with Play.it Client (saves me from manual port forwarding). Once the bot is live, it has full control over the server's behavior — from start to shutdown. To top it off, I integrated RCON to remotely access in-game commands like: Saving the world manually Gracefully shutting down the server without corrupting the world file And many more intentionally locked to avoid "griefing". All handled through Discord, without ever touching the terminal by anyone and from anywhere ╰( °▽° )╯. low res demonstration of how things worked Source Code The Fall of the Bot¡ o(￣┰￣)ゞ In the beginning, everything went so smooth — almost perfectly. But the happiness didn’t last long. My faulty Wi-Fi card started acting up. Soon, my OS began freezing and crashing due to the hardware failure. I tried every fix I could find on the forums — and thanks to DeepSeek , it suggested a firmware update. So... I updated the firmware. Spoiler alert: it corrupted my input drivers . That was the final straw. The last string it pulled to bring my castle of patience crashing down. I removed Linux, rolled back to Windows (sadly), and that marked the end of the Huginn bot — at least for now. The Conclusion... In this weird adventure project, I learned a lot about: Node.js and its powerful package library Different tools to work around problems like manual port forwarding, as I didn't have admin access to the router settings The importance of good hardware for the functionality of systems Hosting and maintaining servers, and running automated scripts to make life easier But does it mean I will stop working on Huginn bot? I think I won't , as I already have ideas for Huginn bot V2 with features like: Server host rotation with a hosting toolkit to make setting up the environment easy on any computer Currency and mob level control for better player experience And many more... So folks, that's enough for today. I might drop updates for the new version — but I found this story worth sharing. ~ Thank you (^///^) Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Pratyush Soni Follow Aspiring Game & Graphics Programmer (•̀ᴗ•́)و Studying @ Amity Univ (¬‿¬) Learning C++, C#, OpenGL, Vulkan ＼(＾O＾)／ Passionate about real-time rendering & cool visuals! (ﾉ◕ヮ◕)ﾉ:･ﾟ✧ Joined May 26, 2025 Trending on DEV Community Hot I Debug Code Like I Debug Life (Spoiler: Both Throw Exceptions) # discuss # career # programming # beginners How Rube MCP Solves Context Overload When Using Hundreds of MCP Servers # mcp # productivity # programming # ai AI should not be in Code Editors # programming # ai # productivity # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account	2026-01-13T09:29:24
https://git-scm.com/book/be/v2/Git-on-the-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. Першыя крокі 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 4.7 Git on the 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. Малюнак 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 web 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 dnf , so you may want to try that first. We’ll walk through 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="/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/ 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:24
https://git-scm.com/book/bg/v2/%d0%9e%d1%81%d0%bd%d0%be%d0%b2%d0%b8-%d0%bd%d0%b0-Git-%d0%9f%d1%81%d0%b5%d0%b2%d0%b4%d0%be%d0%bd%d0%b8%d0%bc%d0%b8-%d0%b2-Git	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 За 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 2.7 Основи на Git - Псевдоними в Git Псевдоними в Git Преди да приключим с тази глава за основите на Git, има още една малка секция, която може да направи работата ви по-лесна и удобна: псевдонимите (aliases). По-късно в книгата няма да се обръщаме към тях или да считаме, че сте ги овладяли, но е хубаво да знаете как да ги ползвате. 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 commit , можете да напишете git ci . Колкото повече започнете да ползвате Git, толкова по-вероятно е да искате нещо подобно, така че - не се притеснявайте да си създавате нови псевдоними. Тази техника също така ви позволява да си създавате команда, която не съществува, а ви се иска да я имате под ръка. Например, за коригиране на не много удобния похват за де-индексиране на файл: $ git config --global alias.unstage 'reset HEAD --' Това ще направи следните две команди еквивалентни: $ 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:24
https://dev.to/pratyush_soni_853633e1553/huginn-a-discord-bot-for-my-valheim-server-felt-too-lazy-to-click-on-bash-script-so-made-a-42l8#heres-what-happens-behind-the-scenes	𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Pratyush Soni Posted on May 26, 2025           𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 # linux # discord # programming # functional Why Valheim?(●'◡'●) It’s been a while — I’ve been playing the game Valheim quite often, and I keep falling deeper in love with its gameplay, graphics, and atmosphere. This is the kind of game that captivates you with its procedurally generated , vast world, pushing you to explore, face dangers, plan ahead, and ultimately — survive. It’s already incredibly fun in single-player, but guess what? It also supports multiplayer . You can play with friends using Steam’s built-in multiplayer, host your own server, or use a dedicated server hosting service. Being broke $ , having friends across different time zones 🌏︎, and needing flexibility meant I decided to host a dedicated server on my local machine . But here’s the thing — it was so annoying to manage the server. Not because it was resource-hungry or overly complicated — it was the repetitive process of running scripts and notifying everyone that the server was up (┬┬﹏┬┬)... My Solution to the Laziness of Clicking What I Was Too Lazy To Do Manually launching the server’s .sh script Notifying friends when the server was up Responding to friend requests to start the server Providing an easy way for people to check if the server was running All this made me feel a need of automation of all this task! Hence came up with a discord bot Huginn (‾◡◝). The Rise of the Bot! (/≧▽≦)/ The bot runs on pure Node.js , executing a series of bash commands triggered by simple in-text slash commands from Discord. Here’s what happens behind the scenes: I set the bot script to autostart on system boot along with Play.it Client (saves me from manual port forwarding). Once the bot is live, it has full control over the server's behavior — from start to shutdown. To top it off, I integrated RCON to remotely access in-game commands like: Saving the world manually Gracefully shutting down the server without corrupting the world file And many more intentionally locked to avoid "griefing". All handled through Discord, without ever touching the terminal by anyone and from anywhere ╰( °▽° )╯. low res demonstration of how things worked Source Code The Fall of the Bot¡ o(￣┰￣)ゞ In the beginning, everything went so smooth — almost perfectly. But the happiness didn’t last long. My faulty Wi-Fi card started acting up. Soon, my OS began freezing and crashing due to the hardware failure. I tried every fix I could find on the forums — and thanks to DeepSeek , it suggested a firmware update. So... I updated the firmware. Spoiler alert: it corrupted my input drivers . That was the final straw. The last string it pulled to bring my castle of patience crashing down. I removed Linux, rolled back to Windows (sadly), and that marked the end of the Huginn bot — at least for now. The Conclusion... In this weird adventure project, I learned a lot about: Node.js and its powerful package library Different tools to work around problems like manual port forwarding, as I didn't have admin access to the router settings The importance of good hardware for the functionality of systems Hosting and maintaining servers, and running automated scripts to make life easier But does it mean I will stop working on Huginn bot? I think I won't , as I already have ideas for Huginn bot V2 with features like: Server host rotation with a hosting toolkit to make setting up the environment easy on any computer Currency and mob level control for better player experience And many more... So folks, that's enough for today. I might drop updates for the new version — but I found this story worth sharing. ~ Thank you (^///^) Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Pratyush Soni Follow Aspiring Game & Graphics Programmer (•̀ᴗ•́)و Studying @ Amity Univ (¬‿¬) Learning C++, C#, OpenGL, Vulkan ＼(＾O＾)／ Passionate about real-time rendering & cool visuals! (ﾉ◕ヮ◕)ﾉ:･ﾟ✧ Joined May 26, 2025 Trending on DEV Community Hot I Debug Code Like I Debug Life (Spoiler: Both Throw Exceptions) # discuss # career # programming # beginners How Rube MCP Solves Context Overload When Using Hundreds of MCP Servers # mcp # productivity # programming # ai AI should not be in Code Editors # programming # ai # productivity # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account	2026-01-13T09:29:24
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#param-keyword	Pinterest API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Pinterest API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Discover by Keywords Posts API Collect by URL Discover by Profile URL Discover by Keywords Social Media APIs Pinterest API Scrapers Copy page Copy page Overview The Pinterest API Suite offers multiple types of APIs, each designed for specific data collection needs from Pinterest. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Discover by Keywords. Interesting Columns : name , following_count , website , follower_count . Posts API This API allows users to collect multiple posts based on a single input. Discovery functionality : - Discover by profile URL. - Discover by Keywords. Interesting Columns : title , content , user_name , likes . Profiles API Collect by URL This API allows users to retrieve detailed Pinterest profile information using the provided profile URL. Input Parameters : URL string required The Pinterest profile URL. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metrics : following_count , follower_count , boards_num , saved . Additional Information : last_updated , posts_page_url , discovery_input . This API allows users to collect detailed insights into a Pinterest profile, including user statistics, engagement metrics, and profile information. Discover by Keywords This API allows users to discover Pinterest profiles based on a specified keyword. Input Parameters : keyword string required The keyword to search for profiles. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metric s: following_count , follower_count , boards_num , saved. Additional Information : last_updated , posts_page_url , discovery_input . This API enables users to find Pinterest profiles related to a specific keyword, offering insights into user statistics, engagement, and profile details. Posts API Collect by URL This API allows users to collect detailed post data from a specific Pinterest post using the provided post URL. Input Parameters : URL string required The Pinterest post URL. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , post_type . For all data points, click here . User Details : user_name , user_url , user_id , followers . Post Metrics : likes , comments_num , comments , categories . Media & Attachments : image_video_url , video_length , attached_files . Hashtags & Discovery : hashtags , discovery_input . This API allows users to retrieve detailed insights into a specific Pinterest post, including user engagement, post content, media, and other related information. Discover by Profile URL This API allows users to retrieve posts from a specific Pinterest profile based on the provided profile URL. Input Parameters : URL string required The Pinterest profile URL from which to collect posts. num_of_posts number The number of posts to collect. If omitted, there is no limit. posts_to_not_include array An array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date ). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date ). Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users tso collect posts from a specific Pinterest profile, allowing for filtering by date, exclusion of specific posts, and retrieval of detailed post data including media, comments, and engagement metrics. Discover by Keywords This API allows users to discover Pinterest posts based on a specific keyword, enabling efficient content discovery. Input Parameters : keyword string required The keyword to search for posts, such as “food” or any other relevant term. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users to search for Pinterest posts based on a specific keyword, providing detailed insights into the content, engagement, media, and associated metrics for efficient discovery. Was this page helpful? Yes No Twitter Quora ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:24
https://dev.to/pratyush_soni_853633e1553/huginn-a-discord-bot-for-my-valheim-server-felt-too-lazy-to-click-on-bash-script-so-made-a-42l8#the-conclusion	𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Pratyush Soni Posted on May 26, 2025           𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 # linux # discord # programming # functional Why Valheim?(●'◡'●) It’s been a while — I’ve been playing the game Valheim quite often, and I keep falling deeper in love with its gameplay, graphics, and atmosphere. This is the kind of game that captivates you with its procedurally generated , vast world, pushing you to explore, face dangers, plan ahead, and ultimately — survive. It’s already incredibly fun in single-player, but guess what? It also supports multiplayer . You can play with friends using Steam’s built-in multiplayer, host your own server, or use a dedicated server hosting service. Being broke $ , having friends across different time zones 🌏︎, and needing flexibility meant I decided to host a dedicated server on my local machine . But here’s the thing — it was so annoying to manage the server. Not because it was resource-hungry or overly complicated — it was the repetitive process of running scripts and notifying everyone that the server was up (┬┬﹏┬┬)... My Solution to the Laziness of Clicking What I Was Too Lazy To Do Manually launching the server’s .sh script Notifying friends when the server was up Responding to friend requests to start the server Providing an easy way for people to check if the server was running All this made me feel a need of automation of all this task! Hence came up with a discord bot Huginn (‾◡◝). The Rise of the Bot! (/≧▽≦)/ The bot runs on pure Node.js , executing a series of bash commands triggered by simple in-text slash commands from Discord. Here’s what happens behind the scenes: I set the bot script to autostart on system boot along with Play.it Client (saves me from manual port forwarding). Once the bot is live, it has full control over the server's behavior — from start to shutdown. To top it off, I integrated RCON to remotely access in-game commands like: Saving the world manually Gracefully shutting down the server without corrupting the world file And many more intentionally locked to avoid "griefing". All handled through Discord, without ever touching the terminal by anyone and from anywhere ╰( °▽° )╯. low res demonstration of how things worked Source Code The Fall of the Bot¡ o(￣┰￣)ゞ In the beginning, everything went so smooth — almost perfectly. But the happiness didn’t last long. My faulty Wi-Fi card started acting up. Soon, my OS began freezing and crashing due to the hardware failure. I tried every fix I could find on the forums — and thanks to DeepSeek , it suggested a firmware update. So... I updated the firmware. Spoiler alert: it corrupted my input drivers . That was the final straw. The last string it pulled to bring my castle of patience crashing down. I removed Linux, rolled back to Windows (sadly), and that marked the end of the Huginn bot — at least for now. The Conclusion... In this weird adventure project, I learned a lot about: Node.js and its powerful package library Different tools to work around problems like manual port forwarding, as I didn't have admin access to the router settings The importance of good hardware for the functionality of systems Hosting and maintaining servers, and running automated scripts to make life easier But does it mean I will stop working on Huginn bot? I think I won't , as I already have ideas for Huginn bot V2 with features like: Server host rotation with a hosting toolkit to make setting up the environment easy on any computer Currency and mob level control for better player experience And many more... So folks, that's enough for today. I might drop updates for the new version — but I found this story worth sharing. ~ Thank you (^///^) Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Pratyush Soni Follow Aspiring Game & Graphics Programmer (•̀ᴗ•́)و Studying @ Amity Univ (¬‿¬) Learning C++, C#, OpenGL, Vulkan ＼(＾O＾)／ Passionate about real-time rendering & cool visuals! (ﾉ◕ヮ◕)ﾉ:･ﾟ✧ Joined May 26, 2025 Trending on DEV Community Hot I Debug Code Like I Debug Life (Spoiler: Both Throw Exceptions) # discuss # career # programming # beginners How Rube MCP Solves Context Overload When Using Hundreds of MCP Servers # mcp # productivity # programming # ai AI should not be in Code Editors # programming # ai # productivity # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account	2026-01-13T09:29:24
https://dev.to/pratyush_soni_853633e1553/huginn-a-discord-bot-for-my-valheim-server-felt-too-lazy-to-click-on-bash-script-so-made-a-42l8#the-rise-of-the-bot-%E2%89%A7%E2%96%BD%E2%89%A6	𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Pratyush Soni Posted on May 26, 2025           𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 # linux # discord # programming # functional Why Valheim?(●'◡'●) It’s been a while — I’ve been playing the game Valheim quite often, and I keep falling deeper in love with its gameplay, graphics, and atmosphere. This is the kind of game that captivates you with its procedurally generated , vast world, pushing you to explore, face dangers, plan ahead, and ultimately — survive. It’s already incredibly fun in single-player, but guess what? It also supports multiplayer . You can play with friends using Steam’s built-in multiplayer, host your own server, or use a dedicated server hosting service. Being broke $ , having friends across different time zones 🌏︎, and needing flexibility meant I decided to host a dedicated server on my local machine . But here’s the thing — it was so annoying to manage the server. Not because it was resource-hungry or overly complicated — it was the repetitive process of running scripts and notifying everyone that the server was up (┬┬﹏┬┬)... My Solution to the Laziness of Clicking What I Was Too Lazy To Do Manually launching the server’s .sh script Notifying friends when the server was up Responding to friend requests to start the server Providing an easy way for people to check if the server was running All this made me feel a need of automation of all this task! Hence came up with a discord bot Huginn (‾◡◝). The Rise of the Bot! (/≧▽≦)/ The bot runs on pure Node.js , executing a series of bash commands triggered by simple in-text slash commands from Discord. Here’s what happens behind the scenes: I set the bot script to autostart on system boot along with Play.it Client (saves me from manual port forwarding). Once the bot is live, it has full control over the server's behavior — from start to shutdown. To top it off, I integrated RCON to remotely access in-game commands like: Saving the world manually Gracefully shutting down the server without corrupting the world file And many more intentionally locked to avoid "griefing". All handled through Discord, without ever touching the terminal by anyone and from anywhere ╰( °▽° )╯. low res demonstration of how things worked Source Code The Fall of the Bot¡ o(￣┰￣)ゞ In the beginning, everything went so smooth — almost perfectly. But the happiness didn’t last long. My faulty Wi-Fi card started acting up. Soon, my OS began freezing and crashing due to the hardware failure. I tried every fix I could find on the forums — and thanks to DeepSeek , it suggested a firmware update. So... I updated the firmware. Spoiler alert: it corrupted my input drivers . That was the final straw. The last string it pulled to bring my castle of patience crashing down. I removed Linux, rolled back to Windows (sadly), and that marked the end of the Huginn bot — at least for now. The Conclusion... In this weird adventure project, I learned a lot about: Node.js and its powerful package library Different tools to work around problems like manual port forwarding, as I didn't have admin access to the router settings The importance of good hardware for the functionality of systems Hosting and maintaining servers, and running automated scripts to make life easier But does it mean I will stop working on Huginn bot? I think I won't , as I already have ideas for Huginn bot V2 with features like: Server host rotation with a hosting toolkit to make setting up the environment easy on any computer Currency and mob level control for better player experience And many more... So folks, that's enough for today. I might drop updates for the new version — but I found this story worth sharing. ~ Thank you (^///^) Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Pratyush Soni Follow Aspiring Game & Graphics Programmer (•̀ᴗ•́)و Studying @ Amity Univ (¬‿¬) Learning C++, C#, OpenGL, Vulkan ＼(＾O＾)／ Passionate about real-time rendering & cool visuals! (ﾉ◕ヮ◕)ﾉ:･ﾟ✧ Joined May 26, 2025 Trending on DEV Community Hot I Debug Code Like I Debug Life (Spoiler: Both Throw Exceptions) # discuss # career # programming # beginners How Rube MCP Solves Context Overload When Using Hundreds of MCP Servers # mcp # productivity # programming # ai AI should not be in Code Editors # programming # ai # productivity # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account	2026-01-13T09:29:24
https://git-scm.com/book/es/v2/Inicio---Sobre-el-Control-de-Versiones-La-L%c3%adnea-de-Comandos	Git - La Línea de Comandos 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. Inicio - Sobre el Control de Versiones 1.1 Acerca del Control de Versiones 1.2 Una breve historia de Git 1.3 Fundamentos de Git 1.4 La Línea de Comandos 1.5 Instalación de Git 1.6 Configurando Git por primera vez 1.7 ¿Cómo obtener ayuda? 1.8 Resumen 2. Fundamentos de Git 2.1 Obteniendo un repositorio Git 2.2 Guardando cambios en el Repositorio 2.3 Ver el Historial de Confirmaciones 2.4 Deshacer Cosas 2.5 Trabajar con Remotos 2.6 Etiquetado 2.7 Alias de Git 2.8 Resumen 3. Ramificaciones en Git 3.1 ¿Qué es una rama? 3.2 Procedimientos Básicos para Ramificar y Fusionar 3.3 Gestión de Ramas 3.4 Flujos de Trabajo Ramificados 3.5 Ramas Remotas 3.6 Reorganizar el Trabajo Realizado 3.7 Recapitulación 4. Git en el Servidor 4.1 Los Protocolos 4.2 Configurando Git en un servidor 4.3 Generando tu clave pública SSH 4.4 Configurando el servidor 4.5 El demonio Git 4.6 HTTP Inteligente 4.7 GitWeb 4.8 GitLab 4.9 Git en un alojamiento externo 4.10 Resumen 5. Git en entornos distribuidos 5.1 Flujos de trabajo distribuidos 5.2 Contribuyendo a un Proyecto 5.3 Manteniendo un proyecto 5.4 Resumen 6. GitHub 6.1 Creación y configuración de la cuenta 6.2 Participando en Proyectos 6.3 Mantenimiento de un proyecto 6.4 Gestión de una organización 6.5 Scripting en GitHub 6.6 Resumen 7. Herramientas de Git 7.1 Revisión por selección 7.2 Organización interactiva 7.3 Guardado rápido y Limpieza 7.4 Firmando tu trabajo 7.5 Buscando 7.6 Reescribiendo la Historia 7.7 Reiniciar Desmitificado 7.8 Fusión Avanzada 7.9 Rerere 7.10 Haciendo debug con Git 7.11 Submódulos 7.12 Agrupaciones 7.13 Replace 7.14 Almacenamiento de credenciales 7.15 Resumen 8. Personalización de Git 8.1 Configuración de Git 8.2 Git Attributes 8.3 Puntos de enganche en Git 8.4 Un ejemplo de implantación de una determinada política en Git 8.5 Recapitulación 9. Git y Otros Sistemas 9.1 Git como Cliente 9.2 Migración a Git 9.3 Resumen 10. Los entresijos internos de Git 10.1 Fontanería y porcelana 10.2 Los objetos Git 10.3 Referencias Git 10.4 Archivos empaquetadores 10.5 Las especificaciones para hacer referencia a… (refspec) 10.6 Protocolos de transferencia 10.7 Mantenimiento y recuperación de datos 10.8 Variables de entorno 10.9 Recapitulación A1. Apéndice A: Git en otros entornos A1.1 Interfaces gráficas A1.2 Git en Visual Studio A1.3 Git en Eclipse A1.4 Git con Bash A1.5 Git en Zsh A1.6 Git en Powershell A1.7 Resumen A2. Apéndice B: Integrando Git en tus Aplicaciones A2.1 Git mediante Línea de Comandos A2.2 Libgit2 A2.3 JGit A3. Apéndice C: Comandos de Git A3.1 Configuración A3.2 Obtener y Crear Proyectos A3.3 Seguimiento Básico A3.4 Ramificar y Fusionar A3.5 Compartir y Actualizar Proyectos A3.6 Inspección y Comparación A3.7 Depuración A3.8 Parcheo A3.9 Correo Electrónico A3.10 Sistemas Externos A3.11 Administración A3.12 Comandos de Fontanería 2nd Edition 1.4 Inicio - Sobre el Control de Versiones - La Línea de Comandos La Línea de Comandos Existen muchas formas de usar Git. Por un lado tenemos las herramientas originales de línea de comandos, y por otro lado tenemos una gran variedad de interfaces de usuario con distintas capacidades. En este libro vamos a utilizar Git desde la línea de comandos. La línea de comandos es el único lugar en donde puedes ejecutar todos los comandos de Git - la mayoría de interfaces gráficas de usuario solo implementan una parte de las características de Git por motivos de simplicidad. Si tú sabes cómo realizar algo desde la línea de comandos, seguramente serás capaz de averiguar cómo hacer lo mismo desde una interfaz gráfica. Sin embargo, la relación opuesta no es necesariamente cierta. Así mismo, la decisión de qué cliente gráfico utilizar depende totalmente de tu gusto, pero todos los usuarios tendrán las herramientas de línea de comandos instaladas y disponibles. Nosotros esperamos que sepas cómo abrir el Terminal en Mac, o el "Command Prompt" o "Powershell" en Windows. Si no entiendes de lo que estamos hablando aquí, te recomendamos que hagas una pausa para investigar acerca de esto, de tal forma que puedas entender el resto de las explicaciones y descripciones que siguen en este libro. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://dev.to/pratyush_soni_853633e1553/huginn-a-discord-bot-for-my-valheim-server-felt-too-lazy-to-click-on-bash-script-so-made-a-42l8#why-valheim%E2%97%8F%E2%97%A1%E2%97%8F	𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Pratyush Soni Posted on May 26, 2025           𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 # linux # discord # programming # functional Why Valheim?(●'◡'●) It’s been a while — I’ve been playing the game Valheim quite often, and I keep falling deeper in love with its gameplay, graphics, and atmosphere. This is the kind of game that captivates you with its procedurally generated , vast world, pushing you to explore, face dangers, plan ahead, and ultimately — survive. It’s already incredibly fun in single-player, but guess what? It also supports multiplayer . You can play with friends using Steam’s built-in multiplayer, host your own server, or use a dedicated server hosting service. Being broke $ , having friends across different time zones 🌏︎, and needing flexibility meant I decided to host a dedicated server on my local machine . But here’s the thing — it was so annoying to manage the server. Not because it was resource-hungry or overly complicated — it was the repetitive process of running scripts and notifying everyone that the server was up (┬┬﹏┬┬)... My Solution to the Laziness of Clicking What I Was Too Lazy To Do Manually launching the server’s .sh script Notifying friends when the server was up Responding to friend requests to start the server Providing an easy way for people to check if the server was running All this made me feel a need of automation of all this task! Hence came up with a discord bot Huginn (‾◡◝). The Rise of the Bot! (/≧▽≦)/ The bot runs on pure Node.js , executing a series of bash commands triggered by simple in-text slash commands from Discord. Here’s what happens behind the scenes: I set the bot script to autostart on system boot along with Play.it Client (saves me from manual port forwarding). Once the bot is live, it has full control over the server's behavior — from start to shutdown. To top it off, I integrated RCON to remotely access in-game commands like: Saving the world manually Gracefully shutting down the server without corrupting the world file And many more intentionally locked to avoid "griefing". All handled through Discord, without ever touching the terminal by anyone and from anywhere ╰( °▽° )╯. low res demonstration of how things worked Source Code The Fall of the Bot¡ o(￣┰￣)ゞ In the beginning, everything went so smooth — almost perfectly. But the happiness didn’t last long. My faulty Wi-Fi card started acting up. Soon, my OS began freezing and crashing due to the hardware failure. I tried every fix I could find on the forums — and thanks to DeepSeek , it suggested a firmware update. So... I updated the firmware. Spoiler alert: it corrupted my input drivers . That was the final straw. The last string it pulled to bring my castle of patience crashing down. I removed Linux, rolled back to Windows (sadly), and that marked the end of the Huginn bot — at least for now. The Conclusion... In this weird adventure project, I learned a lot about: Node.js and its powerful package library Different tools to work around problems like manual port forwarding, as I didn't have admin access to the router settings The importance of good hardware for the functionality of systems Hosting and maintaining servers, and running automated scripts to make life easier But does it mean I will stop working on Huginn bot? I think I won't , as I already have ideas for Huginn bot V2 with features like: Server host rotation with a hosting toolkit to make setting up the environment easy on any computer Currency and mob level control for better player experience And many more... So folks, that's enough for today. I might drop updates for the new version — but I found this story worth sharing. ~ Thank you (^///^) Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Pratyush Soni Follow Aspiring Game & Graphics Programmer (•̀ᴗ•́)و Studying @ Amity Univ (¬‿¬) Learning C++, C#, OpenGL, Vulkan ＼(＾O＾)／ Passionate about real-time rendering & cool visuals! (ﾉ◕ヮ◕)ﾉ:･ﾟ✧ Joined May 26, 2025 Trending on DEV Community Hot I Debug Code Like I Debug Life (Spoiler: Both Throw Exceptions) # discuss # career # programming # beginners How Rube MCP Solves Context Overload When Using Hundreds of MCP Servers # mcp # productivity # programming # ai AI should not be in Code Editors # programming # ai # productivity # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account	2026-01-13T09:29:24
https://dev.to/pratyush_soni_853633e1553/huginn-a-discord-bot-for-my-valheim-server-felt-too-lazy-to-click-on-bash-script-so-made-a-42l8#the-fall-of-the-bot-o%EF%BF%A3%E2%94%B0%EF%BF%A3%E3%82%9E	𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Pratyush Soni Posted on May 26, 2025           𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 # linux # discord # programming # functional Why Valheim?(●'◡'●) It’s been a while — I’ve been playing the game Valheim quite often, and I keep falling deeper in love with its gameplay, graphics, and atmosphere. This is the kind of game that captivates you with its procedurally generated , vast world, pushing you to explore, face dangers, plan ahead, and ultimately — survive. It’s already incredibly fun in single-player, but guess what? It also supports multiplayer . You can play with friends using Steam’s built-in multiplayer, host your own server, or use a dedicated server hosting service. Being broke $ , having friends across different time zones 🌏︎, and needing flexibility meant I decided to host a dedicated server on my local machine . But here’s the thing — it was so annoying to manage the server. Not because it was resource-hungry or overly complicated — it was the repetitive process of running scripts and notifying everyone that the server was up (┬┬﹏┬┬)... My Solution to the Laziness of Clicking What I Was Too Lazy To Do Manually launching the server’s .sh script Notifying friends when the server was up Responding to friend requests to start the server Providing an easy way for people to check if the server was running All this made me feel a need of automation of all this task! Hence came up with a discord bot Huginn (‾◡◝). The Rise of the Bot! (/≧▽≦)/ The bot runs on pure Node.js , executing a series of bash commands triggered by simple in-text slash commands from Discord. Here’s what happens behind the scenes: I set the bot script to autostart on system boot along with Play.it Client (saves me from manual port forwarding). Once the bot is live, it has full control over the server's behavior — from start to shutdown. To top it off, I integrated RCON to remotely access in-game commands like: Saving the world manually Gracefully shutting down the server without corrupting the world file And many more intentionally locked to avoid "griefing". All handled through Discord, without ever touching the terminal by anyone and from anywhere ╰( °▽° )╯. low res demonstration of how things worked Source Code The Fall of the Bot¡ o(￣┰￣)ゞ In the beginning, everything went so smooth — almost perfectly. But the happiness didn’t last long. My faulty Wi-Fi card started acting up. Soon, my OS began freezing and crashing due to the hardware failure. I tried every fix I could find on the forums — and thanks to DeepSeek , it suggested a firmware update. So... I updated the firmware. Spoiler alert: it corrupted my input drivers . That was the final straw. The last string it pulled to bring my castle of patience crashing down. I removed Linux, rolled back to Windows (sadly), and that marked the end of the Huginn bot — at least for now. The Conclusion... In this weird adventure project, I learned a lot about: Node.js and its powerful package library Different tools to work around problems like manual port forwarding, as I didn't have admin access to the router settings The importance of good hardware for the functionality of systems Hosting and maintaining servers, and running automated scripts to make life easier But does it mean I will stop working on Huginn bot? I think I won't , as I already have ideas for Huginn bot V2 with features like: Server host rotation with a hosting toolkit to make setting up the environment easy on any computer Currency and mob level control for better player experience And many more... So folks, that's enough for today. I might drop updates for the new version — but I found this story worth sharing. ~ Thank you (^///^) Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Pratyush Soni Follow Aspiring Game & Graphics Programmer (•̀ᴗ•́)و Studying @ Amity Univ (¬‿¬) Learning C++, C#, OpenGL, Vulkan ＼(＾O＾)／ Passionate about real-time rendering & cool visuals! (ﾉ◕ヮ◕)ﾉ:･ﾟ✧ Joined May 26, 2025 Trending on DEV Community Hot I Debug Code Like I Debug Life (Spoiler: Both Throw Exceptions) # discuss # career # programming # beginners How Rube MCP Solves Context Overload When Using Hundreds of MCP Servers # mcp # productivity # programming # ai AI should not be in Code Editors # programming # ai # productivity # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account	2026-01-13T09:29:24
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#param-num-of-posts	Pinterest API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Pinterest API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Discover by Keywords Posts API Collect by URL Discover by Profile URL Discover by Keywords Social Media APIs Pinterest API Scrapers Copy page Copy page Overview The Pinterest API Suite offers multiple types of APIs, each designed for specific data collection needs from Pinterest. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Discover by Keywords. Interesting Columns : name , following_count , website , follower_count . Posts API This API allows users to collect multiple posts based on a single input. Discovery functionality : - Discover by profile URL. - Discover by Keywords. Interesting Columns : title , content , user_name , likes . Profiles API Collect by URL This API allows users to retrieve detailed Pinterest profile information using the provided profile URL. Input Parameters : URL string required The Pinterest profile URL. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metrics : following_count , follower_count , boards_num , saved . Additional Information : last_updated , posts_page_url , discovery_input . This API allows users to collect detailed insights into a Pinterest profile, including user statistics, engagement metrics, and profile information. Discover by Keywords This API allows users to discover Pinterest profiles based on a specified keyword. Input Parameters : keyword string required The keyword to search for profiles. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metric s: following_count , follower_count , boards_num , saved. Additional Information : last_updated , posts_page_url , discovery_input . This API enables users to find Pinterest profiles related to a specific keyword, offering insights into user statistics, engagement, and profile details. Posts API Collect by URL This API allows users to collect detailed post data from a specific Pinterest post using the provided post URL. Input Parameters : URL string required The Pinterest post URL. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , post_type . For all data points, click here . User Details : user_name , user_url , user_id , followers . Post Metrics : likes , comments_num , comments , categories . Media & Attachments : image_video_url , video_length , attached_files . Hashtags & Discovery : hashtags , discovery_input . This API allows users to retrieve detailed insights into a specific Pinterest post, including user engagement, post content, media, and other related information. Discover by Profile URL This API allows users to retrieve posts from a specific Pinterest profile based on the provided profile URL. Input Parameters : URL string required The Pinterest profile URL from which to collect posts. num_of_posts number The number of posts to collect. If omitted, there is no limit. posts_to_not_include array An array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date ). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date ). Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users tso collect posts from a specific Pinterest profile, allowing for filtering by date, exclusion of specific posts, and retrieval of detailed post data including media, comments, and engagement metrics. Discover by Keywords This API allows users to discover Pinterest posts based on a specific keyword, enabling efficient content discovery. Input Parameters : keyword string required The keyword to search for posts, such as “food” or any other relevant term. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users to search for Pinterest posts based on a specific keyword, providing detailed insights into the content, engagement, media, and associated metrics for efficient discovery. Was this page helpful? Yes No Twitter Quora ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:24
https://git-scm.com/book/pt-br/v2/Git-no-servidor-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. Começando 1.1 Sobre Controle de Versão 1.2 Uma Breve História do Git 1.3 O Básico do Git 1.4 A Linha de Comando 1.5 Instalando o Git 1.6 Configuração Inicial do Git 1.7 Pedindo Ajuda 1.8 Sumário 2. Fundamentos de Git 2.1 Obtendo um Repositório Git 2.2 Gravando Alterações em Seu Repositório 2.3 Vendo o histórico de Commits 2.4 Desfazendo coisas 2.5 Trabalhando de Forma Remota 2.6 Criando Tags 2.7 Apelidos Git 2.8 Sumário 3. Branches no Git 3.1 Branches em poucas palavras 3.2 O básico de Ramificação (Branch) e Mesclagem (Merge) 3.3 Gestão de Branches 3.4 Fluxo de Branches 3.5 Branches remotos 3.6 Rebase 3.7 Sumário 4. Git no servidor 4.1 Os Protocolos 4.2 Getting Git on a Server 4.3 Gerando Sua Chave Pública SSH 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 Sumário 5. Distributed Git 5.1 Fluxos de Trabalho Distribuídos 5.2 Contribuindo com um Projeto 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Configurando uma conta 6.2 Contribuindo em um projeto 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. Funcionamento Interno do Git 10.1 Encanamento e Porcelana 10.2 Objetos do Git 10.3 Referências do Git 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Variáveis de ambiente 10.9 Sumário A1. Appendix A: Git em Outros Ambientes 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 Resumo 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 no servidor - 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 through 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="/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/ 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:24
https://git-scm.com/book/tl/v2/Distributed-Git-Summary	Git - Summary 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 5.4 Distributed Git - Summary Summary You should feel fairly comfortable contributing to a project in Git as well as maintaining your own project or integrating other users' contributions. Congratulations on being an effective Git developer! In the next chapter, you’ll learn about how to use the largest and most popular Git hosting service, GitHub. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
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-%d8%ae%d9%84%d8%a7%d8%b5%d9%87-Summary	Git - خلاصه (Summary) 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.10 گیت روی سرور (Git on the server) - خلاصه (Summary) خلاصه (Summary) شما چندین گزینه برای راه‌اندازی و به کار انداختن یک مخزن ریموت گیت دارید تا با دیگران همکاری کنید یا کارتان را به اشتراک بگذارید. راه‌اندازی سرور شخصی خودتان دسترسی‌ها و کنترل‌های زیادی به شما می‌دهد و به شما اجازه می‌دهد تا سرور را در فایروال خودتان اجرا کنید، امامعمولاً راه‌اندازی و نگه‌داری چنین سروری نیازمند سهم زیادی از وقت شماست. اگر داده‌های خود را بر روی یک سرور میزبانی شده قرار دهید، راه‌اندازی و نگه‌داری آن آسان خواهد بود؛ با این حال شما باید قادر باشید تا کد خود را بر روی سرورهای شخص دیگری نگه‌داری کنید و بعضی از سازمان‌ها این اجازه را نمی‌دهند. تعیین این که چه راه‌حل یا ترکیبی از راه‌حل‌ها مناسب شما و سازمان شما است باید نسبتاً ساده باشد. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://dev.to/pratyush_soni_853633e1553/huginn-a-discord-bot-for-my-valheim-server-felt-too-lazy-to-click-on-bash-script-so-made-a-42l8#my-solution-to-the-laziness-of-clicking	𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Pratyush Soni Posted on May 26, 2025           𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 # linux # discord # programming # functional Why Valheim?(●'◡'●) It’s been a while — I’ve been playing the game Valheim quite often, and I keep falling deeper in love with its gameplay, graphics, and atmosphere. This is the kind of game that captivates you with its procedurally generated , vast world, pushing you to explore, face dangers, plan ahead, and ultimately — survive. It’s already incredibly fun in single-player, but guess what? It also supports multiplayer . You can play with friends using Steam’s built-in multiplayer, host your own server, or use a dedicated server hosting service. Being broke $ , having friends across different time zones 🌏︎, and needing flexibility meant I decided to host a dedicated server on my local machine . But here’s the thing — it was so annoying to manage the server. Not because it was resource-hungry or overly complicated — it was the repetitive process of running scripts and notifying everyone that the server was up (┬┬﹏┬┬)... My Solution to the Laziness of Clicking What I Was Too Lazy To Do Manually launching the server’s .sh script Notifying friends when the server was up Responding to friend requests to start the server Providing an easy way for people to check if the server was running All this made me feel a need of automation of all this task! Hence came up with a discord bot Huginn (‾◡◝). The Rise of the Bot! (/≧▽≦)/ The bot runs on pure Node.js , executing a series of bash commands triggered by simple in-text slash commands from Discord. Here’s what happens behind the scenes: I set the bot script to autostart on system boot along with Play.it Client (saves me from manual port forwarding). Once the bot is live, it has full control over the server's behavior — from start to shutdown. To top it off, I integrated RCON to remotely access in-game commands like: Saving the world manually Gracefully shutting down the server without corrupting the world file And many more intentionally locked to avoid "griefing". All handled through Discord, without ever touching the terminal by anyone and from anywhere ╰( °▽° )╯. low res demonstration of how things worked Source Code The Fall of the Bot¡ o(￣┰￣)ゞ In the beginning, everything went so smooth — almost perfectly. But the happiness didn’t last long. My faulty Wi-Fi card started acting up. Soon, my OS began freezing and crashing due to the hardware failure. I tried every fix I could find on the forums — and thanks to DeepSeek , it suggested a firmware update. So... I updated the firmware. Spoiler alert: it corrupted my input drivers . That was the final straw. The last string it pulled to bring my castle of patience crashing down. I removed Linux, rolled back to Windows (sadly), and that marked the end of the Huginn bot — at least for now. The Conclusion... In this weird adventure project, I learned a lot about: Node.js and its powerful package library Different tools to work around problems like manual port forwarding, as I didn't have admin access to the router settings The importance of good hardware for the functionality of systems Hosting and maintaining servers, and running automated scripts to make life easier But does it mean I will stop working on Huginn bot? I think I won't , as I already have ideas for Huginn bot V2 with features like: Server host rotation with a hosting toolkit to make setting up the environment easy on any computer Currency and mob level control for better player experience And many more... So folks, that's enough for today. I might drop updates for the new version — but I found this story worth sharing. ~ Thank you (^///^) Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Pratyush Soni Follow Aspiring Game & Graphics Programmer (•̀ᴗ•́)و Studying @ Amity Univ (¬‿¬) Learning C++, C#, OpenGL, Vulkan ＼(＾O＾)／ Passionate about real-time rendering & cool visuals! (ﾉ◕ヮ◕)ﾉ:･ﾟ✧ Joined May 26, 2025 Trending on DEV Community Hot I Debug Code Like I Debug Life (Spoiler: Both Throw Exceptions) # discuss # career # programming # beginners How Rube MCP Solves Context Overload When Using Hundreds of MCP Servers # mcp # productivity # programming # ai AI should not be in Code Editors # programming # ai # productivity # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account	2026-01-13T09:29:24
https://dev.to/pratyush_soni_853633e1553/huginn-a-discord-bot-for-my-valheim-server-felt-too-lazy-to-click-on-bash-script-so-made-a-42l8#what-i-was-too-lazy-to-do	𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 - DEV Community Forem Feed Follow new Subforems to improve your feed DEV Community Follow A space to discuss and keep up software development and manage your software career Future Follow News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more. Open Forem Follow A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here Gamers Forem Follow An inclusive community for gaming enthusiasts Music Forem Follow From composing and gigging to gear, hot music takes, and everything in between. Vibe Coding Forem Follow Discussing AI software development, and showing off what we're building. Popcorn Movies and TV Follow Movie and TV enthusiasm, criticism and everything in-between. DUMB DEV Community Follow Memes and software development shitposting Design Community Follow Web design, graphic design and everything in-between Security Forem Follow Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike Golf Forem Follow A community of golfers and golfing enthusiasts Crypto Forem Follow A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis. Parenting Follow A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other. Forem Core Follow Discussing the core forem open source software project — features, bugs, performance, self-hosting. Maker Forem Follow A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more. HMPL.js Forem Follow For developers using HMPL.js to build fast, lightweight web apps. A space to share projects, ask questions, and discuss server-driven templating Dropdown menu Dropdown menu Skip to content Navigation menu Search Powered by Algolia Search Log in Create account DEV Community Close Add reaction Like Unicorn Exploding Head Raised Hands Fire Jump to Comments Save Boost More... Copy link Copy link Copied to Clipboard Share to X Share to LinkedIn Share to Facebook Share to Mastodon Share Post via... Report Abuse Pratyush Soni Posted on May 26, 2025           𓅪 Huginn: A Discord Bot for My Valheim Server ~ felt too lazy to click on bash script — so made a bot ;3 # linux # discord # programming # functional Why Valheim?(●'◡'●) It’s been a while — I’ve been playing the game Valheim quite often, and I keep falling deeper in love with its gameplay, graphics, and atmosphere. This is the kind of game that captivates you with its procedurally generated , vast world, pushing you to explore, face dangers, plan ahead, and ultimately — survive. It’s already incredibly fun in single-player, but guess what? It also supports multiplayer . You can play with friends using Steam’s built-in multiplayer, host your own server, or use a dedicated server hosting service. Being broke $ , having friends across different time zones 🌏︎, and needing flexibility meant I decided to host a dedicated server on my local machine . But here’s the thing — it was so annoying to manage the server. Not because it was resource-hungry or overly complicated — it was the repetitive process of running scripts and notifying everyone that the server was up (┬┬﹏┬┬)... My Solution to the Laziness of Clicking What I Was Too Lazy To Do Manually launching the server’s .sh script Notifying friends when the server was up Responding to friend requests to start the server Providing an easy way for people to check if the server was running All this made me feel a need of automation of all this task! Hence came up with a discord bot Huginn (‾◡◝). The Rise of the Bot! (/≧▽≦)/ The bot runs on pure Node.js , executing a series of bash commands triggered by simple in-text slash commands from Discord. Here’s what happens behind the scenes: I set the bot script to autostart on system boot along with Play.it Client (saves me from manual port forwarding). Once the bot is live, it has full control over the server's behavior — from start to shutdown. To top it off, I integrated RCON to remotely access in-game commands like: Saving the world manually Gracefully shutting down the server without corrupting the world file And many more intentionally locked to avoid "griefing". All handled through Discord, without ever touching the terminal by anyone and from anywhere ╰( °▽° )╯. low res demonstration of how things worked Source Code The Fall of the Bot¡ o(￣┰￣)ゞ In the beginning, everything went so smooth — almost perfectly. But the happiness didn’t last long. My faulty Wi-Fi card started acting up. Soon, my OS began freezing and crashing due to the hardware failure. I tried every fix I could find on the forums — and thanks to DeepSeek , it suggested a firmware update. So... I updated the firmware. Spoiler alert: it corrupted my input drivers . That was the final straw. The last string it pulled to bring my castle of patience crashing down. I removed Linux, rolled back to Windows (sadly), and that marked the end of the Huginn bot — at least for now. The Conclusion... In this weird adventure project, I learned a lot about: Node.js and its powerful package library Different tools to work around problems like manual port forwarding, as I didn't have admin access to the router settings The importance of good hardware for the functionality of systems Hosting and maintaining servers, and running automated scripts to make life easier But does it mean I will stop working on Huginn bot? I think I won't , as I already have ideas for Huginn bot V2 with features like: Server host rotation with a hosting toolkit to make setting up the environment easy on any computer Currency and mob level control for better player experience And many more... So folks, that's enough for today. I might drop updates for the new version — but I found this story worth sharing. ~ Thank you (^///^) Top comments (0) Subscribe Personal Trusted User Create template Templates let you quickly answer FAQs or store snippets for re-use. Submit Preview Dismiss Code of Conduct • Report abuse Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink . Hide child comments as well Confirm For further actions, you may consider blocking this person and/or reporting abuse Pratyush Soni Follow Aspiring Game & Graphics Programmer (•̀ᴗ•́)و Studying @ Amity Univ (¬‿¬) Learning C++, C#, OpenGL, Vulkan ＼(＾O＾)／ Passionate about real-time rendering & cool visuals! (ﾉ◕ヮ◕)ﾉ:･ﾟ✧ Joined May 26, 2025 Trending on DEV Community Hot I Debug Code Like I Debug Life (Spoiler: Both Throw Exceptions) # discuss # career # programming # beginners How Rube MCP Solves Context Overload When Using Hundreds of MCP Servers # mcp # productivity # programming # ai AI should not be in Code Editors # programming # ai # productivity # discuss 💎 DEV Diamond Sponsors Thank you to our Diamond Sponsors for supporting the DEV Community Google AI is the official AI Model and Platform Partner of DEV Neon is the official database partner of DEV Algolia is the official search partner of DEV DEV Community — A space to discuss and keep up software development and manage your software career Home DEV++ Podcasts Videos DEV Education Tracks DEV Challenges DEV Help Advertise on DEV DEV Showcase About Contact Free Postgres Database Software comparisons Forem Shop Code of Conduct Privacy Policy Terms of Use Built on Forem — the open source software that powers DEV and other inclusive communities. Made with love and Ruby on Rails . DEV Community © 2016 - 2026. We're a place where coders share, stay up-to-date and grow their careers. Log in Create account	2026-01-13T09:29:24
https://git-scm.com/book/ru/v2/Git-%d0%bd%d0%b0-%d1%81%d0%b5%d1%80%d0%b2%d0%b5%d1%80%d0%b5-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 Протоколы 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 4.8 Git на сервере - GitLab GitLab GitWeb довольно-таки прост. Если вам нужен более современный, полнофункциональный Git-сервер, есть несколько решений с открытым исходным кодом, которые можно использовать. Так как GitLab это один из самых популярных, мы рассмотрим его установку и использование в качестве примера. Это немного сложнее, чем GitWeb, и скорее всего потребует больше обслуживания, но и функциональность гораздо богаче. Установка GitLab — это веб-приложение на основе базы данных, так что его установка немного сложней, чем у некоторых других серверов Git. К счастью, этот процесс хорошо документирован и поддерживается. GitLab настоятельно рекомендует установить GitLab на ваш сервер через официальный пакет Omnibus GitLab. Другие варианты установки: GitLab Helm chart для использования с Kubernetes. Официальные образы GitLab для использования с Docker. Из исходных файлов. Облачный провайдер, такой как AWS, Google Cloud Platform, Azure, OpenShift или Digital Ocean. Для получения дополнительной информации прочтите GitLab Community Edition (CE) readme . Администрирование Административный интерфейс GitLab доступен через веб. Просто направьте ваш браузер на имя или IP-адрес хоста, где установлен GitLab, и войдите как администратор. Имя пользователя по умолчанию admin@local.host , пароль по умолчанию 5iveL!fe (вас попросят изменить их при входе). Войдя, нажмите иконку «Административная зона» в меню справа и сверху. Рисунок 50. Пункт «Административная зона» в меню GitLab Пользователи Пользователи в GitLab — это учётные записи, соответствующие людям. Пользовательские учётные записи не очень сложны; в основном это набор персональной информации, прикреплённый к имени. У каждого пользователя есть пространство имён , логически группирующее проекты данного пользователя. Если у пользователя jane есть проект project, адрес этого проекта будет http://server/jane/project . Рисунок 51. Экран управления пользователями GitLab Удаление пользователя может быть выполнено двумя способами. «Блокирование» («Blocking») пользователя запрещает ему вход в GitLab, но все данные в его пространстве имён сохраняются, и коммиты, подписанные этим пользователем, будут указывать на его профиль. «Разрушение» («Destroying») пользователя, с другой стороны, полностью удаляет его из базы данных и файловой системы. Все проекты и данные в его пространстве имён удаляются, как и все принадлежащие ему группы. Конечно, этим более постоянным и разрушительным действием пользуются реже. Группы Группы GitLab — это коллекция проектов с указанием того, как пользователи получают к ним доступ. Каждая группа имеет пространство имён проектов (так же как и пользователи), так что если в группе training есть проект materials, его адрес будет http://server/training/materials . Рисунок 52. Экран управления группами GitLab Каждая группа связана с пользователями, каждый из которых имеет уровень доступа к проектам группы и к самой группе. Он разнится от «Гостя» («Guest», только проблемы и чат) до «Владельца» («Owner», полный контроль над группой, её членами и проектами). Типы разрешений слишком обширны, чтобы перечислять их здесь, но на экране управления GitLab есть полезная ссылка с описанием. Проекты Проект GitLab примерно соответствует одному git-репозиторию. Каждый проект принадлежит одному пространству имён, групповому или пользовательскому. Если проект принадлежит пользователю, владелец контролирует, кто имеет доступ к проекту; если проект принадлежит группе, действуют групповые уровни доступа для пользователей. Каждый проект также имеет уровень видимости, который контролирует, кто имеет доступ на чтение страниц проекта или репозитория. Если проект Приватный ( Private ), владелец должен явно дать доступ на чтение отдельным пользователям. Внутренний ( Internal ) проект виден любому вошедшему пользователю GitLab, а Публичный ( Public ) проект видим всем. Это относится как к доступу git fetch , так и к доступу к проекту через веб-интерфейс. Хуки GitLab включает поддержку хуков (перехватчиков, hooks) на уровне проектов и всей системы. В обоих случаях, когда происходит некоторое событие, сервер GitLab выполняет запрос HTTP POST с осмысленным JSON-содержанием. Это отличный способ соединить ваши git-репозитории и инсталляцию GitLab с автоматикой инфраструктуры разработки, такой как сервера непрерывной интеграции, комнаты чатов или инструменты деплоя. Базовое использование Первое, чего вы захотите от GitLab, это создать новый проект. Это достигается нажатием иконки «+» на панели инструментов. Будут запрошены имя проекта, пространство имён, которому он должен принадлежать, и уровень видимости. Большинство из этих настроек можно потом изменить через интерфейс настроек. Нажмите «Создать проект» («Create Project»), чтобы закончить. Когда проект создан, вы, наверное, захотите соединить его с локальным git-репозиторием. Каждый проект может быть доступен через HTTPS или SSH, каждый из которых может быть использован для указания удалённого репозитория. Адреса (URL) видимы наверху домашней страницы проекта. Для существующего локального репозитория, следующая команда создаст удалённый репозиторий с именем gitlab и размещением на сервере: $ git remote add gitlab https://server/namespace/project.git Если у вас нет локального репозитория, можно просто сделать его: $ git clone https://server/namespace/project.git Веб-интерфейс даёт доступ к нескольким полезным видам самого репозитория. Домашняя страница каждого проекта показывает недавнюю активность, а ссылки наверху ведут на список файлов проекта и журнала коммитов. Совместная работа Самый простой метод совместной работы над проектом GitLab — это выдача другому пользователю прямого доступа на запись (push) в git-репозитории. Вы можете добавить пользователя в проект в разделе «Участники» («Members») настроек проекта, указав уровень доступа (уровни доступа кратко обсуждались в Группы ). Получая уровень доступа «Разработчик» («Developer») или выше, пользователь может беспрепятственно отсылать свои коммиты и ветки непосредственно в репозиторий. Другой, более разобщённый способ совместной работы — использование запросов на слияние (merge requests). Эта возможность позволяет любому пользователю, который видит проект, вносить свой вклад подконтрольным способом. Пользователи с прямым доступом могут просто создать ветку, отослать в неё коммиты и открыть запрос на слияние из их ветки обратно в master или любую другую ветку. Пользователи без доступа на запись могут «форкнуть» репозиторий («fork», создать собственную копию), отправить коммиты в эту копию и открыть запрос на слияние из их форка обратно в основной проект. Эта модель позволяет владельцу полностью контролировать, что попадает в репозиторий и когда, принимая помощь от недоверенных пользователей. Запросы на слияние и проблемы (issues) это основные единицы долгоживущих дискуссий в GitLab. Каждый запрос на слияние допускает построчное обсуждение предлагаемого изменения (поддерживая облегчённое рецензирование кода), равно как и общее обсуждение. И те и другие могут присваиваться пользователям или организовываться в вехи (milestones). Мы в основном сосредоточились на частях GitLab, связанных с git, но это — довольно зрелая система, и она предоставляет много других возможностей, помогающих вашей команде работать совместно, например вики-страницы для проектов и инструменты поддержки системы. Одно из преимуществ GitLab в том, что, однажды запустив и настроив сервер, вам редко придётся изменять конфигурацию или заходить на него по SSH; большинство административных и пользовательских действий можно выполнять через веб-браузер. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://git-scm.com/book/tl/v2/Pag-branch-ng-Git-Remote-na-mga-Branch	Git - Remote na mga 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.5 Pag-branch ng Git - Remote na mga Branch Remote na mga Branch Ang remote na mga reperensiya ay mga reperensiya (mga pointer) sa iyong remote na mga repositoryo, na nagsasama ng mga branch, mga tag, at iba pa. Maaari kang tahasang makakuha ng isang buong listahan ng remote na mga reperensya gamit ang git ls-remote [remote] , o git remote show [remote] para sa remote na mga branch at marami pang impormasyon. Gayunpaman, isang mas karaniwang paraan ay ang pagsasamantala sa remote-tracking na mga branch. Ang remote-tracking na mga branch ay mga reperensya sa estado ng remote na mga branch. Sila ay lokal na mga reperensya na hindi mo magagalaw; ginagalaw ng Git ang mga ito para sa iyo sa tuwing ikaw ay gumawa ng anumang network na komunikasyon, upang siguraduhing sila ay tama nagrerepresenta ng estado ng remote na repositoryo. Isipin sila bilang mga bookmark, upang paalalahanan ka kung saan ang mga branch sa iyong remote na mga repositoryo noong huling panahon na ikaw ay nakakonekta sa kanila. Ang remote-tracking na mga branch ay nag-aanyong <remote>/<branch> . Halimbawa, kung gusto mong tingnan kung ano ang hitsura ng master na branch sa iyong origin na remote noong huling panahon na ikaw ay nakipag-usap nito, susuriin mo ang origin/master na branch. Kung ikaw ay nagtatrabaho sa isang isyu kasama ang isang kasosyo at sila ay nag-push paitaas ng isang iss53 na branch, maaaring mayroon kang sariling lokal na iss53 na branch, ngunit ang branch sa server ay marerepresenta ng remote-tracking na branch na origin/iss53 . Maaaring ito ay medyo nakakalito, kaya tumingin tayo sa isang halimbawa. Sabihin nating mayroon kang isang Git na server sa iyong network sa git.ourcompany.com . Kung ikaw ay magku-clone mula nito, ang clone na utos ng Git ay awtomatikong papangalanan itong origin para sa iyo, ipu-pull nito pababa ang lahat ng datos nito, gagawa ng isang pointer patungo kung saan ang master na branch nito, at lokal itong papangalanang origin/master . Ang Git ay nagbibigay din sa iyo ng iyong sariling lokal na master na branch sa pagsisimula sa parehong lugar bilang master na branch ng origin, kaya mayroon kang bagay na tatrabahuan. Example 5. Ang “origin” ay hindi espesyal Kutulad ng pangalan ng branch na “master” ay walang espesyal na kahulugan sa Git, pati na ring ang “origin”. Habang ang “master” ay ang default na pangalan para sa isang panimulang branch kapag ikaw ay nagpatakbo ng git init na ang natatanging dahilan kaya ito ay malawakang ginagamit, ang “origin” ay ang default na pangalan para sa isang remote kapag ikaw ay nagpatakbo ng git clone . Kung sa halip ikaw ay nagpatakbo ng git clone -o booyah , ikaw ay magkakaroon ng booyah/master bilang iyong default na remote na branch. Figure 30. Ang server at lokal na mga repositoryo pagkatapos ng pag-clone Kung ikaw ay gumawa ng ilang trabaho sa iyong lokal na master na branch, at, sa pansamantala, may ibang nagpu-push sa git.ourcompany.com at nag-update ng master na branch nito, ang iyong mga kasaysayan ay kakaibang ililipat nang pasulong. Gayundin, hangga’t mananatili kang umiwas sa pakikipag-usap sa iyong origin na server, ang iyong origin/master na pointer ay hindi gagalaw. Figure 31. Ang lokal at remote na trabaho ay maaaring ihiwalay Upang mapagsabay-sabay ang iyong trabaho, magpapatakbo ka ng isang git fetch origin na utos. Ang utos na ito ay titingnan kung anong server ang “origin” (sa kasong ito, ito ay git.ourcompany.com ), ipi-fetch ang anumang datos mula dito na hindi pa nasa iyo, at ia-update ang iyong lokal na database, ililipat ang iyong origin/master na pointer sa bago, mas napapanahon nitong posisyon. Figure 32. Ang git fetch ay ia-update ang iyong remote na mga reperensya Upang ipakita ang pagkakaroon ng maramihang remote na mga server at kung ano ang hitsura ng remote na mga branch para sa mga remote na proyekto, ating ipalagay na mayroon kang ibang panloob na Git na server na ginagamit lamang para sa pag-develop ng isa sa iyong mga sprint na mga koponan. Ang server na ito ay nasa git.team1.ourcompany.com . Maaari mong idagdag ito bilang isang panibagong remote na reperensya kung saan mo kasalukuyang tinatrabaho ang git remote add na utos na ating nasakop sa Mga Pangunahing Kaalaman sa Git . Pangalanan itong remote na teamone , na magiging iyong maikling pangalan para sa buong URL na iyon. Figure 33. Pagdagdag ng ibang server bilang isang remote Ngayon, maaari mong patakbuhin ang git fetch teamone upang i-fetch ang lahat ng nasa remote na teamone na hindi pa nasa iyo. Dahil ang server na iyon ay may isang subset ng datos na nasa iyong origin na server na ngayon, walang datos na ipi-fetch ang Git ngunit magtatakda ng isang remote-tracking na branch na tinatawag na teamone/master upang tumuro sa commit na mayroon sa teamone bilang master na branch nito. Figure 34. Ang remote tracking na branch para sa teamone/master Pag-push Kapag gusto mong magbahagi ng isang branch sa mundo, kailangan mong i-push ito pataas sa isang remote na mayroon kang access sa pagsulat. Ang iyong lokal na mga branch ay hindi awtomatikong magkasabay-sabay sa mga remote na susulatan mo — kailangang mong tahasang i-push ang mga branch na gusto mong ibahagi. Sa paraang iyon, maaari kang gumamit ng pribadong mga branch para sa trabahong hindi mo gustong ibahagi, at i-push pataas ang mga paksa na mga branch lamang na gusto mong makipagtulungan. Kung mayroon kang isang branch na nakapangalang serverfix na gusto mong trabahuin kasama ang iba, maaari mong i-push ito pataas sa parehong paraan na na-push mo ang iyong unang branch. Patakbuhin ang git push <remote> <branch> : $ git push origin serverfix Counting objects: 24, done. Delta compression using up to 8 threads. Compressing objects: 100% (15/15), done. Writing objects: 100% (24/24), 1.91 KiB \| 0 bytes/s, done. Total 24 (delta 2), reused 0 (delta 0) To https://github.com/schacon/simplegit * [new branch] serverfix -> serverfix Ito ay medyo parang isang daang tuwiran. Ang Git ay awtomatikong pinapalaki ang serverfix na pangalan ng branch palabas sa refs/heads/serverfix:refs/heads/serverfix , na nangangahulugang, “Kunin mo ang aking serverfix na lokal na branch at i-push ito upang i-update ang serverfix na branch ng remote.” Dumako tayo sa refs/heads/ na bahagi sa detalye sa Mga Panloob ng GIT , ngunit kadalasan ay maaari mo itong hayaan. Maaari ka ring gumawa ng git push origin serverfix:serverfix , na gumagawa ng parehong bagay — nagsasabi ito na, “Kunin mo ang aking serverfix at gawin itong serverfix ng remote.” Maaari mong gamitin ang format na ito upang mag-push ng isang lokal na branch sa isang remote na branch na kakaibang nakapangalan. Kung hindi mo gustong tawagin itong serverfix sa remote, sa halip ay maaari mong patakbuhin ang git push origin serverfix:awesomebranch upang i-push ang iyong lokal na serverfix na branch patungo sa awesomebranch na branch sa remote na proyekto. Example 6. Huwag i-type ang iyong password sa bawat panahon Kung ikaw ay gumagamit ng isang HTTPS na URL upang mag-push paitaas, ang Git na server ay hihingian ka para sa iyong username at password para sa pagpapatunay. Bilang default ito ay mag-uudyok sayo sa terminal para sa impormasyong ito upang mapagpasyahan ng server kung ikaw ay pinapahintulutang mag-push. Kung hindi mo gustong i-type ito sa bawat isang pagkakataon na magpu-push ka, maaari mong magtakda ng isang “credential cache”. Ang pinakasimple ay ang panatilihin ito sa memorya sa isang maikling minuto, kung saan maaari mong madaling itakda sa pamamagitan ng pagpapatakbo ng git config --global credential.helper cache . Para sa karagdagang impormasyon sa iba’t ibang mga opsyon ng credential caching na maaaring magamit, tingnan ang Kredensyal na ImbakanCredential Storage . Sa susunod na panahon na isa sa iyong mga katulong ay mag-fetch mula sa server, sila ay makakatanggap ng isang reperensya kung saan ang bersyon ng server ng serverfix sa ilalim ng remote na branch na origin/serverfix : $ git fetch origin remote: Counting objects: 7, done. remote: Compressing objects: 100% (2/2), done. remote: Total 3 (delta 0), reused 3 (delta 0) Unpacking objects: 100% (3/3), done. From https://github.com/schacon/simplegit * [new branch] serverfix -> origin/serverfix Importanteng tandaan na kapag ikaw ay gumawa ng isang fetch na humihila pababa ng bagong remote-tracking na mga branch, hindi ka awtomatikong magkakaroon ng lokal, mababagong mga kopya nito. Sa ibang mga salita, sa kasong ito, wala kang isang bagong serverfix na branch — mayroon ka lang isang origin/serverfix na pointer na hindi mo mababago. Upang ma-merge ang trabahong ito sa iyong kasalukuyang tinatrabahong branch, maaari mong patakbuhin ang git merge origin/serverfix . Kung gusto mong magkaroon ng sariling serverfix na branch kung saan ka pwedeng magtrabaho, maaari kang mag-base nito sa iyong remote-tracking na branch: $ git checkout -b serverfix origin/serverfix Branch serverfix set up to track remote branch serverfix from origin. Switched to a new branch 'serverfix' Ito ay nagbibigay sa iyo ng isang lokal na branch na kung saan maaari kang magtrabaho na nagsisimula kung saan ang origin/serverfix . Sumusubaybay na mga Branch Ang pag-check out ng isang lokal na branch mula sa isang remote-tracking na branch ay awtomatikong gumagawa ng kung tawagin ay isang “sumusubaybay branch” (at ang branch na sinusubaybayan ay tinatawag na isang “upstream branch”). Ang sumusubaybay na mga branch ay lokal na mga branch na may isang direktang relasyon sa isang remote na branch. Kung ikaw ay nasa sumusubaybay na branch at magta-type ng git pull , ang Git ay awtomatikong nalalaman kung anong server ang ipi-fetch at branch na imi-merge. Kapag ikaw ay magko-clone ng isang repositoryo, ito ay kadalasang awtomatikong gumagawa ng isang master na branch na sumusubaybay sa origin/master . Samantala, maaari kang magtalaga ng ibang sumusubaybay na mga branch kung gugustuhin mo — yung mga sumusubaybay ng mga branch sa ibang mga remote, o huwag subaybayan ang master na branch. Ang simpleng kaso ay ang halimbawa na nakita mo kamakailan lamang, ang pagpapatakbo ng git checkout -b <branch> <remote>/<branch> . Ito ay isang karaniwang sapat na operasyon na ibinibigay ng Git ay ang --track na takigrapya: $ git checkout --track origin/serverfix Branch serverfix set up to track remote branch serverfix from origin. Switched to a new branch 'serverfix' Sa katunayan, ito ay sobrang karaniwan na mayroon ding isang takigrapya para sa daang tuwiran na iyon. Kung ang pangalan ng branch na sinusubukan mong i-checkout (a) ay hindi umiiral at ang (b) ay eksaktong tumutugma sa isang pangalan sa isang remote lamang, ang Git ay gagawa ng isang sumusubaybay na branch para sa iyo: $ git checkout serverfix Branch serverfix set up to track remote branch serverfix from origin. Switched to a new branch 'serverfix' Upang magtakda ng isang lokal na branch gamit ang isang naiibang pangalan kaysa sa remote branch, maaaring madali mong magamit ang unang bersyon gamit ang isang naiibang lokal na pangalan ng branch: $ git checkout -b sf origin/serverfix Branch sf set up to track remote branch serverfix from origin. Switched to a new branch 'sf' Ngayon, ang iyong lokal na branch na sf ay awtomatikong magpu-pull mula sa origin/serverfix . Kung ikaw ay mayroon nang isang lokal na branch at gustong itakda ito sa isang remote na branch na iyong na pull pababa, o gustong baguhin ang upstream na branch na iyong sinusubaybayan, maaari mong gamitin ang -u o --set-upstream-to na opsyon sa git branch upang tahasang itakda ito sa anumang panahon. $ git branch -u origin/serverfix Branch serverfix set up to track remote branch serverfix from origin. Example 7. Upstream na takigrapya Kapag mayroon kang isang sumusubaybay na branch na naitakda, maaari mong ireperensya ang upstream na branch nito gamit ang @{upstream} o @{u} na takigrapya. Kaya kung ikaw ay nasa master na branch at ito ay sumusubaybay sa origin/master , maaari kang magsabi ng anuman katulad ng git merge @{u} sa halip ng git merge origin/master kung gugustuhin mo. Kung gusto mong tingnan kung anong sumusubaybay na mga branch ang naitakda mo, maaari mong gamitin ang -vv na opsyon sa git branch . Ito ay ililista ang iyong lokal na mga branch na may maraming impormasyon na naglalaman ng kung ano ang sinusubaybayan ng bawat branch at kung ang iyong lokal na branch ay nauuna, nahuhuli, o pareho. $ git branch -vv iss53 7e424c3 [origin/iss53: ahead 2] forgot the brackets master 1ae2a45 [origin/master] deploying index fix * serverfix f8674d9 [teamone/server-fix-good: ahead 3, behind 1] this should do it testing 5ea463a trying something new Kaya dito ay makikita natin ang ating iss53 na branch na sumusubaybay sa origin/iss53 at “nauuna” ng dalawa, nangangahulugang may dalawang commit sa lokal na hindi pa na-push sa server. Maaari rin nating tingnan kung ang ating master na branch ay sumusubaybay sa origin/master at napapanahon. Susunod nakikita natin na ang ating serverfix na branch ay sumusubaybay sa server-fix-good na branch sa ating teamone na server at nauuna ng tatlo at nahuhuli ng isa, nangangahulugan na may isang commit sa server na hindi pa natin na merge at tatlong mga commit na nasa lokal na hindi pa natin na-push. Sa huli makikita natin na ang ating testing na branch ay hindi sumusubaybay ng anumang remote na branch. Importanteng tandaan na ang mga ito ay numero lamang mula noong huling panahon na nag-fetch ka mula sa bawat server. Ang utos na ito hindi umaabot sa mga server, at sinasabi nito sa iyon ang tungkol sa kung ano ang lokal na na-cache nito mula sa mga server na ito. Kung gusto mong buong napapanahon na nauuna at nahuhuli sa mga numero, kailangan mong mag-fetch mula sa lahat ng iyong mga remote bago mo patakbuhin ito. Maaari mong gawin iyon kagaya nito: $ git fetch --all; git branch -vv Pag-pull Habang ang git fetch na utos ay magpi-fetch pababa ng lahat ng mga pagbabago sa server na hindi pa nasa iyo, hindi nito babaguhin ang iyong tinatrabaho na direktoryo. Ito ay simpleng kukunin ang data para sa iyo at hahayaan kang i-merge ito. Samantala, mayroong isang utos na tinatawag na git pull na tunay na isang git fetch na kaagad na sinusundan ng isang git merge sa kadalasang kaso. Kung ikaw ay may isang sumusubaybay na branch na nakatakda base sa ipinakita sa huling seksyon, alinman sa pamamagitan ng tahas na pagtakda nito o sa pamamagitan ng paggawa nito para sa iyo gamit ang clone o checkout na utos, ang git pull ay hahanapin kung anong server at branch ang sinusubaybayan ng iyong kasalukuyang branch, mag-fetch mula sa server na iyon at pagkatapos ay susubukang i-merge ang remote na branch na iyon. Sa pangkalahatan mas mabuti na simpleng gamitin ang fetch at merge na mga utos nang tahasan dahil ang mahika ng git pull ay maaaring nakakalito. Pagbubura ng Remote na mga Branch Ipagpalagay na natapos ka na sa isang remote na branch – sabihing ikaw at ang iyong mga katulong ay natapos na sa isang tampok at na-merge ito sa iyong master na branch ng remote (o anumang branch kung saan nandoon ang iyong matatag na codeline). Maaari mong burahin ang isang remote na branch gamit ang --delete na opsyon sa git push . Kung gusto mong burahin ang iyong serverfix na branch mula sa server, patakbuhin mo ang sumusunod: $ git push origin --delete serverfix To https://github.com/schacon/simplegit - [deleted] serverfix Talagang lahat ng ginagawa nito ay magtanggal ng pointer mula sa server. Ang Git na server ay kadalasang pinapanatili ang data doon sa isang saglit hanggang ang isang koleksyon ng basura ay tatakbo, kaya kung ito ay aksidenteng nabura, ito ay kadalasang madaling bawiin. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#param-url-4	Instagram API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Instagram API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Posts API Collect by URL Discover by URL Comments API Collect by URL Reels API Collect by URL Discover by URL Social Media APIs Instagram API Scrapers Copy page Copy page Overview The Instagram API Suite offers multiple types of APIs, each designed for specific data collection needs from Instagram. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : N/A Interesting Columns : followers , post_count , post_hashtags , profile_name . Posts API This API allows users to collect multiple posts based on a single input URL (such as an Instagram reels URL, search URL or profile URL). Discovery functionality : - Direct URL of the Instagram reel - Direct URL of the search - Direct URL of the profile Interesting Columns : url , followers , hashtags , engagement_score_view . Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : comment_user , comment , likes_number , replies_number . The suite of APIs is designed to offer flexibility for targeted data collection, where users can input specific URLs to gather detailed post and comment data, either in bulk or with precise filtering options. Profiles API Collect by URL This API allows users to collect detailed data about an Instagram profile by providing the profile URL. It provides a comprehensive overview of an Instagram profile, including business and engagement information, posts, and user details. Input Parameters URL string required The Instagram profile URL. Output Structure Includes comprehensive data points: Page/Profile Details : account , id , followers , posts_count , is_business_account , is_professional_account , is_verified , avg_engagement , profile_name , profile_url , profile_image_link , and more. For all data points, click here . Posts API Collect by URL This API enables users to collect detailed data from Instagram posts by providing a post URL. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Post Details : post_id , description , hashtags , date_posted , num_comments , likes , content_type , video_view_count , video_play_count , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : photos , videos , thumbnail , display_url (link only, not the file itself), audio. Discover by URL This API allows users to discover recent Instagram posts from a public profile by providing the profile URL and specifying additional parameters. Input Parameters URL string required The Instagram profile URL. num_of_posts number The number of recent posts to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date). post_type string Specify the type of posts to collect (e.g., post, reel). Output Structure Includes comprehensive data points: Post Details: post_id , description , hashtags , date_posted , num_comments , likes , video_view_count , video_play_count ,and more. For all data points, click here . Page/Profile Details: user_posted , followers , posts_count , profile_image_link , is_verified , profile_url , is_paid_partnership , partnership_details , user_posted_id Attachments and Media: photos , videos , thumbnail , audio , display_url , content_type , product_type , coauthor_producers , tagged_users . This API is designed to allow for filtering, exclusion of specific posts, and collecting posts by type (regular post or reel) within a defined time frame. It provides detailed post and profile information, making it ideal for data collection and analytics. Comments API Collect by URL This API allows users to collect the latest comments from a specific Instagram post by providing the post URL. This API retrieves the most recent 10 comments along with associated metadata. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Comment Details : comment_id , comment_user , comment_user_url , comment_date , comment , likes_number , replies_number , replies , hashtag_comment , tagged_users_in_comment , and more. For all data points, click here . User Details : user_name , user_id , user_url We provide a limited set of data points about the profile. Post Metadata : post_url , post_user , post_id . Reels API Collect by URL This API allows users to collect detailed data about Instagram reels from public profiles by providing the reel URL. Input Parameters URL string required The Instagram reel URL. Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , tagged_users , num_comments , likes , views , video_play_count , length , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : video_url , thumbnail , audio_url . Discover by URL This API allows users to discover Instagram Reels videos from a profile URL or direct search URL. Input Parameters URL string required The Instagram profile or direct search URL. num_of_posts number The number of recent reels to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering reels in MM-DD-YYYY format. end_date string End date for filtering reels in MM-DD-YYYY format (should be later than start_date ). Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , num_comments , likes , views , video_play_count , top_comments , length , video_url , audio_url , content_id , and more. For all data points, click here . Profile Details : user_posted , followers , posts_count , following . Attachments and Media : video_url , thumbnail , audio_url (link only, not the file itself). This API provides detailed information about Instagram Reels, with filtering options by date range, exclusion of specific posts, and a limit on the number of reels collected. Was this page helpful? Yes No Facebook LinkedIn ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:24
https://git-scm.com/book/cs/v2/GitHub-Scripting-GitHub	Git - Scripting GitHub 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.5 GitHub - Scripting GitHub Scripting GitHub So now we’ve covered all of the major features and workflows of GitHub, but any large group or project will have customizations they may want to make or external services they may want to integrate. Luckily for us, GitHub is really quite hackable in many ways. In this section we’ll cover how to use the GitHub hooks system and its API to make GitHub work how we want it to. Hooks The Hooks and Services section of GitHub repository administration is the easiest way to have GitHub interact with external systems. Services First we’ll take a look at Services. Both the Hooks and Services integrations can be found in the Settings section of your repository, where we previously looked at adding Collaborators and changing the default branch of your project. Under the “Webhooks and Services” tab you will see something like Services and Hooks configuration section. . Figure 130. Services and Hooks configuration section. There are dozens of services you can choose from, most of them integrations into other commercial and open source systems. Most of them are for Continuous Integration services, bug and issue trackers, chat room systems and documentation systems. We’ll walk through setting up a very simple one, the Email hook. If you choose “email” from the “Add Service” dropdown, you’ll get a configuration screen like Email service configuration. . Figure 131. Email service configuration. In this case, if we hit the “Add service” button, the email address we specified will get an email every time someone pushes to the repository. Services can listen for lots of different types of events, but most only listen for push events and then do something with that data. If there is a system you are using that you would like to integrate with GitHub, you should check here to see if there is an existing service integration available. For example, if you’re using Jenkins to run tests on your codebase, you can enable the Jenkins builtin service integration to kick off a test run every time someone pushes to your repository. Zásuvné moduly If you need something more specific or you want to integrate with a service or site that is not included in this list, you can instead use the more generic hooks system. GitHub repository hooks are pretty simple. You specify a URL and GitHub will post an HTTP payload to that URL on any event you want. Generally the way this works is you can setup a small web service to listen for a GitHub hook payload and then do something with the data when it is received. To enable a hook, you click the “Add webhook” button in Services and Hooks configuration section. . This will bring you to a page that looks like Web hook configuration. . Figure 132. Web hook configuration. The configuration for a web hook is pretty simple. In most cases you simply enter a URL and a secret key and hit “Add webhook”. There are a few options for which events you want GitHub to send you a payload for — the default is to only get a payload for the push event, when someone pushes new code to any branch of your repository. Let’s see a small example of a web service you may set up to handle a web hook. We’ll use the Ruby web framework Sinatra since it’s fairly concise and you should be able to easily see what we’re doing. Let’s say we want to get an email if a specific person pushes to a specific branch of our project modifying a specific file. We could fairly easily do that with code like this: require 'sinatra' require 'json' require 'mail' post '/payload' do push = JSON.parse(request.body.read) # parse the JSON # gather the data we're looking for pusher = push["pusher"]["name"] branch = push["ref"] # get a list of all the files touched files = push["commits"].map do \|commit\| commit['added'] + commit['modified'] + commit['removed'] end files = files.flatten.uniq # check for our criteria if pusher == 'schacon' && branch == 'ref/heads/special-branch' && files.include?('special-file.txt') Mail.deliver do from 'tchacon@example.com' to 'tchacon@example.com' subject 'Scott Changed the File' body "ALARM" end end end Here we’re taking the JSON payload that GitHub delivers us and looking up who pushed it, what branch they pushed to and what files were touched in all the commits that were pushed. Then we check that against our criteria and send an email if it matches. In order to develop and test something like this, you have a nice developer console in the same screen where you set the hook up. You can see the last few deliveries that GitHub has tried to make for that webhook. For each hook you can dig down into when it was delivered, if it was successful and the body and headers for both the request and the response. This makes it incredibly easy to test and debug your hooks. Figure 133. Web hook debugging information. The other great feature of this is that you can redeliver any of the payloads to test your service easily. For more information on how to write webhooks and all the different event types you can listen for, go to the GitHub Developer documentation at https://developer.github.com/webhooks/ The GitHub API Services and hooks give you a way to receive push notifications about events that happen on your repositories, but what if you need more information about these events? What if you need to automate something like adding collaborators or labeling issues? This is where the GitHub API comes in handy. GitHub has tons of API endpoints for doing nearly anything you can do on the website in an automated fashion. In this section we’ll learn how to authenticate and connect to the API, how to comment on an issue and how to change the status of a Pull Request through the API. Základní použití The most basic thing you can do is a simple GET request on an endpoint that doesn’t require authentication. This could be a user or read-only information on an open source project. For example, if we want to know more about a user named “schacon”, we can run something like this: $ curl https://api.github.com/users/schacon { "login": "schacon", "id": 70, "avatar_url": "https://avatars.githubusercontent.com/u/70", # … "name": "Scott Chacon", "company": "GitHub", "following": 19, "created_at": "2008-01-27T17:19:28Z", "updated_at": "2014-06-10T02:37:23Z" } There are tons of endpoints like this to get information about organizations, projects, issues, commits — just about anything you can publicly see on GitHub. You can even use the API to render arbitrary Markdown or find a .gitignore template. $ curl https://api.github.com/gitignore/templates/Java { "name": "Java", "source": ".class # Mobile Tools for Java (J2ME) .mtj.tmp/ # Package Files # .jar .war .ear # virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml hs_err_pid* " } Commenting on an Issue However, if you want to do an action on the website such as comment on an Issue or Pull Request or if you want to view or interact with private content, you’ll need to authenticate. There are several ways to authenticate. You can use basic authentication with just your username and password, but generally it’s a better idea to use a personal access token. You can generate this from the “Applications” tab of your settings page. Figure 134. Generate your access token from the “Applications” tab of your settings page. It will ask you which scopes you want for this token and a description. Make sure to use a good description so you feel comfortable removing the token when your script or application is no longer used. GitHub will only show you the token once, so be sure to copy it. You can now use this to authenticate in your script instead of using a username and password. This is nice because you can limit the scope of what you want to do and the token is revocable. This also has the added advantage of increasing your rate limit. Without authenticating, you will be limited to 60 requests per hour. If you authenticate you can make up to 5,000 requests per hour. So let’s use it to make a comment on one of our issues. Let’s say we want to leave a comment on a specific issue, Issue #6. To do so we have to do an HTTP POST request to repos/<user>/<repo>/issues/<num>/comments with the token we just generated as an Authorization header. $ curl -H "Content-Type: application/json" \ -H "Authorization: token TOKEN" \ --data '{"body":"A new comment, :+1:"}' \ https://api.github.com/repos/schacon/blink/issues/6/comments { "id": 58322100, "html_url": "https://github.com/schacon/blink/issues/6#issuecomment-58322100", ... "user": { "login": "tonychacon", "id": 7874698, "avatar_url": "https://avatars.githubusercontent.com/u/7874698?v=2", "type": "User", }, "created_at": "2014-10-08T07:48:19Z", "updated_at": "2014-10-08T07:48:19Z", "body": "A new comment, :+1:" } Now if you go to that issue, you can see the comment that we just successfully posted as in A comment posted from the GitHub API. . Figure 135. A comment posted from the GitHub API. You can use the API to do just about anything you can do on the website — creating and setting milestones, assigning people to Issues and Pull Requests, creating and changing labels, accessing commit data, creating new commits and branches, opening, closing or merging Pull Requests, creating and editing teams, commenting on lines of code in a Pull Request, searching the site and on and on. Changing the Status of a Pull Request There is one final example we’ll look at since it’s really useful if you’re working with Pull Requests. Each commit can have one or more statuses associated with it and there is an API to add and query that status. Most of the Continuous Integration and testing services make use of this API to react to pushes by testing the code that was pushed, and then report back if that commit has passed all the tests. You could also use this to check if the commit message is properly formatted, if the submitter followed all your contribution guidelines, if the commit was validly signed — any number of things. Let’s say you set up a webhook on your repository that hits a small web service that checks for a Signed-off-by string in the commit message. require 'httparty' require 'sinatra' require 'json' post '/payload' do push = JSON.parse(request.body.read) # parse the JSON repo_name = push['repository']['full_name'] # look through each commit message push["commits"].each do \|commit\| # look for a Signed-off-by string if /Signed-off-by/.match commit['message'] state = 'success' description = 'Successfully signed off!' else state = 'failure' description = 'No signoff found.' end # post status to GitHub sha = commit["id"] status_url = "https://api.github.com/repos/#{repo_name}/statuses/#{sha}" status = { "state" => state, "description" => description, "target_url" => "http://example.com/how-to-signoff", "context" => "validate/signoff" } HTTParty.post(status_url, :body => status.to_json, :headers => { 'Content-Type' => 'application/json', 'User-Agent' => 'tonychacon/signoff', 'Authorization' => "token #{ENV['TOKEN']}" } ) end end Hopefully this is fairly simple to follow. In this web hook handler we look through each commit that was just pushed, we look for the string Signed-off-by in the commit message and finally we POST via HTTP to the /repos/<user>/<repo>/statuses/<commit_sha> API endpoint with the status. In this case you can send a state ( success , failure , error ), a description of what happened, a target URL the user can go to for more information and a “context” in case there are multiple statuses for a single commit. For example, a testing service may provide a status and a validation service like this may also provide a status — the “context” field is how they’re differentiated. If someone opens a new Pull Request on GitHub and this hook is set up, you may see something like Commit status via the API. . Figure 136. Commit status via the API. You can now see a little green check mark next to the commit that has a “Signed-off-by” string in the message and a red cross through the one where the author forgot to sign off. You can also see that the Pull Request takes the status of the last commit on the branch and warns you if it is a failure. This is really useful if you’re using this API for test results so you don’t accidentally merge something where the last commit is failing tests. Octokit Though we’ve been doing nearly everything through curl and simple HTTP requests in these examples, several open-source libraries exist that make this API available in a more idiomatic way. At the time of this writing, the supported languages include Go, Objective-C, Ruby, and .NET. Check out http://github.com/octokit for more information on these, as they handle much of the HTTP for you. Hopefully these tools can help you customize and modify GitHub to work better for your specific workflows. For complete documentation on the entire API as well as guides for common tasks, check out https://developer.github.com . prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#param-keyword-1	Pinterest API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Pinterest API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Discover by Keywords Posts API Collect by URL Discover by Profile URL Discover by Keywords Social Media APIs Pinterest API Scrapers Copy page Copy page Overview The Pinterest API Suite offers multiple types of APIs, each designed for specific data collection needs from Pinterest. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Discover by Keywords. Interesting Columns : name , following_count , website , follower_count . Posts API This API allows users to collect multiple posts based on a single input. Discovery functionality : - Discover by profile URL. - Discover by Keywords. Interesting Columns : title , content , user_name , likes . Profiles API Collect by URL This API allows users to retrieve detailed Pinterest profile information using the provided profile URL. Input Parameters : URL string required The Pinterest profile URL. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metrics : following_count , follower_count , boards_num , saved . Additional Information : last_updated , posts_page_url , discovery_input . This API allows users to collect detailed insights into a Pinterest profile, including user statistics, engagement metrics, and profile information. Discover by Keywords This API allows users to discover Pinterest profiles based on a specified keyword. Input Parameters : keyword string required The keyword to search for profiles. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metric s: following_count , follower_count , boards_num , saved. Additional Information : last_updated , posts_page_url , discovery_input . This API enables users to find Pinterest profiles related to a specific keyword, offering insights into user statistics, engagement, and profile details. Posts API Collect by URL This API allows users to collect detailed post data from a specific Pinterest post using the provided post URL. Input Parameters : URL string required The Pinterest post URL. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , post_type . For all data points, click here . User Details : user_name , user_url , user_id , followers . Post Metrics : likes , comments_num , comments , categories . Media & Attachments : image_video_url , video_length , attached_files . Hashtags & Discovery : hashtags , discovery_input . This API allows users to retrieve detailed insights into a specific Pinterest post, including user engagement, post content, media, and other related information. Discover by Profile URL This API allows users to retrieve posts from a specific Pinterest profile based on the provided profile URL. Input Parameters : URL string required The Pinterest profile URL from which to collect posts. num_of_posts number The number of posts to collect. If omitted, there is no limit. posts_to_not_include array An array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date ). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date ). Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users tso collect posts from a specific Pinterest profile, allowing for filtering by date, exclusion of specific posts, and retrieval of detailed post data including media, comments, and engagement metrics. Discover by Keywords This API allows users to discover Pinterest posts based on a specific keyword, enabling efficient content discovery. Input Parameters : keyword string required The keyword to search for posts, such as “food” or any other relevant term. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users to search for Pinterest posts based on a specific keyword, providing detailed insights into the content, engagement, media, and associated metrics for efficient discovery. Was this page helpful? Yes No Twitter Quora ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:24
https://docs.brightdata.com/api-reference/web-scraper-api/synchronous-requests#timeout-limit	Synchronous Requests - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Web Scraper API Synchronous Requests Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API Scrape data and return it directly in the response. cURL Copy curl --request POST \ --url https://api.brightdata.com/datasets/v3/scrape \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data ' { "input": [ { "url": "www.linkedin.com/in/bulentakar" } ], "custom_output_fields": "url\|about.updated_on" } ' 200 202 Copy "OK" Web Scraper API Synchronous Requests Copy page This endpoint allows users to fetch data efficiently and ensures seamless integration with their applications or workflows. Copy page POST / datasets / v3 / scrape Try it Scrape data and return it directly in the response. cURL Copy curl --request POST \ --url https://api.brightdata.com/datasets/v3/scrape \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data ' { "input": [ { "url": "www.linkedin.com/in/bulentakar" } ], "custom_output_fields": "url\|about.updated_on" } ' 200 202 Copy "OK" How It Works This synchronous API endpoint allows users to send a scraping request and receive the results in real-time directly in the response, at the point of request - such as a terminal or application - without the need for external storage or manual downloads. This approach streamlines the data collection process by eliminating additional steps for retrieving results. You can specify the desired output format using the format parameter. If no format is provided, the response will default to JSON. Timeout Limit Please note that this synchronous request is subject to a 1 minute timeout limit. If the data retrieval process exceeds this limit, the API will return an HTTP 202 response, indicating that the request is still being processed. In such cases, you will receive a snapshot ID to monitor and retrieve the results asynchronously via the Monitor Snapshot and Download Snapshot endpoints. Example response on timeout: 202 Copy { "snapshot_id" : "s_xxx" , "message" : "Your request is still in progress and cannot be retrieved in this call. Use the provided Snapshot ID to track progress via the Monitor Snapshot endpoint and download it once ready via the Download Snapshot endpoint." } Authorizations Authorization string header required Use your Bright Data API Key as a Bearer token in the Authorization header. How to authenticate: Obtain your API Key from the Bright Data account settings at https://brightdata.com/cp/setting/users Include the API Key in the Authorization header of your requests Format: Authorization: Bearer YOUR_API_KEY Example: Authorization: Bearer b5648e1096c6442f60a6c4bbbe73f8d2234d3d8324554bd6a7ec8f3f251f07df Learn how to get your Bright Data API key: https://docs.brightdata.com/api-reference/authentication Query Parameters dataset_id string required Dataset ID for which data collection is triggered. custom_output_fields string List of output columns, separated by \| (e.g., url\|about.updated_on ). Filters the response to include only the specified fields. Example : "url\|about.updated_on" include_errors boolean Include errors report with the results. format enum<string> default: json Specifies the format of the response (default: ndjson). Available options : ndjson , json , csv Body application/json input object[] required List of input items to scrape. Show child attributes custom_output_fields string List of output columns, separated by \| (e.g., url\|about.updated_on ). Filters the response to include only the specified fields. Example : "url\|about.updated_on" Response 200 text/plain OK The response is of type string . Example : "OK" Was this page helpful? Yes No Asynchronous Requests Crawl API ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:24
https://www.fuse.io/fr/casestudies/zneakrz	Zneakrz 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 Success Stories Web3 Sneaker Marketplace ZNEAKRZ Revolutionizing Sneaker Commerce ZNEAKRZ Web3 Sneaker Marketplace Integrating blockchain technology through Fuse Network has allowed ZNEAKRZ to create a frictionless ecosystem for sneaker enthusiasts. Technology Used: Fuse Network Blockchain Fuse Wallet SDK FuseBox Middleware Available on iOS & Android Useful Links: "Fuse delivered indispensable solutions, accelerating our iteration and testing. Their wallet SDK seamlessly integrated with our needs, featuring crucial elements like gasless transactions and social account recovery, crucial for swift onboarding—making them our ideal partner in this journey." Jeff Lawy at ZNEAKRZ About ZNEAKRZ ZNEAKRZ is making waves as a Web3 sneaker marketplace, disrupting norms and enhancing user experiences through its strategic partnership with Fuse Network. Co-founded by Edwin Vazquez and Jeff Lawy, ZNEAKRZ's roots trace back to Edwin's childhood, where a love for sneakers developed through reselling and sneaker botting due to limited resources. This personal connection laid the foundation for ZNEAKRZ, showcasing a deep understanding of the sneaker market's challenges and opportunities. Together with Fuse Network, ZNEAKRZ is reshaping the industry, prioritizing exclusivity and authenticity. Jeff Lawy Co-Founder Edwin Vasquez Co-Founder One Platform for Buyers & Sellers In the sneaker trading landscape, a prevalent challenge is the necessity for participants to navigate multiple platforms based on their role, leading to a fragmented user experience. Some platforms prioritize sellers, while others lean towards catering to buyers. ZNEAKRZ, however, strategically addresses the needs of both buyers and sellers. By prioritizing a comprehensive approach, ZNEAKRZ establishes itself as a singular, convenient sneaker trading platform, offering the most competitive fees for both parties involved. How Fuse Powers ZNEAKRZ App ZNEAKRZ has harnessed the power of Fuse Network and Wallet SDK to elevate its platform. Through an inventive token system, users seamlessly convert traditional dollars into Zneakerz tokens, circumventing the high transaction fees associated with conventional payment methods. This not only reduces costs for buyers and sellers but also enhances security and efficiency throughout the purchasing process. The platform's success also stems from the ability to build and deliver user-friendly and intuitive experiences on Fuse. Addressing common frustrations in the sneaker market, ZNEAKRZ incorporates key features like drops, auctions, sneaker escrow, and authentication services to deliver a seamless experience, fostering trust and transparency within the community. With ambitious plans for global expansion, the founders aim to bring their innovative approach to sneaker commerce to enthusiasts worldwide. Meet the Team Behind ZNEAKRZ Fuse Meets ZNEAKRZ w/ Co-founders Jeff Lawy & Edwin Vasquez ZNEAKRZ App Walkthrough Download, create a wallet and start trading sneakers! Explore the ZNEAKRZ App with our interactive walkthrough! From exclusive releases to personalized preferences, discover everything you need for an unparalleled sneaker experience. Dive in and unlock the world of ZNEAKRZ! Watch Now More Success Stories Freedom: Real world assets for businesses 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:24
https://docs.brightdata.com/api-reference/web-scraper-api/synchronous-requests#parameter-dataset-id	Synchronous Requests - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Web Scraper API Synchronous Requests Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API Scrape data and return it directly in the response. cURL Copy curl --request POST \ --url https://api.brightdata.com/datasets/v3/scrape \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data ' { "input": [ { "url": "www.linkedin.com/in/bulentakar" } ], "custom_output_fields": "url\|about.updated_on" } ' 200 202 Copy "OK" Web Scraper API Synchronous Requests Copy page This endpoint allows users to fetch data efficiently and ensures seamless integration with their applications or workflows. Copy page POST / datasets / v3 / scrape Try it Scrape data and return it directly in the response. cURL Copy curl --request POST \ --url https://api.brightdata.com/datasets/v3/scrape \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data ' { "input": [ { "url": "www.linkedin.com/in/bulentakar" } ], "custom_output_fields": "url\|about.updated_on" } ' 200 202 Copy "OK" How It Works This synchronous API endpoint allows users to send a scraping request and receive the results in real-time directly in the response, at the point of request - such as a terminal or application - without the need for external storage or manual downloads. This approach streamlines the data collection process by eliminating additional steps for retrieving results. You can specify the desired output format using the format parameter. If no format is provided, the response will default to JSON. Timeout Limit Please note that this synchronous request is subject to a 1 minute timeout limit. If the data retrieval process exceeds this limit, the API will return an HTTP 202 response, indicating that the request is still being processed. In such cases, you will receive a snapshot ID to monitor and retrieve the results asynchronously via the Monitor Snapshot and Download Snapshot endpoints. Example response on timeout: 202 Copy { "snapshot_id" : "s_xxx" , "message" : "Your request is still in progress and cannot be retrieved in this call. Use the provided Snapshot ID to track progress via the Monitor Snapshot endpoint and download it once ready via the Download Snapshot endpoint." } Authorizations Authorization string header required Use your Bright Data API Key as a Bearer token in the Authorization header. How to authenticate: Obtain your API Key from the Bright Data account settings at https://brightdata.com/cp/setting/users Include the API Key in the Authorization header of your requests Format: Authorization: Bearer YOUR_API_KEY Example: Authorization: Bearer b5648e1096c6442f60a6c4bbbe73f8d2234d3d8324554bd6a7ec8f3f251f07df Learn how to get your Bright Data API key: https://docs.brightdata.com/api-reference/authentication Query Parameters dataset_id string required Dataset ID for which data collection is triggered. custom_output_fields string List of output columns, separated by \| (e.g., url\|about.updated_on ). Filters the response to include only the specified fields. Example : "url\|about.updated_on" include_errors boolean Include errors report with the results. format enum<string> default: json Specifies the format of the response (default: ndjson). Available options : ndjson , json , csv Body application/json input object[] required List of input items to scrape. Show child attributes custom_output_fields string List of output columns, separated by \| (e.g., url\|about.updated_on ). Filters the response to include only the specified fields. Example : "url\|about.updated_on" Response 200 text/plain OK The response is of type string . Example : "OK" Was this page helpful? Yes No Asynchronous Requests Crawl API ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:24
https://docs.brightdata.com/api-reference/web-scraper-api/synchronous-requests#parameter-include-errors	Synchronous Requests - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Web Scraper API Synchronous Requests Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API Scrape data and return it directly in the response. cURL Copy curl --request POST \ --url https://api.brightdata.com/datasets/v3/scrape \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data ' { "input": [ { "url": "www.linkedin.com/in/bulentakar" } ], "custom_output_fields": "url\|about.updated_on" } ' 200 202 Copy "OK" Web Scraper API Synchronous Requests Copy page This endpoint allows users to fetch data efficiently and ensures seamless integration with their applications or workflows. Copy page POST / datasets / v3 / scrape Try it Scrape data and return it directly in the response. cURL Copy curl --request POST \ --url https://api.brightdata.com/datasets/v3/scrape \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data ' { "input": [ { "url": "www.linkedin.com/in/bulentakar" } ], "custom_output_fields": "url\|about.updated_on" } ' 200 202 Copy "OK" How It Works This synchronous API endpoint allows users to send a scraping request and receive the results in real-time directly in the response, at the point of request - such as a terminal or application - without the need for external storage or manual downloads. This approach streamlines the data collection process by eliminating additional steps for retrieving results. You can specify the desired output format using the format parameter. If no format is provided, the response will default to JSON. Timeout Limit Please note that this synchronous request is subject to a 1 minute timeout limit. If the data retrieval process exceeds this limit, the API will return an HTTP 202 response, indicating that the request is still being processed. In such cases, you will receive a snapshot ID to monitor and retrieve the results asynchronously via the Monitor Snapshot and Download Snapshot endpoints. Example response on timeout: 202 Copy { "snapshot_id" : "s_xxx" , "message" : "Your request is still in progress and cannot be retrieved in this call. Use the provided Snapshot ID to track progress via the Monitor Snapshot endpoint and download it once ready via the Download Snapshot endpoint." } Authorizations Authorization string header required Use your Bright Data API Key as a Bearer token in the Authorization header. How to authenticate: Obtain your API Key from the Bright Data account settings at https://brightdata.com/cp/setting/users Include the API Key in the Authorization header of your requests Format: Authorization: Bearer YOUR_API_KEY Example: Authorization: Bearer b5648e1096c6442f60a6c4bbbe73f8d2234d3d8324554bd6a7ec8f3f251f07df Learn how to get your Bright Data API key: https://docs.brightdata.com/api-reference/authentication Query Parameters dataset_id string required Dataset ID for which data collection is triggered. custom_output_fields string List of output columns, separated by \| (e.g., url\|about.updated_on ). Filters the response to include only the specified fields. Example : "url\|about.updated_on" include_errors boolean Include errors report with the results. format enum<string> default: json Specifies the format of the response (default: ndjson). Available options : ndjson , json , csv Body application/json input object[] required List of input items to scrape. Show child attributes custom_output_fields string List of output columns, separated by \| (e.g., url\|about.updated_on ). Filters the response to include only the specified fields. Example : "url\|about.updated_on" Response 200 text/plain OK The response is of type string . Example : "OK" Was this page helpful? Yes No Asynchronous Requests Crawl API ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:24
https://git-scm.com/book/sv/v2/Grunder-i-Git-Git-alias	Git - Git alias 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. Kom igång 1.1 Om versionshantering 1.2 En kort historik av Git 1.3 Vad är Git? 1.4 Kommandoraden 1.5 Installera Git 1.6 Använda Git för första gången 1.7 Få hjälp 1.8 Sammanfattning 2. Grunder i Git 2.1 Skaffa ett Git-förvar 2.2 Spara ändringar till förvaret 2.3 Visa historiken 2.4 Ångra saker 2.5 Jobba med fjärrförvar 2.6 Taggning 2.7 Git alias 2.8 Sammanfattning 3. Git förgreningar 3.1 Grenar i ett nötskal 3.2 Grundläggande förgrening och sammanslagning 3.3 Hantera grenar 3.4 Arbetsflöde med grenar 3.5 Fjärrgrenar 3.6 Grenflytt 3.7 Sammanfattning 4. Git på servern 4.1 Protokollen 4.2 Skaffa Git på en server 4.3 Generera din publika SSH-nyckel 4.4 Konvigurera servern 4.5 Git Daemonen 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Alternativ tillhandahållna av tredje part 4.10 Sammanfattning 5. Distribuerade Git 5.1 Distribuerade arbetsflöden 5.2 Medverka i ett projekt 5.3 Underhålla ett projekt 5.4 Sammanfattning 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. Bilaga 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. Bilaga 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. Bilaga 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 Grunder i Git - Git alias Git alias Innan vi avslutar detta kapitel om grundläggande Git, finns det ett litet tips som kan göra din upplevelse av Git lite enklare och mer bekant: alias. Vi kommer inte referera till dem eller anta att du använt dem tidigare i boken, men du bör förmodligen veta hur du använder dem. Git kommer inte automatiskt anta vilket kommando du vill köra om du bara delvis skriver ut det. Om du inte vill skriva hela texten för varje Git-kommandoi, kan du enkelt ställa in ett alias för varje kommando genom att använda git config . Här är några exempel som du kanske vill använda: $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status Detta betyder att istället för att skriva git commit kan du istället skriva git ci . Ju mer du använder Git, så kommer du förmodligen använda andra kommandon flitigt; tveka inte att skapa nya alias för dem. Denna tekniken kan också vara användbar för att skapa kommandon som du tycker borde existera. För att korrigera ett användbarhetsproblem som du påträffat när du tar bort en fil från prepareringsytan kan du lägga till ditt eget kommando för detta scenario: $ git config --global alias.unstage 'reset HEAD --' Detta gör följande kommandon ekvivalenta: $ git unstage fileA $ git reset HEAD -- fileA Det blir lite klarare. Det är också vanligt att lägga till ett last kommando som detta: $ git config --global alias.last 'log -1 HEAD' Nu kan du lätt se den senaste versionen: $ 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> Precis som du ser, kommer Git att ersätta det nya kommandot med vad det är alias för. Kanske vill du köra ett externt kommando istället för ett Git-subkommando. I så fall startar du kommandot med ett ! tecken. Det är användbart om du skiver egna verktyg som fungerar med ett Gitförvar. Vi kan demonstrera genom att lägga till kommandot git visual för att köra 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:24
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#param-url	Instagram API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Instagram API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Posts API Collect by URL Discover by URL Comments API Collect by URL Reels API Collect by URL Discover by URL Social Media APIs Instagram API Scrapers Copy page Copy page Overview The Instagram API Suite offers multiple types of APIs, each designed for specific data collection needs from Instagram. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : N/A Interesting Columns : followers , post_count , post_hashtags , profile_name . Posts API This API allows users to collect multiple posts based on a single input URL (such as an Instagram reels URL, search URL or profile URL). Discovery functionality : - Direct URL of the Instagram reel - Direct URL of the search - Direct URL of the profile Interesting Columns : url , followers , hashtags , engagement_score_view . Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : comment_user , comment , likes_number , replies_number . The suite of APIs is designed to offer flexibility for targeted data collection, where users can input specific URLs to gather detailed post and comment data, either in bulk or with precise filtering options. Profiles API Collect by URL This API allows users to collect detailed data about an Instagram profile by providing the profile URL. It provides a comprehensive overview of an Instagram profile, including business and engagement information, posts, and user details. Input Parameters URL string required The Instagram profile URL. Output Structure Includes comprehensive data points: Page/Profile Details : account , id , followers , posts_count , is_business_account , is_professional_account , is_verified , avg_engagement , profile_name , profile_url , profile_image_link , and more. For all data points, click here . Posts API Collect by URL This API enables users to collect detailed data from Instagram posts by providing a post URL. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Post Details : post_id , description , hashtags , date_posted , num_comments , likes , content_type , video_view_count , video_play_count , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : photos , videos , thumbnail , display_url (link only, not the file itself), audio. Discover by URL This API allows users to discover recent Instagram posts from a public profile by providing the profile URL and specifying additional parameters. Input Parameters URL string required The Instagram profile URL. num_of_posts number The number of recent posts to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date). post_type string Specify the type of posts to collect (e.g., post, reel). Output Structure Includes comprehensive data points: Post Details: post_id , description , hashtags , date_posted , num_comments , likes , video_view_count , video_play_count ,and more. For all data points, click here . Page/Profile Details: user_posted , followers , posts_count , profile_image_link , is_verified , profile_url , is_paid_partnership , partnership_details , user_posted_id Attachments and Media: photos , videos , thumbnail , audio , display_url , content_type , product_type , coauthor_producers , tagged_users . This API is designed to allow for filtering, exclusion of specific posts, and collecting posts by type (regular post or reel) within a defined time frame. It provides detailed post and profile information, making it ideal for data collection and analytics. Comments API Collect by URL This API allows users to collect the latest comments from a specific Instagram post by providing the post URL. This API retrieves the most recent 10 comments along with associated metadata. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Comment Details : comment_id , comment_user , comment_user_url , comment_date , comment , likes_number , replies_number , replies , hashtag_comment , tagged_users_in_comment , and more. For all data points, click here . User Details : user_name , user_id , user_url We provide a limited set of data points about the profile. Post Metadata : post_url , post_user , post_id . Reels API Collect by URL This API allows users to collect detailed data about Instagram reels from public profiles by providing the reel URL. Input Parameters URL string required The Instagram reel URL. Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , tagged_users , num_comments , likes , views , video_play_count , length , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : video_url , thumbnail , audio_url . Discover by URL This API allows users to discover Instagram Reels videos from a profile URL or direct search URL. Input Parameters URL string required The Instagram profile or direct search URL. num_of_posts number The number of recent reels to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering reels in MM-DD-YYYY format. end_date string End date for filtering reels in MM-DD-YYYY format (should be later than start_date ). Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , num_comments , likes , views , video_play_count , top_comments , length , video_url , audio_url , content_id , and more. For all data points, click here . Profile Details : user_posted , followers , posts_count , following . Attachments and Media : video_url , thumbnail , audio_url (link only, not the file itself). This API provides detailed information about Instagram Reels, with filtering options by date range, exclusion of specific posts, and a limit on the number of reels collected. Was this page helpful? Yes No Facebook LinkedIn ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:24
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#discover-by-keywords	Pinterest API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Pinterest API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Discover by Keywords Posts API Collect by URL Discover by Profile URL Discover by Keywords Social Media APIs Pinterest API Scrapers Copy page Copy page Overview The Pinterest API Suite offers multiple types of APIs, each designed for specific data collection needs from Pinterest. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Discover by Keywords. Interesting Columns : name , following_count , website , follower_count . Posts API This API allows users to collect multiple posts based on a single input. Discovery functionality : - Discover by profile URL. - Discover by Keywords. Interesting Columns : title , content , user_name , likes . Profiles API Collect by URL This API allows users to retrieve detailed Pinterest profile information using the provided profile URL. Input Parameters : URL string required The Pinterest profile URL. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metrics : following_count , follower_count , boards_num , saved . Additional Information : last_updated , posts_page_url , discovery_input . This API allows users to collect detailed insights into a Pinterest profile, including user statistics, engagement metrics, and profile information. Discover by Keywords This API allows users to discover Pinterest profiles based on a specified keyword. Input Parameters : keyword string required The keyword to search for profiles. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metric s: following_count , follower_count , boards_num , saved. Additional Information : last_updated , posts_page_url , discovery_input . This API enables users to find Pinterest profiles related to a specific keyword, offering insights into user statistics, engagement, and profile details. Posts API Collect by URL This API allows users to collect detailed post data from a specific Pinterest post using the provided post URL. Input Parameters : URL string required The Pinterest post URL. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , post_type . For all data points, click here . User Details : user_name , user_url , user_id , followers . Post Metrics : likes , comments_num , comments , categories . Media & Attachments : image_video_url , video_length , attached_files . Hashtags & Discovery : hashtags , discovery_input . This API allows users to retrieve detailed insights into a specific Pinterest post, including user engagement, post content, media, and other related information. Discover by Profile URL This API allows users to retrieve posts from a specific Pinterest profile based on the provided profile URL. Input Parameters : URL string required The Pinterest profile URL from which to collect posts. num_of_posts number The number of posts to collect. If omitted, there is no limit. posts_to_not_include array An array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date ). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date ). Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users tso collect posts from a specific Pinterest profile, allowing for filtering by date, exclusion of specific posts, and retrieval of detailed post data including media, comments, and engagement metrics. Discover by Keywords This API allows users to discover Pinterest posts based on a specific keyword, enabling efficient content discovery. Input Parameters : keyword string required The keyword to search for posts, such as “food” or any other relevant term. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users to search for Pinterest posts based on a specific keyword, providing detailed insights into the content, engagement, media, and associated metrics for efficient discovery. Was this page helpful? Yes No Twitter Quora ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:24
https://git-scm.com/book/zh/v2/%e8%b5%b7%e6%ad%a5-%e5%91%bd%e4%bb%a4%e8%a1%8c	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 1.4 起步 - 命令行命令行 Git 有多种使用方式。你可以使用原生的命令行模式，也可以使用 GUI 模式，这些 GUI 软件也能提供多种功能。在本书中，我们将使用命令行模式。这是因为首先，只有在命令行模式下你才能执行 Git 的所有命令，而大多数的 GUI 软件只实现了 Git 所有功能的一个子集以降低操作难度。如果你学会了在命令行下如何操作，那么你在操作 GUI 软件时应该也不会遇到什么困难，但是，反之则不成立。此外，由于每个人的想法与侧重点不同，不同的人常常会安装不同的 GUI 软件，但所有人一定会有命令行工具。假如你是 macOS 用户，我们希望你懂得如何使用终端（Terminal）；假如你是 Windows 用户，我们希望你懂得如何使用命令提示符（Command Prompt）或 PowerShell。如果你尚未掌握以上技能，我们建议你先停下来快速学习一下，本书中的讲述和举例将用到这些技能。 prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://git-scm.com/book/sv/v2/Grunder-i-Git-Spara-%c3%a4ndringar-till-f%c3%b6rvaret	Git - Spara ändringar till förvaret 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. Kom igång 1.1 Om versionshantering 1.2 En kort historik av Git 1.3 Vad är Git? 1.4 Kommandoraden 1.5 Installera Git 1.6 Använda Git för första gången 1.7 Få hjälp 1.8 Sammanfattning 2. Grunder i Git 2.1 Skaffa ett Git-förvar 2.2 Spara ändringar till förvaret 2.3 Visa historiken 2.4 Ångra saker 2.5 Jobba med fjärrförvar 2.6 Taggning 2.7 Git alias 2.8 Sammanfattning 3. Git förgreningar 3.1 Grenar i ett nötskal 3.2 Grundläggande förgrening och sammanslagning 3.3 Hantera grenar 3.4 Arbetsflöde med grenar 3.5 Fjärrgrenar 3.6 Grenflytt 3.7 Sammanfattning 4. Git på servern 4.1 Protokollen 4.2 Skaffa Git på en server 4.3 Generera din publika SSH-nyckel 4.4 Konvigurera servern 4.5 Git Daemonen 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Alternativ tillhandahållna av tredje part 4.10 Sammanfattning 5. Distribuerade Git 5.1 Distribuerade arbetsflöden 5.2 Medverka i ett projekt 5.3 Underhålla ett projekt 5.4 Sammanfattning 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. Bilaga 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. Bilaga 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. Bilaga 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 Grunder i Git - Spara ändringar till förvaret Spara ändringar till förvaret Nu skall du ha ett äkta Git-förvar framför dig på din lokala maskin, och en utcheckad eller arbetskopia av alla dess filer. Vanligtvis vill du nu göra ändringar och spara ögonblicksbilder av dessa ändringarna till ditt förvar varje gång projektet når ett tillstånd du vill spara. Kom ihåg att varje fil i din arbetskatalog kan vara i en av två tillstånd: spårad eller ospårad . Spårade filer är filer som fanns med i den tidigare ögonblicksbilden; de kan vara omodifierade, modifierade eller förberedda. I korthet kan man säga att spårade filer är de filer som Git känner till. Ospårade filer är allt annat — filer i din arbetskatalog som inte var med i din tidigare ögonblicksbild och som inte ligger på prepareringsytan. När du först klonar ett förvar kommer alla filer att vara spårade och omodifierade, eftersom Git precis checkat ut dem utan att du hunnit ändra något. När du ändrar i filer kommer Git markera dem som modifierade, eftersom du har ändrat dem sedan din föregående sparade version. Under arbetets gång väljer du att frysa de modifierade filerna och sedan sparar du dessa ändringarna, och sedan börjar det om på nytt. Figur 8. Livscykeln för statusen hos dina filer. Kontrollera status på dina filer Det huvudsakliga verktyget som används för att avgöra vilka filer är i vilket steg är kommandot git status . Om du kör det kommando direkt efter att ha klonat ett förvar, kommer du se något liknande detta: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean Detta betyder att du har en ren arbetskatalog, vilket i andra termer betyder att inga av dina spårade filer är modifierade. Git ser heller inte några ospårade filer, då de i sådant fall skulle listas här. Slutligen talar kommandot om vilken gren du är på och informerar den om att den inte har divergerat gentemot samma gren på servern. För nu kan du anta att grenen alltid är “master”, vilket är standard; du behöver inte bry dig om detta ännu. Git förgreningar kommer gå igenom grenar och referenser i detalj. Låt oss säga att du lägger till en ny fil i ditt projekt, en simpel README fil. Om filen inte existerar sedan tidigare och du kör git status , kommer du se din ospårade fil: $ 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) Som synes är din nya fil README ospårad eftersom den ligger under rubriken “Untracked files” (Ospårade filer) i din statusutskrift. Ospårad betyder egentligen bara att Git ser en fil som inte finns med i din tidigare ögonblicksbild (version); Git kommer inte inkludera den i kommande ögonblicksbilder om du inte uttryckligen talar om för Git att du vill göra det. Anledningen är för att du inte oavsiktligen skall börja inkludera generarde binärfiler eller andra filer som du inte har för avsikt att inkludera. Du vill ju såklart inkludera filen README , så då gör vi det. Spåra nya filer För att börja spåra en ny fil använder du kommandot git add . För att börja spåra README kör du detta kommando: $ git add README Om du kör ditt statuskommando igen, kommer du se att din README -fil nu är spårad och förberedd för att ingå i nästa version: $ 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 Att filen är förberedd vet du eftersom den finns under rubriken “Changes to be committed” (Ändringar som kommer att sparas). Om du låser ändringen nu kommer filen som den såg ut när du körde kommandot git add att komma med i den kommande ögonblicksbilden. Dra dig till minnes när du förut körde git init så körde du sedan git add <filer> — det var för att börja spåra filer i ditt förvar. Kommandot git add tar en sökväg till antingen en fil eller en katalog; om det är en katalog kommer alla filer i katalogen läggas till rekursivt. Förbereda modifierade filer Låt oss ändra en fil som var spårad sedan tidigare. Om du ändrar en tidigare spårad fil kallad CONTRIBUTING.md och sedan kör kommandot git status igen kommer du få något som liknar detta: $ 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 Filen CONTRIBUTING.md visas under avsnittet “Changes not staged for commit” (Ändringar som inte är markerade att ingå i nästa version) — vilket betyder att en spårad fil har modifierats i arbetskatalogen men ännu inte valts att ingå i nästa version. För att förbereda den, kör du kommandot git add . git add har flera användningsområden — du använder det för att börja spåra nya filer, för att förbereda filer, och för att göra andra saker som att markera sammanslagningskonflikter som lösta. Det kan vara lättare att tänka på det som ett “lägg till exakt detta innehåll i nästa version” snarare än “lägg till denna filen till projektet”. Låt os köra git add nu för att förberade filen CONTRIBUTING.md och sedan köra `git status`igen: $ 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 Båda filer är förberedda och kommer att ingå i din nästa version. Anta att du i detta läget kommer på att du vill göra en liten ändring i CONTRIBUTING.md innan du sparar en version med den. Du öppnar filen igen och gör ändringen, och är nu redo för att göra en förbindning. Låt oss först köra git status en gång till: $ 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 Vad tusan betyder det? Nu är filen CONTRIBUTING.md listad som både förberedd för nästa version och modifierad för att inte ingå i nästa version. Hur är det möjligt? Det visar sig att Git förbereder filen så som den ser ut just när du kör kommandot git add . Om du sparar en version nu, kommer den version av CONTRIBUTING.md som den var då du senast körde kommandot git add att ingå i versionen, inte så som den ser ut i din arbetskatalog när du kör git commit . Om du modifierar en fil efter att du kör git add , så måste du köra git add igen för att välja den senaste versionen av filen: $ 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 Kort status Medan utskriften från git status är ganska omfattande är den också ganska långrandig. Git har också en kort statusflagga så att du kan se dina ändringar mer kompakt. Om du kör kommandot git status -s eller git status --short kommer du få en mer kompakt utskrift: $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt Nya filer som inte spårats har ?? till vänster om namnet, nya filer som lagts till prepareringsytan har ett A , modifierade filer har ett M , och så vidare. Det är två kolumner till vänster om filnamnet i utskriften — den vänstra kolumnen indikerar statusen hos prepareringsytan (vad som kommer ingå i nästa version), och den högra kolumnen indikerar status för arbetsträdet. I det tidigare exemplet är filen README modifierad i arbetsträdet men inte förberedd att ingå i nästa version, medan filen lib/simplegit.rb är modifierad och förberedd att ingå i nästa version. Filen Rakefile var modifierad, förberedd för nästa version och sedan modifierad igen, så den innehåller ändringar som är både förberedda och oförberedda. Ignorera filer Ofta har du en uppsättning filer som du inte vill att Git automatiskt lägger till eller ens visar som ospårade. Till dessa hör i regel automatgenerarde filer såsom loggfiler, eller filer som skapas av ditt byggsystem. I sådana fall kan du skapa en fil med namnet .gitignore som listar de mönster filerna har. Här är ett exempel på en .gitignore -fil: $ cat .gitignore .[oa] ~ Den första raden talar om för Git att ignorera alla filer som slutar på “.o” eller “.a” — objekt- och arkivfiler som kan skapas när du bygger din kod. Den andra raden talar om för Git att ingorera alla filer vars namn slutar med tilde ( ~ ), som används av många texteditorer såsom Emacs för att markera temporära filer. Du kan också inkludera log-, tmp- och pid-kataloger, automatiskt genererad dokumentation, och så vidare. Att skapa en .gitignore -fil för ditt nya förvar innan du börjar arbeta med det är generellt en bra idé så att du inte oavsiktigt versionshanterar filer som du inte vill ha i ditt Git-förvar. De mönster du kan använda i .gitignore -filen måste följa dessa regler: Blanka rader eller rader som börjar med # ignoreras. Vanliga glob-mönster fungerar, och kommer att appliceras rekursivt genom hela arbetsträdet. Använd ett inledande snedstreck ( / ) i ett mönster för att undvika rekursivitet. Avsluta ett mönster med ett snedstreck ( / ) för att specificera en katalog. Genom att inleda med ett utropstecken( ! ) får mönstret en logiskt motsatt betydelse. Glob-mönster är simplifierade reguljära uttryck som skal använder. En asterisk ( * ) matchar en eller flera tecken; [abc] matchar en av tecknen inom hakparentesen (i detta fallet a, b, eller c), ett frågetecken ( ? ) matchar ett enskilt tecken, och hakparenteser som omsluter tecken separerat med ett bindestreck ( [0-9] ) matchar ett tecken mellan dem (i detta fallet från och med 0 till och med 9). Du kan också använda två asterisker för att matcha nästlade kataloger; a/*/z skulle således matcha a/z , a/b/z , a/b/c/z , och så vidare. Här är ytterligare ett exempel på en .gitignore -fil: # ignorera alla .a filer .a # men spåra lib.a, även om du ignorerar .a filer enligt regeln ovan !lib.a # ignorera enbart TODO-filen i den aktuella katalogen, inte underkatalog/TODO. /TODO # ignorera alla filer i kataloger som heter build build/ # ignorera doc/notes.txt, men inte doc/server/arch.txt doc/.txt # ignorera alla .pdf-filer i doc-katalogen och någon av dess underkataloger doc//.pdf Tips GitHub underhåller en ganska omfattande lista av bra exempel på .gitignore -filer för dussintals projekt och språk på https://github.com/github/gitignore om du vill ha en till ditt projekt. Notera I det enklaste fallet kan ett förvar ha en enda .gitignore -fil i sin rotkatalog, vilken appliceras rekursivt i hela förvaret. Det är emellertid möjligt att ha flera .gitignore -filer i underkataloger. Reglerna i de nästlade .gitignore -filerna appliceras endast på filer i och under den katalåg vari filen själv finns. (Linuxkärnans förvar har 206 .gitignore -filer.) Det ligger utanför denna boks omfattning att gå in i detalj på användning av flera .gitignore -filer; se man gitignore för detaljer. Visa dina förberedda och oförberedda ändringar Om kommandot git status är för vagt för dig — du vill veta exakt vad du ändrade, inte bara vilka filer som ändrats — kan du använda kommandot git diff . Vi kommer att gå igenom git diff i mer detalj senare, men du kommer förmodligen oftast att använda det för att svara på följande frågor: Vad har du ändrat men ännu inte förberett? Och vad har du förberett och som du kommer att spara i nästa version? Trots att git status svarar på frågorna väldigt generellt genom att lista filnamnen, kommer `git diff`visa dig exakt vilka rader som lagts till och tagits bort — patchen, som det också kallas. Låt oss säga att du editerar och förbereder README -filen igen och sedan ändrar CONTRIBUTING.md -filen utan att förbereda den. Om du kör ditt git status -kommando, kommer du återigen att se något liknande detta: $ 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 För att se vad du ändrat men ännu inte förberett, skriv git diff utan några andra argument: $ 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 Kommandot jämför det som finns i din arbetskatalog med vad som finns på din prepareringsyta. Resultatet ger dig ändrignarna som du gjort som du ännu inte förberett. Om du vill se vad du förberett och som kommer att ingå i din nästa version, kan du använda git diff --staged . Detta kommando jämför dina ändringar som kommer ingå i din nästa version med din senast sparade version: $ 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 Viktigt att notera är att git diff i sig självt inte visar alla ändringar genomförda sedan din senaste version — bara ändringar som ännu inte kommer ingå i nästa version. Om du har förberett alla dina ändringar att ingå i nästa version, kommer git diff inte att ge någon utskrift. Ytterligare ett exempel, om du förbereder filen CONTRIBUTING.md och sedan ändrar den, kan du använda git diff för att se ändringarna i filen som är förberedda och ändringarna som är oförberedda. Om vår miljö ser ut såhär: $ 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 Nu kan du använda git diff för att se vad som fortfarande är oförberett: $ 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 och git diff --cached för att se vad du förberett hittils ( --staged och --cached är synonymer): $ 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 Notera Git Diff i ett externt verktyg Vi kommer att fortsätta använda git diff på olika sätt under resten av boken. Det finns ytterligare ett sätt att titta på dessa skillnader om du föredrar ett grafiskt eller externt diff-visningsprogram istället. Om du kör git difftool iställlet för git diff , kan du visa vilken som helst av dessa skillnader i program som emerge, vimdiff och många fler (inklusive kommersiella produkter). Kör git difftool --tool-help för att se vad som finns tillgängligt på ditt system. Spara dina ändringar När din prepareringsyta innehåller det du vill, kan du låsa dina ändringar. Kom ihåg att allt som fortfarande är oförberett — alla filer du har skapat eller modifierat sedan du körde git add sedan du editerat dem — inte kommer att ingå i denna version. De kommer fortfarande vara modifierade filer på din hårddisk. I detta fallet, anta att när du sist körde git status så såg du att allt var förberett och du är redo att låsa dina ändringar. Det enklaste sättet att spara en version på är att skriva git commit : $ git commit När du gör det startas din editor. (Det är den editor som är satt i ditt skals miljövariabel EDITOR — vanligtvis vim eller emacs, även om du kan konfigurera den till vilken du vill genom att använda kommandot git config --global core.editor som du såg i Kom igång ). Editorn visar följande text (detta exempel är en Vim-skärm): # 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 Du kan se att standardmeddelandet innehåller den senaste utskriften från kommandot git status bortkommenterat och en tom rad högst upp. Du kan ta bort dessa kommentarer och skriva in ditt versionsmeddelande, eller så lämnar du dem kvar för att hjälpa dig komma ihåg vad du håller på att spara. (För en uttryckligare påminnelse av vad du modifierat, så kan du ge flaggan -v till git commit . Gör du det, får du också diffen av din ändring i editorn så du kan se exakt vilka ändringar du sparar.) När du avslutar editor, skapar Git en version med ditt meddelande (med kommentarer och diffar borttagna). Alterantivt, så kan du ange ditt versionsmeddelande samtidigt som du ger kommandot commit , genom att specificera det efter flaggan -m , såhär: $ 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 Nu har du skapat din första version! Du kan se att versionen har gett dig lite utskrifter om sig själv: vilken gren du sparade på ( master ), vilken SHA-1 checksumma den har ( 463dc4f ), hur många filer som ändrats, samt statistik om antal rader som lagts till och tagits bort i versionen. Kom ihåg att versionen sparar ögonblicksbilden som du satt upp i din prepareringsyta. Allt som du inte förberedde är fortfarande kvar och är modifierat; du kan göra ytterligare en förbidning för att lägga det till din historik. Varje gång du sparar en version så sparar du en ögonblicksbild av ditt projekt som du kan återgå till eller jämföra med vid ett senare tillfälle. Hoppa över prepareringsytan Även om det kan vara fantastiskt användbart att skapa versioner precis som du vill ha dem är prepareringsytan ibland lite för komplex för vad du behöver i ditt arbetsflöde. Om du vill hoppa över den, så erbjuder Git en enkel genväg. Lägger du till växeln -a till kommandot git commit så kommer varje fil som är spårad av Git att automatiskt läggas till prepareringsytan innan en version sparas, så att du kan hoppa över delen med 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(-) Lägg märke till hur du inte behöver köra git add på filen CONTRIBUTING.md innan du skapar din version i detta fallet. Det är eftersom flaggan -a inkluderar alla ändrade filer. Detta är bekvämt, men var försiktig; ibland kommer flaggan göra så att du inkluderar oönskade ändringar. Ta bort filer För att ta bort filer från Git måste du ta bort dem från dina spårade filer (eller mer korrekt, ta bort dem från din prepareringsyta) och sedan spara en version. Kommandot git rm gör just deft, och tar även bort filen från din arbetskatalog så att du inte ser den som en ospårad fil nästa gång. Om du bara tar bort filen från din arbetskatalog kommer den att visas under rubriken “Changes not staged for commit” (det vill säga, oförberedd ) i utskriften från 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") Om du sedan kör git rm , kommer den att förbereda filen för borttagning: $ 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 Nästa gång du sparar en version kommer filen vara borta och inte längre spårad. Om du modifierar filen eller redan har lagt den till din prepareringsyta, måste du tvinga fram borttagning med flaggan -f . Detta är av säkerhetsskäl för att förhindra oavsiktlig borttagning av data som inte har sparats i en ögonblicksbild och som därmed inte kan återskapas av Git. Ytterligare en användbar sak du kan tänkas vilja göra är att behålla filen i din arbetskatalog men ta bort den från din prepareringsyta. Med andra ord kan du vilja ha kvar filen på din hårddisk men inte att Git skall spåra den något mer. Detta är speciellt användbart om du glömde lägga till något till din .gitignore -fil och oavsiktigt förberedde filen, som en stor loggfil eller ett gäng kompilerade .a -filer. För att göra detta, använd växeln --cached : $ git rm --cached README Du kan ange filer, kataloger, och filnamnsmönster till kommandot git rm . Det betyder att du kan göra saker som: $ git rm log/\.log Notera det omvända snedstrecket ( \ ) framför . Detta är nödvändigt eftersom at Git gör sin egna filnamnsexpansion utöver ditt skals filnamnsexpansion. Detta kommandot tar bort alla filer som har filändelsen .log i katalogen log/ . Eller, så kan du göra något liknande detta: $ git rm \*~ Detta kommandot tar bort alla filer som slutar med ~ . Flytta filer Olikt många andra versionshanteringssystem hatnerar inte Git uttryckligen filförflyttningar. Om du byter namn på en fil i Git så sparas ingen metadata i Git som berättar att du ändrat namnet på filen. Dock är Git ganska sofistikerat när det gäller att ta reda på det — vi kommer att gå igenom det inom kort. Det kan tyckas lite förvirrande att Git då har ett flyttkommando, mv . Om du vill byta namn på en fil i Git kan du göra något i stil med: $ git mv file_from file_to och det funkar bra. Faktum är att om du kör något liknande det och kollar på statusen så kommer du se att Git antar att det rör sig om en namnändring: $ 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 Det är dock samma sak som att göra något i stil med detta $ mv README.md README $ git rm README.md $ git add README Git räknar ut att det är en filnamnsändring implicit, så det spelar ingen roll om du byter namn på en fil på det ena eller andra sättet. Den engentliga skillnaden är att git mv är ett kommando istället för tre — det är en bekvämlighetsfunktion. Än viktigare är att du kan använda vilket verktyg som helst för att döpa om filen och ta i håll med lägga till/ta bort senare, innan du sparar din version. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:24
https://git-scm.com/book/tl/v2/Pag-branch-ng-Git-Mga-Daloy-ng-Trabaho-sa-Pag-branch	Git - Mga Daloy ng Trabaho sa Pag-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.4 Pag-branch ng Git - Mga Daloy ng Trabaho sa Pag-branch Mga Daloy ng Trabaho sa Pag-branch Ngayon na mayroon ka nang mga batayan sa pag-branch at pag-merge down, ano ang maaari o dapat mong gawin sa mga ito? Sa seksyong ito, sasakupin natin ang ilang karaniwang mga daloy ng trabaho na ginagawang posible ang magaan na pag-branch, upang ikaw ay makapagpasya kung gusto mong isama ito sa iyong sariling development cycle. Matagal na Tumatakbong mga Branch Dahil ang Git ay gumagamit ng isang simpleng three-way na merge, ang pag-merge mula sa isang branch patungo sa iba pa nang maraming beses sa isang mahabang panahon ay kadalasang madaling gawin. Ang ibig sabihin nito ay maaari kang magkaroon ng iilang mga branch na palaging nakabukas at magagamit mo sa iba’t ibang mga yugto ng iyong development cycle; maaari kang regular na mag-merge mula sa ilan sa kanila patungo sa mga iba pa. Karamihan sa mga developer ng Git ay mayroong isang daloy ng trabaho na tumatanggap ng ganitong paraan, katulad ng pagkakaroon ng code na buong matatag sa kanilang master na branch — posibleng code lamang na na-release o iri-release. Mayroon silang ibang kahilera na branch na nakapangalang develop o next na tinatrabaho nila o ginagamit upang i-test ang katatagan — ito ay hindi kinakailangang palaging matatag, ngunit tuwing ito ay makakakuha ng isang matatag na estado, maaari itong i-merge sa master . Ginagamit ito upang maka-pull sa paksa na mga branch (maikling buhay na mga branch, katulad ng iss53 na branch kamakailan lamang) kapag handa na ang mga ito, upang siguraduhing sila ay pasado sa lahat ng mga pagsubok at hindi magpapakilala ng mga bug. Sa katunayan, tinatalakay natin ang tungkol sa mga pointer na lumilipat paitaas sa linya ng mga commit na iyong ginagawa. Ang matatag na mga branch ay mas malayo sa ibaba sa linya ng iyong kasaysayang ng commit, at ang pinakabago na mga branch ay malayo sa itaas ng kasaysayan. Figure 26. Isang linear na pagtanaw sa progresibong-stabilidad ng pag-branch Ito ay karaniwang mas madaling pag-isipan tungkol sa kanila bilang mga lalagyan ng trabaho, kung saan ang mga pangkat ng commit ay magtatapos sa isang mas matatag na lalagyan kapag sila ay ganap nang nasubukan. Figure 27. Isang “silo” na pagtanaw sa progresibong-stabilidad ng pag-branch Maaari kang manatiling gumawa nito sa ilang mga antas ng stabilidad. Ilang mas malaking mga proyekto ay mayroon ding proposed o pu (iminungkahi na mga update) na branch na may napagsama-sama na mga branch na maaaring hindi pa handang pumunta sa next o master na branch. Ang ideya nito ay ang iyong mga branch ay nasa iba’t ibang antas ng stabilidad; kapag nakaabot sila sa isang mas matatag na antas, sila ay imi-merge sa branch na nasa itaas nila. Muli, ang pagkakaroon ng maramihang matagal na tumatakbong mga branch ay hindi kinakailangan, ngunit ito ay kadalasang kapaki-pakinabang, lalo na kapag ikaw ay nakikipagtungo sa sobrang malaki o kumplikadong mga proyekto. Paksa na mga Branch Ang paksa na mga branch, gayunpaman, ay kapaki-pakinabang sa mga proyekto sa anumang laki. Isang paksa na branch ay isang maikling-buhay na branch na ginagawa mo at gagamitin para sa isang solong partikular na tampok o may kaugnayan na trabaho. Ito ay isang bagay na malamang na hindi mo pa nagawa gamit ang isang VCS dati dahil ito ay kadalasang sobrang magastos upang ilikha at i-merge sa mga branch. Nakita mo ito sa huling seksyon sa iss53 at hotfix na mga branch na iyong ginawa. Gumawa ka ng ilang mga commit sa mga iyon at direktang binura ang mga iyon pagkatapos mong i-merge ang mga ito sa iyong pangunahing branch. Ang pamamaraang ito ay nagpapahintulot sa iyo upang mag context-switch nang mabilis at ganap — dahil ang iyong trabaho ay hiwalay sa mga silo kung saan lahat ng mga pagbabago sa branch na iyo ay may gagawin sa paksang iyon, mas madaling tingnan kung ano ang nangyari sa panahon ng code review at ganoon. Maaari mong panatilihin ang mga pagbabago doon sa ilang mga minuto, mga araw, o mga buwan, at i-merge in ang mga iyon kapag sila ay handa na, kahit sa anumang pagkakaayos sila nabuo o tinrabaho. Isaalang-alang ang isang halimbawa sa paggawa ng ilang trabaho (sa master ), pag-branch off para sa isang isyu ( iss91 ), pagtatrabaho nito sa isang saglit, pag-branch off sa pangalawang branch upang subukan ang ibang paraan ng pag-asikaso ng parehong bagay ( iss91v2 ), pagpunta pabalik sa iyong master na branch at pagtatrabaho dito sa mahabang sandali, at pagkatapos ay mag-branch off doon para gumawa ng ilang trabaho na hindi ka siguradong isang magandang ideya ( dumbidea na branch). Ang iyong kasaysayan ng commit ay magmumukhang katulad nito: Figure 28. Maramihang paksa na mga branch Ngayon, sabihin nating ikaw ay nakapagpasya na pinakagusto mo ang pangalawang solusyon sa iyong isyu ( iss91v2 ); at ipinakita mo ang dumbidea na branch sa iyong katrabaho, and ito ay napatunayang henyo. Maaari mong itapon ang orihinal na iss91 na branch (mawawala ang mga commit na C5 at C6 ) at i-merge in ang dalawang iba pa. Ang iyong kasaysayan ngayon ay magmumukhang katulad nito: Figure 29. Kasaysayan pagkatapos ng pag-merge ng dumbidea at iss91v2 Pupunta tayo sa mas maraming detalye tungkol sa iba’t ibang posibleng mga daloy ng trabaho para sa iyong Git na proyekto sa Distributed Git , kaya bago ka makapagpasya kung anong pamamaraan ng pag-branch ang gagamitin ng iyong susunod na proyekto, siguraduhing basahin ang kabanatang iyon. Importanteng tandaan tuwing ginagawa mo lahat ng mga ito na ang mga branch na ito ay ganap na lokal. Kapag ikaw ay nag-branch at nag-merge, ang lahat ng bagay ay tinatapos lamang sa iyong Git na repositoryo — walang server na komunikasyon ang nagaganap. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:25
https://id-id.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Frootstock.io	Facebook Facebook Email atau telepon Kata Sandi Lupa akun? Buat Akun Baru Anda Diblokir Sementara Anda Diblokir Sementara Sepertinya Anda menyalahgunakan fitur ini dengan menggunakannya terlalu cepat. Anda dilarang menggunakan fitur ini untuk sementara. Back Bahasa Indonesia 한국어 English (US) Tiếng Việt ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Daftar Masuk Messenger Facebook Lite Video Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Konten Meta AI lainnya Instagram Threads Pusat Informasi Pemilu Kebijakan Privasi Pusat Privasi Tentang Buat Iklan Buat Halaman Developer Karier Cookie Pilihan Iklan Ketentuan Bantuan Pengunggahan Kontak & Non-Pengguna Pengaturan Log aktivitas Meta © 2026	2026-01-13T09:29:25
https://docs.brightdata.com/api-reference/web-scraper-api/synchronous-requests#parameter-custom-output-fields	Synchronous Requests - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Web Scraper API Synchronous Requests Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API Scrape data and return it directly in the response. cURL Copy curl --request POST \ --url https://api.brightdata.com/datasets/v3/scrape \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data ' { "input": [ { "url": "www.linkedin.com/in/bulentakar" } ], "custom_output_fields": "url\|about.updated_on" } ' 200 202 Copy "OK" Web Scraper API Synchronous Requests Copy page This endpoint allows users to fetch data efficiently and ensures seamless integration with their applications or workflows. Copy page POST / datasets / v3 / scrape Try it Scrape data and return it directly in the response. cURL Copy curl --request POST \ --url https://api.brightdata.com/datasets/v3/scrape \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data ' { "input": [ { "url": "www.linkedin.com/in/bulentakar" } ], "custom_output_fields": "url\|about.updated_on" } ' 200 202 Copy "OK" How It Works This synchronous API endpoint allows users to send a scraping request and receive the results in real-time directly in the response, at the point of request - such as a terminal or application - without the need for external storage or manual downloads. This approach streamlines the data collection process by eliminating additional steps for retrieving results. You can specify the desired output format using the format parameter. If no format is provided, the response will default to JSON. Timeout Limit Please note that this synchronous request is subject to a 1 minute timeout limit. If the data retrieval process exceeds this limit, the API will return an HTTP 202 response, indicating that the request is still being processed. In such cases, you will receive a snapshot ID to monitor and retrieve the results asynchronously via the Monitor Snapshot and Download Snapshot endpoints. Example response on timeout: 202 Copy { "snapshot_id" : "s_xxx" , "message" : "Your request is still in progress and cannot be retrieved in this call. Use the provided Snapshot ID to track progress via the Monitor Snapshot endpoint and download it once ready via the Download Snapshot endpoint." } Authorizations Authorization string header required Use your Bright Data API Key as a Bearer token in the Authorization header. How to authenticate: Obtain your API Key from the Bright Data account settings at https://brightdata.com/cp/setting/users Include the API Key in the Authorization header of your requests Format: Authorization: Bearer YOUR_API_KEY Example: Authorization: Bearer b5648e1096c6442f60a6c4bbbe73f8d2234d3d8324554bd6a7ec8f3f251f07df Learn how to get your Bright Data API key: https://docs.brightdata.com/api-reference/authentication Query Parameters dataset_id string required Dataset ID for which data collection is triggered. custom_output_fields string List of output columns, separated by \| (e.g., url\|about.updated_on ). Filters the response to include only the specified fields. Example : "url\|about.updated_on" include_errors boolean Include errors report with the results. format enum<string> default: json Specifies the format of the response (default: ndjson). Available options : ndjson , json , csv Body application/json input object[] required List of input items to scrape. Show child attributes custom_output_fields string List of output columns, separated by \| (e.g., url\|about.updated_on ). Filters the response to include only the specified fields. Example : "url\|about.updated_on" Response 200 text/plain OK The response is of type string . Example : "OK" Was this page helpful? Yes No Asynchronous Requests Crawl API ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:25
https://git-scm.com/book/id/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. 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 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 {plus} button in the top toolbar next to your username as seen in The “New repository” dropdown. . Figure 110. The “Your repositories” area. Figure 111. The “New repository” dropdown. This takes you to the “new repository” form: Figure 112. 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 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 HTTP 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 HTTP 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 HTTP 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 113. 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 114. 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 Arudino 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 115. 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 http://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 116. 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” buton 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 117. 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 118. 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 119. 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 120. 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 121. Notification center options. The two choices are to get notifications over “Email” and over “Web” and you can choose either, niether 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 122. 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 it’s name in the left hand sidebar. You can also acknowledge the notifiction by clicking the checkmark icon next to any notification, or acknowledge all of the notifictions 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 123. 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 124. 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 125. Transfer a project to anther 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 it’s 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:25
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:25
https://www.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 투표 정보 센터 개인정보처리방침 개인정보 보호 센터 정보 광고 만들기 페이지 만들기 개발자 채용 정보 쿠키 AdChoices 이용 약관 고객 센터 연락처 업로드 및 비사용자 설정 활동 로그 Meta © 2026	2026-01-13T09:29:25
https://git-scm.com/book/tl/v2/Distributed-Git-Contributing-to-a-Project	Git - Contributing to 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. 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 5.2 Distributed Git - Contributing to a Project Contributing to a Project The main difficulty with describing how to contribute to a project are the numerous variations on how to do that. Because Git is very flexible, people can and do work together in many ways, and it’s problematic to describe how you should contribute — every project is a bit different. Some of the variables involved are active contributor count, chosen workflow, your commit access, and possibly the external contribution method. The first variable is active contributor count — how many users are actively contributing code to this project, and how often? In many instances, you’ll have two or three developers with a few commits a day, or possibly less for somewhat dormant projects. For larger companies or projects, the number of developers could be in the thousands, with hundreds or thousands of commits coming in each day. This is important because with more and more developers, you run into more issues with making sure your code applies cleanly or can be easily merged. Changes you submit may be rendered obsolete or severely broken by work that is merged in while you were working or while your changes were waiting to be approved or applied. How can you keep your code consistently up to date and your commits valid? The next variable is the workflow in use for the project. Is it centralized, with each developer having equal write access to the main codeline? Does the project have a maintainer or integration manager who checks all the patches? Are all the patches peer-reviewed and approved? Are you involved in that process? Is a lieutenant system in place, and do you have to submit your work to them first? The next variable is your commit access. The workflow required in order to contribute to a project is much different if you have write access to the project than if you don’t. If you don’t have write access, how does the project prefer to accept contributed work? Does it even have a policy? How much work are you contributing at a time? How often do you contribute? All these questions can affect how you contribute effectively to a project and what workflows are preferred or available to you. We’ll cover aspects of each of these in a series of use cases, moving from simple to more complex; you should be able to construct the specific workflows you need in practice from these examples. Commit Guidelines Before we start looking at the specific use cases, here’s a quick note about commit messages. Having a good guideline for creating commits and sticking to it makes working with Git and collaborating with others a lot easier. The Git project provides a document that lays out a number of good tips for creating commits from which to submit patches — you can read it in the Git source code in the Documentation/SubmittingPatches file. First, your submissions should not contain any whitespace errors. Git provides an easy way to check for this — before you commit, run git diff --check , which identifies possible whitespace errors and lists them for you. Figure 57. Output of git diff --check . If you run that command before committing, you can tell if you’re about to commit whitespace issues that may annoy other developers. Next, try to make each commit a logically separate changeset. If you can, try to make your changes digestible — don’t code for a whole weekend on five different issues and then submit them all as one massive commit on Monday. Even if you don’t commit during the weekend, use the staging area on Monday to split your work into at least one commit per issue, with a useful message per commit. If some of the changes modify the same file, try to use git add --patch to partially stage files (covered in detail in Staging na Interactive ). The project snapshot at the tip of the branch is identical whether you do one commit or five, as long as all the changes are added at some point, so try to make things easier on your fellow developers when they have to review your changes. This approach also makes it easier to pull out or revert one of the changesets if you need to later. Pagsulat muli ng Kasaysayan describes a number of useful Git tricks for rewriting history and interactively staging files — use these tools to help craft a clean and understandable history before sending the work to someone else. The last thing to keep in mind is the commit message. Getting in the habit of creating quality commit messages makes using and collaborating with Git a lot easier. As a general rule, your messages should start with a single line that’s no more than about 50 characters and that describes the changeset concisely, followed by a blank line, followed by a more detailed explanation. The Git project requires that the more detailed explanation include your motivation for the change and contrast its implementation with previous behavior — this is a good guideline to follow. It’s also a good idea to use the imperative present tense in these messages. In other words, use commands. Instead of “I added tests for” or “Adding tests for,” use “Add tests for.” Here is a template originally written by Tim Pope : Short (50 chars or less) summary of changes More detailed explanatory text, if necessary. Wrap it to about 72 characters or so. In some contexts, the first line is treated as the subject of an email and the rest of the text as the body. The blank line separating the summary from the body is critical (unless you omit the body entirely); tools like rebase can get confused if you run the two together. Further paragraphs come after blank lines. - Bullet points are okay, too - Typically a hyphen or asterisk is used for the bullet, preceded by a single space, with blank lines in between, but conventions vary here If all your commit messages follow this model, things will be much easier for you and the developers with whom you collaborate. The Git project has well-formatted commit messages — try running git log --no-merges there to see what a nicely-formatted project-commit history looks like. Note Do as we say, not as we do. For the sake of brevity, many of the examples in this book don’t have nicely-formatted commit messages like this; instead, we simply use the -m option to git commit . In short, do as we say, not as we do. Private Small Team The simplest setup you’re likely to encounter is a private project with one or two other developers. “Private,” in this context, means closed-source — not accessible to the outside world. You and the other developers all have push access to the repository. In this environment, you can follow a workflow similar to what you might do when using Subversion or another centralized system. You still get the advantages of things like offline committing and vastly simpler branching and merging, but the workflow can be very similar; the main difference is that merges happen client-side rather than on the server at commit time. Let’s see what it might look like when two developers start to work together with a shared repository. The first developer, John, clones the repository, makes a change, and commits locally. (The protocol messages have been replaced with ... in these examples to shorten them somewhat.) # John's Machine $ git clone john@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim lib/simplegit.rb $ git commit -am 'remove invalid default value' [master 738ee87] remove invalid default value 1 files changed, 1 insertions(+), 1 deletions(-) The second developer, Jessica, does the same thing — clones the repository and commits a change: # Jessica's Machine $ 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(-) Now, Jessica pushes her work to the server, which works just fine: # Jessica's Machine $ git push origin master ... To jessica@githost:simplegit.git 1edee6b..fbff5bc master -> master The last line of the output above shows a useful return message from the push operation. The basic format is <oldref>..<newref> fromref -> toref , where oldref means the old reference, newref means the new reference, fromref is the name of the local reference being pushed, and toref is the name of the remote reference being updated. You’ll see similar output like this below in the discussions, so having a basic idea of the meaning will help in understanding the various states of the repositories. More details are available in the documentation for git-push . Continuing with this example, shortly afterwards, John makes some changes, commits them to his local repository, and tries to push them to the same server: # John's Machine $ 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' In this case, John’s push fails because of Jessica’s earlier push of her changes. This is especially important to understand if you’re used to Subversion, because you’ll notice that the two developers didn’t edit the same file. Although Subversion automatically does such a merge on the server if different files are edited, with Git, you must first merge the commits locally. In other words, John must first fetch Jessica’s upstream changes and merge them into his local repository before he will be allowed to push. As a first step, John fetches Jessica’s work (this only fetches Jessica’s upstream work, it does not yet merge it into John’s work): $ git fetch origin ... From john@githost:simplegit + 049d078...fbff5bc master -> origin/master At this point, John’s local repository looks something like this: Figure 58. John’s divergent history. Now John can merge Jessica’s work that he fetched into his own local work: $ git merge origin/master Merge made by the 'recursive' strategy. TODO \| 1 + 1 files changed, 1 insertions(+), 0 deletions(-) As long as that local merge goes smoothly, John’s updated history will now look like this: Figure 59. John’s repository after merging origin/master . At this point, John might want to test this new code to make sure none of Jessica’s work affects any of his and, as long as everything seems fine, he can finally push the new merged work up to the server: $ git push origin master ... To john@githost:simplegit.git fbff5bc..72bbc59 master -> master In the end, John’s commit history will look like this: Figure 60. John’s history after pushing to the origin server. In the meantime, Jessica has created a new topic branch called issue54 , and made three commits to that branch. She hasn’t fetched John’s changes yet, so her commit history looks like this: Figure 61. Jessica’s topic branch. Suddenly, Jessica learns that John has pushed some new work to the server and she wants to take a look at it, so she can fetch all new content from the server that she does not yet have with: # Jessica's Machine $ git fetch origin ... From jessica@githost:simplegit fbff5bc..72bbc59 master -> origin/master That pulls down the work John has pushed up in the meantime. Jessica’s history now looks like this: Figure 62. Jessica’s history after fetching John’s changes. Jessica thinks her topic branch is ready, but she wants to know what part of John’s fetched work she has to merge into her work so that she can push. She runs git log to find out: $ git log --no-merges issue54..origin/master commit 738ee872852dfaa9d6634e0dea7a324040193016 Author: John Smith <jsmith@example.com> Date: Fri May 29 16:01:27 2009 -0700 remove invalid default value The issue54..origin/master syntax is a log filter that asks Git to display only those commits that are on the latter branch (in this case origin/master ) that are not on the first branch (in this case issue54 ). We’ll go over this syntax in detail in Mga Lawak ng Commit . From the above output, we can see that there is a single commit that John has made that Jessica has not merged into her local work. If she merges origin/master , that is the single commit that will modify her local work. Now, Jessica can merge her topic work into her master branch, merge John’s work ( origin/master ) into her master branch, and then push back to the server again. First (having committed all of the work on her issue54 topic branch), Jessica switches back to her master branch in preparation for integrating all this work: $ git checkout master Switched to branch 'master' Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded. Jessica can merge either origin/master or issue54 first — they’re both upstream, so the order doesn’t matter. The end snapshot should be identical no matter which order she chooses; only the history will be different. She chooses to merge the issue54 branch first: $ git merge issue54 Updating fbff5bc..4af4298 Fast forward README \| 1 + lib/simplegit.rb \| 6 +++++- 2 files changed, 6 insertions(+), 1 deletions(-) No problems occur; as you can see it was a simple fast-forward merge. Jessica now completes the local merging process by merging John’s earlier fetched work that is sitting in the origin/master branch: $ git merge origin/master Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb \| 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Everything merges cleanly, and Jessica’s history now looks like this: Figure 63. Jessica’s history after merging John’s changes. Now origin/master is reachable from Jessica’s master branch, so she should be able to successfully push (assuming John hasn’t pushed even more changes in the meantime): $ git push origin master ... To jessica@githost:simplegit.git 72bbc59..8059c15 master -> master Each developer has committed a few times and merged each other’s work successfully. Figure 64. Jessica’s history after pushing all changes back to the server. That is one of the simplest workflows. You work for a while (generally in a topic branch), and merge that work into your master branch when it’s ready to be integrated. When you want to share that work, you fetch and merge your master from origin/master if it has changed, and finally push to the master branch on the server. The general sequence is something like this: Figure 65. General sequence of events for a simple multiple-developer Git workflow. Private Managed Team In this next scenario, you’ll look at contributor roles in a larger private group. You’ll learn how to work in an environment where small groups collaborate on features, after which those team-based contributions are integrated by another party. Let’s say that John and Jessica are working together on one feature (call this “featureA”), while Jessica and a third developer, Josie, are working on a second (say, “featureB”). In this case, the company is using a type of integration-manager workflow where the work of the individual groups is integrated only by certain engineers, and the master branch of the main repo can be updated only by those engineers. In this scenario, all work is done in team-based branches and pulled together by the integrators later. Let’s follow Jessica’s workflow as she works on her two features, collaborating in parallel with two different developers in this environment. Assuming she already has her repository cloned, she decides to work on featureA first. She creates a new branch for the feature and does some work on it there: # Jessica's Machine $ 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(-) At this point, she needs to share her work with John, so she pushes her featureA branch commits up to the server. Jessica doesn’t have push access to the master branch — only the integrators do — so she has to push to another branch in order to collaborate with John: $ git push -u origin featureA ... To jessica@githost:simplegit.git * [new branch] featureA -> featureA Jessica emails John to tell him that she’s pushed some work into a branch named featureA and he can look at it now. While she waits for feedback from John, Jessica decides to start working on featureB with Josie. To begin, she starts a new feature branch, basing it off the server’s master branch: # Jessica's Machine $ git fetch origin $ git checkout -b featureB origin/master Switched to a new branch 'featureB' Now, Jessica makes a couple of commits on the featureB branch: $ 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(-) Jessica’s repository now looks like this: Figure 66. Jessica’s initial commit history. She’s ready to push her work, but gets an email from Josie that a branch with some initial “featureB” work on it was already pushed to the server as the featureBee branch. Jessica needs to merge those changes with her own before she can push her work to the server. Jessica first fetches Josie’s changes with git fetch : $ git fetch origin ... From jessica@githost:simplegit * [new branch] featureBee -> origin/featureBee Assuming Jessica is still on her checked-out featureB branch, she can now merge Josie’s work into that branch with git merge : $ git merge origin/featureBee Auto-merging lib/simplegit.rb Merge made by the 'recursive' strategy. lib/simplegit.rb \| 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) At this point, Jessica wants to push all of this merged “featureB” work back to the server, but she doesn’t want to simply push her own featureB branch. Rather, since Josie has already started an upstream featureBee branch, Jessica wants to push to that branch, which she does with: $ git push -u origin featureB:featureBee ... To jessica@githost:simplegit.git fba9af8..cd685d1 featureB -> featureBee This is called a refspec . See Ang Refspec for a more detailed discussion of Git refspecs and different things you can do with them. Also notice the -u flag; this is short for --set-upstream , which configures the branches for easier pushing and pulling later. Suddenly, Jessica gets email from John, who tells her he’s pushed some changes to the featureA branch on which they are collaborating, and he asks Jessica to take a look at them. Again, Jessica runs a simple git fetch to fetch all new content from the server, including (of course) John’s latest work: $ git fetch origin ... From jessica@githost:simplegit 3300904..aad881d featureA -> origin/featureA Jessica can display the log of John’s new work by comparing the content of the newly-fetched featureA branch with her local copy of the same branch: $ 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 If Jessica likes what she sees, she can merge John’s new work into her local featureA branch with: $ 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(-) Finally, Jessica might want to make a couple minor changes to all that merged content, so she is free to make those changes, commit them to her local featureA branch, and push the end result back to the 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 Jessica’s commit history now looks something like this: Figure 67. Jessica’s history after committing on a feature branch. At some point, Jessica, Josie, and John inform the integrators that the featureA and featureBee branches on the server are ready for integration into the mainline. After the integrators merge these branches into the mainline, a fetch will bring down the new merge commit, making the history look like this: Figure 68. Jessica’s history after merging both her topic branches. Many groups switch to Git because of this ability to have multiple teams working in parallel, merging the different lines of work late in the process. The ability of smaller subgroups of a team to collaborate via remote branches without necessarily having to involve or impede the entire team is a huge benefit of Git. The sequence for the workflow you saw here is something like this: Figure 69. Basic sequence of this managed-team workflow. Forked Public Project Contributing to public projects is a bit different. Because you don’t have the permissions to directly update branches on the project, you have to get the work to the maintainers some other way. This first example describes contributing via forking on Git hosts that support easy forking. Many hosting sites support this (including GitHub, BitBucket, repo.or.cz, and others), and many project maintainers expect this style of contribution. The next section deals with projects that prefer to accept contributed patches via email. First, you’ll probably want to clone the main repository, create a topic branch for the patch or patch series you’re planning to contribute, and do your work there. The sequence looks basically like this: $ git clone <url> $ cd project $ git checkout -b featureA ... work ... $ git commit ... work ... $ git commit Note You may want to use rebase -i to squash your work down to a single commit, or rearrange the work in the commits to make the patch easier for the maintainer to review — see Pagsulat muli ng Kasaysayan for more information about interactive rebasing. When your branch work is finished and you’re ready to contribute it back to the maintainers, go to the original project page and click the “Fork” button, creating your own writable fork of the project. You then need to add this repository URL as a new remote of your local repository; in this example, let’s call it myfork : $ git remote add myfork <url> You then need to push your new work to this repository. It’s easiest to push the topic branch you’re working on to your forked repository, rather than merging that work into your master branch and pushing that. The reason is that if your work isn’t accepted or is cherry-picked, you don’t have to rewind your master branch (the Git cherry-pick operation is covered in more detail in Rebasing and Cherry-Picking Workflows ). If the maintainers merge , rebase , or cherry-pick your work, you’ll eventually get it back via pulling from their repository anyhow. In any event, you can push your work with: $ git push -u myfork featureA Once your work has been pushed to your fork of the repository, you need to notify the maintainers of the original project that you have work you’d like them to merge. This is often called a pull request , and you typically generate such a request either via the website — GitHub has its own “Pull Request” mechanism that we’ll go over in GitHub — or you can run the git request-pull command and email the subsequent output to the project maintainer manually. The git request-pull command takes the base branch into which you want your topic branch pulled and the Git repository URL you want them to pull from, and produces a summary of all the changes you’re asking to be pulled. For instance, if Jessica wants to send John a pull request, and she’s done two commits on the topic branch she just pushed, she can run this: $ 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(-) This output can be sent to the maintainer — it tells them where the work was branched from, summarizes the commits, and identifies from where the new work is to be pulled. On a project for which you’re not the maintainer, it’s generally easier to have a branch like master always track origin/master and to do your work in topic branches that you can easily discard if they’re rejected. Having work themes isolated into topic branches also makes it easier for you to rebase your work if the tip of the main repository has moved in the meantime and your commits no longer apply cleanly. For example, if you want to submit a second topic of work to the project, don’t continue working on the topic branch you just pushed up — start over from the main repository’s master branch: $ git checkout -b featureB origin/master ... work ... $ git commit $ git push myfork featureB $ git request-pull origin/master myfork ... email generated request pull to maintainer ... $ git fetch origin Now, each of your topics is contained within a silo — similar to a patch queue — that you can rewrite, rebase, and modify without the topics interfering or interdepending on each other, like so: Figure 70. Initial commit history with featureB work. Let’s say the project maintainer has pulled in a bunch of other patches and tried your first branch, but it no longer cleanly merges. In this case, you can try to rebase that branch on top of origin/master , resolve the conflicts for the maintainer, and then resubmit your changes: $ git checkout featureA $ git rebase origin/master $ git push -f myfork featureA This rewrites your history to now look like Commit history after featureA work. . Figure 71. Commit history after featureA work. Because you rebased the branch, you have to specify the -f to your push command in order to be able to replace the featureA branch on the server with a commit that isn’t a descendant of it. An alternative would be to push this new work to a different branch on the server (perhaps called featureAv2 ). Let’s look at one more possible scenario: the maintainer has looked at work in your second branch and likes the concept but would like you to change an implementation detail. You’ll also take this opportunity to move the work to be based off the project’s current master branch. You start a new branch based off the current origin/master branch, squash the featureB changes there, resolve any conflicts, make the implementation change, and then push that as a new branch: $ git checkout -b featureBv2 origin/master $ git merge --squash featureB ... change implementation ... $ git commit $ git push myfork featureBv2 The --squash option takes all the work on the merged branch and squashes it into one changeset producing the repository state as if a real merge happened, without actually making a merge commit. This means your future commit will have one parent only and allows you to introduce all the changes from another branch and then make more changes before recording the new commit. Also the --no-commit option can be useful to delay the merge commit in case of the default merge process. At this point, you can notify the maintainer that you’ve made the requested changes, and that they can find those changes in your featureBv2 branch. Figure 72. Commit history after featureBv2 work. Public Project over Email Many projects have established procedures for accepting patches — you’ll need to check the specific rules for each project, because they will differ. Since there are several older, larger projects which accept patches via a developer mailing list, we’ll go over an example of that now. The workflow is similar to the previous use case — you create topic branches for each patch series you work on. The difference is how you submit them to the project. Instead of forking the project and pushing to your own writable version, you generate email versions of each commit series and email them to the developer mailing list: $ git checkout -b topicA ... work ... $ git commit ... work ... $ git commit Now you have two commits that you want to send to the mailing list. You use git format-patch to generate the mbox-formatted files that you can email to the list — it turns each commit into an email message with the first line of the commit message as the subject and the rest of the message plus the patch that the commit introduces as the body. The nice thing about this is that applying a patch from an email generated with format-patch preserves all the commit information properly. $ git format-patch -M origin/master 0001-add-limit-to-log-function.patch 0002-changed-log-output-to-30-from-25.patch The format-patch command prints out the names of the patch files it creates. The -M switch tells Git to look for renames. The files end up looking like this: $ 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 You can also edit these patch files to add more information for the email list that you don’t want to show up in the commit message. If you add text between the --- line and the beginning of the patch (the diff --git line), the developers can read it, but that content is ignored by the patching process. To email this to a mailing list, you can either paste the file into your email program or send it via a command-line program. Pasting the text often causes formatting issues, especially with “smarter” clients that don’t preserve newlines and other whitespace appropriately. Luckily, Git provides a tool to help you send properly formatted patches via IMAP, which may be easier for you. We’ll demonstrate how to send a patch via Gmail, which happens to be the email agent we know best; you can read detailed instructions for a number of mail programs at the end of the aforementioned Documentation/SubmittingPatches file in the Git source code. First, you need to set up the imap section in your ~/.gitconfig file. You can set each value separately with a series of git config commands, or you can add them manually, but in the end your config file should look something like this: [imap] folder = "[Gmail]/Drafts" host = imaps://imap.gmail.com user = user@gmail.com pass = YX]8g76G_2^sFbd port = 993 sslverify = false If your IMAP server doesn’t use SSL, the last two lines probably aren’t necessary, and the host value will be imap:// instead of imaps:// . When that is set up, you can use git imap-send to place the patch series in the Drafts folder of the specified IMAP server: $ 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 At this point, you should be able to go to your Drafts folder, change the To field to the mailing list you’re sending the patch to, possibly CC the maintainer or person responsible for that section, and send it off. You can also send the patches through an SMTP server. As before, you can set each value separately with a series of git config commands, or you can add them manually in the sendemail section in your ~/.gitconfig file: [sendemail] smtpencryption = tls smtpserver = smtp.gmail.com smtpuser = user@gmail.com smtpserverport = 587 After this is done, you can use git send-email to send your patches: $ 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 Then, Git spits out a bunch of log information looking something like this for each patch you’re sending: (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 Summary This section has covered a number of common workflows for dealing with several very different types of Git projects you’re likely to encounter, and introduced a couple of new tools to help you manage this process. Next, you’ll see how to work the other side of the coin: maintaining a Git project. You’ll learn how to be a benevolent dictator or integration manager. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:25
https://www.atlassian.com/blog/bitbucket/the-2025-year-in-review-and-whats-coming-soon/amp	The 2025 Year in Review (and what's coming soon) - Work Life by Atlassian Products & News Atlassian The 2025 Year in Review (and what’s coming soon) Published December 17, 2025 in Bitbucket Chris Clarke Every year is a big year for Bitbucket, but in 2025, we delivered transformative changes that cap off years of work to make Bitbucket Cloud the secure, scalable, cloud-first standard for large engineering teams around the world. Today, 15M developers build on Bitbucket, including all of Atlassian’s 10,000-strong engineering organization, and Bitbucket Pipelines runs more than 1 billion build minutes per month . This year, we also unified our Bitbucket Cloud and Bitbucket Data Center teams, laying the groundwork for the next era of Bitbucket: AI-powered workflows beyond code generation Agentic CI/CD to write complex automations with natural language the upcoming Bitbucket Hybrid License for those with continued self-hosted needs. As we look ahead to 2026, let’s recap what we shipped in 2025 and preview what’s coming, focusing on our three missions: Introduce the AI-native software development lifecycle (SDLC), consolidate tools and scale productivity, and enterprise trust. Introduce the AI-native SDLC As developer interest in AI moves beyond code generation, we’re making AI a core, built-in part of the entire SDLC, automating toilsome work across the most common developer workflows. One example from this year is Rovo Chat in Bitbucket . The same AI teammate that helps you find and write information in Jira and Confluence, can now help you explain your team’s code. In one place and accessible anywhere, Rovo Chat can answer questions like: Who owns this code? Where’s the documentation for this repo? Which Jira ticket is this related to (or which repository is this issue referencing)? And when you add Rovo Dev , our contextual AI agent for developers, you get access to: AI-assisted code review – Speed up code review with Rovo Dev taking the first pass at reviewing your PR for quality, organizational compliance standards, and even acceptance criteria. Within our own teams, we used AI code review to cut PR cycle times by 45%! Pipelines troubleshooter – Manually scanning through logs can be time-consuming. Now, when a build fails, Rovo Dev scans through logs, summarizes the issue, and suggests a fix, allowing developers to resolve the issue quickly and get to production. Pipelines deployment summarizer – When you have deployments with multiple commits, it can be hard to keep track of what shipped. Now, after each deployment, Rovo Dev generates a summary of what shipped, along with Jira issues so you can keep teams in sync. And coming soon… Rovo Dev in Bitbucket Pipelines – Go beyond standard, static CI/CD scripts and use natural language to define steps and create automations such as fixing flaky tests, reviewing PRs, summarizing fixes needed, and more. AI-powered test management – When a test within a pipeline fails, Rovo Dev will be able to triage and attempt to fix the test (documenting all its steps), generate a PR, and re-execute the merge. Consolidate and Scale Developers are most successful when they can stay in the flow of their work, avoiding costly and annoying context switching across tools. We saw the opportunity to remove one of these big friction points with Bitbucket Packages , so developers can store and manage Docker image containers in the same platform they store code and CI/CD, rather than integrate and manage an additional third-party tool. In 2026, we plan to add support for language packages, including NPM, Maven, and PyPI, among others. Here are a few other developer productivity highlights from this year: Draft Pull Requests (and branch deletion on PR merge) Parent/Child Pipelines – Streamlining complex pipelines into modular, more manageable pieces Dynamic Step Condition – Providing even more ways to control pipelines And coming soon… Unified Billing – Atlassian admins for existing workspaces will be able to manage Bitbucket Cloud billing along with other Atlassian products in the same place. We’ve started migrating accounts already and plan for all customers to be on the new system in the coming year. A new look for Bitbucket – Including refreshed iconography, components, and other navigation will make it easier for you to get to your content faster. Enterprise Trust Just as we’ve worked hard to become the one development platform for all Atlassian engineering teams, we’re building Bitbucket to be the trusted development platform for enterprises around the world. This means making the platform faster and more secure, but also means helping you build more secure products too, without sacrificing developer speed. One of the big features we released this year was the ability to sign code commits with both GPG and SSH keys , allowing developers to verify their code contributions and enforce that others do so too. Here are a few other enterprise highlights from this year: Support for third-party secrets within Bitbucket Pipelines – Allowing for secure injection of variables without storing them with the Bitbucket platform Step metrics for Bitbucket Pipelines – So you can manage and optimize your CI/CD consumption API tokens in place of app passwords – To provide a more secure authentication method, increased admin flexibility, and additional expiry controls. Bitbucket integrations with app passwords will be deprecated beginning June 9, 2026. And coming soon… Bitbucket Hybrid License – Existing Bitbucket Data Center customers can keep using Data Center, and use Bitbucket Cloud’s latest AI and CI/CD capabilities under one license ( read more ) Bitbucket Cloud Data Residency – Starting in 2026 with the EU region Bitbucket Pipelines compatibility – As Bamboo Data Center winds down, we will make Bitbucket Pipelines interoperable with Bitbucket Data Center (with Bamboo to Bitbucket Pipelines migration tooling) Infrastructure sharding – To make Bitbucket even faster and more reliable, and set the stage for future data residency capabilities Why we’re so excited about Bitbucket More than any individual feature on our roadmap, we’re excited for how AI and Bitbucket will uniquely transform software development as part of the Atlassian platform. According to IDC , developers spend 84% of their time doing non-coding work, such as searching for information, writing tests, monitoring infrastructure, and more. Our roadmap is full of AI capabilities to address these points of friction, but what’s most delightful is how tailored these capabilities are to everyone’s organization. As part of the Atlassian platform, Bitbucket is connected to the Teamwork Graph —Atlassian’s comprehensive network of all Atlassian apps, third-party tools, and the people who use them—which gives developers access to powerful AI features with context, such as their team’s coding standards, who has worked in which repo, what are the acceptance criteria in Jira, and more, available wherever they’re working. This unique combination of powerful AI, with contextual data, all connected on a single platform, will unlock a new level of developer productivity, and we believe it’s why Gartner named us a Leader in the 2025 Magic Quadrant for DevOps Platforms (and placed highest in Ability to Execute and furthest in Completeness of Vision). We take pride in being trusted by so many organizations as the platform hosting their code and data, and we can’t wait to showcase in the coming year the AI-powered capabilities they’ll have with it. About this article Published December 17, 2025 About the Author Chris Clarke Facebook Twitter Linkedin Pocket Email Related Content More in Bitbucket Bitbucket The 2025 Year in Review (and what’s coming soon) Bitbucket Simplify container management with Bitbucket Packages (now GA) Bitbucket Announcing powerful upgrades & a new pricing model for self-hosted runners Bitbucket Bitbucket’s new look: user experience and navigation updates coming soon Exit mobile version	2026-01-13T09:29:25
https://git-scm.com/book/pt-br/v2/Fundamentos-de-Git-Gravando-Altera%c3%a7%c3%b5es-em-Seu-Reposit%c3%b3rio	Git - Gravando Alterações em Seu Repositório 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. Começando 1.1 Sobre Controle de Versão 1.2 Uma Breve História do Git 1.3 O Básico do Git 1.4 A Linha de Comando 1.5 Instalando o Git 1.6 Configuração Inicial do Git 1.7 Pedindo Ajuda 1.8 Sumário 2. Fundamentos de Git 2.1 Obtendo um Repositório Git 2.2 Gravando Alterações em Seu Repositório 2.3 Vendo o histórico de Commits 2.4 Desfazendo coisas 2.5 Trabalhando de Forma Remota 2.6 Criando Tags 2.7 Apelidos Git 2.8 Sumário 3. Branches no Git 3.1 Branches em poucas palavras 3.2 O básico de Ramificação (Branch) e Mesclagem (Merge) 3.3 Gestão de Branches 3.4 Fluxo de Branches 3.5 Branches remotos 3.6 Rebase 3.7 Sumário 4. Git no servidor 4.1 Os Protocolos 4.2 Getting Git on a Server 4.3 Gerando Sua Chave Pública SSH 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 Sumário 5. Distributed Git 5.1 Fluxos de Trabalho Distribuídos 5.2 Contribuindo com um Projeto 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Configurando uma conta 6.2 Contribuindo em um projeto 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. Funcionamento Interno do Git 10.1 Encanamento e Porcelana 10.2 Objetos do Git 10.3 Referências do Git 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Variáveis de ambiente 10.9 Sumário A1. Appendix A: Git em Outros Ambientes 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 Resumo 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 Fundamentos de Git - Gravando Alterações em Seu Repositório Gravando Alterações em Seu Repositório Você tem um verdadeiro repositório Git e um "checkout" ou cópia de trabalho dos arquivos para aquele projeto. Você precisa fazer algumas alterações e adicionar commits dessas alterações em seu repositório a cada vez que o projeto chegar a um estado que você queira registrar. Lembre-se que cada arquivo em seu diretório de trabalho pode estar em um dos seguintes estados: rastreado e não-rastreado. Arquivos rastreados são arquivos que foram incluídos no último snapshot ; eles podem ser não modificados, modificados ou preparados (adicionados ao stage ). Em resumo, arquivos rastreados são os arquivos que o Git conhece. Arquivos não rastreados são todos os outros - quaisquer arquivos em seu diretório de trabalho que não foram incluídos em seu último snapshot e não estão na área de stage. Quando você clona um repositório pela primeira vez, todos os seus arquivos serão rastreados e não modificados já que o Git acabou de obtê-los e você ainda não editou nada. Assim que você edita alguns arquivos, Git os considera modificados, porque você os editou desde o seu último commit. Você prepara os arquivos editados e então faz commit das suas alterações, e o ciclo se repete. Figure 8. O ciclo de vida dos status de seus arquivos. Verificando os Status de Seus Arquivos A principal ferramenta que você vai usar para determinar quais arquivos estão em qual estado é o comando git status . Se você executar esse comando imediatamente após clonar um repositório, você vai ver algo assim: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean Isso significa que você tem um diretório de trabalho limpo - em outras palavras, nenhum de seus arquivos rastreados foi modificado. O Git também não está vendo nenhum arquivo não rastreado, senão eles estariam listados aqui. Finalmente, o comando lhe diz qual o branch que você está e diz que ele não divergiu do mesmo branch no servidor. Por enquanto, esse branch é sempre “master”, que é o padrão; você não precisa se preocupar com isso agora. [ch03-git-branching] vai abordar branches e referências em detalhe. Digamos que você adiciona um novo arquivo no seu projeto, um simples arquivo README. Se o arquivo não existia antes, e você executar git status , você verá seu arquivo não rastreado da seguinte forma: $ 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) Você pode ver que o seu novo arquivo README é um arquivo não rastreado, porque está abaixo do subtítulo “Untracked files” na saída do seu status. "Não rastreado" basicamente significa que o Git vê um arquivo que você não tinha no snapshot (commit) anterior; o Git não vai passar a incluir o arquivo nos seus commits a não ser que você o mande fazer isso explicitamente. O comportamento do Git é dessa forma para que você não inclua acidentalmente arquivos binários gerados automaticamente ou outros arquivos que você não deseja incluir. Você quer incluir o arquivo README, então vamos comeaçar a rastreá-lo. Rastreando Arquivos Novos Para começar a rastrear um novo arquivo, você deve usar o comando git add . Para começar a rastrear o arquivo README, você deve executar o seguinte: $ git add README Executando o comando status novamente, você pode ver que seu README agora está sendo rastreado e preparado ( staged ) para o commit : $ 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 É possível saber que o arquivo está preparado porque ele aparece sob o título “Changes to be committed”. Se você fizer um commit neste momento, a versão do arquivo que existia no instante em que você executou git add , é a que será armazenada no histórico de snapshots . Você deve se lembrar que, quando executou git init anteriormente, em seguida, você também executou git add (arquivos) - isso foi para começar a rastrear os arquivos em seu diretório. O comando git add recebe o caminho de um arquivo ou de um diretório. Se for um diretório, o comando adiciona todos os arquivos contidos nesse diretório recursivamente. Preparando Arquivos Modificados Vamos modificar um arquivo que já estava sendo rastreado. Se você modificar o arquivo CONTRIBUTING.md , que já era rastreado, e então executar git status novamente, você deve ver algo como: $ 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 O arquivo CONTRIBUTING.md aparece sob a seção “Changes not staged for commit” — que indica que um arquivo rastreado foi modificado no diretório de trabalho mas ainda não foi mandado para o stage (preparado). Para mandá-lo para o stage , você precisa executar o comando git add . O git add é um comando de múltiplos propósitos: serve para começar a rastrear arquivos e também para outras coisas, como marcar arquivos que estão em conflito de mesclagem como resolvidos. Pode ser útil pensar nesse comando mais como “adicione este conteúdo ao próximo commit ”. Vamos executar git add agora, para mandar o arquivo CONTRIBUTING.md para o stage , e então executar git status novamente: $ 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 Ambos os arquivos estão preparados (no stage ) e entrarão no seu próximo commit . Neste momento, suponha que você se lembre de uma pequena mudança que quer fazer no arquivo CONTRIBUTING.md antes de fazer o commit . Você abre o arquivo, faz a mudança e está pronto para fazer o commit . No entanto, vamos executar git status mais uma vez: $ 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 Que negócio é esse? Agora o CONTRIBUTING.md está listado como preparado ( staged ) e também como não-preparado ( unstaged ). Como isso é possível? Acontece que o Git põe um arquivo no stage exatamente como ele está no momento em que você executa o comando git add . Se você executar git commit agora, a versão do CONTRIBUTING.md que vai para o repositório é aquela de quando você executou git add , não a versão que está no seu diretório de trabalho. Se você modificar um arquivo depois de executar git add , você tem que executar git add de novo para por sua versão mais recente no stage : $ 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 Status Curto Ao mesmo tempo que a saída do git status é bem completa, ela também é bastante verbosa. O Git também tem uma flag para status curto, que permite que você veja suas alterações de forma mais compacta. Se você executar git status -s ou git status --short a saída do comando vai ser bem mais simples: $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt Arquivos novos que não são rastreados têm um ?? do lado, novos arquivos que foram adicionados à área de stage têm um A , arquivos modificados têm um M e assim por diante. Há duas colunas de status na saída: a coluna da esquerda indica o status da área de stage e a coluna da direita indica o status do diretório de trabalho. No exemplo anterior, o arquivo README foi modificado no diretório de trabalho mas ainda não foi para o stage , enquanto o arquivo lib/simplegit.rb foi modificado e foi para o stage . O arquivo Rakefile foi modificado, foi para o stage e foi modificado de novo, de maneira que há alterações para ele tanto no estado preparado quanto no estado não-preparado. Ignorando Arquivos Frequentemente você terá uma classe de arquivos que não quer que sejam adicionados automaticamente pelo Git e nem mesmo que ele os mostre como não-rastreados. Geralmente, esses arquivos são gerados automaticamente, tais como arquivos de log ou arquivos produzidos pelo seu sistema de compilação ( build ). Nesses casos, você pode criar um arquivo chamado .gitignore , contendo uma lista de padrões de nomes de arquivo que devem ser ignorados. Aqui está um exemplo de arquivo .gitignore : $ cat .gitignore .[oa] ~ A primeira linha diz ao Git para ignorar todos os arquivos que terminem com “.o” ou “.a” – arquivos objeto ou de arquivamento, que podem ser produtos do processo de compilação. A segunda linha diz ao Git para ignorar todos os arquivos cujo nome termine com um til ( ~ ), que é usado por muitos editores de texto, como o Emacs, para marcar arquivos temporários. Você também pode incluir diretórios log , tmp ou pid ; documentação gerada automaticamente; e assim por diante. Configurar um arquivo .gitignore , antes de você começar um repositório, geralmente é uma boa ideia para que você não inclua acidentalmente em seu repositório Git arquivos que você não quer. As regras para os padrões que podem ser usados no arquivo .gitignore são as seguintes: Linhas em branco ou começando com # são ignoradas. Os padrões que normalmente são usados para nomes de arquivos funcionam. Você pode iniciar padrões com uma barra ( / ) para evitar recursividade. Você pode terminar padrões com uma barra ( / ) para especificar um diretório. Você pode negar um padrão ao fazê-lo iniciar com um ponto de exclamação ( ! ). Padrões de nome de arquivo são como expressões regulares simplificadas usadas em ambiente shell . Um asterisco ( * ) casa com zero ou mais caracteres; [abc] casa com qualquer caracter dentro dos colchetes (neste caso, a, b ou c); um ponto de interrogação ( ? ) casa com um único caracter qualquer; e caracteres entre colchetes separados por hífen ( [0-9] ) casam com qualquer caracter entre eles (neste caso, de 0 a 9). Você também pode usar dois asteriscos para criar uma expressão que case com diretórios aninhados; a/*/z casaria com a/z , a/b/z , a/b/c/z , e assim por diante. Aqui está outro exemplo de arquivo .gitignore : # ignorar arquivos com extensão .a .a # mas rastrear o arquivo lib.a, mesmo que você esteja ignorando os arquivos .a acima !lib.a # ignorar o arquivo TODO apenas no diretório atual, mas não em subdir/TODO /TODO # ignorar todos os arquivos no diretório build/ build/ # ignorar doc/notes.txt, mas não doc/server/arch.txt doc/.txt # ignorar todos os arquivos .pdf no diretório doc/ doc//.pdf Tip O GitHub mantém uma lista bem abrangente com bons exemplos de arquivo .gitignore para vários projetos e linguagens em https://github.com/github/gitignore , se você quiser um ponto de partida para o seu projeto. Note Em casos simples, um repositório deve ter um único arquivo .gitignore em seu diretório raiz, o qual é aplicado recursivamente a todo o repositório. Contudo, também é possível ter arquivos .gitignore adicionais em subdiretórios. As regras definidas nesses .gitignore internos se aplicam somente aos arquivos contidos no diretório em que eles estão localizados. (O repositório do kernel do Linux tem 206 arquivos .gitignore .) Está fora do escopo deste livro explicar os detalhes de múltiplos arquivos .gitignore ; veja man gitignore para mais informações. Visualizando Suas Alterações Dentro e Fora do Stage Se o comando git status for vago demais para você — você quer saber exatamente o que você alterou, não apenas quais arquivos foram alterados — você pode usar o comando git diff . Nós explicaremos o git diff em detalhes mais tarde, mas provavelmente você vai usá-lo com maior frequência para responder a essas duas perguntas: O que você alterou mas ainda não mandou para o stage (estado preparado)? E o que está no stage , pronto para o commit ? Apesar de o git status responder a essas perguntas de forma genérica, listando os nomes dos arquivos, o git diff exibe exatamente as linhas que foram adicionadas e removidas — o patch , como costumava se chamar. Digamos que você altere o arquivo README e o mande para o stage e então altere o arquivo CONTRIBUTING.md sem mandá-lo para o stage . Se você executar o comando git status , você verá mais uma vez alguma coisa como o seguinte: $ 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 Para ver o que você alterou mas ainda não mandou para o stage , digite o comando git diff sem nenhum argumento: $ 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 Esse comando compara o que está no seu diretório de trabalho com o que está no stage . O resultado permite que você saiba quais alterações você fez que ainda não foram mandadas para o stage . Se você quiser ver as alterações que você mandou para o stage e que entrarão no seu próximo commit , você pode usar git diff --staged . Este comando compara as alterações que estão no seu stage com o seu último 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 É importante notar que o git diff sozinho não mostra todas as alterações feitas desde o seu último commit — apenas as alterações que ainda não estão no stage (não-preparado). Isso pode ser confuso porque, se você já tiver mandado todas as suas alterações para o stage , a saída do git diff vai ser vazia. Um outro exemplo: se você mandar o arquivo CONTRIBUTING.md para o stage e então alterá-lo, você pode usar o git diff para ver as alterações no arquivo que estão no stage e também as que não estão. Se o nosso ambiente se parecer com isso: $ 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 Agora você poderá usar o git diff para ver o que ainda não foi mandado para o stage : $ 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 e git diff --cached para ver o que você já mandou para o stage até agora ( --staged e --cached são sinônimos): $ 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 em uma Ferramenta Externa Nós continuaremos usando o comando git diff de várias maneiras pelo resto do livro. Há outra maneira de ver essas diferenças, se você preferir usar uma ferramenta gráfica ou um programa externo. Se você executar git difftool em vez de git diff , você pode ver qualquer dessas diferenças em um software como emerge, vimdiff e muitos outros (incluindo produtos comerciais). Execute git difftool --tool-help para ver o que há disponível em seu sistema. Fazendo Commit das Suas Alterações Agora que sua área de stage está preparada do jeito que você quer, você pode fazer commit das suas alterações. Lembre-se que qualquer coisa que ainda não foi enviada para o stage — qualquer arquivo que você tenha criado ou alterado e que ainda não tenha sido adicionado com git add — não entrará nesse commit . Esses arquivos permanecerão no seu disco como arquivos alterados. Nesse caso, digamos que, da última vez que você executou git status , você viu que tudo estava no stage , então você está pronto para fazer commit de suas alterações. O jeito mais simples de fazer commit é digitar git commit : $ git commit Fazendo isso, será aberto o editor de sua escolha. Note O editor é determinado pela variável de ambiente EDITOR — normalmente o vim ou emacs, mas você pode escolher qualquer editor que quiser usando o comando git config --global core.editor como você viu em [ch01-introduction] . O editor mostra o seguinte texto (este é um exemplo da tela do 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 Você pode ver que a mensagem de commit padrão contém a saída mais recente do comando git status , comentada, e uma linha em branco no topo. Você pode remover esses comentários e digitar sua mensagem de commit , ou você pode deixá-los lá para ajudá-lo a lembrar o que faz parte do commit . Note Para um lembrete ainda mais explícito do que você alterou, você pode passar a opção -v para o git commit . Isso inclui as diferenças ( diff ) da sua alteração no editor, para que você possa ver exatamente quais alterações estão entrando no commit . Quando você sair do editor, o Git criará seu commit com essa mensagem (com os comentários e diferenças removidos). Alternativamente, você pode digitar sua mensagem de commit diretamente na linha de comando, depois da opção -m do comando commit , assim: $ 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 Você acaba de criar seu primeiro commit ! Veja que a saída do comando fornece algumas informações: em qual branch foi feito o commit ( master ), seu checksum SHA-1 ( 463dc4f ), quantos arquivos foram alterados e estatísticas sobre o número de linhas adicionadas e removidas. Lembre-se de que o commit grava o snapshot que você deixou na área de stage . Qualquer alteração que você não tiver mandado para o stage permanecerá como estava, em seu lugar; você pode executar outro commit para adicioná-la ao seu histórico. Toda vez que você executa um commit , você está gravando um snapshot do seu projeto que você pode usar posteriormente para fazer comparações, ou mesmo restaurá-lo. Pulando a Área de Stage Mesmo sendo incrivelmente útil para preparar commits exatamente como você quer, a área de stage algumas vezes é um pouco mais complexa do que o necessário. Se você quiser pular a área de stage , o Git fornece um atalho simples. A opção -a , do comando git commit , faz o Git mandar todos arquivos rastreados para o stage automaticamente, antes de fazer o commit , permitindo que você pule a parte do 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(-) Perceba que, nesse caso, você não tem que executar git add antes, para adicionar o arquivo CONTRIBUTING.md ao commit . Isso ocorre porque a opção -a inclui todos os arquivos alterados. Isso é conveniente, mas cuidado; algumas vezes esta opção fará você incluir alterações indesejadas. Removendo Arquivos Para remover um arquivo do Git, você tem que removê-lo dos seus arquivos rastreados (mais precisamente, removê-lo da sua área de stage ) e então fazer um commit . O comando git rm faz isso, e também remove o arquivo do seu diretório de trabalho para que você não o veja como um arquivo não-rastreado nas suas próximas interações. Se você simplesmente remover o arquivo do seu diretório, ele aparecerá sob a área “Changes not staged for commit” (isto é, fora do stage ) da saída do seu 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") Mas, se você executar git rm , o arquivo será preparado para remoção (retirado do stage ): $ 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 Da próxima vez que você fizer um commit , o arquivo será eliminado e não será mais rastreado. Se o arquivo tiver sido alterado ou se já tiver adicionado à área de stage , você terá que forçar a remoção com a opção -f . Essa é uma medida de segurança para prevenir a exclusão acidental de dados que ainda não tenham sido gravados em um snapshot e que não poderão ser recuperados do histórico. Outra coisa útil que você pode querer fazer é manter o arquivo no seu diretório de trabalho, mas removê-lo da sua área de stage . Em outras palavras, você pode querer manter o arquivo no seu disco rígido, mas não deixá-lo mais sob controle do Git. Isso é particularmente útil se você esquecer de adicionar alguma coisa ao seu arquivo .gitignore e, acidentalmente, mandá-la para o stage , como um grande arquivo de log ou um monte de arquivos compilados .a . Para fazer isso, use a opção --cached : $ git rm --cached README Você pode passar arquivos, diretórios e padrões de nomes para o comando git rm . Isso quer dizer que você pode fazer coisas como: $ git rm log/\.log Note a barra invertida ( \ ) na frente do . Isso é necessário porque o Git faz sua própria expansão de nomes de arquivos em adição a que é feita pela sua shell . Esse comando remove todos os arquivos que tenham a extensão .log do diretório log/ . Ou, você pode fazer algo como o seguinte: $ git rm \*~ Esse comando remove todos os arquivos cujos nomes terminem com um ~ . Movendo Arquivos Diferentemente de outros sistemas de controle de versão, o Git não rastreia explicitamente a movimentação de arquivos. Se você renomear um arquivo no Git, ele não armazena metadados indicando que determinado arquivo foi renomeado. Porém, o Git é bastante esperto para perceber isso depois do fato ocorrido — nós trataremos de movimentação de arquivos daqui a pouco. Assim, é um pouco confuso o fato de o Git ter um comando mv . Se você quiser renomear um arquivo no Git, você pode executar alguma coisa como: $ git mv arq_origem arq_destino e vai funcionar bem. Na verdade, se você executar alguma coisa assim e verificar o status , você vai ver que o Git considera que arquivo foi renomeado: $ 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 Contudo, isso é equivalente a executar algo como: $ mv README.md README $ git rm README.md $ git add README O Git percebe que, implicitamente, se trata de um arquivo renomeado, de maneira que não importa se você renomear um arquivo desse jeito ou com o comando mv . A única diferença real é que git mv é um comando em vez de três — é uma função de conveniência. Mais importante, você pode usar qualquer ferramenta que quiser para renomear um arquivo e cuidar do add / rm depois, antes de fazer o commit . prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:25
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#collect-by-url-3	Instagram API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Instagram API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Posts API Collect by URL Discover by URL Comments API Collect by URL Reels API Collect by URL Discover by URL Social Media APIs Instagram API Scrapers Copy page Copy page Overview The Instagram API Suite offers multiple types of APIs, each designed for specific data collection needs from Instagram. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : N/A Interesting Columns : followers , post_count , post_hashtags , profile_name . Posts API This API allows users to collect multiple posts based on a single input URL (such as an Instagram reels URL, search URL or profile URL). Discovery functionality : - Direct URL of the Instagram reel - Direct URL of the search - Direct URL of the profile Interesting Columns : url , followers , hashtags , engagement_score_view . Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : comment_user , comment , likes_number , replies_number . The suite of APIs is designed to offer flexibility for targeted data collection, where users can input specific URLs to gather detailed post and comment data, either in bulk or with precise filtering options. Profiles API Collect by URL This API allows users to collect detailed data about an Instagram profile by providing the profile URL. It provides a comprehensive overview of an Instagram profile, including business and engagement information, posts, and user details. Input Parameters URL string required The Instagram profile URL. Output Structure Includes comprehensive data points: Page/Profile Details : account , id , followers , posts_count , is_business_account , is_professional_account , is_verified , avg_engagement , profile_name , profile_url , profile_image_link , and more. For all data points, click here . Posts API Collect by URL This API enables users to collect detailed data from Instagram posts by providing a post URL. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Post Details : post_id , description , hashtags , date_posted , num_comments , likes , content_type , video_view_count , video_play_count , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : photos , videos , thumbnail , display_url (link only, not the file itself), audio. Discover by URL This API allows users to discover recent Instagram posts from a public profile by providing the profile URL and specifying additional parameters. Input Parameters URL string required The Instagram profile URL. num_of_posts number The number of recent posts to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date). post_type string Specify the type of posts to collect (e.g., post, reel). Output Structure Includes comprehensive data points: Post Details: post_id , description , hashtags , date_posted , num_comments , likes , video_view_count , video_play_count ,and more. For all data points, click here . Page/Profile Details: user_posted , followers , posts_count , profile_image_link , is_verified , profile_url , is_paid_partnership , partnership_details , user_posted_id Attachments and Media: photos , videos , thumbnail , audio , display_url , content_type , product_type , coauthor_producers , tagged_users . This API is designed to allow for filtering, exclusion of specific posts, and collecting posts by type (regular post or reel) within a defined time frame. It provides detailed post and profile information, making it ideal for data collection and analytics. Comments API Collect by URL This API allows users to collect the latest comments from a specific Instagram post by providing the post URL. This API retrieves the most recent 10 comments along with associated metadata. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Comment Details : comment_id , comment_user , comment_user_url , comment_date , comment , likes_number , replies_number , replies , hashtag_comment , tagged_users_in_comment , and more. For all data points, click here . User Details : user_name , user_id , user_url We provide a limited set of data points about the profile. Post Metadata : post_url , post_user , post_id . Reels API Collect by URL This API allows users to collect detailed data about Instagram reels from public profiles by providing the reel URL. Input Parameters URL string required The Instagram reel URL. Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , tagged_users , num_comments , likes , views , video_play_count , length , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : video_url , thumbnail , audio_url . Discover by URL This API allows users to discover Instagram Reels videos from a profile URL or direct search URL. Input Parameters URL string required The Instagram profile or direct search URL. num_of_posts number The number of recent reels to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering reels in MM-DD-YYYY format. end_date string End date for filtering reels in MM-DD-YYYY format (should be later than start_date ). Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , num_comments , likes , views , video_play_count , top_comments , length , video_url , audio_url , content_id , and more. For all data points, click here . Profile Details : user_posted , followers , posts_count , following . Attachments and Media : video_url , thumbnail , audio_url (link only, not the file itself). This API provides detailed information about Instagram Reels, with filtering options by date range, exclusion of specific posts, and a limit on the number of reels collected. Was this page helpful? Yes No Facebook LinkedIn ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:25
https://website.informer.com/	Website Informer Website Informer The richest source of website information Home Browser Extension Emails Menu Website Search Terms of Service Emails About Contacts Removal Request Get Complete Report About Any Website With One Click Search Web Stats Get an aggregated view of a website's daily visitors, safety status, global rank, owners, and more. Competitors Identify a website's main competitors to strategize effectively against the leading players in your field. Similar Websites Research similar websites to find the best ones to subscribe to and understand how saturated a niche is. IP & DNS Lookup Reveal DNS servers used by a website, its registrars, hosting company and find IP addresses behind it. WHOIS Get WHOIS record of any website represented in all-around report. Websites Reports Get detailed reports to evaluate and monitor the performance of your online platforms effectively. Our reports provide essential insights such as global rankings, daily visitors, and hosting details, empowering you with accurate and up-to-date metrics. With information like domain age, profile setup timelines, and network data, you can make informed decisions about your website’s growth and trustworthiness. Gain a deeper understanding of your website’s structure, including hosting companies, IP ranges, and DNS records. Our platform also highlights relevant keywords to boost your SEO strategy, ensuring better online visibility. Open Sample Report Use Browser Extension Enhance your browsing experience with our powerful browser extension, designed to provide instant website analysis and security checks. With a single click, access critical details such as global website ratings, domain age, hosting information, and safety evaluations. Ensure your online interactions are secure with real-time checks for malware, phishing, and scams, offering peace of mind during every session. Our extension is the perfect companion for web professionals and users who value transparency and security. Identify potential risks like spam and review website trustworthiness instantly, directly from your browser. Download Extension Learn More Reveal Website Relationships Discover valuable connections between email addresses and domains with our advanced email-to-domain matching service. By extracting email information from WHOIS data, our platform identifies relationships between websites and the emails associated with their registration. This enables you to see all websites linked to a particular email address, offering deep insights into domain ownership and connections. Ideal for digital investigators, marketers, and cybersecurity professionals, this tool streamlines the process of uncovering hidden relationships across the web. Gain an edge by understanding the network of domains associated with a single email, ensuring transparency, better decision-making, and enhanced security in your online operations. Learn More Recently Updated Websites manfrotto.com.au olybuilt.com cainz.co.jp zfm123.com lumpzmedia.org turkeycommerce.com baojinews.com tencrazy.com lengoctrac.com weizhaixing.com Most Popular Websites servicenterlatam.mx coinsterminingfarm.com topcareemergency.com zhenfanjixie.com eluy.net mmc.com.my yummypuffs.com vertech.com.cn ringgitohringgit.com dracoglass.com Browser Extension Terms of Service Cookie Policy Emails Privacy Policy Removal Request Contact Us Copyright © 2010-2026 Informer Technologies, Inc.	2026-01-13T09:29:25
https://git-scm.com/book/tl/v2/Git-sa-Server-Ang-paglikha-ng-iyong-Pampublikong-Susi-ng-SSH	Git - Ang paglikha ng iyong Pampublikong Susi ng SSH 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.3 Git sa Server - Ang paglikha ng iyong Pampublikong Susi ng SSH Ang paglikha ng iyong Pampublikong Susi ng SSH Maraming mga server sa Git ang nagpapatunay gamit ang pampublikong susi ng SSH. Upang makapagbigay ng pampublikong susi, bawat user sa iyong sistema ay dapat maglikha ng isa kung wala pa silang nalikha. Ang proseso na ito ay pareho sa iba’t ibang mga operating system. Una, dapat mong suriin upang masigurado na wala ka pang susi. Bilang default, ang susi sa SSH ng gumagamit ay nakaimbak sa ~/.ssh na direktorya ng gumagamit. Madali mo lamang masuri upang makita kung mayroon ka ng susi sa pamamagitan ng pagpunta sa direktoryo at pag-lista sa mga nilalaman: $ cd ~/.ssh $ ls authorized_keys2 id_dsa known_hosts config id_dsa.pub Naghahanap ka para sa isang pares ng mga file na pinagalan katulad ng id_dsa o id_rsa at isang tumugmang file na may karugtong na .pub . Ang .pub na file ay ang iyong pampublikong susi, at ang ibang file ang iyong pribadong susi. Kung wala ka nitong mga file (o wala kahit isang .ssh` na direktorya), maaari kang maglikha sa pamamagitan ng pagpapatakbo sa programang ssh-keygen , kung saan ay ibinigay kasama sa SSH na pakete sa Linux/Mac na mga sistema at kasama ng Git para sa Windows: $ ssh-keygen Lumilikha ng pampubliko/pribadong rsa na pares ng susi. Ilagay ang file kung saan i-save ang susi (/home/schacon/.ssh/id_rsa): Nalikha na direktorya '/home/schacon/.ssh'. Ilagay ang passphrase (walang laman para sa walang passphrase): Ilagay ang parehong passphrase muli: Ang iyong pagkakakilanlan ay na-save sa /home/schacon/.ssh/id_rsa. Ang iyong pampublikong susi ay na-save sa /home/schacon/.ssh/id_rsa.pub. Ang key fingerprint ay: d0:82:24:8e:d7:f1:bb:9b:33:53:96:93:49:da:9b:e3 schacon@mylaptop.local Kinukumpirma muna nito kung asa mo gusto i-save ang susi ( .ssh/id_rsa ), sunod ay magtatanong ito ng dalawang beses para sa isang passphrase, na kung saan ay maaari mong iiwan na bakante kung ayaw mo mag-type ng isang password kapag ginamit mo ang key. Ngayon, ang bawat gumagamit na ginawa ito ay dapat ipadala ang kanilang pampublikong susi sayo o sinuman ang namamahala sa server ng Git (sa pag-aakala na ikaw ay gumagamit ng isang SSH server na setup na nangangailangan ng mga pampublikong susi). Ang kailangan lamang nila gawin ay kopyahin ang nilalaman ng .pub na file at i-email ito. Ang mga pampublikong susi ay mukhang ganito: $ cat ~/.ssh/id_rsa.pub ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAklOUpkDHrfHY17SbrmTIpNLTGK9Tjom/BWDSU GPl+nafzlHDTYW7hdI4yZ5ew18JH4JW9jbhUFrviQzM7xlELEVf4h9lFX5QVkbPppSwg0cda3 Pbv7kOdJ/MTyBlWXFCR+HAo3FXRitBqxiX1nKhXpHAZsMciLq8V6RjsNAQwdsdMFvSlVK/7XA t3FaoJoAsncM1Q9x5+3V0Ww68/eIFmb1zuUFljQJKprrX88XypNDvjYNby6vw/Pb0rwert/En mZ+AW4OZPnTPI89ZPmVMLuayrD2cE86Z/il8b+gw3r3+1nKatmIkjn2so1d01QraTlMqVSsbx NrRFi9wrf+M7Q== schacon@mylaptop.local Para sa malalim na tutoryal sa paglikha ng SSH na susi sa maramihang mga operating system, tingnan ang gabay sa GitHub tungkol sa SSH na mga susi sa https://help.github.com/articles/generating-ssh-keys . prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:25
https://git-scm.com/book/sl/v2/Za%c4%8detek-Ukazna-vrstica	Git - Ukazna vrstica 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 1.4 Začetek - Ukazna vrstica Ukazna vrstica Obstaja veliko različnih načinov uporabe Gita. Obstajajo izvorna orodja ukazne vrstice in na voljo je mnogo grafičnih vmesnikov različnih zmogljivosti. Za to knjigo bomo uporabljali Git v ukazni vrstici. Kot prvič, ukazna vrstica je edino mesto, kjer lahko poženete vse ukaze Git — večina GUI-jev samo implementira nekaj podnaborov funkcionalnosti Git zaradi enostavnosti. Če veste, kako pognati verzijo ukazne vrstice, lahko verjetno tudi ugotovite, kako pognati verzijo GUI, medtem ko nasprotno ni nujno res. Medtem tudi, ko je izbira grafičnega odjemalca stvar osebnega okusa, imajo vsi uporabniki nameščena in na voljo orodja ukazne vrstice. Torej pričakovali bomo, da veste, kako odpreti Terminal v macOS oziroma ukazno vrstico ali Powershell v Windows. Če ne veste, o čem je tu govora, bi se bilo dobro ustaviti in to na hitro raziskati, da lahko sledite preostalim primerom in opisom v tej knjigi. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:25
https://git-scm.com/book/zh/v2/%e6%9c%8d%e5%8a%a1%e5%99%a8%e4%b8%8a%e7%9a%84-Git-%e6%80%bb%e7%bb%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 4.10 服务器上的 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:25
https://www.linkedin.com/uas/login?session_redirect=%2Fservices%2Fproducts%2Fnxofrance-cybers%25C3%25A9curit%25C3%25A9%2F&fromSignIn=true&trk=products_details_guest_nav-header-signin	LinkedIn Login, Sign in \| LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional))	2026-01-13T09:29:25
https://vi-vn.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Frootstock.io	Facebook Facebook Email hoặc điện thoại Mật khẩu Bạn quên tài khoản ư? Tạo tài khoản mới Bạn tạm thời bị chặn Bạn tạm thời bị chặn Có vẻ như bạn đang dùng nhầm tính năng này do sử dụng quá nhanh. Bạn tạm thời đã bị chặn sử dụng nó. Back Tiếng Việt 한국어 English (US) Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Đăng ký Đăng nhập Messenger Facebook Lite Video Meta Pay Cửa hàng trên Meta Meta Quest Ray-Ban Meta Meta AI Nội dung khác do Meta AI tạo Instagram Threads Trung tâm thông tin bỏ phiếu Chính sách quyền riêng tư Trung tâm quyền riêng tư Giới thiệu Tạo quảng cáo Tạo Trang Nhà phát triển Tuyển dụng Cookie Lựa chọn quảng cáo Điều khoản Trợ giúp Tải thông tin liên hệ lên & đối tượng không phải người dùng Cài đặt Nhật ký hoạt động Meta © 2026	2026-01-13T09:29:25
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#profiles-api	Instagram API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Instagram API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Posts API Collect by URL Discover by URL Comments API Collect by URL Reels API Collect by URL Discover by URL Social Media APIs Instagram API Scrapers Copy page Copy page Overview The Instagram API Suite offers multiple types of APIs, each designed for specific data collection needs from Instagram. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : N/A Interesting Columns : followers , post_count , post_hashtags , profile_name . Posts API This API allows users to collect multiple posts based on a single input URL (such as an Instagram reels URL, search URL or profile URL). Discovery functionality : - Direct URL of the Instagram reel - Direct URL of the search - Direct URL of the profile Interesting Columns : url , followers , hashtags , engagement_score_view . Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : comment_user , comment , likes_number , replies_number . The suite of APIs is designed to offer flexibility for targeted data collection, where users can input specific URLs to gather detailed post and comment data, either in bulk or with precise filtering options. Profiles API Collect by URL This API allows users to collect detailed data about an Instagram profile by providing the profile URL. It provides a comprehensive overview of an Instagram profile, including business and engagement information, posts, and user details. Input Parameters URL string required The Instagram profile URL. Output Structure Includes comprehensive data points: Page/Profile Details : account , id , followers , posts_count , is_business_account , is_professional_account , is_verified , avg_engagement , profile_name , profile_url , profile_image_link , and more. For all data points, click here . Posts API Collect by URL This API enables users to collect detailed data from Instagram posts by providing a post URL. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Post Details : post_id , description , hashtags , date_posted , num_comments , likes , content_type , video_view_count , video_play_count , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : photos , videos , thumbnail , display_url (link only, not the file itself), audio. Discover by URL This API allows users to discover recent Instagram posts from a public profile by providing the profile URL and specifying additional parameters. Input Parameters URL string required The Instagram profile URL. num_of_posts number The number of recent posts to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date). post_type string Specify the type of posts to collect (e.g., post, reel). Output Structure Includes comprehensive data points: Post Details: post_id , description , hashtags , date_posted , num_comments , likes , video_view_count , video_play_count ,and more. For all data points, click here . Page/Profile Details: user_posted , followers , posts_count , profile_image_link , is_verified , profile_url , is_paid_partnership , partnership_details , user_posted_id Attachments and Media: photos , videos , thumbnail , audio , display_url , content_type , product_type , coauthor_producers , tagged_users . This API is designed to allow for filtering, exclusion of specific posts, and collecting posts by type (regular post or reel) within a defined time frame. It provides detailed post and profile information, making it ideal for data collection and analytics. Comments API Collect by URL This API allows users to collect the latest comments from a specific Instagram post by providing the post URL. This API retrieves the most recent 10 comments along with associated metadata. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Comment Details : comment_id , comment_user , comment_user_url , comment_date , comment , likes_number , replies_number , replies , hashtag_comment , tagged_users_in_comment , and more. For all data points, click here . User Details : user_name , user_id , user_url We provide a limited set of data points about the profile. Post Metadata : post_url , post_user , post_id . Reels API Collect by URL This API allows users to collect detailed data about Instagram reels from public profiles by providing the reel URL. Input Parameters URL string required The Instagram reel URL. Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , tagged_users , num_comments , likes , views , video_play_count , length , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : video_url , thumbnail , audio_url . Discover by URL This API allows users to discover Instagram Reels videos from a profile URL or direct search URL. Input Parameters URL string required The Instagram profile or direct search URL. num_of_posts number The number of recent reels to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering reels in MM-DD-YYYY format. end_date string End date for filtering reels in MM-DD-YYYY format (should be later than start_date ). Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , num_comments , likes , views , video_play_count , top_comments , length , video_url , audio_url , content_id , and more. For all data points, click here . Profile Details : user_posted , followers , posts_count , following . Attachments and Media : video_url , thumbnail , audio_url (link only, not the file itself). This API provides detailed information about Instagram Reels, with filtering options by date range, exclusion of specific posts, and a limit on the number of reels collected. Was this page helpful? Yes No Facebook LinkedIn ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:25
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#discover-by-url	Instagram API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Instagram API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Posts API Collect by URL Discover by URL Comments API Collect by URL Reels API Collect by URL Discover by URL Social Media APIs Instagram API Scrapers Copy page Copy page Overview The Instagram API Suite offers multiple types of APIs, each designed for specific data collection needs from Instagram. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : N/A Interesting Columns : followers , post_count , post_hashtags , profile_name . Posts API This API allows users to collect multiple posts based on a single input URL (such as an Instagram reels URL, search URL or profile URL). Discovery functionality : - Direct URL of the Instagram reel - Direct URL of the search - Direct URL of the profile Interesting Columns : url , followers , hashtags , engagement_score_view . Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : comment_user , comment , likes_number , replies_number . The suite of APIs is designed to offer flexibility for targeted data collection, where users can input specific URLs to gather detailed post and comment data, either in bulk or with precise filtering options. Profiles API Collect by URL This API allows users to collect detailed data about an Instagram profile by providing the profile URL. It provides a comprehensive overview of an Instagram profile, including business and engagement information, posts, and user details. Input Parameters URL string required The Instagram profile URL. Output Structure Includes comprehensive data points: Page/Profile Details : account , id , followers , posts_count , is_business_account , is_professional_account , is_verified , avg_engagement , profile_name , profile_url , profile_image_link , and more. For all data points, click here . Posts API Collect by URL This API enables users to collect detailed data from Instagram posts by providing a post URL. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Post Details : post_id , description , hashtags , date_posted , num_comments , likes , content_type , video_view_count , video_play_count , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : photos , videos , thumbnail , display_url (link only, not the file itself), audio. Discover by URL This API allows users to discover recent Instagram posts from a public profile by providing the profile URL and specifying additional parameters. Input Parameters URL string required The Instagram profile URL. num_of_posts number The number of recent posts to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date). post_type string Specify the type of posts to collect (e.g., post, reel). Output Structure Includes comprehensive data points: Post Details: post_id , description , hashtags , date_posted , num_comments , likes , video_view_count , video_play_count ,and more. For all data points, click here . Page/Profile Details: user_posted , followers , posts_count , profile_image_link , is_verified , profile_url , is_paid_partnership , partnership_details , user_posted_id Attachments and Media: photos , videos , thumbnail , audio , display_url , content_type , product_type , coauthor_producers , tagged_users . This API is designed to allow for filtering, exclusion of specific posts, and collecting posts by type (regular post or reel) within a defined time frame. It provides detailed post and profile information, making it ideal for data collection and analytics. Comments API Collect by URL This API allows users to collect the latest comments from a specific Instagram post by providing the post URL. This API retrieves the most recent 10 comments along with associated metadata. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Comment Details : comment_id , comment_user , comment_user_url , comment_date , comment , likes_number , replies_number , replies , hashtag_comment , tagged_users_in_comment , and more. For all data points, click here . User Details : user_name , user_id , user_url We provide a limited set of data points about the profile. Post Metadata : post_url , post_user , post_id . Reels API Collect by URL This API allows users to collect detailed data about Instagram reels from public profiles by providing the reel URL. Input Parameters URL string required The Instagram reel URL. Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , tagged_users , num_comments , likes , views , video_play_count , length , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : video_url , thumbnail , audio_url . Discover by URL This API allows users to discover Instagram Reels videos from a profile URL or direct search URL. Input Parameters URL string required The Instagram profile or direct search URL. num_of_posts number The number of recent reels to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering reels in MM-DD-YYYY format. end_date string End date for filtering reels in MM-DD-YYYY format (should be later than start_date ). Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , num_comments , likes , views , video_play_count , top_comments , length , video_url , audio_url , content_id , and more. For all data points, click here . Profile Details : user_posted , followers , posts_count , following . Attachments and Media : video_url , thumbnail , audio_url (link only, not the file itself). This API provides detailed information about Instagram Reels, with filtering options by date range, exclusion of specific posts, and a limit on the number of reels collected. Was this page helpful? Yes No Facebook LinkedIn ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:25
https://git-scm.com/book/ms/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. 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 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, as well as any newly staged files; 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. 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 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. Note GitHub changed the default branch name from master to main in mid-2020, and other Git hosts followed suit. So you may find that the default branch name in some newly created repositories is main and not master . In addition, the default branch name can be changed (as you have seen in Your default branch name ), so you may see a different name for the default branch. However, Git itself still uses master as the default, so we will use it throughout the book. 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), and which hasn’t yet been staged; 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 Tip 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. Note 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 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 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. Note 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 Getting Started . 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. Note 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:25
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#param-start-date	Instagram API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Instagram API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Posts API Collect by URL Discover by URL Comments API Collect by URL Reels API Collect by URL Discover by URL Social Media APIs Instagram API Scrapers Copy page Copy page Overview The Instagram API Suite offers multiple types of APIs, each designed for specific data collection needs from Instagram. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : N/A Interesting Columns : followers , post_count , post_hashtags , profile_name . Posts API This API allows users to collect multiple posts based on a single input URL (such as an Instagram reels URL, search URL or profile URL). Discovery functionality : - Direct URL of the Instagram reel - Direct URL of the search - Direct URL of the profile Interesting Columns : url , followers , hashtags , engagement_score_view . Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : comment_user , comment , likes_number , replies_number . The suite of APIs is designed to offer flexibility for targeted data collection, where users can input specific URLs to gather detailed post and comment data, either in bulk or with precise filtering options. Profiles API Collect by URL This API allows users to collect detailed data about an Instagram profile by providing the profile URL. It provides a comprehensive overview of an Instagram profile, including business and engagement information, posts, and user details. Input Parameters URL string required The Instagram profile URL. Output Structure Includes comprehensive data points: Page/Profile Details : account , id , followers , posts_count , is_business_account , is_professional_account , is_verified , avg_engagement , profile_name , profile_url , profile_image_link , and more. For all data points, click here . Posts API Collect by URL This API enables users to collect detailed data from Instagram posts by providing a post URL. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Post Details : post_id , description , hashtags , date_posted , num_comments , likes , content_type , video_view_count , video_play_count , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : photos , videos , thumbnail , display_url (link only, not the file itself), audio. Discover by URL This API allows users to discover recent Instagram posts from a public profile by providing the profile URL and specifying additional parameters. Input Parameters URL string required The Instagram profile URL. num_of_posts number The number of recent posts to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date). post_type string Specify the type of posts to collect (e.g., post, reel). Output Structure Includes comprehensive data points: Post Details: post_id , description , hashtags , date_posted , num_comments , likes , video_view_count , video_play_count ,and more. For all data points, click here . Page/Profile Details: user_posted , followers , posts_count , profile_image_link , is_verified , profile_url , is_paid_partnership , partnership_details , user_posted_id Attachments and Media: photos , videos , thumbnail , audio , display_url , content_type , product_type , coauthor_producers , tagged_users . This API is designed to allow for filtering, exclusion of specific posts, and collecting posts by type (regular post or reel) within a defined time frame. It provides detailed post and profile information, making it ideal for data collection and analytics. Comments API Collect by URL This API allows users to collect the latest comments from a specific Instagram post by providing the post URL. This API retrieves the most recent 10 comments along with associated metadata. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Comment Details : comment_id , comment_user , comment_user_url , comment_date , comment , likes_number , replies_number , replies , hashtag_comment , tagged_users_in_comment , and more. For all data points, click here . User Details : user_name , user_id , user_url We provide a limited set of data points about the profile. Post Metadata : post_url , post_user , post_id . Reels API Collect by URL This API allows users to collect detailed data about Instagram reels from public profiles by providing the reel URL. Input Parameters URL string required The Instagram reel URL. Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , tagged_users , num_comments , likes , views , video_play_count , length , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : video_url , thumbnail , audio_url . Discover by URL This API allows users to discover Instagram Reels videos from a profile URL or direct search URL. Input Parameters URL string required The Instagram profile or direct search URL. num_of_posts number The number of recent reels to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering reels in MM-DD-YYYY format. end_date string End date for filtering reels in MM-DD-YYYY format (should be later than start_date ). Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , num_comments , likes , views , video_play_count , top_comments , length , video_url , audio_url , content_id , and more. For all data points, click here . Profile Details : user_posted , followers , posts_count , following . Attachments and Media : video_url , thumbnail , audio_url (link only, not the file itself). This API provides detailed information about Instagram Reels, with filtering options by date range, exclusion of specific posts, and a limit on the number of reels collected. Was this page helpful? Yes No Facebook LinkedIn ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:25
https://www.sushi.com/rootstock/explore/pools	Trade Explore Positions Stake Rootstock Mainnet TVL Volume Tokens Pools Blade Pools Type Network Rootstock Mainnet 🧑‍🌾 Farms only Name TVL Volume (24h) Volume (1w) Transactions (24h) APR Rootstock Mainnet Connect Wallet Connect Rootstock Mainnet TVL Volume Pools \| Sushi 🍣	2026-01-13T09:29:25
https://www.linkedin.com/uas/login?session_redirect=%2Fproducts%2Foutsystems&trk=products_details_guest_primary_call_to_action	LinkedIn Login, Sign in \| LinkedIn Sign in Sign in with Apple Sign in with a passkey By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . or Email or phone Password Show Forgot password? Keep me logged in Sign in We’ve emailed a one-time link to your primary email address Click on the link to sign in instantly to your LinkedIn account. If you don’t see the email in your inbox, check your spam folder. Resend email Back New to LinkedIn? Join now Agree & Join LinkedIn By clicking Continue, you agree to LinkedIn’s User Agreement , Privacy Policy , and Cookie Policy . LinkedIn © 2026 User Agreement Privacy Policy Community Guidelines Cookie Policy Copyright Policy Send Feedback Language العربية (Arabic) বাংলা (Bangla) Čeština (Czech) Dansk (Danish) Deutsch (German) Ελληνικά (Greek) English (English) Español (Spanish) فارسی (Persian) Suomi (Finnish) Français (French) हिंदी (Hindi) Magyar (Hungarian) Bahasa Indonesia (Indonesian) Italiano (Italian) עברית (Hebrew) 日本語 (Japanese) 한국어 (Korean) मराठी (Marathi) Bahasa Malaysia (Malay) Nederlands (Dutch) Norsk (Norwegian) ਪੰਜਾਬੀ (Punjabi) Polski (Polish) Português (Portuguese) Română (Romanian) Русский (Russian) Svenska (Swedish) తెలుగు (Telugu) ภาษาไทย (Thai) Tagalog (Tagalog) Türkçe (Turkish) Українська (Ukrainian) Tiếng Việt (Vietnamese) 简体中文 (Chinese (Simplified)) 正體中文 (Chinese (Traditional))	2026-01-13T09:29:25
https://git-scm.com/book/ru/v2/%d0%92%d0%b2%d0%b5%d0%b4%d0%b5%d0%bd%d0%b8%d0%b5-%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 1.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:25
https://babelfish.money/wp-json/oembed/1.0/embed?url=https%3A%2F%2F%2F	Babelfish – BabelFish BABELFISH Github Docs Forum Launch Dapp X sun (Traced) crescent-moon-phase-shape-with-two-stars (Traced)2022 BABELFISH Github Docs Analytics X LAUNCH DAPP UNIVERSAL MULTI-CHAIN STABLECOIN BabelFish's mind-boggling objective is to aggregate and distribute stablecoins, enhance flow, and push hyperBitcoinization.   ABOUT BabelFish DAO Money Protocol is the simplest and most mind-bogglingly useful thing in the DeFi Universe. It absorbs, aggregates and distributes USD-pegged stablecoins across chains; the practical upshot of all this is that if you stick stablecoins to it, you can neatly cross the language divide between any chains. BabelFish's meta-stablecoin, XUSD, is backed by the underlying aggregated stablecoins to leverage and enhance their combined flow and utility across protocols and users. FISH holders can vote on improvement proposals, such as which stablecoins to accept, or what percent of collateral to lend. Learn More About It GO TO OUR GITBOOK What It Does What It Does: Since the big bang of DeFi in the crypto galaxy, many stablecoin projects have been created to meet the demand for USD. Different stablecoin brands with unique selling points are competing to represent the same dollar, but they do not translate 1:1, and crypto dollar liquidity is fractured between issuers and protocols. As DeFi markets expand beyond Ethereum to multiple chains, stablecoin liquidity is fractured further by the bridges used, which is suboptimal for the industry. BabelFish abstracts away these differences by aggregating stablecoins from multiple isolated liquidity lakes and providing users with access to the combined ocean of crypto-dollars available. Think of it as a translator or a converter: if a user wants to use crypto dollars on another chain, she can stick it on BabelFish and seamlessly get a par-value equivalent on the other side. What Is The FISH DAO The BabelFish DAO Money Protocol is ultimately directed by the will of FISH token holders participating in governance. From protocol improvement proposals to budget allocation and partnerships, it is the community that will be able to decide on the direction of the protocol. If you are passionate about the stablecoin ecosystem, this is the DAO for you. Help define protocol rules and parameters around the collateral accepted, discuss community incentives, manage risk, and much more. The future of BabelFish depends on active FISH holder participation. Help build, shape and enhance the stablecoin ecosystem. Participate in stablecoin collateral management. Be rewarded for staking and actively participating with FISH in governance. Mind-Bogglingly Useful XUSD is collateralized 1:1 by a hedged basket of accepted stablecoins across chains, which enables users and protocols to tap into the combined liquidity and utility of the underlying collateral and also enhances stablecoin flow across the ecosystem. User deposits an accepted stablecoin on BabelFish protocol. Protocol issues XUSD, its convertible stablecoin backed 1:1 User can use XUSD on accepted protocols, bridge between chains, and redeem back at any time What Moves BabelFish The need for a "trustless stablecoin translation device" seems painfully clear. The accelerated growth and velocity of crypto dollars is unstoppable, we expect demand for programmable money to continue accelerating as we onboard the first billion users. But the market remains fragmented, two players dominate >80% of the total USD-stablecoin float, and systemic and idiosyncratic risks abound. In the decentralised economy we ought not to rely on one or two issuers of USD-stablecoins but rather enable a thousand stablecoins to bloom and communicate with each other to bring mass adoption. For BabelFish DAO Money Protocol it is important that our first product, XUSD, is the safest, easiest and ultimate stablecoin instrument out there in crypto space. JOIN US TO EXPERIENCE BABELFISH	2026-01-13T09:29:25
https://git-scm.com/book/tl/v2/Distributed-Git-Distributed-Workflows	Git - Distributed Workflows 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 5.1 Distributed Git - Distributed Workflows Now that you have a remote Git repository set up as a focal point for all the developers to share their code, and you’re familiar with basic Git commands in a local workflow, you’ll look at how to utilize some of the distributed workflows that Git affords you. In this chapter, you’ll see how to work with Git in a distributed environment as a contributor and an integrator. That is, you’ll learn how to contribute code successfully to a project and make it as easy on you and the project maintainer as possible, and also how to maintain a project successfully with a number of developers contributing. Distributed Workflows Unlike Centralized Version Control Systems (CVCSs), the distributed nature of Git allows you to be far more flexible in how developers collaborate on projects. In centralized systems, every developer is a node working more or less equally on a central hub. In Git, however, every developer is potentially both a node and a hub — that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to. This opens a vast range of workflow possibilities for your project and/or your team, so we’ll cover a few common paradigms that take advantage of this flexibility. We’ll go over the strengths and possible weaknesses of each design; you can choose a single one to use, or you can mix and match features from each. Centralized Workflow In centralized systems, there is generally a single collaboration model — the centralized workflow. One central hub, or repository , can accept code, and everyone synchronizes their work to it. A number of developers are nodes — consumers of that hub — and synchronize to that one place. Figure 54. Centralized workflow. This means that if two developers clone from the hub and both make changes, the first developer to push their changes back up can do so with no problems. The second developer must merge in the first one’s work before pushing changes up, so as not to overwrite the first developer’s changes. This concept is as true in Git as it is in Subversion (or any CVCS), and this model works perfectly well in Git. If you are already comfortable with a centralized workflow in your company or team, you can easily continue using that workflow with Git. Simply set up a single repository, and give everyone on your team push access; Git won’t let users overwrite each other. Say John and Jessica both start working at the same time. John finishes his change and pushes it to the server. Then Jessica tries to push her changes, but the server rejects them. She is told that she’s trying to push non-fast-forward changes and that she won’t be able to do so until she fetches and merges. This workflow is attractive to a lot of people because it’s a paradigm that many are familiar and comfortable with. This is also not limited to small teams. With Git’s branching model, it’s possible for hundreds of developers to successfully work on a single project through dozens of branches simultaneously. Integration-Manager Workflow Because Git allows you to have multiple remote repositories, it’s possible to have a workflow where each developer has write access to their own public repository and read access to everyone else’s. This scenario often includes a canonical repository that represents the “official” project. To contribute to that project, you create your own public clone of the project and push your changes to it. Then, you can send a request to the maintainer of the main project to pull in your changes. The maintainer can then add your repository as a remote, test your changes locally, merge them into their branch, and push back to their repository. The process works as follows (see Integration-manager workflow. ): The project maintainer pushes to their public repository. A contributor clones that repository and makes changes. The contributor pushes to their own public copy. The contributor sends the maintainer an email asking them to pull changes. The maintainer adds the contributor’s repository as a remote and merges locally. The maintainer pushes merged changes to the main repository. Figure 55. Integration-manager workflow. This is a very common workflow with hub-based tools like GitHub or GitLab, where it’s easy to fork a project and push your changes into your fork for everyone to see. One of the main advantages of this approach is that you can continue to work, and the maintainer of the main repository can pull in your changes at any time. Contributors don’t have to wait for the project to incorporate their changes — each party can work at their own pace. Dictator and Lieutenants Workflow This is a variant of a multiple-repository workflow. It’s generally used by huge projects with hundreds of collaborators; one famous example is the Linux kernel. Various integration managers are in charge of certain parts of the repository; they’re called lieutenants . All the lieutenants have one integration manager known as the benevolent dictator. The benevolent dictator pushes from his directory to a reference repository from which all the collaborators need to pull. The process works like this (see Benevolent dictator workflow. ): Regular developers work on their topic branch and rebase their work on top of master . The master branch is that of the reference directory to which the dictator pushes. Lieutenants merge the developers' topic branches into their master branch. The dictator merges the lieutenants' master branches into the dictator’s master branch. Finally, the dictator pushes that master branch to the reference repository so the other developers can rebase on it. Figure 56. Benevolent dictator workflow. This kind of workflow isn’t common, but can be useful in very big projects, or in highly hierarchical environments. It allows the project leader (the dictator) to delegate much of the work and collect large subsets of code at multiple points before integrating them. Workflows Summary These are some commonly used workflows that are possible with a distributed system like Git, but you can see that many variations are possible to suit your particular real-world workflow. Now that you can (hopefully) determine which workflow combination may work for you, we’ll cover some more specific examples of how to accomplish the main roles that make up the different flows. In the next section, you’ll learn about a few common patterns for contributing to a project. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:25
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_PE	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:25
https://www.linkedin.com/products/dataport-a%C3%B6r-dataport-consulting/?trk=products_seo_search#main-content	Dataport Consulting \| LinkedIn Skip to main content LinkedIn Dataport AöR in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Dataport Consulting Strategic Planning Software by Dataport AöR See who's skilled in this Add as skill Contact us Report this product About Der öffentlichen Verwaltung eröffnen sich z. B. durch das OZG, KI sowie eine notwendige Ende-zu-Ende-Digitalisierung neue Möglichkeiten. Dataport Consulting, Ihr Digitalisierungs- und Innovationspartner, unterstützt Sie dabei, passende Lösungen für Sie zu finden und Veränderungen nachhaltig in Ihrer Organisation zu verankern. Lassen Sie sich beraten und kontaktieren Sie uns. ✅ Strategieberatung ✅ Innovationsberatung und Service Design ✅ Prozessmanagement und -automation ✅ Changemanagement und Organisationsentwicklung This product is intended for Head of Section Resort Manager Department Manager Senior Administrative Officer Civil Servant State Secretary Chief Information Security Officer Chief Digital Officer Chief Information Officer Process Manager Media Products media viewer No more previous content Dataport Consulting. Verwaltungswissen. Beratungskompetenz. Trendaffinität. No more next content Similar products Focus Focus Strategic Planning Software Aha! Roadmaps Aha! Roadmaps Strategic Planning Software DIGITAL PRODUCTS DIGITAL PRODUCTS Strategic Planning Software Cascade Cascade Strategic Planning Software WorkBoard WorkBoard Strategic Planning Software Stratsys platform for compliance and efficiency Stratsys platform for compliance and efficiency Strategic Planning Software Sign in to see more Show more Show less Dataport AöR products data[port]ai data[port]ai Data Science & Machine Learning Platforms dDataBox dDataBox Managed File Transfer (MFT) Software dMessenger dMessenger Enterprise Messaging Software dProjectTracking dProjectTracking Project Management Software dWebService dWebService Web Hosting dWorkflow dWorkflow Workflow Management Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language	2026-01-13T09:29:25
https://git-scm.com/book/fr/v2/Les-bases-de-Git-Les-alias-Git	Git - Les alias 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. 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 2.7 Les bases de Git - Les alias Git Les alias Git Avant de clore ce chapitre sur les bases de Git, il reste une astuce qui peut rendre votre apprentissage de Git plus simple, facile ou familier : les alias. Nous n’y ferons pas référence ni ne les considérerons utilisés dans la suite du livre, mais c’est un moyen de facilité qui mérite d’être connu. Git ne complète pas votre commande si vous ne la tapez que partiellement. Si vous ne voulez pas avoir à taper l’intégralité du texte de chaque commande, vous pouvez facilement définir un alias pour chaque commande en utilisant git config . Voici quelques exemples qui pourraient vous intéresser : $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status Ceci signifie que, par exemple, au lieu de taper git commit , vous n’avez plus qu’à taper git ci . Au fur et à mesure de votre utilisation de Git, vous utiliserez probablement d’autres commandes plus fréquemment. Dans ce cas, n’hésitez pas à créer de nouveaux alias. Cette technique peut aussi être utile pour créer des commandes qui vous manquent. Par exemple, pour corriger le problème d’ergonomie que vous avez rencontré lors de la désindexation d’un fichier, vous pourriez créer un alias pour désindexer : $ git config --global alias.unstage 'reset HEAD --' Cela rend les deux commandes suivantes équivalentes : $ git unstage fileA $ git reset HEAD fileA Cela rend les choses plus claires. Il est aussi commun d’ajouter un alias last , de la manière suivante : $ git config --global alias.last 'log -1 HEAD' Ainsi, vous pouvez visualiser plus facilement le dernier commit : $ 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> Pour explication, Git remplace simplement la nouvelle commande par tout ce que vous lui aurez demandé d’aliaser. Si par contre vous souhaitez lancer une commande externe plutôt qu’une sous-commande Git, vous pouvez commencer votre commande par un caractère ! . C’est utile si vous écrivez vos propres outils pour travailler dans un dépôt Git. On peut par exemple aliaser git visual pour lancer 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:25
https://git-scm.com/book/fr/v2/Les-branches-avec-Git-Les-branches-en-bref	Git - Les branches en bref 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 3.1 Les branches avec Git - Les branches en bref Presque tous les VCS proposent une certaine forme de gestion de branches. Créer une branche signifie diverger de la ligne principale de développement et continuer à travailler sans impacter cette ligne. Pour de nombreux VCS, il s’agit d’un processus coûteux qui nécessite souvent la création d’une nouvelle copie du répertoire de travail, ce qui peut prendre longtemps dans le cas de gros projets. Certaines personnes considèrent le modèle de gestion de branches de Git comme ce qu’il a de plus remarquable et il offre sûrement à Git une place à part au sein de la communauté des VCS. En quoi est-il si spécial ? La manière dont Git gère les branches est incroyablement légère et permet de réaliser les opérations sur les branches de manière quasi instantanée et, généralement, de basculer entre les branches aussi rapidement. À la différence de nombreux autres VCS, Git encourage des méthodes qui privilégient la création et la fusion fréquentes de branches, jusqu’à plusieurs fois par jour. Bien comprendre et maîtriser cette fonctionnalité vous permettra de faire de Git un outil puissant et unique et peut totalement changer votre manière de développer. Les branches en bref Pour réellement comprendre la manière dont Git gère les branches, nous devons revenir en arrière et examiner de plus près comment Git stocke ses données. Si vous vous souvenez bien du chapitre Démarrage rapide , Git ne stocke pas ses données comme une série de modifications ou de différences successives mais plutôt comme une série d’instantanés (appelés snapshots ). Lorsque vous faites un commit, Git stocke un objet commit qui contient un pointeur vers l’instantané ( snapshot ) du contenu que vous avez indexé. Cet objet contient également les noms et prénoms de l’auteur, le message que vous avez renseigné ainsi que des pointeurs vers le ou les commits qui précèdent directement ce commit : aucun parent pour le commit initial, un parent pour un commit normal et de multiples parents pour un commit qui résulte de la fusion d’une ou plusieurs branches. Pour visualiser ce concept, supposons que vous avez un répertoire contenant trois fichiers que vous indexez puis validez. L’indexation des fichiers calcule une empreinte ( checksum ) pour chacun (via la fonction de hachage SHA-1 mentionnée au chapitre Démarrage rapide ), stocke cette version du fichier dans le dépôt Git (Git les nomme blobs ) et ajoute cette empreinte à la zone d’index ( staging area ) : $ git add README test.rb LICENSE $ git commit -m 'initial commit of my project' Lorsque vous créez le commit en lançant la commande git commit , Git calcule l’empreinte de chaque sous-répertoire (ici, seulement pour le répertoire racine) et stocke ces objets de type arbre dans le dépôt Git. Git crée alors un objet commit qui contient les méta-données et un pointeur vers l’arbre de la racine du projet de manière à pouvoir recréer l’instantané à tout moment. Votre dépôt Git contient à présent cinq objets : un blob pour le contenu de chacun de vos trois fichiers, un arbre ( tree ) qui liste le contenu du répertoire et spécifie quels noms de fichiers sont attachés à quels blobs et enfin un objet commit portant le pointeur vers l’arbre de la racine ainsi que toutes les méta-données attachées au commit . Figure 9. Un commit et son arbre Si vous faites des modifications et validez à nouveau, le prochain commit stocke un pointeur vers le commit le précédant immédiatement. Figure 10. Commits et leurs parents Une branche dans Git est simplement un pointeur léger et déplaçable vers un de ces commits . La branche par défaut dans Git s’appelle master . Au fur et à mesure des validations, la branche master pointe vers le dernier des commits réalisés. À chaque validation, le pointeur de la branche master avance automatiquement. Note La branche master n’est pas une branche spéciale. Elle est identique à toutes les autres branches. La seule raison pour laquelle chaque dépôt en a une est que la commande git init la crée par défaut et que la plupart des gens ne s’embêtent pas à la changer. Figure 11. Une branche et l’historique de ses commits Créer une nouvelle branche Que se passe-t-il si vous créez une nouvelle branche ? Eh bien, cela crée un nouveau pointeur pour vous. Supposons que vous créez une nouvelle branche nommée test . Vous utilisez pour cela la commande git branch : $ git branch testing Cela crée un nouveau pointeur vers le commit courant. Figure 12. Deux branches pointant vers la même série de commits Comment Git connaît-il alors la branche sur laquelle vous vous trouvez ? Il conserve à cet effet un pointeur spécial appelé HEAD . Vous remarquez que sous cette appellation se cache un concept très différent de celui utilisé dans les autres VCS tels que Subversion ou CVS. Dans Git, il s’agit simplement d’un pointeur sur la branche locale où vous vous trouvez. Dans ce cas, vous vous trouvez toujours sur master . En effet, la commande git branch n’a fait que créer une nouvelle branche — elle n’a pas fait basculer la copie de travail vers cette branche. Figure 13. HEAD pointant vers une branche Vous pouvez vérifier cela facilement grâce à la commande git log qui vous montre vers quoi les branches pointent. Il s’agit de l’option --decorate . $ git log --oneline --decorate f30ab (HEAD, master, test) add feature #32 - ability to add new 34ac2 fixed bug #ch1328 - stack overflow under certain conditions 98ca9 initial commit of my project Vous pouvez voir les branches master et test qui se situent au niveau du commit f30ab . Basculer entre les branches Pour basculer sur une branche existante, il suffit de lancer la commande git checkout . Basculons sur la nouvelle branche testing : $ git checkout testing Cela déplace HEAD pour le faire pointer vers la branche testing . Figure 14. HEAD pointe vers la branche courante Qu’est-ce que cela signifie ? Et bien, faisons une autre validation : $ vim test.rb $ git commit -a -m 'made a change' Figure 15. La branche HEAD avance à chaque commit C’est intéressant parce qu’à présent, votre branche testing a avancé tandis que la branche master pointe toujours sur le commit sur lequel vous étiez lorsque vous avez lancé la commande git checkout pour changer de branche. Retournons sur la branche master : $ git checkout master Note git log ne montre pas toutes les branches tout le temps Si vous alliez lancer git log maintenant, vous pourriez vous demander où se trouve la branche « testing » que vous avez tout juste créée, car elle n’apparaît pas dans la sortie. La branche n’a pas disparu ; Git ne sait juste pas que cette branche vous intéresse et il essaie de vous montrer ce qu’il pense être le plus pertinent. Autrement dit, par défaut, git log ne montre que l’historique des commits sous la branche qui est extraite. Pour montrer l’historique des commites de la branche désirée, vous devez la spécifier explicitement : git log testing . Pour afficher toutes les branches, ajoutez l’option --all à la commande git log . Figure 16. HEAD est déplacé lors d’un checkout Cette commande a réalisé deux actions. Elle a remis le pointeur HEAD sur la branche master et elle a replacé les fichiers de votre répertoire de travail dans l’état du snapshot pointé par master . Cela signifie aussi que les modifications que vous réalisez à partir de ce point divergeront de l’ancienne version du projet. Cette commande annule les modifications réalisées dans la branche testing pour vous permettre de repartir dans une autre direction. Note Changer de branche modifie les fichiers dans votre répertoire de travail Il est important de noter que lorsque vous changez de branche avec Git, les fichiers de votre répertoire de travail sont modifiés. Si vous basculez vers une branche plus ancienne, votre répertoire de travail sera remis dans l’état dans lequel il était lors du dernier commit sur cette branche. Si git n’est pas en mesure d’effectuer cette action proprement, il ne vous laissera pas changer de branche. Réalisons quelques autres modifications et validons à nouveau : $ vim test.rb $ git commit -a -m 'made other changes' Maintenant, l’historique du projet a divergé (voir Divergence d’historique ). Vous avez créé une branche et basculé dessus, y avez réalisé des modifications, puis vous avez rebasculé sur la branche principale et réalisé d’autres modifications. Ces deux modifications sont isolées dans des branches séparées : vous pouvez basculer d’une branche à l’autre et les fusionner quand vous êtes prêt. Et vous avez fait tout ceci avec de simples commandes : branch , checkout et commit . Figure 17. Divergence d’historique Vous pouvez également voir ceci grâce à la commande git log . La commande git log --oneline --decorate --graph --all va afficher l’historique de vos commits , affichant les endroits où sont positionnés vos pointeurs de branche ainsi que la manière dont votre historique a divergé. $ git log --oneline --decorate --graph --all * c2b9e (HEAD, master) made other changes \| * 87ab2 (test) made a change \|/ * f30ab add feature #32 - ability to add new formats to the * 34ac2 fixed bug #ch1328 - stack overflow under certain conditions * 98ca9 initial commit of my project Parce qu’une branche Git n’est en fait qu’un simple fichier contenant les 40 caractères de l’empreinte SHA-1 du commit sur lequel elle pointe, les branches ne coûtent quasiment rien à créer et à détruire. Créer une branche est aussi simple et rapide qu’écrire 41 caractères dans un fichier (40 caractères plus un retour chariot). C’est une différence de taille avec la manière dont la plupart des VCS gèrent les branches, qui implique de copier tous les fichiers du projet dans un second répertoire. Cela peut durer plusieurs secondes ou même quelques minutes selon la taille du projet, alors que pour Git, le processus est toujours instantané. De plus, comme nous enregistrons les parents quand nous validons les modifications, la détermination de l’ancêtre commun approprié pour la fusion est réalisée automatiquement pour nous et est généralement une opération très facile. Ces fonctionnalités encouragent naturellement les développeurs à créer et utiliser souvent des branches. Voyons pourquoi vous devriez en faire autant. Note Créer une branche et basculer dessus en même temps Il est habituel de créer une nouvelle branche et de vouloir basculer sur cette nouvelle branche en même temps — ça peut être réalisé en une seule opération avec git checkout -b <nouvelle-branche> . Note Depuis Git version 2.23, on peut utiliser git switch au lieu de git checkout pour : basculer sur une branche existante : git switch testing-branch , créer une branche et basculer dessus ; git switch -c nouvelle-branche ; le drapeau -c signifie créer, vous pouvez aussi utiliser le drapeau complet --create , revenir sur votre branche précédemment extraite : 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:25
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#param-url-1	Pinterest API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Pinterest API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Discover by Keywords Posts API Collect by URL Discover by Profile URL Discover by Keywords Social Media APIs Pinterest API Scrapers Copy page Copy page Overview The Pinterest API Suite offers multiple types of APIs, each designed for specific data collection needs from Pinterest. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Discover by Keywords. Interesting Columns : name , following_count , website , follower_count . Posts API This API allows users to collect multiple posts based on a single input. Discovery functionality : - Discover by profile URL. - Discover by Keywords. Interesting Columns : title , content , user_name , likes . Profiles API Collect by URL This API allows users to retrieve detailed Pinterest profile information using the provided profile URL. Input Parameters : URL string required The Pinterest profile URL. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metrics : following_count , follower_count , boards_num , saved . Additional Information : last_updated , posts_page_url , discovery_input . This API allows users to collect detailed insights into a Pinterest profile, including user statistics, engagement metrics, and profile information. Discover by Keywords This API allows users to discover Pinterest profiles based on a specified keyword. Input Parameters : keyword string required The keyword to search for profiles. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metric s: following_count , follower_count , boards_num , saved. Additional Information : last_updated , posts_page_url , discovery_input . This API enables users to find Pinterest profiles related to a specific keyword, offering insights into user statistics, engagement, and profile details. Posts API Collect by URL This API allows users to collect detailed post data from a specific Pinterest post using the provided post URL. Input Parameters : URL string required The Pinterest post URL. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , post_type . For all data points, click here . User Details : user_name , user_url , user_id , followers . Post Metrics : likes , comments_num , comments , categories . Media & Attachments : image_video_url , video_length , attached_files . Hashtags & Discovery : hashtags , discovery_input . This API allows users to retrieve detailed insights into a specific Pinterest post, including user engagement, post content, media, and other related information. Discover by Profile URL This API allows users to retrieve posts from a specific Pinterest profile based on the provided profile URL. Input Parameters : URL string required The Pinterest profile URL from which to collect posts. num_of_posts number The number of posts to collect. If omitted, there is no limit. posts_to_not_include array An array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date ). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date ). Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users tso collect posts from a specific Pinterest profile, allowing for filtering by date, exclusion of specific posts, and retrieval of detailed post data including media, comments, and engagement metrics. Discover by Keywords This API allows users to discover Pinterest posts based on a specific keyword, enabling efficient content discovery. Input Parameters : keyword string required The keyword to search for posts, such as “food” or any other relevant term. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users to search for Pinterest posts based on a specific keyword, providing detailed insights into the content, engagement, media, and associated metrics for efficient discovery. Was this page helpful? Yes No Twitter Quora ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:25
https://git-scm.com/book/pt-br/v2/Branches-no-Git-Branches-em-poucas-palavras	Git - Branches em poucas palavras 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. Começando 1.1 Sobre Controle de Versão 1.2 Uma Breve História do Git 1.3 O Básico do Git 1.4 A Linha de Comando 1.5 Instalando o Git 1.6 Configuração Inicial do Git 1.7 Pedindo Ajuda 1.8 Sumário 2. Fundamentos de Git 2.1 Obtendo um Repositório Git 2.2 Gravando Alterações em Seu Repositório 2.3 Vendo o histórico de Commits 2.4 Desfazendo coisas 2.5 Trabalhando de Forma Remota 2.6 Criando Tags 2.7 Apelidos Git 2.8 Sumário 3. Branches no Git 3.1 Branches em poucas palavras 3.2 O básico de Ramificação (Branch) e Mesclagem (Merge) 3.3 Gestão de Branches 3.4 Fluxo de Branches 3.5 Branches remotos 3.6 Rebase 3.7 Sumário 4. Git no servidor 4.1 Os Protocolos 4.2 Getting Git on a Server 4.3 Gerando Sua Chave Pública SSH 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 Sumário 5. Distributed Git 5.1 Fluxos de Trabalho Distribuídos 5.2 Contribuindo com um Projeto 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Configurando uma conta 6.2 Contribuindo em um projeto 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. Funcionamento Interno do Git 10.1 Encanamento e Porcelana 10.2 Objetos do Git 10.3 Referências do Git 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Variáveis de ambiente 10.9 Sumário A1. Appendix A: Git em Outros Ambientes 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 Resumo 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 3.1 Branches no Git - Branches em poucas palavras Quase todo Sistema de Controle de Versionamento tem alguma forma de suporte a ramificações (Branches). Ramificação significa que você diverge da linha principal de desenvolvimento e continua a trabalhar sem alterar essa linha principal. Em muitas ferramentas de versionamento, este é um processo um tanto difícil, geralmente exigindo que você crie uma nova cópia do diretório do código-fonte, o que pode demorar muito em projetos maiores. Algumas pessoas se referem ao modelo de ramificação do Git como seu “recurso matador” e certamente diferencia o Git na comunidade de sistemas de versionamento. Por que isso é tão especial? A forma como o Git cria branches é incrivelmente leve, tornando as operações de ramificação quase instantâneas, alternando entre os branches geralmente com a mesma rapidez. Ao contrário de muitos outros sistemas, o Git incentiva fluxos de trabalho que se ramificam e se fundem com frequência, até mesmo várias vezes ao dia. Compreender e dominar esse recurso oferece uma ferramenta poderosa e única e pode mudar totalmente a maneira como você desenvolve. Branches em poucas palavras Para realmente entender como o Git trabalha com Branches, precisamos dar um passo atrás e examinar como o Git armazena seus dados. Como você deve se lembrar de << ch01-introdução >>, o Git não armazena dados como uma série de mudanças ou diferenças, mas sim como uma série de snapshots (instantâneos de um momento) . Quando você faz um commit, o Git armazena um objeto de commit que contém um ponteiro para o snapshot do conteúdo que você testou. Este objeto também contém o nome do autor e o e-mail, a mensagem que você digitou e ponteiros para o commit ou commits que vieram antes desse commit (seu pai ou pais): sem pai para o commit inicial, um pai para um commit normal, e vários pais para um commit que resulta de uma fusão de dois ou mais branches. Para verificar isso, vamos assumir que você tem um diretório contendo três arquivos, e você seleciona todos eles e efetua o commit. Ele Prepara os arquivos e calcula uma verificação para cada um (o hash SHA-1 que mencionamos em << ch01-introdução >>), armazena essa versão do arquivo no repositório Git (Git se refere a eles como blobs), e adiciona esse hash de verificação à área de preparação (staging area): $ git add README test.rb LICENSE $ git commit -m 'The initial commit of my project' Quando você faz um commit executando git commit , o Git verifica cada subdiretório (neste caso, apenas o diretório raiz do projeto) e armazena esses objetos no repositório do Git. O Git então cria um objeto de commit que possui os metadados e um ponteiro para a raiz do projeto para que ele possa recriar aquele snapshot quando necessário. Seu repositório Git agora contém cinco objetos: um blob para o conteúdo de cada um dos seus três arquivos, uma árvore que lista o conteúdo do diretório e especifica quais nomes de arquivo são armazenados e quais seus blobs e um commit com o ponteiro para essa árvore e todos os metadados de commit. Figure 9. Um commit e sua árvore Se você fizer algumas mudanças e confirmar novamente, o próximo commit armazena um ponteiro para o commit que veio imediatamente antes dele. Figure 10. Commits e seus pais Um branch no Git é simplesmente um ponteiro móvel para um desses commits. O nome do branch padrão no Git é master . Conforme você começa a fazer commits, você recebe um branch master que aponta para o último commit que você fez. Cada vez que você faz um novo commit, ele avança automaticamente. Note O branch ' master ' no Git não é um branch especial. É exatamente como qualquer outra ramificação. A única razão pela qual quase todo repositório tem um é que o comando git init o cria por padrão e a maioria das pessoas não se preocupa em alterá-lo. Figure 11. Um branch e seu histórico de commits Criando um Novo Branch O que acontece se você criar um novo branch? Bem, fazer isso cria um novo ponteiro para você mover. Digamos que você crie um novo branch chamado: testing. Você faz isso com o comando git branch : $ git branch testing Isso cria um novo ponteiro para o mesmo commit em que você está atualmente. Figure 12. Duas branches apontando para a mesma série de commits Como o Git sabe em qual branch você está atualmente? Ele mantém um ponteiro especial chamado HEAD . Note que isso é muito diferente do conceito de HEAD em outros sistemas de versionamento com os quais você pode estar acostumado, como Subversion ou CVS. No Git, isso é um ponteiro para o branch local em que você está. Neste caso, você ainda está em master . O comando git branch apenas criou um novo branch - ele não mudou para aquele branch. Figure 13. HEAD apontando para um branch Você pode ver isso facilmente executando um simples comando git log que mostra para onde os ponteiros do branch estão apontando. Esta opção é chamada de --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 Você pode ver os branches master e testing que estão bem ali ao lado do commit f30ab . Alternando entre Branches Para mudar para um branch existente, você executa o comando git checkout . Vamos mudar para o novo branch testing : $ git checkout testing Isso move o HEAD e o aponta para o branch testing . Figure 14. HEAD aponta para o branch atual O que isso significa? Bem, vamos fazer outro commit: $ vim test.rb $ git commit -a -m 'made a change' Figure 15. O branch do HEAD avança quando um commit é feito Isso é interessante, porque agora seu branch testing avançou, mas seu branch master ainda aponta para o commit em que você estava quando executou git checkout para alternar entre os branches. Vamos voltar para o branch master : $ git checkout master Figure 16. O HEAD se move quando você faz o checkout Esse comando fez duas coisas. Ele moveu o ponteiro HEAD de volta para apontar para o branch master , e reverteu os arquivos em seu diretório de trabalho de volta para o snapshot para o qual master aponta. Isso também significa que as alterações feitas a partir deste ponto irão divergir de uma versão mais antiga do projeto. Essencialmente, ele retrocede o trabalho que você fez em seu branch testing para que você possa ir em uma direção diferente. Note A troca de branches muda os arquivos em seu diretório de trabalho É importante notar que quando você muda de branches no Git, os arquivos em seu diretório de trabalho mudam. Se você mudar para um branch mais antigo, seu diretório de trabalho será revertido para se parecer com a última vez que você fez commit naquele branch. Se o Git não puder fazer, ele não permitirá que você faça a troca. Vamos fazer algumas mudanças e confirmar novamente: $ vim test.rb $ git commit -a -m 'made other changes' Agora o histórico do seu projeto divergiu (consulte Histórico de diferenças ). Você criou e mudou para um branch, fez algum trabalho nele e, em seguida, voltou para o seu branch principal e fez outro trabalho. Ambas as mudanças são isoladas em branches separados: você pode alternar entre os branches e mesclá-los quando estiver pronto. E você fez tudo isso com comandos simples branch , checkout e commit . Figure 17. Histórico de diferenças Você também pode ver isso facilmente com o comando git log . Se você executar git log --oneline --decorate --graph --all , ele mostrará o histórico de seus commits, exibindo onde estão seus ponteiros de branch e como seu histórico divergiu. $ 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 Como um branch no Git é na verdade um arquivo simples que contém a verificação SHA-1 de 40 caracteres do commit para o qual ele aponta, branches são fáceis de criar e destruir. Criar um novo branch é tão rápido e simples quanto escrever 41 bytes em um arquivo (40 caracteres e uma nova linha). Isso está em nítido contraste com a forma como as ferramentas de versionamento mais antigas se ramificam, o que envolve a cópia de todos os arquivos do projeto em um segundo diretório. Isso pode levar vários segundos ou até minutos, dependendo do tamanho do projeto, enquanto no Git o processo é sempre instantâneo. Além disso, como estamos gravando os pais quando fazemos o commit, encontrar uma base adequada para a mesclagem é feito automaticamente para nós e geralmente é muito fácil de fazer. Esses recursos ajudam a incentivar os desenvolvedores a criar e usar branches com frequência. Vamos ver por que você deve fazer isso. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:25
https://git-scm.com/book/es/v2/Git-en-el-Servidor-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. Inicio - Sobre el Control de Versiones 1.1 Acerca del Control de Versiones 1.2 Una breve historia de Git 1.3 Fundamentos de Git 1.4 La Línea de Comandos 1.5 Instalación de Git 1.6 Configurando Git por primera vez 1.7 ¿Cómo obtener ayuda? 1.8 Resumen 2. Fundamentos de Git 2.1 Obteniendo un repositorio Git 2.2 Guardando cambios en el Repositorio 2.3 Ver el Historial de Confirmaciones 2.4 Deshacer Cosas 2.5 Trabajar con Remotos 2.6 Etiquetado 2.7 Alias de Git 2.8 Resumen 3. Ramificaciones en Git 3.1 ¿Qué es una rama? 3.2 Procedimientos Básicos para Ramificar y Fusionar 3.3 Gestión de Ramas 3.4 Flujos de Trabajo Ramificados 3.5 Ramas Remotas 3.6 Reorganizar el Trabajo Realizado 3.7 Recapitulación 4. Git en el Servidor 4.1 Los Protocolos 4.2 Configurando Git en un servidor 4.3 Generando tu clave pública SSH 4.4 Configurando el servidor 4.5 El demonio Git 4.6 HTTP Inteligente 4.7 GitWeb 4.8 GitLab 4.9 Git en un alojamiento externo 4.10 Resumen 5. Git en entornos distribuidos 5.1 Flujos de trabajo distribuidos 5.2 Contribuyendo a un Proyecto 5.3 Manteniendo un proyecto 5.4 Resumen 6. GitHub 6.1 Creación y configuración de la cuenta 6.2 Participando en Proyectos 6.3 Mantenimiento de un proyecto 6.4 Gestión de una organización 6.5 Scripting en GitHub 6.6 Resumen 7. Herramientas de Git 7.1 Revisión por selección 7.2 Organización interactiva 7.3 Guardado rápido y Limpieza 7.4 Firmando tu trabajo 7.5 Buscando 7.6 Reescribiendo la Historia 7.7 Reiniciar Desmitificado 7.8 Fusión Avanzada 7.9 Rerere 7.10 Haciendo debug con Git 7.11 Submódulos 7.12 Agrupaciones 7.13 Replace 7.14 Almacenamiento de credenciales 7.15 Resumen 8. Personalización de Git 8.1 Configuración de Git 8.2 Git Attributes 8.3 Puntos de enganche en Git 8.4 Un ejemplo de implantación de una determinada política en Git 8.5 Recapitulación 9. Git y Otros Sistemas 9.1 Git como Cliente 9.2 Migración a Git 9.3 Resumen 10. Los entresijos internos de Git 10.1 Fontanería y porcelana 10.2 Los objetos Git 10.3 Referencias Git 10.4 Archivos empaquetadores 10.5 Las especificaciones para hacer referencia a… (refspec) 10.6 Protocolos de transferencia 10.7 Mantenimiento y recuperación de datos 10.8 Variables de entorno 10.9 Recapitulación A1. Apéndice A: Git en otros entornos A1.1 Interfaces gráficas A1.2 Git en Visual Studio A1.3 Git en Eclipse A1.4 Git con Bash A1.5 Git en Zsh A1.6 Git en Powershell A1.7 Resumen A2. Apéndice B: Integrando Git en tus Aplicaciones A2.1 Git mediante Línea de Comandos A2.2 Libgit2 A2.3 JGit A3. Apéndice C: Comandos de Git A3.1 Configuración A3.2 Obtener y Crear Proyectos A3.3 Seguimiento Básico A3.4 Ramificar y Fusionar A3.5 Compartir y Actualizar Proyectos A3.6 Inspección y Comparación A3.7 Depuración A3.8 Parcheo A3.9 Correo Electrónico A3.10 Sistemas Externos A3.11 Administración A3.12 Comandos de Fontanería 2nd Edition 4.7 Git en el Servidor - GitWeb GitWeb Ahora que ya tienes acceso básico de lectura/escritura y de solo-lectura a tu proyecto, puedes querer instalar un visualizador web. Git trae un script CGI, denominado GitWeb, que es el que usaremos para este propósito. Figura 49. The GitWeb web-based user interface. Si quieres comprobar cómo podría quedar GitWeb con tu proyecto, Git dispone de un comando para activar una instancia temporal, si en tu sistema tienes un servidor web ligero, como por ejemplo lighttpd o webrick . En las máquinas Linux, lighttpd suele estar habitualmente instalado, por lo que tan solo has de activarlo lanzando el comando git instaweb , estando en la carpeta de tu proyecto. Si tienes una máquina Mac, Leopard trae preinstalado Ruby, por lo que webrick puede ser tu mejor apuesta. Para instalar instaweb disponiendo de un controlador no-lighttpd, puedes lanzarlo con la opción --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] Esto arranca un servidor HTTPD en el puerto 1234, y luego arranca un navegador que abre esa página. Es realmente sencillo. Cuando ya hayas terminado y quieras apagar el servidor, puedes lanzar el mismo comando con la opción --stop : $ git instaweb --httpd=webrick --stop Si quieres disponer permanentemente de un interfaz web para tu equipo o para un proyecto de código abierto que albergues, necesitarás ajustar el script CGI para ser servido por tu servidor web habitual. Algunas distribuciones Linux suelen incluir el paquete gitweb , y podrás instalarlo a través de las utilidades apt o yum ; merece la pena probarlo en primer lugar. Enseguida vamos a revisar el proceso de instalar GitWeb manualmente. Primero, necesitas el código fuente de Git, que viene con GitWeb, para generar un script CGI personalizado: $ 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/ Fíjate que es necesario indicar la ubicación donde se encuentran los repositorios Git, utilizando la variable GITWEB_PROJECTROOT . A continuación, tienes que preparar Apache para que utilice dicho script. Para ello, puedes añadir un 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> Recordar una vez más que GitWeb puede servirse desde cualquier servidor web con capacidades CGI o Perl. Por lo que si prefieres utilizar algún otro, no debería ser difícil configurarlo. En este momento, deberías poder visitar http://gitserver/ para ver tus repositorios online. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:25
https://www.sushi.com/rootstock/cross-chain-swap	Trade Explore Positions Stake Rootstock Mainnet Connect Wallet Connect Swap Limit DCA Cross-Chain Sell RBTC Rootstock Mainnet Buy Select token $ 0 . 00 Insufficient RBTC balance on Rootstock Mainnet to cover the network fee. Please lower your input amount or swap for more RBTC . Price impact Est. received Min. received Fee ( 0.35 %) Network fee Cross-Chain Swap \| Sushi 🍣	2026-01-13T09:29:25
https://www.linkedin.com/products/aha-labs-inc--aha-knowledge/	Aha! Knowledge \| LinkedIn Skip to main content LinkedIn Aha! in Asan Expand search This button displays the currently selected search type. When expanded it provides a list of search options that will switch the search inputs to match the current selection. Jobs People Learning Clear text Clear text Clear text Clear text Clear text Join now Sign in Aha! Knowledge Knowledge Management Software by Aha! See who's skilled in this Add as skill Try now Report this product About Aha! Knowledge is the product information hub — craft documents, add visuals, and share everything in a central place. This product is intended for Product Manager Product Marketer Program Manager Project Manager Technical Writer Product Operations Manager Media Products media viewer No more previous content Getting started with Aha! Knowledge This video provides an introductory tour of the Aha! Knowledge product — you will see why it is the obvious choice for creating, organizing, and sharing documentation. Aha! Knowledge — Bring everything together Manage all of your product documents in one place. Capture plans, processes, research, meeting notes, and more — so you finally have a single source of product truth. Aha! Knowledge — Create a knowledge base Empower customers and colleagues with the resources they need to be successful. Create unlimited sites for different products and audiences. Aha! Knowledge — Use the AI assistant Produce high-quality documents in record time. From research summaries to product announcements, the AI assistant is on hand to help you outline, draft, and refine. Aha! Knowledge — Share your roadmap Proactively share plans and updates via your knowledge base. Use Aha! Knowledge as part of Aha! Roadmaps to keep your community informed. No more next content Similar products Notion Notion Knowledge Management Software Stack Overflow for Teams Stack Overflow for Teams Knowledge Management Software Stack Overflow Advertising Stack Overflow Advertising Knowledge Management Software Scribe Scribe Knowledge Management Software BeVigil BeVigil Knowledge Management Software Document360 Document360 Knowledge Management Software Sign in to see more Show more Show less Aha! products Aha! Academy Aha! Academy Product Management Software Aha! Develop Aha! Develop DevOps Software Aha! Discovery Aha! Discovery Product Management Software Aha! Ideas Aha! Ideas Idea Management Software Aha! Roadmaps Aha! Roadmaps Strategic Planning Software Aha! Teamwork Aha! Teamwork Project Management Software Aha! Whiteboards Aha! Whiteboards Whiteboard Software Show more Show less LinkedIn © 2026 About Accessibility User Agreement Privacy Policy Cookie Policy Copyright Policy Brand Policy Guest Controls Community Guidelines English (English) Language	2026-01-13T09:29:25
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#overview	Instagram API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Instagram API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Posts API Collect by URL Discover by URL Comments API Collect by URL Reels API Collect by URL Discover by URL Social Media APIs Instagram API Scrapers Copy page Copy page Overview The Instagram API Suite offers multiple types of APIs, each designed for specific data collection needs from Instagram. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : N/A Interesting Columns : followers , post_count , post_hashtags , profile_name . Posts API This API allows users to collect multiple posts based on a single input URL (such as an Instagram reels URL, search URL or profile URL). Discovery functionality : - Direct URL of the Instagram reel - Direct URL of the search - Direct URL of the profile Interesting Columns : url , followers , hashtags , engagement_score_view . Comments API This API allows users to collect multiple comments from a post using its URL. Discovery functionality : N/A Interesting Columns : comment_user , comment , likes_number , replies_number . The suite of APIs is designed to offer flexibility for targeted data collection, where users can input specific URLs to gather detailed post and comment data, either in bulk or with precise filtering options. Profiles API Collect by URL This API allows users to collect detailed data about an Instagram profile by providing the profile URL. It provides a comprehensive overview of an Instagram profile, including business and engagement information, posts, and user details. Input Parameters URL string required The Instagram profile URL. Output Structure Includes comprehensive data points: Page/Profile Details : account , id , followers , posts_count , is_business_account , is_professional_account , is_verified , avg_engagement , profile_name , profile_url , profile_image_link , and more. For all data points, click here . Posts API Collect by URL This API enables users to collect detailed data from Instagram posts by providing a post URL. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Post Details : post_id , description , hashtags , date_posted , num_comments , likes , content_type , video_view_count , video_play_count , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : photos , videos , thumbnail , display_url (link only, not the file itself), audio. Discover by URL This API allows users to discover recent Instagram posts from a public profile by providing the profile URL and specifying additional parameters. Input Parameters URL string required The Instagram profile URL. num_of_posts number The number of recent posts to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date). post_type string Specify the type of posts to collect (e.g., post, reel). Output Structure Includes comprehensive data points: Post Details: post_id , description , hashtags , date_posted , num_comments , likes , video_view_count , video_play_count ,and more. For all data points, click here . Page/Profile Details: user_posted , followers , posts_count , profile_image_link , is_verified , profile_url , is_paid_partnership , partnership_details , user_posted_id Attachments and Media: photos , videos , thumbnail , audio , display_url , content_type , product_type , coauthor_producers , tagged_users . This API is designed to allow for filtering, exclusion of specific posts, and collecting posts by type (regular post or reel) within a defined time frame. It provides detailed post and profile information, making it ideal for data collection and analytics. Comments API Collect by URL This API allows users to collect the latest comments from a specific Instagram post by providing the post URL. This API retrieves the most recent 10 comments along with associated metadata. Input Parameters URL string required The Instagram post URL. Output Structure Includes comprehensive data points: Comment Details : comment_id , comment_user , comment_user_url , comment_date , comment , likes_number , replies_number , replies , hashtag_comment , tagged_users_in_comment , and more. For all data points, click here . User Details : user_name , user_id , user_url We provide a limited set of data points about the profile. Post Metadata : post_url , post_user , post_id . Reels API Collect by URL This API allows users to collect detailed data about Instagram reels from public profiles by providing the reel URL. Input Parameters URL string required The Instagram reel URL. Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , tagged_users , num_comments , likes , views , video_play_count , length , and more. For all data points, click here . Page/Profile Details : user_posted , followers , posts_count , profile_image_link , is_verified , profile_url . We provide a limited set of data points about the profile. Attachments and Media : video_url , thumbnail , audio_url . Discover by URL This API allows users to discover Instagram Reels videos from a profile URL or direct search URL. Input Parameters URL string required The Instagram profile or direct search URL. num_of_posts number The number of recent reels to collect. If omitted, there is no limit. posts_to_not_include array Array of post IDs to exclude from the results. start_date string Start date for filtering reels in MM-DD-YYYY format. end_date string End date for filtering reels in MM-DD-YYYY format (should be later than start_date ). Output Structure Includes comprehensive data points: Reel Details : post_id , description , hashtags , date_posted , num_comments , likes , views , video_play_count , top_comments , length , video_url , audio_url , content_id , and more. For all data points, click here . Profile Details : user_posted , followers , posts_count , following . Attachments and Media : video_url , thumbnail , audio_url (link only, not the file itself). This API provides detailed information about Instagram Reels, with filtering options by date range, exclusion of specific posts, and a limit on the number of reels collected. Was this page helpful? Yes No Facebook LinkedIn ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:25
https://git-scm.com/book/pl/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. Pierwsze kroki 1.1 Wprowadzenie do kontroli wersji 1.2 Krótka historia Git 1.3 Podstawy Git 1.4 Linia poleceń 1.5 Instalacja Git 1.6 Wstępna konfiguracja Git 1.7 Uzyskiwanie pomocy 1.8 Podsumowanie 2. Podstawy Gita 2.1 Pierwsze repozytorium Gita 2.2 Rejestrowanie zmian w repozytorium 2.3 Podgląd historii rewizji 2.4 Cofanie zmian 2.5 Praca ze zdalnym repozytorium 2.6 Tagowanie 2.7 Aliasy 2.8 Podsumowanie 3. Gałęzie Gita 3.1 Czym jest gałąź 3.2 Podstawy rozgałęziania i scalania 3.3 Zarządzanie gałęziami 3.4 Sposoby pracy z gałęziami 3.5 Gałęzie zdalne 3.6 Zmiana bazy 3.7 Podsumowanie 4. Git na serwerze 4.1 Protokoły 4.2 Uruchomienie Git na serwerze 4.3 Generowanie Twojego publicznego klucza SSH 4.4 Konfigurowanie serwera 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Inne opcje hostowania przez podmioty zewnętrzne 4.10 Podsumowanie 5. Rozproszony Git 5.1 Rozproszone przepływy pracy 5.2 Wgrywanie zmian do projektu 5.3 Utrzymywanie projektu 5.4 Podsumowanie 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. Narzędzia Gita 7.1 Wskazywanie rewizji 7.2 Interaktywne używanie przechowali 7.3 Schowek i czyszczenie 7.4 Signing Your Work 7.5 Searching 7.6 Przepisywanie historii 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugowanie z Gitem 7.11 Moduły zależne 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Podsumowanie 8. Dostosowywanie Gita 8.1 Konfiguracja Gita 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git i inne systemy 9.1 Git jako klient 9.2 Migracja do Gita 9.3 Podsumowanie 10. Mechanizmy wewnętrzne w Git 10.1 Komendy typu plumbing i porcelain 10.2 Obiekty Gita 10.3 Referencje w Git 10.4 Spakowane pliki (packfiles) 10.5 Refspec 10.6 Protokoły transferu 10.7 Konserwacja i odzyskiwanie danych 10.8 Environment Variables 10.9 Podsumowanie 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 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 {plus} button in the top toolbar next to your username as seen in The “New repository” dropdown. . Figure 110. The “Your repositories” area. Figure 111. The “New repository” dropdown. This takes you to the “new repository” form: Figure 112. 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 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 Podstawy Gita . 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 HTTP 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 HTTP 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 HTTP 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 113. 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 114. 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 115. 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 http://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 116. 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 117. 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 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 Komendy typu plumbing i 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 118. 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 119. 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 120. 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 121. 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 122. 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 123. 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 124. 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 125. 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:25
https://git-scm.com/book/cs/v2/Distribuovan%c3%bd-Git-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 5.4 Distribuovaný Git - Shrnutí Shrnutí Teď už byste měli mít pocit jistoty jak při přispívání do projektu v Gitu, tak při správě svého vlastního projektu, nebo při integraci příspěvků od ostatních uživatelů. Gratulujeme, nyní je z vás efektivní gitový vývojář! V další kapitole se naučíte, jak se používá největší a nejpopulárnějí služba pro hostování Gitu, známá jako GitHub. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:25
https://git-scm.com/book/sv/v2/Git-f%c3%b6rgreningar-Grenar-i-ett-n%c3%b6tskal	Git - Grenar i ett nötskal 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. Kom igång 1.1 Om versionshantering 1.2 En kort historik av Git 1.3 Vad är Git? 1.4 Kommandoraden 1.5 Installera Git 1.6 Använda Git för första gången 1.7 Få hjälp 1.8 Sammanfattning 2. Grunder i Git 2.1 Skaffa ett Git-förvar 2.2 Spara ändringar till förvaret 2.3 Visa historiken 2.4 Ångra saker 2.5 Jobba med fjärrförvar 2.6 Taggning 2.7 Git alias 2.8 Sammanfattning 3. Git förgreningar 3.1 Grenar i ett nötskal 3.2 Grundläggande förgrening och sammanslagning 3.3 Hantera grenar 3.4 Arbetsflöde med grenar 3.5 Fjärrgrenar 3.6 Grenflytt 3.7 Sammanfattning 4. Git på servern 4.1 Protokollen 4.2 Skaffa Git på en server 4.3 Generera din publika SSH-nyckel 4.4 Konvigurera servern 4.5 Git Daemonen 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Alternativ tillhandahållna av tredje part 4.10 Sammanfattning 5. Distribuerade Git 5.1 Distribuerade arbetsflöden 5.2 Medverka i ett projekt 5.3 Underhålla ett projekt 5.4 Sammanfattning 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. Bilaga 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. Bilaga 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. Bilaga 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 förgreningar - Grenar i ett nötskal Nästan alla versionshanteringssystem har någon form av stöd för förgreningar. En förgrening innbär att du avviker från utvecklingens huvudspår och fortsätter att arbeta utan att påverka huvudspåret. I många versionshanteringsverktyg är detta är ganska dyr process som ofta innebär att skapa en ny kopia av källkodsmappen och tar lång tid för stora projekt. En del refererar till Gits förgreningsmodell som dess “mördarfunktion,” och den gör verkligen att Git sticker ut i versionshanteringsvärlden. Vad är så speciellt? Det sätt som Git gör grenar på är fantastiskt lättviktigt och att skapa nya grenar görs näst intill ögonblickligen, likaså att byta mellan olika grenar. Olikt många andra versionshanteringssystem uppmuntrar Git till ett arbetsflöde där man ofta förgrenar och slår ihop dem ofta, även flera gånger dagligen. Att förstå och behärska denna teknik ger dig ett kraftfullt och unikt verktyg och kan helt påvekar hur du väljer att utveckla. Grenar i ett nötskal För att verligen förstå hur Git använder grenar måste vi ta ett steg tillbaka och undersöka hur Git sparar data. Som du kanske kommer ihåg från Kom igång så sparar Git inte data som en serie ändringar eller skillnader, utan istället som en serie ögonblicksbilder . När du skapar en version, skapar Git ett versionsobjekt som innehåller en pekare till ögonblicksbilden av innehållet du förberett för ändringen. Detta objektet innehåller författarens namn och e-postadress, meddelandet som angavs, och pekare till den version eller de versioner som var direkt före denna version (dess förälder eller föräldrar): Ina föräldrar för den första versionen, en förälder för en normal version och flera föräldrar för en version som är resultatet efter en sammanslagning mellan två eller flera grenar. För att visualisera detta, anta att du har en mapp som innehåller tre filer. Du preparerar alla och därefter skapar din version. När du preparerar filerna beräknas en checksumma för varje fil (SHA-1 kontrollsumman som vi nämnt tidigare i Kom igång ), lagrar versionen av filen i Git-förvaret (Git refererar till dem som blobbar ), och lägger till kontrollsumman till prepareringsytan: $ git add README test.rb LICENSE $ git commit -m 'The initial commit of my project' När du skapar en version genom att köra git commit , beräknar Git en kontrollsumma för varje underkatalog (i detta fall enbart projektets rotkatalog) och sparar dessa tre objekt i Git-förvar. Git skapar sedan ett versionsobjekt som har metadata och en pekare till rotkatalogens projektträd så att den kan återskapa den ögonblicksbilden när så behövs. Ditt Git-förvar innehåller nu fem objekt: tre blobbar (varje representerar innehållet i en av de tre filerna), ett träd som listar innehållet i en katalog och specificerar vilka filnamn som finns lagrade som vilka blobbar, och en version med pekaren till det rotträdet och versionens metadata. Figur 9. En version och dess träd. Om du gör några ändringar och skapar en ny version, kommer nästa version spara en pekare till den version som var omedelbart före denna. Figur 10. Versioner och deras föräldrar En gren i Git är bara en enkel flyttbar pekare till någon av dessa versioner. Standardgrenen i Git är master . Om du börjar skapa vereionser, så får du en master -gren som pekar på din senast sparade version. Varje gång du gör en ny version, så förflyttas master -pekaren med framåt automatiskt. Notera Grenen “master” i Git är inte speciell. Den är precis som vilken annan gren som helst. Enda anledningen att nästan alla förvar har en, är för att kommandot git init skapar den som standard och de flesta bryr sig inte om att ändra det. Figur 11. En gren och dess versionshistorik. Skapa en ny gren Vad händer när du skapar en ny gren? Att göra det skapar en ny pekare som du kan flyutta runt. Anta att du vill skapa en gren som heter testing . Du kan göra detta med kommandot git branch : $ git branch testing Detta skapar en ny pekare till samma version som du just nu står på. Figur 12. Två grenar pekar på samma serie av versioner Hur vet Git vilken gren du just nu står på? Den har en speciell pekare som kallas HEAD . Notera att detta är mycket annorlunda än konceptet HEAD i andra versionshanteringssystem som du kanske använt, som t.ex. Subversion eller CVS. I Git är detta en pekare till den lokala gren du just nu står på. I detta fallet är du fortfarande på master . Kommandot git branch skapade bara en ny gren — den bytte inte till den grenen. Figur 13. HEAD pekar på en gren Du kan enkelt se detta genom att köra kommandot git log som visar va grenpekarna pekar på. Denna flagga kallas --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 Du kan se grenarna “master” och “testing” som är precis vid versionen f30ab . Byta grenar Att byta till en existerande gren görs med kommandot git checkout . Låt oss byta till den nya grenen testing : $ git checkout testing Detta flyttar HEAD till att peka på grenen testing . Figur 14. HEAD pekar på aktuell gren Vad är vitsen med det? Låt oss illustrera genom att skapa en ny version: $ vim test.rb $ git commit -a -m 'made a change' Figur 15. Grenen som HEAD pekar på flyttar fram när en version sparas Det intressanta är att din gren testing har flyttat fram, men din master -gren pekar fortfarande på versionen du var på innan du körde git checkout för att byta gren. Låt oss gå tillbaks till master -grenen: $ git checkout master Figur 16. HEAD flyttar när du gör checkout Kommandot gjorde två saker. Den flyttade din HEAD pekare tillaka till grenen master och den återställde filerna i din arbetskopia till ögonblicksbilden som master pekar på. Detta betyder att alla ändringar från och med nu kommer divergera från en tidigare version av projektet. I praktiken gör den det jobb du gjort i din testing -gren ogjort så att du kan gå i en annan riktning. Notera Byta grenar ändrar filer i din arbetskopia Det är viktigt att veta att när du byter gren i Git så ändras filer i din arbetskopia. Om du byter till en äldre gren kommer din arbetskopia återställas till att se ut som den gjorde senast du gjorde en version på den grenen. Om Git inte kan göra detta utan att kasta icke-versionshanterat arbete, kommer du inte tillåtas byta alls. Låt oss göra några ändringar och spara en till version: $ vim test.rb $ git commit -a -m 'made other changes' Nu har din projekthistorik divergerat (se Divergent historik ). Du skapade och bytte till en gren, gjorde lite arbete på den, och sedan bytte du tillbaks till ditt huvudspår och gjorde lite annat arbete. Båda ändringarna är isolerade i olika grenar: du kan byta fram och tillbaka mellan grenarna och slå ihop dem när du är redo. Allt detta gjorde du med några enkla kommandon; branch , checkout och commit . Figur 17. Divergent historik Du kan också se detta enkelt med kommandot git log . Om du kör git log --oneline --decorate --graph --all så skrivs hela din versionshistorik ut, samt var dina grenar pekar och visar hur din historik har divergerat. $ 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 Eftersom en gren i Git egentligen är en fil som innehåller den 40 tecken långa SHA-1 kontrollsumman av versionen den pekar på, är grenar enkla att skapa och ta bort. Att skapa en ny gren är lika enkelt som att skriva 41 byte till en fil (40 tecken och ett nyradstecken). Detta är i skarp kontrast till hur de flesta äldre versionshanteringssystem fungerar, då förgreningar innefattar att kopiera hela projektets filer till en ny katalog. Detta kan ta flera sekunder eller till och med minuter, beroende på storleken på projektet, men i Git är processen alltid momentan. Eftersom vi lagrar informationen om föräldrarna till en version blir det lätt att automatiskt hitta en bra bas för sammanslagning och det är ganska lätt att genomföra. Detta uppmuntrar utvecklare att skapa och använda grenar ofta. Låt oss undersöka varför vi skall göra på detta viset. Notera Skapa en ny gren och byta till den samtidigt Det händer ofta att du vill skapa en ny gren och byta till den omedelbart. — Detta kan göras med en operation genom kommandot git checkout -b <nyttgrennamn> . prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:25
https://babelfish.money/wp-json/wp/v2/pages/6	Babelfish – BabelFish BABELFISH Github Docs Forum Launch Dapp X sun (Traced) crescent-moon-phase-shape-with-two-stars (Traced)2022 BABELFISH Github Docs Analytics X LAUNCH DAPP UNIVERSAL MULTI-CHAIN STABLECOIN BabelFish's mind-boggling objective is to aggregate and distribute stablecoins, enhance flow, and push hyperBitcoinization.   ABOUT BabelFish DAO Money Protocol is the simplest and most mind-bogglingly useful thing in the DeFi Universe. It absorbs, aggregates and distributes USD-pegged stablecoins across chains; the practical upshot of all this is that if you stick stablecoins to it, you can neatly cross the language divide between any chains. BabelFish's meta-stablecoin, XUSD, is backed by the underlying aggregated stablecoins to leverage and enhance their combined flow and utility across protocols and users. FISH holders can vote on improvement proposals, such as which stablecoins to accept, or what percent of collateral to lend. Learn More About It GO TO OUR GITBOOK What It Does What It Does: Since the big bang of DeFi in the crypto galaxy, many stablecoin projects have been created to meet the demand for USD. Different stablecoin brands with unique selling points are competing to represent the same dollar, but they do not translate 1:1, and crypto dollar liquidity is fractured between issuers and protocols. As DeFi markets expand beyond Ethereum to multiple chains, stablecoin liquidity is fractured further by the bridges used, which is suboptimal for the industry. BabelFish abstracts away these differences by aggregating stablecoins from multiple isolated liquidity lakes and providing users with access to the combined ocean of crypto-dollars available. Think of it as a translator or a converter: if a user wants to use crypto dollars on another chain, she can stick it on BabelFish and seamlessly get a par-value equivalent on the other side. What Is The FISH DAO The BabelFish DAO Money Protocol is ultimately directed by the will of FISH token holders participating in governance. From protocol improvement proposals to budget allocation and partnerships, it is the community that will be able to decide on the direction of the protocol. If you are passionate about the stablecoin ecosystem, this is the DAO for you. Help define protocol rules and parameters around the collateral accepted, discuss community incentives, manage risk, and much more. The future of BabelFish depends on active FISH holder participation. Help build, shape and enhance the stablecoin ecosystem. Participate in stablecoin collateral management. Be rewarded for staking and actively participating with FISH in governance. Mind-Bogglingly Useful XUSD is collateralized 1:1 by a hedged basket of accepted stablecoins across chains, which enables users and protocols to tap into the combined liquidity and utility of the underlying collateral and also enhances stablecoin flow across the ecosystem. User deposits an accepted stablecoin on BabelFish protocol. Protocol issues XUSD, its convertible stablecoin backed 1:1 User can use XUSD on accepted protocols, bridge between chains, and redeem back at any time What Moves BabelFish The need for a "trustless stablecoin translation device" seems painfully clear. The accelerated growth and velocity of crypto dollars is unstoppable, we expect demand for programmable money to continue accelerating as we onboard the first billion users. But the market remains fragmented, two players dominate >80% of the total USD-stablecoin float, and systemic and idiosyncratic risks abound. In the decentralised economy we ought not to rely on one or two issuers of USD-stablecoins but rather enable a thousand stablecoins to bloom and communicate with each other to bring mass adoption. For BabelFish DAO Money Protocol it is important that our first product, XUSD, is the safest, easiest and ultimate stablecoin instrument out there in crypto space. JOIN US TO EXPERIENCE BABELFISH	2026-01-13T09:29:25
https://git-scm.com/book/tl/v2/Mga-Pangunahing-Kaalaman-sa-Git-Pagtitingin-sa-Kasaysayan-ng-Commit	Git - Pagtitingin sa Kasaysayan ng Commit 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 2.3 Mga Pangunahing Kaalaman sa Git - Pagtitingin sa Kasaysayan ng Commit Pagtitingin sa Kasaysayan ng Commit Pagkatapos mong gumawa ng iilang mga commit, o kung na-clone mo ang isang repositoryo na may umiiral na kasaysayan ng commit, malamang na gusto mong tumingin pabalik kung ano ang nangyari. Ang pinaka pangunahin at malakas na kagamitan upang gawin ito ay ang git log na utos. Ang mga halimbawang ito ay gumagamit ng pinaka simpleng proyekto na tinatawag na “simplegit”. Upang makuha ang proyekto, patakbuhin ang $ git clone https://github.com/schacon/simplegit-progit Kapag ikaw ay nagpatakbo ng git log sa proyektong ito, dapat kang makakuha ng output na parang kagaya nito: $ git log commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 changed the version number commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 16:40:33 2008 -0700 removed unnecessary test commit a11bef06a3f659402fe7563abf99ad00de2209e6 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 10:31:28 2008 -0700 first commit Bilang default, na may walang mga argumento,ang git log ay naglilista ng mga commit na ginawa sa repositoryo na iyon sa baliktad na pagkasunod-sunod — yan ay, ang pinaka-kamakailang mga commit lang ipinapakita muna. Tulad ng iyong nakikita, ang utos na ito ay naglilista sa bawat commit na kasama ang SHA-1 checksum nito, ang pangalan ng may-akda at email, ang petsa ng pagkasulat, at ang mensahe ng commit. Isang malaking bilang at iba’t ibang mga opsyon sa git log na utos ay magagamit para ipakita sayo ang eksakto na kung ano ang iyong hinahanap. Dito, ipapakita namin sa iyo ang ilang mga pinaka sikat. Isa sa maraming nakakatulong na mga opsyon ay ang -p o --patch , na nagpapakita ng pagkakaiba (ang tapal na output) ay ipinakilala sa bawat commit. Maaari mo ring limitahan ang bilang ng iyong ng mga log entry na ipinapakita, tulad ng paggamit ng -2 upang ipakita lamang ang huling dalawang entry. $ git log -p -2 commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 changed the version number diff --git a/Rakefile b/Rakefile index a874b73..8f94139 100644 --- a/Rakefile +++ b/Rakefile @@ -5,7 +5,7 @@ require 'rake/gempackagetask' spec = Gem::Specification.new do \|s\| s.platform = Gem::Platform::RUBY s.name = "simplegit" - s.version = "0.1.0" + s.version = "0.1.1" s.author = "Scott Chacon" s.email = "schacon@gee-mail.com" s.summary = "A simple gem for using Git in Ruby code." commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 16:40:33 2008 -0700 removed unnecessary test diff --git a/lib/simplegit.rb b/lib/simplegit.rb index a0a60ae..47c6340 100644 --- a/lib/simplegit.rb +++ b/lib/simplegit.rb @@ -18,8 +18,3 @@ class SimpleGit end end - -if $0 == __FILE__ - git = SimpleGit.new - puts git.show -end Ang opsyon na ito ay nagpapakita ng parehong impormasyon ngunit may direktang diff na sumusunod na bawat entry. Ito ay kapaki-pakinabang para sa pagsusuri ng code o upang mabilis ang pag-browse kung ano ang nangyari sa panahon ng isang serye ng mga commit na naidagdag sa isang tagatulong. Maaari ka ring gumamit ng isang serye ng pagsasama ng mga opsyon sa git log . Halimbawa, kung nais mong makita ang ilang pinaliit na mga stat para sa bawat commit, maaari mong gamitin ang --stat na opsyon: $ git log --stat commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 changed the version number Rakefile \| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 16:40:33 2008 -0700 removed unnecessary test lib/simplegit.rb \| 5 ----- 1 file changed, 5 deletions(-) commit a11bef06a3f659402fe7563abf99ad00de2209e6 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 10:31:28 2008 -0700 first commit README \| 6 ++++++ Rakefile \| 23 +++++++++++++++++++++++ lib/simplegit.rb \| 25 +++++++++++++++++++++++++ 3 files changed, 54 insertions(+) Tulad ng iyong nakikita, ang --stat na opsyon ay nagpapakita sa ibabaw sa bawat commit na entry sa listahan ng mga binagong mga file, kung gaano karaming mga file ang binago, at gaano karami ang mga linya sa mga file ang idinagdag at inalis. Naglalagay din ito ng buod ng impormasyon sa dulo. Ang isa pang talagang kapaki-pakinabang na opsyon ay ang --pretty . Ang opsyon na ito ay nagbabago ng log output para i-format maliban sa nakatakda. Ang kaunting prebuilt na mga opsyon ay magagamit para gamitin mo. Ang oneline na opsyon ay nagpapakita ng bawat commit sa isang solong linya, na kung saan ay kapaki-pakinabang kung ikaw ay naghahanap ng maraming mga commit. At saka, ang short , full , at fuller ang mga opsyon ay nagpapakita ng halos lahat na parehong format ngunit may mas kaunti o higit pang impormasyon, ayon sa pagkakabangit: $ git log --pretty=oneline ca82a6dff817ec66f44342007202690a93763949 changed the version number 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 removed unnecessary test a11bef06a3f659402fe7563abf99ad00de2209e6 first commit Ang pinakawili-wili na opsyon ay ang format , na nagbibigay-daan upang tukuyin ang iyong sariling log output na format. Ito ay lalong magagamit kapag ikaw ay bumubuo ng output para sa pag-parse ng makina — dahil ikaw ay tumukoy sa format ng malinaw, alam mo na hindi ito magbabago kahit na may mga update sa Git: $ git log --pretty=format:"%h - %an, %ar : %s" ca82a6d - Scott Chacon, 6 years ago : changed the version number 085bb3b - Scott Chacon, 6 years ago : removed unnecessary test a11bef0 - Scott Chacon, 6 years ago : first commit Mga kapaki-pakinabang na mga opsyon para sa git log --pretty=format ay naglilista ng ilan sa maraming kapaki-pakinabang na mga opsyon na makukuha sa format . Table 1. Mga kapaki-pakinabang na mga opsyon para sa git log --pretty=format Opsyon Paglalarawan ng Output %H Commit hash %h Pinaiksing commit hash %T Tree hash %t Pinaiksing tree hash %P Magulang na mga hash %p Pinaiksing magulang na mga hash %an Pangalan ng may-akda %ae Email ng may-akda %ad Petsa ng may-akda (ang format ay gumagalang sa --date=option) %ar Petsa ng may-akda, kaugnay %cn Pangalan ng nag-commit %ce Email ng nag-commit %cd Petsa ng nag-commit %cr Petsa ng nag-commit , kaugnay %s Paksa Maaaring ikaw ay nagtataka kung ano ang pagkakaiba na nasa pagitan ng may-akda at ang nag-commit . Ang may-akda ay isang tao na orihinal na sumulat sa trabaho, samantala ang nag-commit ay isang tao na huling inilapat ang trabaho. Kaya, kung magpadala ka sa isang tapal sa isang proyekto at isa sa mga pangunahing miyembro na naglalapat ng patch, kapwa kayo ay makakuha ng credit — ikaw bilang ang may-akda, at ang core na miyembro bilang ang nag-commit. Isali natin ang pagkakaiba nito na mas kaunti pa sa Distributed Git . Ang oneline at format na mga opsyon ay patikular na kapaki-pakinabang sa ibang log na opsyon na tinatawag na --graph . Ang opsyon na ito ay nagdaragdag ng magandang maliit na ASCII graph na nagpapakita sa iyong branch at merge na kasaysayan: $ git log --pretty=format:"%h %s" --graph * 2d3acf9 ignore errors from SIGCHLD on trap * 5e3ee11 Merge branch 'master' of git://github.com/dustin/grit \|\ \| * 420eac9 Added a method for getting the current branch. * \| 30e367c timeout code and tests * \| 5a09431 add timeout protection to grit * \| e1193f8 support for heads with slashes in them \|/ * d6016bc require time for xmlschema * 11d191e Merge branch 'defunkt' into local Ang tipo ng output na ito ay magiging mas kawili-wili habang tayo ay gumagamit ng pag-branching at pag-merging sa susunod na kabanata. Iyan ay ilan lamang sa simple na output-formatting na mga opsyon sa git log — marami pang iba. Pangkaraniwang mga opsyon sa git log Naglilista ng mga opsyon na sinali natin kamakailan lang, pati na rin ang ilan pang ibang mga pangkaraniwang formatting na mga opsyon na maaaring kapaki-pakinabang, kasama ng kung papaano sila nagbabago sa output ng log command. Table 2. Pangkaraniwang mga opsyon sa git log Option Paglalarawan -p Nagpapakita sa ipinapakitang tapal sa bawat commit. --stat Nagpapakita ng mga istatistika para sa mga file na nabago sa bawat commit. --shortstat Nagpakita lamang ang nabago/mga ipinasok/mga binura na linya mula sa --stat na utos. --name-only Nagpakita ng listahan ng mga file na nabago pagkatapos ng impormasyon ng commit. --name-status Nagpakita ng listahan ng mga file na apektado na may idinagdag/binago/binura na impormasyon din. --abbrev-commit Nagpakita lamang ang unang ilang mga karakter ng SHA-1 checksum sa halip na lahat 40. --relative-date Nagpakita ng petsa sa isang kaugnay na format (halimbawa, “2 linggong nakaraan”) sa halip na gamitin ang buong format ng petsa. --graph Nagpakita ng ASCII graph sa branch at merge na kasaysayan bukod sa output ng log. --pretty Nagpapakita ng mga commit sa isang humahalili na format. Mga opsyon na kasama ay oneline, short, full, fuller, at format (kung saan ikaw ay tumutukoy ng iyong sariling format). --oneline Shorthand para sa --pretty=oneline --abbrev-commit na ginagamit na magkasama. Paglilimit ng Log Output Sa karagdagan sa output-formatting na mga opsyon, ang git log ay kumukuha ng isang bilang ng kapaki-pakinabang na paglilimit na mga opsyon — yan ay, ang mga opsyon na nagpapakita sa iyo lamang ng subset ng mga commit. Nakita mo na ang opsyon na iyon — ang -2 na opsyon, na nagpapakita lamang sa huling dalawang commit. Sa katunayan, maaari mong gawin -<n> , kung saan n ang anumang integer na ipinakita sa huling n na mga commit. Sa totoo, ikaw ay malamang hindi ka gumagamit niyan ng madalas, dahil ang Git sa pamamagitan ng default na mga pipe sa lahat ng output sa pamamagitan ng isang pager kaya nakikita lamang ang isang pahina sa log output sa isang pagkakataon. Gayunpaman, ang oras na naglilimita na mga opsyon tulad ng --since at --until ay lubhang nakakatulong. For example, this command gets the list of commits made in the last two weeks: $ git log --since=2.weeks Ang utos na ito ay gumagana sa maraming mga format — maaari mong tukuyin ang tiyak na petsa tulad ng "2008-01-15" , o isang kaugnay na petsa tulad ng "2 years 1 day 3 minutes ago" . Maaari mo ring i-filter ang listahan ng mga nai-commit na tumugma sa ilang pamantayan sa paghahanap. Ang --author na opsyon ay nagpapahintulot sayo na i-filter sa isang tiyak na may-akda, at ang --grep na opsyon na hinahayaan kang maghanap para sa mga keyword na nasa commit na mga mensahe. Maaari mong tukuyin ang higit pa sa isang instance sa parehong --author at --grep na pamantayan sa paghahanap , kung saan ay naglilimita sa output ng commit upang ang mga commit na tumugma sa anuman sa --author na mga palatandaan at anuman sa --grep na mga palatandaan; gayunpaman, pagdagdag sa --all-match na opsyon sa karagdagang mga limitasyon sa output sa mga nai-commit lang na tumutugma _sa lahat _ --grep ng mga palatandaan. Isa pang nakakatulong talaga na filter ay ang -S na opsyon (ang pananalita ay tinutukoy bilang Git’s “pickaxe” na opsyon), na kung saan kay kumukuha ng isang string at nagpapakita lamang sa mga commit na iyon na nagbago ang bilang ng mga pangyayari ng string na iyon. Halimbawa, kung gusto mong humanap sa huling commit na nagdagdag o nag-alis ng isang reperensiya sa tiyak na pag-andar, maaari kang tumawag: $ git log -S function_name Ang huling talagang kapaki-pakinabang na opsyon na maipasa sa git log bilang isang fitler ay ang path. Kung ikaw ay tumukoy ng direktoryo o pangalan ng file, maaari mong limitahan ang log output para i-commit ang ipinakilala na pagbago ng mga file na iyon. Ito ay laging huling opsyon at sa pangkalahatan ay nauna ng dobleng mga gitling ( -- ) upang ihiwalay ang mga path mula sa mga opsyon. Sa Mga opsyon upang limitahan ang output sa git log kami ay maglista nito at ilan pang iba na pangkaraniwang mga opsyon para sa iyong reperensiya. Table 3. Mga opsyon upang limitahan ang output sa git log Opsyon Paglalarawan -<n> Ipinakita lamang ang huling n na mga commit --since , --after Limitahan ang mga commit sa mga ginawa pagkatapos sa tinutukoy na petsa. --until , --before Limitahan ang mga commit sa mga ginawa bago ang tinutukoy na petsa. --author Ipinapakita lamang ang mga commit na kung saan ang entry ng may-akda ay tumugma sa tinutukoy na string. --committer Ipinapakita lamang ang mga commit na kung saan ang entry ng taga-commit ay tumugma sa tinutukoy na string. --grep Ipinapakita lamang ang mga commit na may isang mensahe ng commit na naglalaman ng string -S Ipinapakita lamang ang mga commit na pagdaragdag o pag-alis sa code na tumutugma sa string Halimbawa, kung gusto mong tingnan kung saan ang mga commit na nagbago sa mga test files sa loob ng kasaysayan ng Git source code na nai-commit ni Junio Hamano sa buwan ng Oktubre 2008 at hindi mga merge na commit, maaari kang magpatakbo sa isang bagay na tulad nito: $ git log --pretty="%h - %s" --author=gitster --since="2008-10-01" \ --before="2008-11-01" --no-merges -- t/ 5610e3b - Fix testcase failure when extended attributes are in use acd3b9e - Enhance hold_lock_file_for_{update,append}() API f563754 - demonstrate breakage of detached checkout with symbolic link HEAD d1a43f2 - reset --hard/read-tree --reset -u: remove unmerged new paths 51a94af - Fix "checkout --track -b newbranch" on detached HEAD b0ad11e - pull: allow "git pull origin $something:$current_branch" into an unborn branch Na nasa halos 40,000 na mga commit sa Git source code na kasaysayan, itong utos ay nagpapakita ng 6 na tumugma sa pamantayan na iyon. Tip Pag-iwas sa pagpakita sa pinagsamang mga commit Depende sa workflow na ginagamit sa iyong repositoryo, ito’y posible na ang malaking porsyento sa mga commit sa iyong kasaysayan ng log ay pinagsama lamang ng mga commit, na karaniwang hindi masyadong makabuluhan. Upang iwasan ang pagpakita sa pinagsamang mga commit na gumugulo sa iyong kasaysayan ng log, idagdag lamang ang opsyon ng log`--no-merges`. prev \| next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy	2026-01-13T09:29:25
https://git-scm.com/book/es/v2/Fundamentos-de-Git-Alias-de-Git	Git - Alias de 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. Inicio - Sobre el Control de Versiones 1.1 Acerca del Control de Versiones 1.2 Una breve historia de Git 1.3 Fundamentos de Git 1.4 La Línea de Comandos 1.5 Instalación de Git 1.6 Configurando Git por primera vez 1.7 ¿Cómo obtener ayuda? 1.8 Resumen 2. Fundamentos de Git 2.1 Obteniendo un repositorio Git 2.2 Guardando cambios en el Repositorio 2.3 Ver el Historial de Confirmaciones 2.4 Deshacer Cosas 2.5 Trabajar con Remotos 2.6 Etiquetado 2.7 Alias de Git 2.8 Resumen 3. Ramificaciones en Git 3.1 ¿Qué es una rama? 3.2 Procedimientos Básicos para Ramificar y Fusionar 3.3 Gestión de Ramas 3.4 Flujos de Trabajo Ramificados 3.5 Ramas Remotas 3.6 Reorganizar el Trabajo Realizado 3.7 Recapitulación 4. Git en el Servidor 4.1 Los Protocolos 4.2 Configurando Git en un servidor 4.3 Generando tu clave pública SSH 4.4 Configurando el servidor 4.5 El demonio Git 4.6 HTTP Inteligente 4.7 GitWeb 4.8 GitLab 4.9 Git en un alojamiento externo 4.10 Resumen 5. Git en entornos distribuidos 5.1 Flujos de trabajo distribuidos 5.2 Contribuyendo a un Proyecto 5.3 Manteniendo un proyecto 5.4 Resumen 6. GitHub 6.1 Creación y configuración de la cuenta 6.2 Participando en Proyectos 6.3 Mantenimiento de un proyecto 6.4 Gestión de una organización 6.5 Scripting en GitHub 6.6 Resumen 7. Herramientas de Git 7.1 Revisión por selección 7.2 Organización interactiva 7.3 Guardado rápido y Limpieza 7.4 Firmando tu trabajo 7.5 Buscando 7.6 Reescribiendo la Historia 7.7 Reiniciar Desmitificado 7.8 Fusión Avanzada 7.9 Rerere 7.10 Haciendo debug con Git 7.11 Submódulos 7.12 Agrupaciones 7.13 Replace 7.14 Almacenamiento de credenciales 7.15 Resumen 8. Personalización de Git 8.1 Configuración de Git 8.2 Git Attributes 8.3 Puntos de enganche en Git 8.4 Un ejemplo de implantación de una determinada política en Git 8.5 Recapitulación 9. Git y Otros Sistemas 9.1 Git como Cliente 9.2 Migración a Git 9.3 Resumen 10. Los entresijos internos de Git 10.1 Fontanería y porcelana 10.2 Los objetos Git 10.3 Referencias Git 10.4 Archivos empaquetadores 10.5 Las especificaciones para hacer referencia a… (refspec) 10.6 Protocolos de transferencia 10.7 Mantenimiento y recuperación de datos 10.8 Variables de entorno 10.9 Recapitulación A1. Apéndice A: Git en otros entornos A1.1 Interfaces gráficas A1.2 Git en Visual Studio A1.3 Git en Eclipse A1.4 Git con Bash A1.5 Git en Zsh A1.6 Git en Powershell A1.7 Resumen A2. Apéndice B: Integrando Git en tus Aplicaciones A2.1 Git mediante Línea de Comandos A2.2 Libgit2 A2.3 JGit A3. Apéndice C: Comandos de Git A3.1 Configuración A3.2 Obtener y Crear Proyectos A3.3 Seguimiento Básico A3.4 Ramificar y Fusionar A3.5 Compartir y Actualizar Proyectos A3.6 Inspección y Comparación A3.7 Depuración A3.8 Parcheo A3.9 Correo Electrónico A3.10 Sistemas Externos A3.11 Administración A3.12 Comandos de Fontanería 2nd Edition 2.7 Fundamentos de Git - Alias de Git Alias de Git Antes de terminar este capítulo sobre fundamentos de Git, hay otro pequeño consejo que puede hacer que tu experiencia con Git sea más simple, sencilla y familiar: los alias. No volveremos a mencionarlos más adelante en este libro, ni supondremos que los has utilizado, pero probablemente deberías saber cómo utilizarlos. Git no deduce automáticamente tu comando si lo tecleas parcialmente. Si no quieres teclear el nombre completo de cada comando de Git, puedes establecer fácilmente un alias para cada comando mediante git config . Aquí tienes algunos ejemplos que te pueden interesar: $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status Esto significa que, por ejemplo, en lugar de teclear git commit , solo necesitas teclear git ci . A medida que uses Git, probablemente también utilizarás otros comandos con frecuencia; no dudes en crear nuevos alias para ellos. Esta técnica también puede resultar útil para crear comandos que en tu opinión deberían existir. Por ejemplo, para corregir el problema de usabilidad que encontraste al quitar del área de preparación un archivo, puedes añadir tu propio alias a Git: $ git config --global alias.unstage 'reset HEAD --' Esto hace que los dos comandos siguientes sean equivalentes: $ git unstage fileA $ git reset HEAD fileA Esto parece un poco más claro. También es frecuente añadir un comando last , de este modo: $ git config --global alias.last 'log -1 HEAD' De esta manera, puedes ver fácilmente cuál fue la última confirmación: $ 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> Como puedes ver, Git simplemente sustituye el nuevo comando por lo que sea que hayas puesto en el alias. Sin embargo, quizás quieras ejecutar un comando externo en lugar de un subcomando de Git. En ese caso, puedes comenzar el comando con un carácter ! . Esto resulta útil si escribes tus propias herramientas para trabajar con un repositorio de Git. Podemos demostrarlo creando el alias git visual para ejecutar 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:25
https://www.sushi.com/rootstock/pool	Trade Explore Positions Stake Manage Liquidity Positions You can adjust and claim rewards for your liquidity positions on the connected network. For V2 pools, you can migrate to increase capital efficiency. I want to create a position I want to incentivize a pool My Positions Network Rootstock Mainnet 🍣 SushiSwap v3 🍣 SushiSwap v2 Hide closed My Positions ( 0 ) Name Price Range Position Size Unclaimed fees No results. Rows per page 10 Page 1 of 0 Go to first page Go to previous page Go to next page Go to last page Rootstock Mainnet Connect Wallet Connect My Positions \| Sushi 🍣	2026-01-13T09:29:25
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#param-url-2	Pinterest API Scrapers - Bright Data Docs Skip to main content Bright Data Docs home page English Search... ⌘ K Support Sign up Sign up Search... Navigation Social Media APIs Pinterest API Scrapers Welcome Proxy Infrastructure Web Access APIs Data Feeds AI API Reference General Integrations Overview Authentication Terminology Postman collection Python SDK JavaScript SDK Products Unlocker API SERP API Marketplace Dataset API Web Scraper API POST Asynchronous Requests POST Synchronous Requests POST Crawl API Delivery APIs Management APIs Social Media APIs Overview Facebook Instagram LinkedIn TikTok Reddit Twitter Pinterest Quora Vimeo YouTube Scraper Studio API Scraping Shield Proxy Networks Proxy Manager Unlocker & SERP API Deep Lookup API (Beta) Administrative API Account Management API On this page Overview Profiles API Collect by URL Discover by Keywords Posts API Collect by URL Discover by Profile URL Discover by Keywords Social Media APIs Pinterest API Scrapers Copy page Copy page Overview The Pinterest API Suite offers multiple types of APIs, each designed for specific data collection needs from Pinterest. Below is an overview of how these APIs connect and interact, based on the available features: Profiles API This API allows users to collect profile details based on a single input: profile URL. Discovery functionality : Discover by Keywords. Interesting Columns : name , following_count , website , follower_count . Posts API This API allows users to collect multiple posts based on a single input. Discovery functionality : - Discover by profile URL. - Discover by Keywords. Interesting Columns : title , content , user_name , likes . Profiles API Collect by URL This API allows users to retrieve detailed Pinterest profile information using the provided profile URL. Input Parameters : URL string required The Pinterest profile URL. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metrics : following_count , follower_count , boards_num , saved . Additional Information : last_updated , posts_page_url , discovery_input . This API allows users to collect detailed insights into a Pinterest profile, including user statistics, engagement metrics, and profile information. Discover by Keywords This API allows users to discover Pinterest profiles based on a specified keyword. Input Parameters : keyword string required The keyword to search for profiles. Output Structure : Includes comprehensive data points: Profile Details : url , profile_picture , name , nickname , website , bio , country_code , profile_id . For all data points, click here . Engagement & Metric s: following_count , follower_count , boards_num , saved. Additional Information : last_updated , posts_page_url , discovery_input . This API enables users to find Pinterest profiles related to a specific keyword, offering insights into user statistics, engagement, and profile details. Posts API Collect by URL This API allows users to collect detailed post data from a specific Pinterest post using the provided post URL. Input Parameters : URL string required The Pinterest post URL. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , post_type . For all data points, click here . User Details : user_name , user_url , user_id , followers . Post Metrics : likes , comments_num , comments , categories . Media & Attachments : image_video_url , video_length , attached_files . Hashtags & Discovery : hashtags , discovery_input . This API allows users to retrieve detailed insights into a specific Pinterest post, including user engagement, post content, media, and other related information. Discover by Profile URL This API allows users to retrieve posts from a specific Pinterest profile based on the provided profile URL. Input Parameters : URL string required The Pinterest profile URL from which to collect posts. num_of_posts number The number of posts to collect. If omitted, there is no limit. posts_to_not_include array An array of post IDs to exclude from the results. start_date string Start date for filtering posts in MM-DD-YYYY format (should be earlier than end_date ). end_date string End date for filtering posts in MM-DD-YYYY format (should be later than start_date ). Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users tso collect posts from a specific Pinterest profile, allowing for filtering by date, exclusion of specific posts, and retrieval of detailed post data including media, comments, and engagement metrics. Discover by Keywords This API allows users to discover Pinterest posts based on a specific keyword, enabling efficient content discovery. Input Parameters : keyword string required The keyword to search for posts, such as “food” or any other relevant term. Output Structure : Includes comprehensive data points: Post Details : url , post_id , title , content , date_posted , user_name , user_url , user_id , followers , likes , categories , source , attached_files , image_video_url , video_length , hashtags , comments_num , comments , post_type . For all data points, click here . Engagement & Metrics : followers , likes , comments_num . Media & Attachments : image_video_url , video_length , attached_files . Additional Information : discovery_input . This API enables users to search for Pinterest posts based on a specific keyword, providing detailed insights into the content, engagement, media, and associated metrics for efficient discovery. Was this page helpful? Yes No Twitter Quora ⌘ I linkedin youtube github Powered by	2026-01-13T09:29:25

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.