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://git-scm.com/book/tl/v2/Git-sa-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. 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.7 Git sa Server - GitWeb GitWeb Now that you have basic read/write and read-only access to your project, you may want to set up a simple web-based visualizer. Git comes with a CGI script called GitWeb that is sometimes used for this. Figure 49. The GitWeb web-based user interface. If you want to check out what GitWeb would look like for your project, Git comes with a command to fire up a temporary instance if you have a lightweight 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:23 |
https://git-scm.com/book/de/v2/Erste-Schritte-Die-Kommandozeile | Git - Die Kommandozeile About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Erste Schritte 1.1 Was ist Versionsverwaltung? 1.2 Kurzer Überblick über die Historie von Git 1.3 Was ist Git? 1.4 Die Kommandozeile 1.5 Git installieren 1.6 Git Basis-Konfiguration 1.7 Hilfe finden 1.8 Zusammenfassung 2. Git Grundlagen 2.1 Ein Git-Repository anlegen 2.2 Änderungen nachverfolgen und im Repository speichern 2.3 Anzeigen der Commit-Historie 2.4 Ungewollte Änderungen rückgängig machen 2.5 Mit Remotes arbeiten 2.6 Taggen 2.7 Git Aliases 2.8 Zusammenfassung 3. Git Branching 3.1 Branches auf einen Blick 3.2 Einfaches Branching und Merging 3.3 Branch-Management 3.4 Branching-Workflows 3.5 Remote-Branches 3.6 Rebasing 3.7 Zusammenfassung 4. Git auf dem Server 4.1 Die Protokolle 4.2 Git auf einem Server einrichten 4.3 Erstellung eines SSH-Public-Keys 4.4 Einrichten des Servers 4.5 Git-Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Von Drittanbietern gehostete Optionen 4.10 Zusammenfassung 5. Verteiltes Git 5.1 Verteilter Arbeitsablauf 5.2 An einem Projekt mitwirken 5.3 Ein Projekt verwalten 5.4 Zusammenfassung 6. GitHub 6.1 Einrichten und Konfigurieren eines Kontos 6.2 Mitwirken an einem Projekt 6.3 Ein Projekt betreuen 6.4 Verwalten einer Organisation 6.5 Skripte mit GitHub 6.6 Zusammenfassung 7. Git Tools 7.1 Revisions-Auswahl 7.2 Interaktives Stagen 7.3 Stashen und Bereinigen 7.4 Deine Arbeit signieren 7.5 Suchen 7.6 Den Verlauf umschreiben 7.7 Reset entzaubert 7.8 Fortgeschrittenes Merging 7.9 Rerere 7.10 Debuggen mit Git 7.11 Submodule 7.12 Bundling 7.13 Replace (Ersetzen) 7.14 Anmeldeinformationen speichern 7.15 Zusammenfassung 8. Git einrichten 8.1 Git Konfiguration 8.2 Git-Attribute 8.3 Git Hooks 8.4 Beispiel für Git-forcierte Regeln 8.5 Zusammenfassung 9. Git und andere VCS-Systeme 9.1 Git als Client 9.2 Migration zu Git 9.3 Zusammenfassung 10. Git Interna 10.1 Basisbefehle und Standardbefehle (Plumbing and Porcelain) 10.2 Git Objekte 10.3 Git Referenzen 10.4 Packdateien (engl. Packfiles) 10.5 Die Referenzspezifikation (engl. Refspec) 10.6 Transfer Protokolle 10.7 Wartung und Datenwiederherstellung 10.8 Umgebungsvariablen 10.9 Zusammenfassung A1. Anhang A: Git in anderen Umgebungen A1.1 Grafische Schnittstellen A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Zusammenfassung A2. Anhang B: Git in deine Anwendungen einbetten A2.1 Die Git-Kommandozeile A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Anhang C: Git Kommandos A3.1 Setup und Konfiguration A3.2 Projekte importieren und erstellen A3.3 Einfache Snapshot-Funktionen A3.4 Branching und Merging A3.5 Projekte gemeinsam nutzen und aktualisieren A3.6 Kontrollieren und Vergleichen A3.7 Debugging A3.8 Patchen bzw. Fehlerkorrektur A3.9 E-mails A3.10 Externe Systeme A3.11 Administration A3.12 Basisbefehle 2nd Edition 1.4 Erste Schritte - Die Kommandozeile Die Kommandozeile Es gibt viele verschiedene Möglichkeiten Git einzusetzen. Auf der einen Seite gibt es die Werkzeuge, die per Kommandozeile bedient werden und auf der anderen, die vielen grafischen Benutzeroberflächen (engl. graphical user interface, GUI), die sich im Leistungsumfang unterscheiden. In diesem Buch verwenden wir die Kommandozeile. In der Kommandozeile können nämlich wirklich alle vorhandenen Git Befehle ausgeführt werden. Bei den meisten grafischen Oberflächen ist dies nicht möglich, da aus Gründen der Einfachheit nur ein Teil der Git-Funktionalitäten zur Verfügung gestellt werden. Wenn du dich in der Kommandozeilenversion von Git auskennen, findest du dich wahrscheinlich auch in einer GUI-Version relativ schnell zurecht, aber andersherum muss das nicht unbedingt zutreffen. Außerdem ist die Wahl der grafischen Oberfläche eher Geschmackssache, wohingegen die Kommandozeilenversion auf jedem Rechner installiert und verfügbar ist. In diesem Buch gehen wir deshalb davon aus, dass du weißt, wie man bei einem Mac ein Terminal öffnet, oder wie man unter Windows die Eingabeaufforderung oder die Powershell öffnet. Falls du jetzt nur Bahnhof verstehst, solltest du an dieser Stelle abbrechen und dich schlau machen, was ein Terminal bzw. eine Eingabeaufforderung ist und wie man diese bedient. Nur so ist sichergestellt, dass du unsere Beispiele und Ausführungen im weiteren Verlauf des Buches folgen kannst. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
http://ccmixter.org/query-api | ccMixter - Query API 2.0 (beta) Listen to the Light skip Not logged in Log In Search Find content Collaborative Community Home The Mixversation Picks Remixes Samples A Cappellas People Extras Query API 2.0 (beta) The Query API is how you get data from a ccHost site installation. This information can used as widgets in a blog or other web page, a feed or raw data for programmatic manipulation. Parameter Passing No matter what the calling context, the information in the results and how they are formatted are controlled by setting up parameters and values using the URL query parameter syntax: name = value & another_name = another_value For example, to return uploads that have been tagged with either foo or bar you would say: tags = foo + bar & type = any To see the results in a RSS feed format, you would add the rss value as a format ( f for short) parameter: tags = foo + bar & type = any & f = rss Unlike the RSS format which has a pre-defined output format, the HTML format can be further controlled by specifying a template ( t for short) to be used. For example, to embed the same results into a web page with links and attribution: tags = foo + bar & type = any & format = html & t = links_by See the parameter reference for a detailed explanation of what parameters are available. Calling Context The Query API can invoked from several contexts: Remotely via a URL Directly from PHP in a ccHost installation Embedded in a template in a ccHost installation Embedded into a topic using ccHost formatting Embedded into ccHost navigation tabs URL Remote invocation The base URL for the Query API is http://example.com/api/query where 'example.com' is the base of the ccHost site installation. Parameters and values are passed URL query parameters. In the following example the user ( u for short) is used to limit the results to uploads by a specific uploader: https://ccmixter.org/api/query? tags = hip_hop & sort = name & u = teru https://ccmixter.org/api/query? f = rss & datasource = topics & type = review & u = victor This type of query request can be used anywhere an URL is used, however only certain formats make sense in some URL contexts. For example, when typing in an URL in your browser, only the f = page is useful. When embedding into a blog use f = html or if used in the SRC parameter of a <script> then f = docwrite should be used. Directly from PHP Developers that write extensions to ccHost use the URL query syntax to call the CCQuery object: require_once('cchost_lib/cc-query.php'); $query = new CCQuery(); $args = $query->ProcessAdminArgs('tags=hip_hop&sort=name&user=teru'); $query->Query($args); In order to facilitate using query parameters passed to a URL other than api/query, either via GET or POST: require_once('cchost_lib/cc-query.php'); $query = new CCQuery(); $args = $query-> ProcessUriArgs (); $query->Query($args); Instead of outputting the results into the page directly, the results can be returned as a PHP array by using f = php . The following is an example of using a dataview to retrieve the upload_ids of all uploads by teru tagged as hip_hop require_once('cchost_lib/cc-query.php'); $query = new CCQuery(); $args = $query->ProcessAdminArgs('tags=hip_hop&u=teru& dataview=ids&b=php '); $results = $query->Query($args); foreach( $results[0] as $row ) { $id = $row['upload_id']; //... } The $results variable now contains an array that contains the results Embedded in a template in a ccHost installation Template developers use the URL query sytax but in a more concise way: %query('tags=hip_hop&t=links_by_ul&limit=5')% Embedded into a topic using ccHost formatting Queries can be embedded into topic content posts in a ccHost site using the following syntax: [query=template=mplayer&playlist=340][/query] Embedded into ccHost navigation tabs ccHost site admins can embed queries into the navigation tabs by selecting 'Query' for the tab type and entering the query. Format is always page . Concepts and Definitions Formats Every query must have a format parameter (or f for short). The f parameter determines how the final data is returned. There are several categories: Category Format Values HTML page , html Feeds/XML atom , rss , xspf , xml Javascript js , json , docwrite Plain text csv , textfile Special m3u , ids , count The default format is page which will embed the results into a full HTML page based on the current skin of the ccHost installation. For HTML without the full page use format = html Templates For the HTML format s page and html there are many different specialized templates that return the requested in specific HTML snippets. See the Templates Appendix for details. Data Views For non HTML queries a dataview is used to return rows of data. The dataview acts as a column selector while the other query parameters (such as tags and user ) determine which rows to return and sort will determine the order. See the Dataview Appendix section for a list of dataview values in the system. Specifying Parameters Use parameters to select which records, how many of them and in which order. For example in order to return the 10 latest uploads that are tagged as sample with an Attribution license we use the follow query: limit = 10 & tags = sample & lic = by Usage Cookbook Combining Parameters That Make Sense When queries for a set of uploads it might be helpful to group the parameters so the results are not too limited. For example you probably never want to combine the following parameters: collab , ids , playlist , remixes , remixesof , and sources because they each return a very small set of records. But things get interesting when you refine the results with some set parameters like lic , reccby , remixmax , remixmin , reqtags , score , sinceu , sinced , tags , or user . Suppose that you know of a playlist (986) and you want to know which songs are available under an Attribution license: f = html & t = links & playlist = 986 & lic = by You want to know of a cappellas by calendargirl that have been remixed less than 5 times... f = html & t = links & user = calendargirl & tags = acappella & remixmax = 5 Example Queries The lastest 15 uploads sorted by user's full name f=html&t=links_by&limit=15&chop=0&sort=fullname The latest 15 modified uploads f=html&t=links_by&limit=15&chop=0&sort=last_edit Playlists created in the last 3 weeks that have at least 3 items t=playlist_2_browse&since=3 weeks ago&minitems=3 Playlists created by user 'teru' sorted alphabetically t=playlist_2_browse&u=teru&sort=name&ord=asc Uploads sorted by number of playlists they are included in t=playlist_2_uploads&sort=num_playlists&ord=desc Uploads by user 'teru' ordered by times included in playlists t=playlist_2_uploads&sort=num_playlists&ord=desc&u=teru Raw header information about a playlier f=html&t=playlist_2_info&ids=1651 Link to the latest 5 topics on the page 'Featured Samples' f=html&t=topic_page_links&limit=5&page=featured-samples Avatar for the user 'mcjackinthebox' f=html&t=avatar&u=mcjackinthebox XML formatted search results for 'anthony' in user table. f=xml&t=search_users&limit=5&search_type=any&search=anthony Yahoo! Easy Listener Flash(tm) plugin with uploads that are tagged 'remix' and either 'ambient' or 'chill' f=html&t=easy_listener&limit=10&reqtags=remix&tags=ambient+chill&type=any Count of uploads during the month of July 2006 sinced=July 2006&befored=Aug 2006&f=count Highest recommended uploads from 3 weeks ago sinced=3 weeks ago&befored=2 weeks ago&sort=num_scores XML with basic user info of the last 3 registered users dataview=user_basic&limit=3&f=xml Appendix A: Parameter Reference Parameter Short Form Description beforeu Unix time befored Date string (see php's strtodate ) chop Several of the embedding HTML templates will "chop" long names to this value. collab Return files belonging to a given collaboration project. Value is a numeric id of the project. datasource Set to topics with format = rss to get topics related feeds. (See type parameter.) dataview (see Data View section ) format f (see Formats section ) ids Comma-separated numeric ids lic (See License Values ) limit This will tell the QAPI to return "no more than" a certain number of records. Valid values are: numeric value A paging system can simulated by setting a limit, combined with offset . page This tells the QAPI to return no more than the number of records shown on a typical page listing. This is the default value for f = page . This is assigned by the site's administrator, typically in the 10-15 range, and can not be surpassed in URL context. feed This tells the QAPI to return no more than the number of records in a feed listing. This is the default value for any of the feed category of formats ( rss , atom , etc.). This is assigned by the site's administrator, typically in the 15-20 range, and can not be surpassed in URL context. query This tells the QAPI to return no more than the number of records in a feed listing. This is the default value for any of the non feed or page category of formats ( html , csv , etc.). This is assigned by the site's administrator, typically in the 100-200 range, and can not be surpassed in URL context. default This tells the QAPI to use whatever is the admin assigned value for the current context and format. This is the same as leaving out the limit parameter. match Template specific, for example t=review_upload&match=%upload_id% and t=topic_thread&match=%thread_id% nosort Used with param ids to honor the order of ids passed in. offset Combine with limit to page through results. paging Used with format s page and html to include prev/next buttons. Valid values are on and off The default for page is on , for html is off playlist Return records belonging to a specific playlist. Value is the numeric playlist id rand Set to 1 to return records in a random order reccby Return records ecommended by a user at the site. Value is the login name of the user. remixes Request for remixes of a given upload id remixesof Request for remixes of a given user (value is login name) remixmax Uploads that have been remixed no more than remixmax times remixmin Uploads that have been rmeixed no less than remixmin times reqtags These tags must be included in upload reviewee Review topics authored by reviewee score Uploads that have at least score number of ratings search s Search for text words or a phrase. search_type Valid values are match for an exact phrase, any for matches of any of the terms, all for matches of all of the terms. sinceu Unix time sinced Date string (see php's strtodate ) sort (See Valid Sorts ) ord Order of score. Valid values are ASC and DESC . sources Sources of a given remix tags Return uploads with the tags (separated by '+'). For multiple tags set the type parameter to either all to see records with all tags or any to see records that have any of the tags. template t (See Templates Appendix ) thread Used with forum related templates to specify the topics associated with a given thread. title Used with format = page and some feed formats to display a title at the top of the page or XML file. type When data source is uploads this is a modifier for the tags parameter. When data source is topics this restricts the returning records to topics of that type (e.g. forum , review , artist_qa , etc.) The exact types available are site specific. user u Return records that were uploaded by a certain user. Value is the login name. Appendix B: License Values by Attribution nc NonCommercial sa Share-Alike nod NoDerives byncsa NonCommercial ShareAlike byncnd NonCommercial NoDerives s Sampling splus Sampling+ ncsplus NonCommercial Sampling+ pd Public Domain Appendix C: Data Views The following is a list of Data Views. In order to peek into a Data View use he following query: f =csv& limit =1& dataview =NAME_OF_DATA_VIEW replacing NAME_OF_DATA_VIEW with one of the following names: content_page_blog Blog Content Page datasource - topics count count_pool_items datasource - pool_items count_ratings datasource - ratings count_tags datasource - tags count_topics datasource - topics default datasource - uploads files ids info Deep info for upload details info_avatar Deep info (no remixes, user avatar) links datasource - uploads links_by links_by_chop links_by_dl links_by_pool Used by upload listing for Samples are From datasource - pool_item links_dl links_extra links_short list_narrow datasource - uploads passthru Pass Thru (noop) playlist_detail Playlist details datasource - cart playlist_line playlist_reorder playlists Playlist line info datasource - cart pool_item datasource - pool_item pool_item_history_list Used by upload histogram datasource - pool_item pool_item_list Pool Item Listing datasource - pool_item pool_item_search datasource - pool_item required_args - match pool_item_search_gen datasource - pool_item required_args - match remixes_of rss_20 For RSS 2.0 Feed rss_20_topics For RSS 2.0 Topic Feed datasource - topics search_remix required_args - match search_remix_artist required_args - match search_remix_gen required_args - match search_remix_gen_artist required_args - match search_remix_gen_title required_args - match search_remix_title required_args - match tag_alias Return tag aliases datasource - tag_alias require_arg - search tag_cat Basic tag categories datasource - tag_cat tags Basic tags datasource - tags tags_with_cat Tags that only have categories datasource - tags topic_info Simple Topic Info datasource - topics topics Generic Topics datasource - topics upload_column upload_description Upload Description datasource - uploads upload_extra upload_histogram All the information needed for upload history upload_list_wide Multiple upload listing (wide) datasource - uploads upload_menu upload_owner Upload name, id with owner name, id upload_page All the information needed for uploads page user_basic Basic user info for data mining datasource - user Appendix D: Sort values Valid sort requests depends on the data source: Data Source Value Description users fullname Aritst display name date Registration date user Artist login name user_remixes Number of remixes remixed Number of times remixed uploads Number of uploads userscore Artistss average rating user_num_scores Number of ratings user_reviews Reviews left by artist user_reviewed Reviews left for artist posts Forum topics by artist uploads Same as user + name Upload name lic Upload license date Upload date last_edit Upload last edited remixes Upload's remixes sources Upload's sources num_scores Number of ratings num_playlists Number of playlists id Internal upload id local_remixes Upload's local remixes pool_remixes Upload's remote remixes local_sources Upload's local sources pool_sources Upload's sample pool sources rank Upload Rank score Upload's ratings topics name Topic name date Topic date type Topic type left Topic tree collab Same as user + name Collaboration name date Collaboration creation date user Collaboration owner (instead of every artist) pool_items name Pool item name user Pool item artist Appendix E: HTML Templates The templates are grouped by specifc usage scenarios they where designed for. Formats - Designed for blogs and other off-site pages big_contact Big Contact Flash Player links Links to upload page links_ul Links to upload page (UL) links_by Links to upload page with attribution links_by_dl_ul Links to upload page with attribution and download links (UL) links_stream Links to upload page with attribution and stream links links_dl Links to upload page with download links links_by_ul Links to uploads with attribution (UL) links_by_lic Links with license, attribution) med Medium verbose (license, attribution, download link, tags, description) links_by_dl_names Named download links (good for Y! Music player) easy_listener Y!(tm) Easy Listener Player Topic Formats - Designed for blogs and other off-site pages (topics) topic_page_links Content topic links (set page=content_page_name) required_args page topic_dump Content topic links (set type=topic_type datasource topics required_args type news New blurbs (set type=news datasource topics required_args type topic_links_next Next-prev Content topic links(set page=content_page_name,topic=topic_name) required_args page topic Single topic [ids = topic] required_args ids upload_description Single upload descrption [ids = upload_id] required_args ids topic_reply Topic text for reply form [ids = topic] required_args ids Object Embeddings - Object/Flash embeddings mplayer-button Fabricio Zuardi's Button Player - Requires Flash mplayer Fabricio Zuardi's Music Player - Requires Flash mplayerbig Fabricio Zuardi's Music Player BIG - Requires Flash yahoo_black Fabricio Zuardi's Player - (Yahoo Repl.) Page - Designed to be used within the main site upload_page_narrow Single upload page (narrow) require_args ids upload_page_wide Single upload page (wide) Search Results - Used by site search feature search_forums For forums search results (set type=forum) example type=forum&t=search_forums&limit=30&search_type=any&s=charlie+rose datasource topics required_args type, search search_playlists For playlist search results example limit=30&search_type=any&search=charlie+rose datasource cart required_args search search_pool_items For pool items search results (set type=pools) example type=pools&t=search_pool_items&limit=30&search_type=any&s=rooster datasource pool_items required_args type, search search_reviews For reviews search results (set type=review) example type=review&t=search_reviews&limit=30&search_type=any&s=charlie+rose datasource topics required_args type, search search_uploads For upload search results example t=search_uploads&limit=30&search_type=any&s=charlie+rose valid_args search, search_type required_args search search_users For user search results example t=search_users&limit=30&search_type=any&search=charlie+rose datasource users required_args search Ajax - Designed to be used in response to ajax requests reviewers_recent 7 most recent reviewers (for menu) datasource topics collab_thread Collab style topic thread (set match=collab_id) example t=collab_thread&f=html&type=collab&upload=123 datasource topics valid_args type,match required_args match pools_list Display remix searchable pools datasource pools info Info popup for upload collab_users List collab users (embedded in collab page) datasource collab_users valid_args collab collab_files List files in collaboration valid_args ids, collab playlist_2_uploads List playlist lines (Headless playlist with style) example t=playlist_2_uploads&sort=num_playlists&ord=desc playable_list Listing with Play All/in Window playlist_2_head Playlist head (set ids=playlist_id) required_args ids playlist_2_info Playlist head alt (set ids=playlist_id) required_args ids playlist_2_nostyle Playlist head and listing (no styles) required_args playlist playlist_2_popup_window Playlist in a popop window required_args playlist playlists_links Playlist links datasource cart ajax_menu Return a menu for an upload valid_args ids playlist_2_show_one Show a playlist (with styles) required_args playlist avatar User avatar datasource user require_args user upload_menu upload_menu required_args ids remix_pool_checks used by pool remix search datasource pool_items dataview_param ok remix_checks used by remix search dataview_param ok Visitors Find Music Forums About Looking for...? Artists Log In Register Search our archives for music for your video, podcast or school project at dig.ccMixter New Remixes weatherPatter... My Heart Beat... Je suis un Ph... From Two Dire... The Fade Out More new remixes New Uploads weatherPatter... My Heart Beat... Je suis un Ph... No Constant Tascam Amateu... More new uploads Editors' Picks Time Machine Happiness Dee... New Year Begi... Yorke And Lou Hollow Crown ... More picks... Highest Rated Queen of K... New Year B... Frost-Free... Queen of K... Javomatics Weather Or... Recent Reviewers texasradiofis... Speck Javolenus panu Stefan Karten... Bluemillenium airtone More reviews... Support ccMixter This text and images on this site are licensed under a Creative Commons Attribution-Noncommercial 4.0 International License . This site uses ccHost , licensed under CC-GNU-GPL , which is a product of the ccTools project and uses GetID3 . This site is sponsored by ArtisTech Media . By using this site, you agree to our Terms of Use and Privacy Policy . Please note our site credits . Contact: site administrator . | 2026-01-13T09:29:23 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#param-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:23 |
https://git-scm.com/book/zh-tw/v2/%e4%bc%ba%e6%9c%8d%e5%99%a8%e4%b8%8a%e7%9a%84-Git-%e7%b8%bd%e7%b5%90 | Git - 總結 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 開始 1.1 關於版本控制 1.2 Git 的簡史 1.3 Git 基礎要點 1.4 命令列 1.5 Git 安裝教學 1.6 初次設定 Git 1.7 取得說明文件 1.8 摘要 2. Git 基礎 2.1 取得一個 Git 倉儲 2.2 紀錄變更到版本庫中 2.3 檢視提交的歷史記錄 2.4 復原 2.5 與遠端協同工作 2.6 標籤 2.7 Git Aliases 2.8 總結 3. 使用 Git 分支 3.1 簡述分支 3.2 分支和合併的基本用法 3.3 分支管理 3.4 分支工作流程 3.5 遠端分支 3.6 衍合 3.7 總結 4. 伺服器上的 Git 4.1 通訊協定 4.2 在伺服器上佈署 Git 4.3 產生你的 SSH 公鑰 4.4 設定伺服器 4.5 Git 常駐程式 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第3方 Git 託管方案 4.10 總結 5. 分散式的 Git 5.1 分散式工作流程 5.2 對專案進行貢獻 5.3 維護一個專案 5.4 Summary 6. GitHub 6.1 建立帳戶及設定 6.2 參與一個專案 6.3 維護專案 6.4 Managing an organization 6.5 Scripting GitHub 6.6 總結 7. Git 工具 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 總結 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. 附錄 A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. 附錄 B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. 附錄 C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.10 伺服器上的 Git - 總結 總結 You have several options to get a remote Git repository up and running so that you can collaborate with others or share your work. Running your own server gives you a lot of control and allows you to run the server within your own firewall, but such a server generally requires a fair amount of your time to set up and maintain. If you place your data on a hosted server, it’s easy to set up and maintain; however, you have to be able to keep your code on someone else’s servers, and some organizations don’t allow that. It should be fairly straightforward to determine which solution or combination of solutions is appropriate for you and your organization. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
http://ccmixter.org/terms | ccMixter - CCMIXTER TERMS OF USE Listen to the Light skip Not logged in Log In Search Find content Collaborative Community Home The Mixversation Picks Remixes Samples A Cappellas People Extras CCMIXTER TERMS OF USE 1. General Information Regarding These Terms of Use Master terms: Welcome, and thank you for your interest in ccMixter (“ccM,”), operated by ArtisTech Media (“ATM,” “ArtisTech,” “we,” “our,” or “us”). Unless otherwise noted on a particular site or service, these master terms of use (“Master Terms”) apply to your use of all of the websites that ArtisTech Media operates. These include http://ccmixter.org/ , http://beta.ccmixter.org/ , http://beta.ccmixter.org/pells , http://beta.ccmixter.org/stems , http://dig.ccmixter.org/ , http://beta.ccmixter.org/playlists/browse , and http://tunetrack.net/ , together with all other subdomains thereof, (collectively, the “Websites”) The Master Terms also apply to all information and services provided through the Websites (“Services”). Additional terms: In addition to these Master Terms, your use of the Websites and/or Services is subject to the ccMixter Privacy Policy, outlined here: http://ccmixter.org/privacy . Collectively, the Terms: The Master Terms, together with the Privacy Policy, form a binding legal agreement between you and ArtisTech in relation to your use of the Websites and Services. Collectively, this legal agreement is referred to below as the “Terms.” Human-readable summary of Sec 1: These terms create a contract between you and ArtisTech Media. The contract governs your use of all websites operated by ArtisTech media, unless a particular website indicates otherwise. These human-readable summaries of each section are not part of the contract, but are intended to help you understand its terms. 2. Your Agreement to the Terms BY CLICKING “I ACCEPT” OR OTHERWISE ACCESSING OR USING ANY OF THE WEBSITES OR SERVICES, YOU ACKNOWLEDGE THAT YOU HAVE READ, UNDERSTOOD, AND AGREED TO BE BOUND BY THE TERMS. By clicking “I ACCEPT” or otherwise accessing or using any Websites or Services you also represent that you have the legal authority to accept the Terms on behalf of yourself and any party you represent in connection with your use of any Websites or Services. If you do not agree to the Terms, you are not authorized to use any Websites and/or Services. If you are an individual who is entering into these Terms on behalf of an entity, you represent and warrant that you have the power to bind that entity, and you hereby agree on that entity’s behalf to be bound by these Terms, with the terms “you,” and “your” applying to you, that entity, and other users accessing the Websites and/or Services on behalf of that entity. Human-readable summary of Sec 2: Please read these terms and only use our sites and services if you agree to them. 3. Changes to the Terms From time to time, ATM may change, remove, or add to the Terms, and reserves the right to do so in its discretion. In that case, we will post updated Terms and indicate the date of revision. If we feel the modifications are material, we will make reasonable efforts to post a prominent notice on the relevant Website(s), in the ccMixter forum or elsewhere. All new and/or revised Terms take effect immediately and apply to your use of the Services from that date on, except that material changes will take effect 30 days after the change is made and identified as material. Your continued use of any Websites or Services after new or revised Terms are effective indicates that you have read, understood, and agreed to those Terms. Human-readable summary of Sec 3: These terms may change. When the changes are important, we will put a notice on the website. If you continue to use the sites after the changes are made, you agree to the changes. 4. Content Available through the Services Provided as-is: You acknowledge that ATM does not make any representations or warranties about the content, material, data, and information, such as data files, text, computer software, code, music, audio files or other sounds, photographs, videos, or other images (collectively, the “Content”) which you may have access to as part of, or through your use of, the Websites and/or Services. Under no circumstances is ATM liable in any way for any Content, including, but not limited to: any infringing Content, any errors or omissions in Content, or for any loss or damage of any kind incurred as a result of the use of any Content posted, transmitted, linked from, or otherwise accessible through or made available via the Websites and/or Services. You understand that by using the Websites and/or Services, you may be exposed to Content that is offensive, indecent, or objectionable. What you may do with the music on ccMixter: Different Creative Commons licenses may apply to different tracks made available at ccMixter. You must use each track in accordance with its license terms. For this reason, you should check the Creative Commons license that applies to each track before you use it so that you know what you can and cannot do with it. By using ccMixter, you agree that you are solely responsible for your use of any and all tracks made available at ccMixter. You also acknowledge that under all Creative Commons licenses, you are granted a license to use the tracks only; all rights not expressly granted under the terms of the license are reserved to the creator. You represent and warrant to ArtisTech that you will use any and all tracks made available at ccMixter in accordance with the applicable license. For the avoidance of doubt, you must attribute all tracks in the manner required by the author or licensor and in accordance with the terms of the applicable Creative Commons license: (a) attribute the work in the manner specified by the author or licensor; (b) do not use the track to advertise or promote anything other than the work you create from it or yourself; (c) make clear to others the license terms of the track as part of your reuse, and (d) otherwise use the track in accordance with the terms of the selected Creative Commons license. You must not remove or alter any copyright, trademark, name or other notice or legend that appears in connection with a track. You agree that you are solely responsible for your use of Content made available through the Websites and/or Services, including providing proper attribution and commercial or non-commercial use. You should review the terms of the applicable license before you use the Content so that you know what you can and cannot do. About the ccMixter site generally: ArtisTech makes ccMixter available to you on these Terms. You may only use ccMixter in accordance with these Terms and, in particular but without limitation, you may not use ccMixter for any purpose that is unlawful or prohibited by these Terms or any other conditions or notices that are made available at ccMixter. For example, you may not (and may not authorize another party to): (i) frame or otherwise co-brand this site (for example, by displaying a name, logo, trademark or other means of attribution of a third party that is reasonably likely to give the user the impression that that third party has the right to display, publish or distribute this site; or, (ii) use ccMixter in any manner that could disable, overburden, damage or impair ccMixter services (including but not limited to its servers) or interfere with any other party's use and enjoyment of ccMixter. You agree that, while ArtisTech Media makes efforts to ensure that the Content made available at ccMixter is legal, noninfringing and that the use of it in accordance with the Terms and the applicable Creative Commons license will not infringe the rights of any third party, ArtisTech cannot and does not guarantee that the Content made available at this site, in whole or in part, does not infringe the rights of any third party. In the event that content is posted to ccMixter and made available for download that is subsequently found to be infringing, ArtisTech will undertake reasonable efforts to notify you about this, for example, by posting a notice to the discussion forum or contacting you via email in accordance with the ccMixter Privacy Policy . Links to third party sites: The ccMixter website may contain links to third party sites that are not operated and controlled by ArtisTech Media. You acknowledge that ArtisTech: (a) is not responsible or liable for any third party site, including without limitation, the content, information or products made available at any third party site for third party linked sites; (b) has not reviewed any third party linked sites; (c) has not sponsored or otherwise endorsed third party linked sites; and (d) makes no representations or warranties about any third party linked sites. For the avoidance of doubt, the only sites operated and controlled by ArtisTech Media, in addition to ccMixter and its varying subdomains, are http://tunetrack.net and http://artistechmedia.com . What you may do with ccHost: ArtisTech makes ccHost, the software that runs the ccMixter site, available under a CC-GNU-GPL license ( http://creativecommons.org/licenses/GPL/2.0/ ). You may use ccHost in accordance with the terms of that license. You agree that you are solely responsible for your use of ccHost and you represent and warrant to ArtisTech that your use of ccHost will comply with the CC-GNU-GPL. Human-readable summary of Sec 4: We try our best to have useful Content on our sites, but we cannot promise that everything is accurate or appropriate for your situation. Be sure to check the Content’s license terms before using it. 5. Content Supplied by You Your responsibility: You represent, warrant, and agree that no Content posted or otherwise shared by you on or through any of the Websites/Services (“Your Content”), violates or infringes upon the rights of any third party, including copyright, trademark, privacy, publicity, or other personal or proprietary rights, breaches or conflicts with any obligation, such as a confidentiality obligation, or contains libelous, defamatory, or otherwise unlawful material. You agree to refrain from posting, sharing or submitting material which you do not have the right to submit pursuant to copyright law, trademark law, moral rights law, contract or otherwise. Nothing in this provision abridges any right you have, if any, pursuant to the legal principle of fair use. About the music you post to ccMixter: You may only post music to ccMixter that you have the right to post and license under a Creative Commons license. You hereby agree that Your Content: (a) is music or sounds that you yourself have created, (b) music that is in the public domain (such as Content that is not copyrightable or Content available under CC0), (c) if not owned by you, (i) is a music/media file available under any Creative Commons license or (ii) is a music/media file you are authorized by law to post or share through any of the Websites/Services, such as under the fair use doctrine, and that is prominently marked as being subject to third party copyright. All of Your Content must be appropriately marked with licensing (or other permission status such as fair use) and attribution information. For the avoidance of doubt, materials that infringe the rights of any third party (ie. materials used without express permission of the copyright owner) may not be used. By submitting music to ccMixter, you represent and warrant to ArtisTech Media that you have the necessary rights and authority to upload the track to http://ccmixter.org site and license it to the world under the Creative Commons license that you apply to that music. You retain any copyright that you may have in Your Content. To protect the integrity of ccMixter's library, ArtisTech Media has the option to assert your rights to Attribution on your behalf. Removal: ATM may, but is not obligated to, review Your Content and may delete or remove Your Content (without notice) from any of the Websites/Services in its sole discretion. Removal of any of Your Content from the Websites/Services (by you or ATM) does not impact any rights you granted in Your Content under the terms of a Creative Commons license. Your conduct in the discussion forums: ArtisTech Media offers the discussion forums on ccMixter for you and the other users of ccMixter to discuss music, tracks on ccMixter and directly related issues. You may only use the discussion forums to post, send and receive messages that properly conform to these Terms and are related to the purpose for which the forums are made available. Human-readable summary of Sec 5: We do not take any ownership of your content when you post it on our sites. If you post content you own, you agree it can be used under the terms of the Creative Commons license you select. If you do not own the content, then you should not post it unless it is in the public domain or under a Creative Commons license (and properly attributed accordingly), except that you may also post media files if you are authorized to use them under law (e.g., fair use). You must note that information on the file when you upload it. You are responsible for any content you upload to our sites. 6. No Legal Advice ArtisTech is not a law firm, does not provide legal advice, and is not a substitute for a law firm. Sending us an email or using any of the Websites and/or Services, including Content, does not constitute legal advice or create an attorney-client relationship.ArtisTech provides no legal advice, nor should any interaction with ArtisTech on the ccMixter site be considered legal advice. Human-readable summary of Sec 6: We aren’t your lawyer. Please consult your own attorney if you need legal advice. 7. Prohibited Conduct You agree not to engage in any of the following activities: a. Violating laws and rights: You may not (a) use any Websites/Service for any illegal purpose or in violation of any local, state, national, or international laws, (b) violate or encourage others to violate any right of or obligation to a third party, including by infringing, misappropriating, or violating intellectual property, contractual obligations, confidentiality, or privacy rights. b. Solicitation: You may not use the Websites/Services or any information provided through the Websites/Services for the transmission of advertising or promotional materials, including junk mail, spam, chain letters, pyramid schemes, or any other form of unsolicited or unwelcome solicitation. c. Disruption: You may not use the Websites/Services in any manner that could disable, overburden, damage, or impair the Websites/Services, or interfere with any other party’s use and enjoyment of the Websites/Services; including by (a) uploading or otherwise disseminating any virus, adware, spyware, worm or other malicious code, or (b) interfering with or disrupting any network, equipment, or server connected to or used to provide any of the Services, or violating any regulation, policy, or procedure of any network, equipment, or server. You may not deface, spam, otherwise adversely affect the Websites/Services. d. Harming others: You may not post or transmit Content on or through the Websites/Services that is harmful, offensive, obscene, abusive, invasive of privacy, defamatory, hateful or otherwise discriminatory, false or misleading, or incites an illegal act; You may not intimidate or harass another through the Websites/Services; and, you may not post or transmit any personally identifiable information about persons under 13 years of age on or through the Websites/Services. e. Impersonation or unauthorized access: You may not impersonate another person or entity, or misrepresent your affiliation with a person or entity when using the Websites/Services; You may not use or attempt to use another’s account or personal information without authorization; and You may not attempt to gain unauthorized access to the Websites/Services, or the computer systems or networks connected to the Websites/Services, through hacking password mining or any other means. Human-readable summary of Sec 7: Play nice. Be yourself. Don’t break the law or be disruptive. 8. ccMixter API When using the ccMixter API (“API”), you acknowledge that you have read, understood, and, agree to these Terms. Please see Our Privacy Policy for more information about how your information (as a user of the API) will be used. Human-readable summary of Sec 8: When you use the API, you agree to certain policies. Please read them before using it. 9. DISCLAIMER OF WARRANTIES TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, ARTISTECH MEDIA OFFERS THE WEBSITES/SERVICES (INCLUDING ALL CONTENT AVAILABLE ON OR THROUGH THE WEBSITES/SERVICES) AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE WEBSITES/SERVICES, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. ARTISTECH MEDIA DOES NOT WARRANT THAT THE FUNCTIONS OF THE WEBSITES/SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, THAT CONTENT MADE AVAILABLE ON OR THROUGH THE WEBSITES/SERVICES WILL BE ERROR-FREE, THAT DEFECTS WILL BE CORRECTED, OR THAT ANY SERVERS USED BY ATM ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS. ATM DOES NOT WARRANT OR MAKE ANY REPRESENTATION REGARDING USE OF THE CONTENT AVAILABLE THROUGH THE WEBSITES/SERVICES IN TERMS OF ACCURACY, RELIABILITY, OR OTHERWISE. ARTISTECH MEDIA DISCLAIMS ALL WARRANTIES TO THE GREATEST EXTENT PERMITTED BY LAW IN CONNECTION WITH THE WEBSITES/SERVICES. Human-readable summary of Sec 9: ATM does not make any guarantees about the sites, services, or content available on the sites. 10. LIMITATION OF LIABILITY TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL ARTISTECH MEDIA BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY INCIDENTAL, DIRECT, INDIRECT, PUNITIVE, ACTUAL, CONSEQUENTIAL, SPECIAL, EXEMPLARY, OR OTHER DAMAGES, INCLUDING WITHOUT LIMITATION, LOSS OF REVENUE OR INCOME, LOST PROFITS, PAIN AND SUFFERING, EMOTIONAL DISTRESS, COST OF SUBSTITUTE GOODS OR SERVICES, OR SIMILAR DAMAGES SUFFERED OR INCURRED BY YOU OR ANY THIRD PARTY THAT ARISE IN CONNECTION WITH THE WEBSITES/SERVICES (OR THE TERMINATION THEREOF FOR ANY REASON), EVEN IF ATM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, ARTISTECH MEDIA IS NOT RESPONSIBLE OR LIABLE WHATSOEVER IN ANY MANNER FOR ANY CONTENT POSTED ON OR AVAILABLE THROUGH THE WEBSITES/SERVICES (INCLUDING CLAIMS OF INFRINGEMENT RELATING TO THAT CONTENT), FOR YOUR USE OF THE WEBSITES/SERVICES, OR FOR THE CONDUCT OF THIRD PARTIES ON OR THROUGH THE WEBSITES/SERVICES. Certain jurisdictions do not permit the exclusion of certain warranties or limitation of liability for incidental or consequential damages, which means that some of the above limitations may not apply to you. IN THESE JURISDICTIONS, THE FOREGOING EXCLUSIONS AND LIMITATIONS WILL BE ENFORCED TO THE GREATEST EXTENT PERMITTED BY APPLICABLE LAW. Human-readable summary of Sec 10: ATM is not responsible for the content on the sites, your use of our services, or for the conduct of others on our sites. 11. Indemnification To the extent authorized by law, you agree to indemnify and hold harmless ArtisTech Media, its employees, officers, directors, affiliates, and agents from and against any and all claims, losses, expenses, damages, and costs, including reasonable attorneys’ fees, resulting directly or indirectly from or arising out of (a) your violation of the Terms, (b) your use of any of the Services, and/or (c) the Content you make available on any of the Websites/Services. Human-readable summary of Sec 11: If something happens because you violate these terms, because of your use of the services, or because of the content you post on the sites, you agree to repay ATM for the damage it causes. 12. Privacy Policy ArtisTech is committed to responsibly handling the information and data we collect through our Websites/Services in compliance with our Privacy Policy , which is incorporated by reference into these Master Terms. Please review the Privacy Policy so you are aware of how we collect and use your personal information. Human-readable summary of Sec 12: Please read our Privacy Policy . It is part of these terms, too. 13. Trademark Policy ccMixter may contain trademarks, service marks, logos and other names that are the property of ArtisTech Media or the Creative Commons or such other party as indicated with respect to that name or icon. In the case of Creative Commons' trademarks, logos and icons, these may only be used in accordance with their trademark policy ( https://creativecommons.org/policies/#trademark ). Furthermore, the names, logos, icons, and other trademarks of ATM (including but not limited to ccMixter, dig.ccMixter, TuneTrack) may be used for referential use (e.g., to refer to ArtisTech Media as an organization, ccMixter as a music service, etc.), provided that such use does not imply endorsement by or association with ArtisTech Media or Creative Commons. For the avoidance of doubt, no user of the ccMixter API, ccHost, or any Content on the Websites or through the Services is authorized to use ATM’s trademarks except in compliance with these Terms or the trademark policy of Creative Commons, referenced above. Human-readable summary of Sec 13: Please read the Trademark Policy of Creative Commons because their logo is contained in some of our logos. It is part of these terms, too. 14. Copyright Complaints ArtisTech Media complies with the provisions of the Digital Millennium Copyright Act (DMCA). ArtisTech respects copyright, and we prohibit users of the Websites/Services from submitting, uploading, posting, or otherwise transmitting any Content on the Websites/Services that violates another person’s proprietary rights. In compliance with the DMCA, a Designated Agent has been established with proper documentation sent to the US Copyright Office. If you have a concern regarding the use of copyrighted material on any ArtisTech Media Web Site, please contact the agent designated to respond to reports alleging copyright infringement. The designated agent for Sponsor to receive notification of claimed infringement under Title II of the DMCA is Emily Richards. info@artistechmedia.com ArtisTech Media, LLC 2118 Wilshire Blvd Ste 644 Santa Monica, CA 90403 Fax: 810-454-1663 Human-readable summary of Sec 14: Please let us know if you find infringing content on our websites. 15. Termination By ArtisTech Media: ArtisTech may modify, suspend, or terminate the operation of, or access to, all or any portion of the Websites/Services at any time for any reason. Additionally, your individual access to, and use of, the Websites/Services may be terminated by ArtisTech Media at any time and for any reason. By you: If you wish to terminate this agreement, you may immediately stop accessing or using the Websites/Services at any time. Automatic upon breach: Your right to access and use the Websites/Services (including use of your ccMixter Login) terminates automatically upon your breach of any of the Terms. For the avoidance of doubt, termination of the Terms does not require you to remove or delete any reference to previously-applied Creative Commons licenses from your own Content. Survival: The disclaimer of warranties, the limitation of liability, and the jurisdiction and applicable law provisions will survive any termination. The license grants applicable to Your Content are not impacted by the termination of the Terms and shall continue in effect subject to the terms of the applicable license. Your warranties and indemnification obligations will survive for one year after termination. Human-readable summary of Sec 15: If you violate these terms, you may no longer use our sites. 16. Miscellaneous Terms Choice of law: The Terms are governed by and construed by the laws of the State of California in the United States, not including its choice of law rules. Dispute resolution: The parties agree that any disputes between ArtisTech Media and you concerning these Terms, and/or any of the Websites/Services may only brought in a federal or state court of competent jurisdiction sitting in the Central District of California, and you hereby consent to the personal jurisdiction and venue of such court. If you are an authorized agent of a government or intergovernmental entity using the Services in your official capacity, including an authorized agent of the federal, state, or local government in the United States, and you are legally restricted from accepting the controlling law, jurisdiction, or venue clauses above, then those clauses do not apply to you. For any such U.S. federal government entities, these Terms and any action related thereto will be governed by the laws of the United States of America (without reference to conflict of laws) and, in the absence of federal law and to the extent permitted under federal law, the laws of the State of California (excluding its choice of law rules). No waiver: Either party’s failure to insist on or enforce strict performance of any of the Terms will not be construed as a waiver of any provision or right. Severability: If any part of the Terms is held to be invalid or unenforceable by any law or regulation or final determination of a competent court or tribunal, that provision will be deemed severable and will not affect the validity and enforceability of the remaining provisions. No agency relationship: The parties agree that no joint venture, partnership, employment, or agency relationship exists between you and ArtisTech Media as a result of the Terms or from your use of any of the Services. Integration: These Master Terms and any applicable Additional Terms constitute the entire agreement between you and ArtisTech relating to this subject matter and supersede any and all prior communications and/or agreements between you and ArtisTech Media relating to access and use of the Websites/Services. Human-readable summary of Sec 16: If there is a lawsuit arising from these terms, it should be in California and governed by California law. We are glad you use our sites, but this agreement does not mean we are partners. Note about Reusing these Terms of Use. The ArtisTech Media Terms of Use are dedicated to the public domain under the Creative Commons CC0 Public Domain Dedication . You are free to use and adapt these Master Terms and any applicable Additional Terms for your own purposes. However, please keep in mind that these Terms may not be completely suitable for your situation. ArtisTech Media strongly encourages you to seek the advice of your own attorney before repurposing these Terms on your own site. Archived Versions of this Document Terms pre 2018-12-29 Visitors Find Music Forums About Looking for...? Artists Log In Register Search our archives for music for your video, podcast or school project at dig.ccMixter New Remixes weatherPatter... My Heart Beat... Je suis un Ph... From Two Dire... The Fade Out More new remixes New Uploads weatherPatter... My Heart Beat... Je suis un Ph... No Constant Tascam Amateu... More new uploads Editors' Picks Time Machine Happiness Dee... New Year Begi... Yorke And Lou Hollow Crown ... More picks... Highest Rated Queen of K... New Year B... Frost-Free... Queen of K... Javomatics Weather Or... Recent Reviewers texasradiofis... Speck Javolenus panu Stefan Karten... Bluemillenium airtone More reviews... Support ccMixter This text and images on this site are licensed under a Creative Commons Attribution-Noncommercial 4.0 International License . This site uses ccHost , licensed under CC-GNU-GPL , which is a product of the ccTools project and uses GetID3 . This site is sponsored by ArtisTech Media . By using this site, you agree to our Terms of Use and Privacy Policy . Please note our site credits . Contact: site administrator . | 2026-01-13T09:29:23 |
https://t.me/BabelFishTalk | Telegram: View @BabelFishTalk Download BabelFish 908 members, 47 online Official BabelFish Telegram Group. Join Discord: https://discord.gg/QHvrrRnwzd Warning: Admins Never DM for money. Never Send any funds to anyone directly. Protect Your Keys View in Telegram If you have Telegram , you can view and join BabelFish right away. | 2026-01-13T09:29:23 |
https://www.linkedin.com/products/planview-product-portfolio-management/?trk=products_seo_search | Product Portfolio Management | LinkedIn Skip to main content LinkedIn Planview 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 Product Portfolio Management Product Management Software by Planview See who's skilled in this Add as skill Learn more Report this product About Planview’s product portfolio management solution enables R&D leaders and product organizations to optimize product portfolios and accelerate time-to-market with an integrated solution that connects product strategy, planning, ideation, prioritization, and development to delivery. Similar products Productboard Productboard Product Management Software Aha! Academy Aha! Academy Product Management Software Producer Producer Product Management Software Dovetail Dovetail Product Management Software Interim Product Managers Interim Product Managers Product Management Software Aha! Discovery Aha! Discovery Product Management Software Sign in to see more Show more Show less Planview products Enterprise Agile Planning Enterprise Agile Planning Project Management Software Professional Services Automation Professional Services Automation Professional Services Automation (PSA) Software Project Portfolio Management Project Portfolio Management Project Portfolio Management (PPM) Software Strategic Portfolio Management Strategic Portfolio Management Value Stream Management Value Stream Management 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:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=ro | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 �� | 2026-01-13T09:29:23 |
https://git-scm.com/book/fr/v2/Git-sur-le-serveur-R%c3%a9sum%c3%a9 | Git - Résumé 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 4.10 Git sur le serveur - Résumé Résumé Vous disposez de plusieurs moyens de mettre en place un dépôt Git distant pour pouvoir collaborer avec d’autres et partager votre travail. Gérer votre propre serveur vous donne une grande maîtrise et vous permet de l’installer derrière un pare-feu, mais un tel serveur nécessite généralement une certaine quantité de travail pour l’installation et la maintenance. Si vous placez vos données sur un serveur hébergé, c’est très simple à installer et maintenir. Cependant vous devez pouvoir héberger votre code sur des serveurs tiers et certaines politiques d’organisation ne le permettent pas. Choisir la meilleure solution ou combinaison de solutions pour votre cas ou celui de votre société ne devrait pas poser de problème. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://pt-br.facebook.com/login/?next=https%3A%2F%2Fwww.facebook.com%2Frootstock.io | Facebook Facebook Email ou telefone Senha Esqueceu a conta? Criar nova conta Você está bloqueado temporariamente Você está bloqueado temporariamente Parece que você estava usando este recurso de forma indevida. Bloqueamos temporariamente sua capacidade de usar o recurso. Back Português (Brasil) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Français (France) Deutsch Cadastre-se Entrar Messenger Facebook Lite Vídeo Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Mais conteúdo da Meta AI Instagram Threads Central de Informações de Votação Política de Privacidade Central de Privacidade Sobre Criar anúncio Criar Página Desenvolvedores Carreiras Cookies Escolhas para anúncios Termos Ajuda Upload de contatos e não usuários Configurações Registro de atividades Meta © 2026 | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=km | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 등록된 상품 및 | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/Mga-Pangunahing-Kaalaman-sa-Git-Mga-Alyas-sa-Git | Git - Mga Alyas sa 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. 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.7 Mga Pangunahing Kaalaman sa Git - Mga Alyas sa Git Mga Alyas sa Git Bago natin tapusin ang kabanatang ito tungkol sa pangunahing kaalaman sa git, mayroon lang isang maliit na tip na para mas maging simple ang iyong karanasa sa Git, mas madali, at mas pamilyar: mga alyas. Hindi namin babanggitin ang mga ito o magpalagay na gagamitin mo ang mga ito mamaya sa aklat na ito, ngunit dapat mong malaman kung paano gamitin ang mga ito. Ang Git ay hindi awtomatikong magpapahayag sa iyong command kapag hindi mo itong kumpletong itina-type. Kung hindi mo gustong i-type ang buong teksto sa bawat isa sa mga Git command, madali mo lang mai-setup ang alyas para sa bawat command sa pamamagitan ng paggamit ng gitconfig . Ito ang iilang mga halimbawa na marahil ay gusto mong i-setup: $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status Ibig sabihin nito, halimbawa, sa halip na mag-type ng git commit , kailangan mo lang mag-type ng git ci . Habang patuloy kang gumagamit ng Git, marahil ay parati mo ring ginagamit ang ibang mga command; kaya huwag mag-atubiling maglikha ng bagong mga alyas. Ang pamamaraang ito ay sobrang nakakatulong sa paglikha ng mga command na naisip mo na dapat umiiral. Halimbawa, para maitama ang problema sa paggamamit na naranasan mo sa pag-unstage ng isang file, maaari kang magdagdag ng sarili mong unstage na alyas nang Git: $ git config --global alias.unstage 'reset HEAD --' Ito ay nagpatimbang sa sumusunod na dalawang mga command: $ git unstage fileA $ git reset HEAD -- fileA Ito ay parang mas malinaw nang kaunti. Pangkaraniwan din ang pagdagdag ng last na command, gaya nito: $ git config --global alias.last 'log -1 HEAD' Sa ganitong paraan, madali mo lang makita ang huling 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> Gaya ng nakikita ninyo, ang Git ay simpleng nagpapalit lang ng bagong utos sa kung para saan talaga ang iyong alyas. Gayunman, marahil ay gugustuhin mong magpapatakbo ng external na command, sa halip na isang Git na subcommand. Sa kasong iyan, sisimulan mo ang command sa karakter na ! . Ito ay magagamit kung magsusulat ka ng iyong sariling mga kagamitan na gagana sa Git na repository. Maaari nating ipakita sa pamamagitan ng pag-alyas sa git visual na mapapatakbo ng gitk : $ git config --global alias.visual '!gitk' prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
http://dig.ccmixter.org/games | Music for Video Games Toggle navigation donate to keep this library available! licenses tag search featured music for film music for games free for commercial use royalty free licensed 1 - 40 of 3,222 display 10 20 40 Music for Video Games Our artists count on you returning their generosity. It Really Helps when you filters × all licenses free for commercial use royalty free ccPlus license all time magic sort recent latest instrumental only reset filters Frost-Free Jazz Speck Tags: remix , de , Boer , Mr_Yesterday , martinsea , Wired Sonic Liberty Speck Tags: remix ECHO Ant.Survila Tags: instrumental , drums , electronic , synthesizer , loops , remix , non_commercial , CBR Elephant in the room J.Lang Tags: drums , bass , instrumental , experimental , hip_hop , loops , remix , CBR More Tactless Reconstruction Speck Tags: remix , de , Boer , Javolenus , martinsea Remains (cdk Mix) cdk Tags: hip_hop , boom_bap , lofi , drums , bass , instrumental , remix , non_commercial Inheritance Calling Sister Midnight Tags: instrumental , electronic , synthesizer , experimental , remix , VBR Fragments of You jaspertine Tags: experimental , remix Wake 'n' Break Speck Tags: Javomatics Martijn de Boer (NiGiD) Tags: bass , drums , funk , funky , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , uptempo , remix , ccplus February (Halfway There Remix) Ben Blohowiak Tags: rock , alternative , music_for_film , instrumental , guitar , drums , bass , electronic , synthesizer , remix , non_commercial Exquisite Extinction Speck Tags: remix , MalreDeszik , Martijn , de Ex Mas Speck Tags: remix , de , Boer , Javolenus , Admiral Groucho Breaks Orbit Speck Tags: remix , de , Boer Gramophone Of Lament coruscate Tags: alternative , music_for_film , instrumental , hip_hop , downtempo , ambient , funky , remix , ccplus_stem , ccplus Je suis un Phoenix Bluemillenium Tags: electronic , bass , synthesizer , experimental , ambient , remix , CBR a night flight martinsea Tags: flight , synthesizer , remix Hibernation Stefan Kartenberg Tags: remix , VBR , Martijn , de , Boer A Good Text Hang Speck Tags: remix , CBR , archive , Apoxode Tactfully Less Speck Tags: remix , ccplus , CBR , archive , de , Boer No Greaties Martijn de Boer (NiGiD) Tags: funk , funky , jazz , jazzy , groove , instrumental , electronic , remix , VBR Fine Man "SUB layer added" salvatorej Tags: rock , electronic , synthesizer , guitar , remix , CBR , CBR backWhen airtone Tags: soul , guitar , instrumental , remix , non_commercial , CBR Black Ark Piano (4 Counting Down) Speck Tags: remix Lesser Tact Improvisation Martijn de Boer (NiGiD) Tags: bass , fretless , folk , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , moody , melancholical , melancholic , duo Falling Season Fresh_Morning_Duet Tags: electronic , instrumental , guitar , synthesizer , remix , Blohowiak , Fresh , Morning Reconstruct Darkroom Tags: drums , synthesizer , chill , remix , ccplus_stem , CBR Imaginary Line Speck Tags: upbeat , circuit_bent , remix , ccplus , CBR , archive , zip , archive , de , Boer The Fade Out coruscate Tags: alternative , electronic , synthesizer , experimental , chill , hip_hop , downtempo , spoken_word , electro , funky , music_for_film , jazz , remix Halloween Sun Bocrew Tags: boombap , nocoast , instrumental , remix Unaskewed Speck Tags: remix , CBR , archive , de , Boer Chromatic Fall Speck Tags: jazz , remix , de , Boer , Siobhan , Dakay , Javolenus , MalreDeszik , Mr_Yesterday Reconstructor Martijn de Boer (NiGiD) Tags: funk , funky , jazz , jazzy , groove , instrumental , electronic , remix , ccplus , VBR Sixeight 06 (6806 Remix) Ben Blohowiak Tags: electronic , glitch , drums , bass , synthesizer , instrumental , experimental , piano , music_for_film , techno , remix , non_commercial Later That Morning Speck Tags: remix , ccplus , CBR , archive , zip , archive , de , Boer Zombie Christmas 2025 Speck Tags: jingle_bells , remix , Square A Grand Looking Back Speck Tags: remix , jaspertine , zeusjones Happy Alchemy Beat coruscate Tags: chill , hip_hop , downtempo , remix †hr34db∆®∑ Vidian Tags: bass , experimental , electronic , instrumental , remix , non_commercial SONIC DIVE Ant.Survila Tags: instrumental , drums , bass , electronic , synthesizer , loops , piano , remix , nc_sampling_plus Here Licenses Privacy Terms Donate(!) Credits There Everywhere Twitter YouTube Vimeo Facebook Instagram Resources GitHub Query API Forums Contact | 2026-01-13T09:29:23 |
https://www.atlassian.com/blog/bitbucket/the-2025-year-in-review-and-whats-coming-soon#content | The 2025 Year in Review (and what's coming soon) - Work Life by Atlassian Skip to main content Atlassian Work Life Products & news Team Playbook Community More from Atlassian Products & news Products Apps Atlassian Guard Bamboo Bitbucket Confluence Crowd Crucible Fisheye Focus Halp Jira Jira Align Jira Product Discovery Jira Service Management Loom Sourcetree Statuspage Trello Topics AI Agile How we build Continuous Delivery Design Developers DevOps Enterprise Git IT Service Management Inside Atlassian Project Management Work Management Company News Subscribe Search Primary Menu Search in https://www.atlassian.com/blog/ Search Products All Products Apps Atlassian Guard Bamboo Bitbucket Confluence Crowd Crucible Fisheye Halp Jira Jira Align Jira Service Management Loom Opsgenie Sourcetree Statuspage Trello Topics AI Agile Continuous Delivery Developer DevOps Enterprise Git IT Service Management Inside Atlassian Project Management Work Management Company News Blog Published December 17, 2025 in Bitbucket Chris Clarke Published December 17, 2025 in Bitbucket The 2025 Year in Review (and what’s coming soon) 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 More Collections Collection Ways of Working How you work is just as important as the work you're doing. View Collection Collection Wellbeing | Well-doing Strategies for individuals and leaders to cultivate a flexible, balanced, and inclusive work life. View Collection Collection The Flywheel Growth Model There are loads of ways to grow a company – learn about our approach here. View Collection The 2025 Year in Review (and what’s coming soon) Subscribe Facebook Twitter Linkedin Pocket Email Join over 150,000 working professionals By Atlassian Culture, tech, teams, and tips, delivered twice a month Sign me up! Atlassian.com Terms of Use Privacy Policy Notice at Collection Copyright © 2026 Atlassian Subscribe to Work Life Advice, stories, and expertise about work life today. Email * | 2026-01-13T09:29:23 |
https://www.atlassian.com/blog/software-teams/page/2 | Software Teams - Atlassian Blog - Page 2 Skip to main content Atlassian Work Life Products & news Team Playbook Community More from Atlassian Products & news Products Apps Atlassian Guard Bamboo Bitbucket Confluence Crowd Crucible Fisheye Focus Halp Jira Jira Align Jira Product Discovery Jira Service Management Loom Sourcetree Statuspage Trello Topics AI Agile How we build Continuous Delivery Design Developers DevOps Enterprise Git IT Service Management Inside Atlassian Project Management Work Management Company News Subscribe Search Primary Menu Search in https://www.atlassian.com/blog/ Search Products All Products Apps Atlassian Guard Bamboo Bitbucket Confluence Crowd Crucible Fisheye Halp Jira Jira Align Jira Service Management Loom Opsgenie Sourcetree Statuspage Trello Topics AI Agile Continuous Delivery Developer DevOps Enterprise Git IT Service Management Inside Atlassian Project Management Work Management Company News Blog Articles About Software Teamwork How to run a remote retrospective and have fun doing it Bringing this time-honored team tradition into the virtual world is easier than you might think. Here are a few pointers. Bitbucket Introducing step failure strategies in Bitbucket Pipelines We are excited to introduce a new capability in Bitbucket Pipelines – Step Failure Strategies. This is the first of... Bitbucket Quickly diagnose issues by viewing previous Pipeline runs We are excited to announce the release of a new capability in Bitbucket Pipelines that will improve your experience diagnosing... Apps How visuals can boost the accuracy of product development This is a guest post written by Mac McConnell, VP of Marketing at Gliffy, creators of visual planning apps on... Apps How using checklists in Jira can help teams be more Agile This article was written with Olga Rusnak of Railsware. —— In the late ‘90s and early 2000s, most technology companies... Apps Atlassian Marketplace Monthly: automation add-ons relieve your pain The Atlassian Marketplace has killer add-ons – built by those who've been there and know your pain. Automation add-ons like these increase your team's productivity and efficiency. What's more, these are only a few... Posts pagination Previous 1 2 3 4 5 … 130 131 132 133 134 Next Atlassian Atlassian.com Terms of Use Privacy Policy Notice at Collection Subscribe to Work Life Advice, stories, and expertise about work life today. Email * | 2026-01-13T09:29:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=pt_PT | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Play에 | 2026-01-13T09:29:23 |
https://www.facebook.com/CCMixter | 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:23 |
https://git-scm.com/book/ko/v2/GitHub-GitHub-%ed%94%84%eb%a1%9c%ec%a0%9d%ed%8a%b8-%ea%b4%80%eb%a6%ac%ed%95%98%ea%b8%b0 | Git - 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. 시작하기 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 6.3 GitHub - GitHub 프로젝트 관리하기 GitHub 프로젝트 관리하기 지금까지 남의 프로젝트에 기여하는 법을 살펴보았고 이번에는 직접 프로젝트를 운영하는 법을 살펴보자. 프로젝트를 생성해서 관리하는 방식 말이다. 새 저장소 만들기 저장소를 새로 만들고 프로젝트 코드를 공유해 보자. 대시보드 오른쪽에 있는 “New repository” 버튼을 클릭하면 저장소를 만드는 폼으로 이동한다. 맨 위 툴바의 사용자이름 옆에 있는 + 버튼을 클릭해도 된다. 그림 110. “Your repositories” 박스. 그림 111. 사용자이름 옆 “New repository” 메뉴. 위 버튼을 누르면 “새 저장소” 를 만드는 화면으로 이동한다. 그림 112. “새 저장소” 만들기. 프로젝트 이름을 넣는 것만 필수다. 다른 것은 생략해도 된다. “Create Repository” 버튼을 클릭하면 '뿅’하고 <user>/<project_name> 위치에 GitHub 저장소가 생긴다. 아직 저장소에 코드가 하나도 없어서, GitHub는 Git 저장소를 만드는 방법이나 기존 Git 프로젝트를 넣는 방법을 보여준다. 이 내용을 다시 살펴보고 싶다면 Git의 기초 를 보라. 여기서 또 설명하지 않는다. GitHub에 프로젝트를 올렸으면 다른 사람들에게 프로젝트 URL을 알려주고 공유할 수 있다. 모든 프로젝트의 HTTPS URL은 https://github.com/<user>/<project_name> 처럼 생겼고 SSH는 git@github.com:<user>/<project_name> 처럼 생겼다. Git은 이 두 URL을 통해서 Fetch 하고 Push 할 수 있지만, 인증 방식은 사용하는 프로토콜에 따라 다르다. 노트 GitHub 계정 없이 Clone 할 수 있기 때문에 공개 프로젝트를 공유할 때는 SSH보다 HTTP URL를 더 많이 공유한다. SSH URL을 사용하려면 계정도 있어야 하고 SSH 키도 GitHub에 등록해야 한다. 브라우저에서 프로젝트 페이지에 접속할 때도 저장소 URL로 사용하는 HTTP URL을 그대로 사용한다. 동료 추가하기 저장소에 커밋 권한을 주고 싶은 동료가 있으면 “Collaborator” 로 추가해야 한다. Ben과 Jeff, Louise라는 동료가 있는데 그들이 내 저장소에 Push 할 수 있도록 하고 싶으면 내 프로젝트에 GitHub 계정들을 추가해야 한다. 계정이 추가된 사람은 해당 프로젝트와 Git 저장소에 “Push” 할 수 있을 뿐만 아니라 읽고 쓰기도 가능하다. 오른쪽 밑에 있는 ` Settings ` 링크를 클릭한다. 그림 113. 저장소 설정 링크. 왼쪽 메뉴에서 “Collaborators” 를 선택한다. 텍스트 박스에 사용자이름을 입력하고 “Add collaborator” 를 클릭한다. 필요한 사람을 모두 추가할 때까지 반복한다. 그리고 오른쪽에 있는 “X” 를 클릭하면 권한이 회수된다. 그림 114. 저장소의 동료. Pull Request 관리하기 프로젝트를 만들고 코드도 넣고 동료가 Push 할 수 있게 했다. 이제 Pull Request가 왔을 때 어떻게 해야 하는지 보자. Pull Request는 같은 저장소나 Fork 한 저장소에서 브랜치를 보내오는 것이다. 그 둘의 차이는 권한에 있다. Fork 한 저장소는 다른 사람의 저장소이기 때문에 그 보내온 브랜치에 Push 할 권한이 없다. 하지만, 같은 저장소의 브랜치에는 Push 할 수 있다. “tonychacon” 이라는 사람이 “fade” 라는 Arduino 프로젝트를 만든 상황을 살펴보자. 이메일 알림 어떤 사람이 코드를 수정해서 Pull Request를 보내왔다. 그러면 새로운 Pull Request가 왔다는 메일이 담당자에게 간다. 새 Pull Request에 대한 이메일 알림. 같은 메일이 보내진다. 그림 115. 새 Pull Request에 대한 이메일 알림. 이 이메일은 무엇이 달라진 것인지 간략히 보여준다. 해당 Pull Request에서 어떤 파일이 얼마나 변경됐는지 보여준다. 그리고 Pull Request 페이지 링크도 있고 CLI로 Merge 하는 방법과 URL도 간략히 보여준다. git pull <url> patch-1 라는 명령이 궁금할 텐데 이렇게 하면 리모트 브랜치를 간단히 Merge 할 수 있다. 저장소를 리모트로 추가하지 않아도 된다. 필요하면 토픽 브랜치를 만들고 리모트 브랜치로부터 통합하기 에서 배운 명령어로 Pull Request로 직접 Merge 해도 된다. 그리고 눈치챘을 테지만 .diff 와 .patch URL은 Pull Request의 'Unified Diff’와 Patch 버전의 URL이다. 이 URL로 아래와 같이 Pull Request를 Merge 할 수 있다. $ curl http://github.com/tonychacon/fade/pull/1.patch | git am Pull Request로 함께 일하기 GitHub 플로우 에서 설명했듯이 Pull Request를 만든 사람과 토론할 수 있다. GFM을 사용하여 특정 커밋을 선택하거나, 특정 라인을 지정하거나, 혹은 전체 Pull Request 자체에도 코멘트를 남길 수 있다. 일단 대화에 참여하고 나면 누군가 코멘트할 때마다 이메일 알림이 계속 온다. 그 이메일에는 Pull Request 페이지의 링크가 포함돼 있기 때문에 어떤 일이 일어나고 있는지 쉽게 알 수 있다. 그리고 답 메일을 보내면 Pull Request의 코멘트로 달린다. 그림 116. 답변 메일이 Pull Request의 스레드가 됨. 보내온 코드가 마음에 들어서 Merge 하고 싶다면 로컬에 가져와서 Merge 할 수 있다. git pull <url> <branch> 명령으로 Merge 하면 되는데 먼저 Fork 한 저장소를 리모트로 추가하고 Fetch 해서 Merge 한다. GitHub 사이트에서 “Merge” 버튼을 누르는 것으로 간편하게 Merge 할 수 있다(Trivial Merge). “fast-forward” 가 가능할 때도 “non-fast-forward” Merge를 하기 때문에 Merge 커밋이 생긴다. 그래서 “Merge” 버튼을 클릭해서 Merge 하면 항상 Merge 커밋이 생긴다. 여기서 어떻게 해야 하는지 'command line' 힌트 링크를 클릭하면 Merge 버튼과 Pull Request를 수동으로 Merge 하기. 과 같이 알려준다. 그림 117. Merge 버튼과 Pull Request를 수동으로 Merge 하기. 만약 Pull Request를 Merge 하지 않기로 했다면 그냥 닫으면 된다. 그러면 그 Pull Request를 보낸 사람에게 알림이 간다. Pull Request의 Ref 일일이 리모트를 등록하고 Pull 하는 것은 Pull Request를 많이 처리하는 사람에게는 고통스럽다. GitHub는 이럴 때 사용하는 방법을 제공한다. 이 내용은 Refspec 에서 자세히 설명할 거고 조금 어려울 수 있다. GitHub는 Pull Request의 브랜치를 서버에 있는 가상 브랜치로 노출해준다. GitHub가 자동으로 해주기 때문에 바로 이용하면 된다. 이걸 해보려면 저수준(“plumbing”) 명령어인 ls-remote 가 필요하다. 이 명령어는 아무래도 매일 쓰는 명령어는 아니지만, 서버에 어떤 Ref가 있는지 보여 준다. “plumbing” 명령어는 Plumbing 명령과 Porcelain 명령 에서 자세히 설명한다. 이 명령어로 좀 전의 “blink” 저장소를 살펴보자. 저장소 브랜치뿐만 아니라 태그 등 온갖 Ref를 보여준다. $ git ls-remote https://github.com/schacon/blink 10d539600d86723087810ec636870a504f4fee4d HEAD 10d539600d86723087810ec636870a504f4fee4d refs/heads/master 6a83107c62950be9453aac297bb0193fd743cd6e refs/pull/1/head afe83c2d1a70674c9505cc1d8b7d380d5e076ed3 refs/pull/1/merge 3c8d735ee16296c242be7a9742ebfbc2665adec1 refs/pull/2/head 15c9f4f80973a2758462ab2066b6ad9fe8dcf03d refs/pull/2/merge a5a7751a33b7e86c5e9bb07b26001bb17d775d1a refs/pull/4/head 31a45fc257e8433c8d8804e3e848cf61c9d3166c refs/pull/4/merge 저장소 안이라면 git ls-remote origin 이라고 실행시켜도 된다. 저장된 리모트 이름을 사용할 수 있다. GitHub 저장소에 어떤 Pull Request라도 열려있다면 refs/pull/ 로 시작하는 이름으로 Ref가 생성된다. 이것도 브랜치지만 refs/heads/ 로 시작하는 브랜치와는 달리 Clone과 Fetch 할 때 받아지지 않으며 기본적으로 무시된다. Pull Request에는 두 종류의 Ref가 있다. /head 로 끝나는 것은 Pull Request 브랜치가 가리키는 마지막 커밋이다. 누군가 우리 저장소에 bug-fix 라는 브랜치를 Pull Request로 보내는 상황을 살펴보자. 이 브랜치는 a5a775 커밋을 가리킨다. bug-fix 브랜치는 Fork 한 저장소에 있는 브랜치라서 우리 저장소에 없다. 그럼에도 a5a775 를 가리키는 pull/<pr#>/head 형식의 브랜치가 자동으로 생긴다. 그래서 매번 다른 저장소를 리모트로 등록하지 않고서도 Pull Request 브랜치를 쉽게 Pull 할 수 있다. 그 브랜치를 한번 가져와 보자. $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD “리모트의 브랜치 origin 을 refs/pull/958/head 로 Fetch 한다” 는 뜻이다. Git은 충실하게 전부 내려받고 마지막 커밋을 .git/FETCH_HEAD 에 저장한다. git merge FETCH_HEAD 으로 Merge 해서 테스트할 수 있다. 이렇게 Merge 하면 Merge 커밋 메시지가 약간 이상해진다. 또한 많은 Pull Request를 처리해야 하는 경우, 쓸데없는 Merge 커밋도 많아진다. 항상 Pull Request를 전부 가져오게 할 수 있다. .git/config 파일을 열어서 origin 리모트를 찾는다. origin 리모트는 사실 아래와 같은 것을 의미한다. [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* fetch = 로 시작하는 라인이 “refspec” 이라는 거다. 리모트 이름과 로컬 .git 디렉토리를 어떻게 매핑하는지 나타낸다. 여기서는 해당 리모트에서 refs/heads 에 해당하는 이름이 refs/remotes/origin 디렉토리에 매핑된다는 의미다. Refspec을 새로 추가해보자. [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* 추가한 마지막 라인의 의미는 refs/pull/123/head 같은 Ref를 refs/remotes/origin/pr/123 에 저장'' 한다는 의미다. git fetch 라고 실행하면 새 Refspec의 브랜치도 가져온다. $ git fetch # … * [new ref] refs/pull/1/head -> origin/pr/1 * [new ref] refs/pull/2/head -> origin/pr/2 * [new ref] refs/pull/4/head -> origin/pr/4 # … 서버에 있는 모든 Pull Request을 추적하는 트래킹 브린치가 생겼다. 쓰기는 불가능하지만 계속 Fetch 해 올 수 있다. 이렇게 하면 Pull Request를 로컬에 가져와서 작업하는 게 편해진다. $ git checkout pr/2 Checking out files: 100% (3769/3769), done. Branch pr/2 set up to track remote branch pr/2 from origin. Switched to a new branch 'pr/2' head 로 끝나는 Refspec에 대해서 살펴봤고 이제 refs/pull/#/merge 처럼 생긴 Refspec을 알아보자. 이 브랜치는 GitHub에서 Merge 버튼으로 Merge 했을 때 적용되는 결과다. GitHub에서 실제로 Merge 하기 전에 로컬로 가져와서 먼저 테스트할 수 있다. Pull Request 이어가기 Pull Request를 Merge 할 브랜치는 master 가 아니어도 된다. 주 브랜치를 고를 수도 있고 Pull Request를 열 때 다른 브랜치를 골라도 된다. 심지어 다른 Pull Request를 고를 수도 있다. 착착 잘 진행하는 어떤 Pull Request가 있는데 거기에 뭔가 아이디어를 더하고 싶다는 생각이 들었다. 좋은 아이디어라는 확신도 부족하고 무엇보다 Merge 될 브랜치에 Push 권한이 없다. 이럴 땐 Pull Request에 Pull Request를 보낼 수 있다. Pull Request를 만들러 가면 페이지 위쪽에 어떤 저장소의 브랜치를 어떤 저장소의 브랜치로 요청하는 것인지를 보여주는 박스가 있다. “Edit” 버튼을 누르면 Fork 한 저장소 중 하나로 저장소를 변경하고 해당 저장소의 브랜치로 변경할 수 있다. 그림 118. Pull Request을 어디로 보낼지 대상을 선택. 쉽게 다른 Fork 저장소나 Pull Request의 브랜치를 골라 Pull Request를 열 수 있다. 멘션과 알림 GitHub는 어떤 팀이나 사람에게 질문하거나 피드백을 받을 수 있도록 쉽고 편한 알림 시스템을 제공한다. GitHub 어디에서나 @ 만 입력해도 동료나 기여자의 사용자이름이 자동완성 된다. 그림 119. @ 만 입력. 자동완성 메뉴에 없는 사람도 입력할 수 있지만, 자동완성이 편하고 빠르다. GitHub에서 글을 쓸 때 @멘션 을 하면 해당 사용자에게 알림이 간다. 일일이 의견을 물으러 다니는 것보다 이렇게 토론에 참여시키는 게 훨씬 유용하다. GitHub에서는 멘션으로 팀의 동료나 다른 사람을 이슈나 Pull Request에 참여시킨다. 한번 @멘션 으로 언급되면 그 사람은 “구독 상태(Subscribed)” 가 된다. 그래서 해당 이슈나 Pull Request에서 계속 알림이 온다. 이슈나 Pull Request를 직접 만들었거나, 해당 저장소를 'Watching’하는 상태이거나, 코멘트를 단 경우에도 구독 상태가 된다. 더는 알림을 받고 싶지 않으면 화면의 “Unsubscribe” 버튼으로 멈출 수 있다. 그림 120. 특정 이슈와 Pull Request의 알림 끊기(Unsubscribe). 알림 페이지 GitHub의 “알림” 은 프로젝트에서 어떤 일이 일어나면 바로 알 수 있도록 안내해 주는 것이다. 이 알림은 원하는 방법으로 설정해 쓸 수 있다. 설정의 “Notification center” 탭에 가면 설정할 수 있는 옵션이 있다. 그림 121. Notification center 옵션. 알림을 이메일로 받을지 웹으로 받을지 선택할 수 있다. 물론 두 가지 방법을 동시에 사용해도 된다. 그리고 그냥 대화에 참여하는 경우와 프로젝트를 'Watching' 하는 경우를 나누어 선택할 수 있다. 웹 알림 웹 알림은 GitHub에서 제공하는 것으로 GitHub 사이트에서만 확인할 수 있다. 이 옵션을 선택하면 알림이 오면 알림 아이콘에 파란 점을 볼 수 있다. Notification center. 을 확인해보자. 그림 122. Notification center. 알림 아이콘을 클릭하면 알림 메시지를 확인할 수 있다. 알림은 프로젝트별로 분류된다. 왼쪽 메뉴에 있는 프로젝트를 선택하면 관련 알림만 걸러서 볼 수 있다. 각 알림에 있는 체크박스를 클릭해서 읽었다고 표시를 할 수 있고 제일 위에 있는 체크박스를 클릭하면 해당 알림에 대해서 전부 읽음 표시를 할 수 있다. 그리고 'Mute' 버튼을 클릭하면 해당 사항에 대해서는 더는 알림이 오지 않는다. 이 기능을 사용하면 쏟아지는 알림들도 매우 효율적으로 처리할 수 있다. GitHub의 파워 유저는 이메일 알림을 꺼놓고 GitHub 사이트에서만 알림을 관리하기도 한다. 이메일 알림 이메일 알림을 켜 놓으면 이메일로도 GitHub 알림을 확인할 수 있다. 이메일 알림으로 온 코멘트 과 새 Pull Request에 대한 이메일 알림. 의 예를 보면 관련 알림들이 이메일 스레드로 잘 분류되는 것을 볼 수 있다. 그래서 이메일 스레드를 잘 지원하는 메일 클라이언트를 사용하는 것이 좋다. GitHub가 보낸 이메일 헤더를 보면 여러 가지 메타데이터가 들어 있다. 그래서 사용자는 이메일 필터나 룰 같은 자동 관리 기능으로 쉽게 관리할 수 있다. 새 Pull Request에 대한 이메일 알림. 에서 보여준 이메일의 헤더는 아래와 같다. To: tonychacon/fade <fade@noreply.github.com> Message-ID: <tonychacon/fade/pull/1@github.com> Subject: [fade] Wait longer to see the dimming effect better (#1) X-GitHub-Recipient: tonychacon List-ID: tonychacon/fade <fade.tonychacon.github.com> List-Archive: https://github.com/tonychacon/fade List-Post: <mailto:reply+i-4XXX@reply.github.com> List-Unsubscribe: <mailto:unsub+i-XXX@reply.github.com>,... X-GitHub-Recipient-Address: tchacon@example.com 프로젝트에 따라 혹은 Pull Request인지에 따라 분류하거나 다른 주소로 재전송하고 싶다면 Message-ID 를 이용하는 게 좋다. 이 데이터는 <user>/<project>/<type>/<id> 형식으로 돼 있다. 만약 이슈에 대한 데이터면 <type> 부분이 “pull” 이 아니라 “issues” 라고 돼 있을 것이다. List-Post 와 List-Unsubscribe 필드를 인식하는 메일 클라이언트를 사용하고 있으면 좀 더 편리하게 사용할 수 있다. List-Post 는 이메일로 리스트에 글을 올리는 데 사용하고 List-Unsubscribe 는 이메일 클라이언트에서 알림을 그만 받도록 할 수 있다. 이슈와 Pull Request페이지의 “Unsubscribe” 버튼을 클릭하거나 웹 알림 페이지에서 “Mute” 버튼을 클릭하는 것과 같다. 이메일과 웹 알림이 둘 다 켜져 있으면 알림이 이메일로도 오고 웹으로도 온다. 이메일 클라이언트에서 이미지가 허용되어 있으면, 메일을 읽었을 때 웹에서도 읽었다고 표시된다. 특별한 파일 저장소에 있는 파일 중에서 GitHub가 사용하는 몇 가지 특이한 파일들이 있다. README GitHub는 저장소 랜딩 페이지를 보여줄 때 README 파일을 이용해서 보여준다. README 파일 형식에 상관없이 잘 보여준다. README 파일이든 README.md 파일이든 README.asciidoc 파일이든 GitHub가 자동으로 렌더링해서 보여준다. 많은 사람이 이 파일에 저장소나 프로젝트에 처음 방문한 사람들에게 필요한 정보를 정리해 둔다. 보통 아래와 같은 내용을 쓴다. 무슨 프로젝트인지 설정하고 설치하는 방법 사용법과 실행 결과에 대한 예제 프로젝트의 라이센스 기여하는 방법 GitHub는 README 파일을 렌더링하는 것이기 때문에 이미지나 외부 링크를 적어도 된다. CONTRIBUTING GitHub는 CONTRIBUTING 파일도 인식한다. README와 마찬가지로 원하는 파일 형식을 사용하면 된다. Pull Request를 열 때 이 파일이 있으면 CONTRIBUTING 파일이 있음을 보여준다. 과 같이 링크를 보여준다. 그림 123. CONTRIBUTING 파일이 있음을 보여준다. 이 파일에는 프로젝트에 기여하는 방법과 Pull Request 규칙 같은 것을 적는다. 그러면 사람들이 Pull Request를 열 때 이 가이드라인을 참고할 수 있다. 프로젝트 관리 특별히 관리할 만한 게 별로 없지만 알고 있으면 유용한 것들을 소개한다. 기본 브랜치 변경하기 기본 브랜치를 “master” 말고 다른 브랜치로 설정할 수 있다. Pull Request를 열 때 설정한 기본 브랜치가 기본으로 선택된다. 기본 브랜치는 저장소 설정 페이지의 “Options” 탭에서 변경한다. 그림 124. 기본 브랜치 변경하기. 기본 브랜치 변경은 쉽고 정말로 기본으로 쓰인다. 저장소를 Clone 하면 여기서 설정한 브랜치가 기본으로 Checkout된다. 프로젝트 넘기기 프로젝트 소유자를 다른 사용자나 Organization으로 변경할 수 있다. 저장소 설정 페이지의 “Options” 탭을 보면 페이지 아래쪽에 “Transfer ownership” 항목이 있다. 여기 있는 Transfer 버튼으로 프로젝트를 넘길 수 있다. 그림 125. 다른 GitHub 사용자나 Organization에 프로젝트 넘기기. 맡던 프로젝트를 다른 사람에게 넘겨주거나 프로젝트가 커져서 Organizaiton 계정으로 옮기고 싶을 때 유용하다. 저장소만 옮겨지는 것이 아니라 'Watching’하는 사람이나 'Star’한 사람까지도 함께 옮겨진다. 그리고 URL은 Redirect되는데 웹 접속뿐만 아니라 Clone 이나 Fetch 요청까지도 Redirect된다. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://git-scm.com/book/tl/v2/Mga-Pangunahing-Kaalaman-sa-Git-Pagtatala-ng-mga-Pagbabago-sa-Repositoryo | Git - Pagtatala ng mga Pagbabago sa Repositoryo 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.2 Mga Pangunahing Kaalaman sa Git - Pagtatala ng mga Pagbabago sa Repositoryo Pagtatala ng mga Pagbabago sa Repositoryo Sa puntong ito, dapat kang magkaroon ng tunay na repositoryo ng Git sa iyong lokal na makina, at isang checkout o gumaganang kopya sa lahat ng mga file nito na nasa harapan mo. Kadalasan, ikaw ay gustong mag-umpisa sa paggawa ng mga pababago at pag-commit sa mga snapshot ng mga pagbabago na iyon sa bawat oras na ang proyekto ay aabot sa estado na gusto mong itala. Tandaan na sa bawat file na nasa iyong tinatrabahong direktoryo ay maaaring nasa isa sa dalawang estado: sinusubaybayan o hindi sinusubaybayan . Ang sinusubaybayan na mga file ay mga file na nasa huling snapshot; maaari silang maging hindi nabago, nabago, o itinanghal. Sa madaling salita, ang sinusubaybayan na mga file ay ang mga file na alam ng Git. Ang hindi sinusubaybayan na mga file ay lahat ng iba pa — ang anumang mga file sa iyong tinatrabahong direktoryo na wala sa iyong huling snapshot at wala sa iyong staging na lugar. Sa una mong pag-clone ng repositoryo, lahat ng iyong mga file ay magiging sinusubaybayan at hindi nabago dahil sinuri ng Git ang mga ito at hindi mo na-edit ang kahit ano. Habang ikaw ay nag-edit ng mga file, nakikita ni Git sila na bilang binago, dahil binago mo ang mga ito mula noong iyong huling commit. Habang ikaw ay nagtrabaho, pinili mong itinanghal ang mga nabagong mga file na ito at pagkatapos nag-commit sa lahat ng itinanghal na mga pagbabago, at ang siklo ay umuulit. Figure 8. Ang lifecycle ng katayuan ng iyong mga file. Pagsusuri ng Katuyuan ng Iyong mga File Ang pangunahing kasangkapan na iyong ginamit para matukoy kung aling mga file ay sa aling estado ay ang git status na utos. Kung patakbuhin mo ang utos na ito na direkta pagkatapos ng clone, dapat mong makita ang isang bagay na tulad nito: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean Nangangahulugan ito na mayroon kang isang malinis na tinatrabahong direktoryo — sa ibang salita, waka sa iyong mga sinusubaybayan na mga file ang nabago. Hindi rin makikita ni Git ang anumang hindi sinusubaybayan na mga file, o sila ay malista dito. Sa wakas, ang utos ay nagsasabi sa iyo na kung saan na branch ikaw ay nandoon at nagsasabi sayo na hindi ito naiiba mula sa parehong branch sa server. Para sa ngayon, ang branch na yan ay laging “master”, kung saan ay default; hindi ka mag-alala dito. Pag-branch ng Git ay magpapatuloy sa mga branch at mga reperensiya sa detalye. Sabihin natin na ikaw ay nagdagdag ng isang bagong file sa iyong proyekto, isang simpleng README na file. Kung ang file ay hindi umiiral noon, at ikaw ay nagpatakbo ng git status , Iyong makikita ang iyong hindi sinusubaybayan na file na tulad nito: $ 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) Makikita mo na ang iyong bagong README na file ay hindi nasubaybayan, dahil ito ay sa ilalim ng “Untracked files” papunta sa iyong katayuan ng output. Ang hindi sinusubaybayan ay talagang ang ibig sabihin nito na ang Git ay nakikita ang isang file na wala sa iyong nakaraang snapshot; Ang Git ay hindi magsisimula kasama ito sa iyong commit na mga snapshot hanggang ikaw ay nagsasabi na gawin ito. Ginagawa ito para ikaw ay hindi aksidenteng makapagsimula na kasama ang nabuong binary na mga file o ibang mga file na hindi mo gustong isama. Gusto mong magsimula na kasama ang README , kaya natin simulan ang pagsubaybay sa file. Pagsubaybay sa Bagong mga File Upang magsimula sa pagsubaybay ng isang bagong file , gagamitn mo ang utos na git add . Para umpisahan ang pagsubaybay sa README na file, maaari mo itong patakbuhin: $ git add README Kung pinapatakbo mo ang iyong katayuan ng utos uli, makikita mo na ang iyong README na file ay ngano nakasubaybay na at itatanghal upang ma-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 Maaari mong sabihin na ito ay itinanghal dahil ito ay sa ilalim ng “Changes to be committed” na heading. Kung ikaw ay mag-commit sa puntong ito, ang bersyon ng file sa oras na pinatakbo ang git add ay kung ano ang magiging makasaysayan na snapshot. Maaari mong isipin na kapag pinatakbo mo ang git init ng maaga, pagkatapos patakbuhin mo ang git add <files> — iyon ang pagsisimula ng pagsubaybay ng mga file sa iyong direktoryo. Ang git add na utos ay kumukuha ng isang pangalan ng path para sa alinman na file o direktoryo; kung ito ay isang direktoryo, ang utos ay nagdagdag ng lahat ng mga file sa direktoryo ng maraming beses. Pagtanghal ng Nabagong mga File Baguhin natin ang file na nasubaybayan na. Kung ikaw ay nagbago sa dating sinusubaybayan na file na tinatawag na CONTRIBUTING.md at pagkatapos pinatakbo mo ang iyong git status na utos uli, may makukuha kang isang bagay na tulad nito: $ 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 Ang CONTRIBUTING.md na file ay lumilitaw sa ilalim ng seksyon na nakapangalan na “Changes not staged for commit” — na ibig sabihin na ang isang file na sinusubaybayan ay nabago sa tinatrabahong direktoryo pero hindi pa naitanghal. Upang itanghal ito, patakbuhin mo ang git add na utos. git add ay isang multipurpose na utos — ginagamit mo ito upang magsimula sa pagsubaybay ng bagong mga file, upang itanghal ang mga file, at gumawa pa ng ibang mga bagay tulad ng pagmamarka ng merge-conflicted na mga file bilang nalutas. Maaaring makatulong ito na isipin ito na mas higit pa “magdagdag ng tumpak na nilalaman na ito sa susunod na commit” sa halip na “idagdag ang file na ito sa proyekto”. Patakbuhin natin ang git add ngayon upang itanghal ang CONTRIBUTING.md na file, at pagkatapos patakbuhin ang git status muli: $ 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 Ang pareho na mga file ay naitanghal at mapupunta sa iyong susunod na commit. Sa puntong ito, ipagpalagay na naaalala mo na isang maliit na pagbago na gusto mong gawin sa CONTRIBUTING.md bago mo i-commit ito. Buksan mo ito uli at gawin ang pagbabago na iyon, at handa kana i-commit. Gayunpaman, patakbuhin natin ang git status ng isa pang pagkakataon: $ 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 Ano ba ‘yan? Ngayon ang CONTRIBUTING.md ay nakalista bilang kapwa nakatanghal at hindi nakatanghal. Paano ito naging posible? Ito ay nagsasabi na ang Git ay nagtatanghal ng isang file na eksakto na kung kailan ikaw ay nagpatakbo sa git add na utos. Kung ikaw ay mag-commit ngayon, ang bersyon ng CONTRIBUTING.md tulad noong huling pinatakbo ang git add na utos ay kung paano ito pupunta sa commit, hindi ang bersyon ng file na tulad ng iyong tinatrabahong direktoryo kapag nagpatakbo ka ng git commit . Kung magbago ka ng isang file pagkatapos iyong pinatakbo ang git add , kailangan mong patakbuhin ang git add muli upang itanghal ang pinakabagong bersyon ng 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 Maikling Katayuan Habang ang git status na output ay medyo komprehensibo, ito din ay medyo sali-salita. Ang Git din ay merong isang maliit na status flag para ikaw ay makakita ng iyong mga binago sa isang mas compact na paraan. Kung patakbuhin mo ang git status -s o git status --short makakuha ka ng mas pinadali na output mula sa utos: $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt Bagong mga file na hindi sinusubaybayan ay merong isang ?? sunod sa kanila, Ang mga bagong files na idinagdag sa pagtatanghal na lugar ay merong A , nabago na mga file ay merong M at iba pa. Mayroong dalawang column sa output - ang kaliwang-kamay na column ay nagpapaliwanag sa katayuan sa pagtatanghal na lugar at ang kanang-kamay na column ay nagpapaliwanag sa katayuan sa tinatrabahong tree. Kaya halimbawa sa output na iyon, ang README na file ay binago sa tinatrabahong direktoryo pero hindi pa natanghal, habang ang lib/simplegit.rb na file ay binago at natanghal. Ang Rakefile ay binago, natanghal at pagkatapos ay binago muli, kaya may mga pagbabago sa mga ito na parehong natanghal at hindi natanghal. Pagbalewala ng mga File Madalas, magkakaroon ka ng klase ng mga file na hindi mo gusto ang Git na awtomatikong magdagdag o kahit na magpakita sayo bilang hindi sinusubaybayan. Ang mga ito ay pangkalahatang awtomatikong nabuo na mga file tulad ng log na mga file o mga file na ginawa ng iyong tinayong sistema. Sa ganitong mga kaso, maaari kang gumawa ng mga palatandaan ng listahan ng file upang tumugma sa kanilang napangalan na .gitignore . Narito ang isang halimbawa sa .gitignore na file: $ cat .gitignore *.[oa] *~ Ang unang linya ay nagsasabi ng Git na hindi pansinin ang anumang mga file na nagtatapos sa “.o” o “.a” — na object at archive na mga file na maaari ang produkto ng pag-build ng iyong code. Ang pangalawang linya ay nagsasabi ng Git na hindi pansinin ang lahat ng mga file na kaninong mga pangalan ay nagtatapos na may ( ~ ), na ginagamit ng maraming mga tekstong editor tulad ng Emacs upang markahan ang pansamantalang mga file. Maaari mo ring magsama ng log, tmp, o pid na direktoryo; awtomatikong nabuo na dokumentasyon; at iba pa. Pag-set ng isang .gitignore na file para sa iyong bagong repositoryo bago ikaw magsimula ay pangkalahatang isang magandang ideya kaya hindi ka aksidenteng mag-commit ng mga file na hindi mo gusto sa iyong Git na repositoryo. Ang mga patakaran para sa mga palatandaan na maaari mong ilagay sa .gitignore na file ay ang mga sumusunod: Mga blankong linya o mga linya na nagsisimula ng # ay hindi pinansin. Ang standard glob na mga palatandaan na trabaho, at ilalapad ng maraming beses sa kabuuan na tinatrabahong tree. Maaari mong simulan ang mga palatandaan na may pasulong na slash ( / ) upang iwasan ang maraming beses. Maaari mong tapusin ang mga palatandaan na may pasulong na slash ( / ) upang tukuyin ang isang direktoryo. Maaari mong kontrahin ang isang palatandaan sa pagsisimula nito ng may tandang padamdam ( ! ). Ang Glob na mga palatandaan ay katulad ng pinasimpleng regular na mga expression na ginagamitan ng mga shell. Isang asterisk ( * ) ay tumutugma sa zero o higit pa na mga karakter; [abc] ay tumugma sa anumang karakter sa loob ng mga bracket (sa kasong ito a, b, o c); isang tanong na marka ( ? ) na tumutugma ng isang solo na karakter; at mga bracket na naglalakip ng mga karakter na pinaghiwalay ng isang hyphen ( [0-9] ) na tumutugma sa anumang karakter sa pagitan nila (sa kasong ito 0 hanggang 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. Narito ang isa pang halimbawa sa .gitignore na 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 the build/ directory 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 Ang GitHub ay nagpapanatili ng isang pantay na komprehensibong listahan ng mabuting .gitignore mga halimbawa ng file para sa mga dose-dosenang mga proyekto at mga wika sa https://github.com/github/gitignore kung gusto mo ng panimulang punto para sa iyong proyekto. Sa simpleng kaso, ang repositoryo ay maaaring mayrong isang solong .gitignore na file sa kanyang root na direktoryo, na kung saan ay naaangkop ng maraming beses sa buong repositoryo. Gayunpaman, ito ay posible rin na magkaroon ng karagdagang .gitignore na mga file sa mga subdirectory. Ang mga patakaran sa mga nested na to ay .gitignore na mga file na nasa ilalim ng direktoryo kung saan matatagpuan ang mga ito. (Ang Linux kernel na pinagmulan na repositoryo ay may 206 na .gitignore na mga file.) Ito ay lampas sa lawak sa librong ito para makuha ng mga detalye ng maramihang .gitignore na mga file; tingnan ang man gitignore para sa karagdagang mga detalye. Pagtingin sa iyong itinanghal at hindi itinanghal na mga pagbabago Kung ang git status na utos ay masyadong malabo para sa iyo — kung gusto mong malaman ang eksakto kung ano ang iyong binago, hindi lamang kung aling mga file — maaari mong gamitin ang git diff na utos. Talakayin natin ang git diff sa mas detalyado mamaya, ngunit malamang ikaw ay gagamit nito ng mas madalas para sagutin ang dalawang tanong na ito: Ano ang iyong nabago pero hindi pa natanghal? At ano ang iyong itinanghal na iyong i-commit pa? Kahit na ang git status ay sasagot sa mga tanong na iyon ng pangkalahatan sa pamamagitan ng paglista ng mga pangalan ng file, ang git diff ay nagpapakita sa iyo ng eksaktong mga linya na idinagdag at inalis — ang patch, na tulad nito. Let’s say you edit and stage the README file again and then edit the CONTRIBUTING.md file without staging it. Kung pinatakbo mo ang iyong git status na utos, makikita mo ulit ang isang bagay na tulad nito: $ 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 tingnan ang iyong binago pero hindi pa naitanghal, i-type ang git diff na walang ibang mga 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 Ang utos na iyon ay inihahambing kung ano ang nasa iyong tinatrabahong direktoryo at kung ano ang nasa iyong itinanghal na lugar. Ang resulta ay nagsasabi sa iyo na ikaw ay nakagawa sa hindi mo pa naitanghal. Kung gusto mong tingnan ang hindi mo pa naitanghal na mapupunta sa iyong susunod na commit, maaari mong gamitin ang git diff --staged . Ang utos na ito ay naghahambing sa iyong itinanghal na pagbabago sa iyong huling 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 Ito ay importanteng tandaan na ang git diff na sa sarili niya ay hindi nagpapakita ng lahat ng mga pagbabago na iyong nagawa sa huli mong commit — mga pagbabago lamang na hindi pa rin naitanghal. Kung iyong natanghal ang lahat ng iyong mga binago, ang git diff ay magbibigay sayo nang walang output. Para sa isa pang halimbawa, kung ikaw ay nagtanghal sa CONTRIBUTING.md na file at pagkatapos ay na-edit ito, maaari mong gamitin ang git diff para tingnan ang mga pagbabago sa file na naitanghal at ang mga pagbabago na hindi pa naitanghal. 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 Ngayon ay maaari mo nang gamitin ang git diff para tingnan kung ano pa ang hindi naitanghal: $ 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 at ang git diff --cached para tingnan kung ano ang iyong naitanghal sa ngayon ( --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 Example 1. Ang Git Diff ay isang Panlabas na Kasangkapan Patuloy tayong gagamit ng git diff na utos sa iba’t ibang paraan sa buong pahina ng aklat. May isa pang paraan para tingnan ang mga diffs na ito na kung ikaw ay mas gusto ang isang graphical o panlabas na diff sa halip na pagtingin sa programa. Kung ikaw ay nagpatakbo ng git difftool sa halip na git diff , makikita mo ang anuman sa mga diffs na ito sa software na tulad ng emerge, vimdiff at marami pang iba (kabilang ang komersyal na mga produkto). Patakbuhin ang git difftool --tool-help para tingnan kung ano ang magagamit para sa iyong sistema. Pag-commit ng iyong mga Binago Ngayon na ang iyong itinanghal na lugar ay nai-setup ayon sa gusto mo, maaari mong i-commit ang iyong mga binago. Tandaan na anuman na hindi pa rin naitanghal — ang anumang mga file na iyong nalikha o nabago na hindi mo pa napatakbo ang git add mula nong iyong na-edit mo sila — hindi ka mapupunta sa pag-commit. Mananatili sila bilang nabago na mga file sa iyong disk. Sa kasong ito, sabihin natin na sa iyong huling beses na iyong pinatakbo ang git status , makikita mo lahat na iyong naitanghal, kaya handa kana i-commit ang iyong mga binago. Ang pinakasimpleng paraan para ma-commit ay mag-type ng git commit : $ git commit Ang paggawa nito ay naglulunsad ng iyong editor na napili. (Ito ay nag-set ng iyong shell ng EDITOR na environment variable — kadalasan ay vim o emacs, bagaman maaari mong i-configure ito kung ano ang gusto sa paggamit ng git config --global core.editor na utos tulad na iyong nakita sa Pagsisimula ). Ang editor ay nagpapakita ng mga sumusunod na teksto(halimbawa nito ay ang Vim na 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 Nakikita mo na ang default na mensahe ng commit ay naglalaman ng pinakabagong output sa git status na utos na nagkomento at isang walang laman na linya sa itaas. Maaari mong alisin ang mga komento na ito at i-type ang iyong mensahe ng commit, o maaari mong iwan ang mga ito doon upang makatulong sayo na tandaan ang iyong mga nai-commit. (Para sa isang mas tahasang paalala kung ano ang iyong nabago, maaari mong ipasa ang -v na opsyon sa git commit . Ang paggawa nito ay naglalagay din ng diff sa iyong nabago sa editor kaya maaari mong tingnan ang eksakto kung ano ang iyong nai-commit.) Kapag lumabas ka sa editor, Ang Git ay lumilikha ng iyong commit na may mensahe sa commit (sa mga komento at diff na nakuha). Bilang alternatibo, maaari mong i-type ang iyong mensahe sa commit na nasa linya ng commit na utos sa pamamagitan ng pagtukoy nito pagkatapos ng isang -m na flag, tulad nito: $ 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 Nalikha mo na ngayon ang iyong unang commit! Maaari mong makita ang commit ay nagbigay sa iyo ng ilang output tungkol sa sarili nito: kung anong branch ang iyong na-commit sa ( master ), kung ano ang SHA-1 checksum na commit na meron ( 463dc4f ), kung gaano karami ang mga file na nabago, at istatistika tungkol sa mga linya na naidagdag at inalis sa commit. Tandaan na ang commit ay nagtatala ng snapshot na iyong nai-setup sa iyong itinanghal na lugar. Anuman ang hindi mo naitanghal ay nakaupo pa rin doon na nabago; maaari mong gawin ang isa pang commit para madagdag sa iyong kasaysayan. Sa bawat oras na magsagawa ka ng commit, Nagtatala ka ng isang snapshot sa iyong proyekto na pwede mong ibalik sa o ihambing sa ibang pagkakataon. Paglaktaw sa Staging Area Kahit na ito ay maaaring nakamamanghang kapaki-pakinabang para sa paglikha ng mga commit na eksakto sa kung ano ang gusto mo sa kanila, ang staging na lawak ay paminsan-minsan isang kaunting kumplikado kaysa sa kailangan mo sa iyong workflow. Kung gusto mong laktawan ang staging na lawak, ang Git ay nagbibigay na isang simpleng daang tuwiran. Pagdaragdag ng -a na opsyon sa git commit na utos ay awtomatikong ginagawa ng Git ang pag-stage sa bawat file na nasubaybayan na bago ginagawa ang pag-commit, na hinahayaan ka na maglaktaw sa git add na parte: $ 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(-) Pansinin kung paano hindi ka kailangan na magpatakbo ng git add sa CONTRIBUTING.md na file sa kasong ito bago ka mag-commit. Iyan ay dahil ang -a na flag ay nagsasama ng lahat na nabago na mga file. Ito ay maginhawa, ngunit mag-ingat; kung minsan ang flag na ito ay magdudulot sa iyo ng pagsasama ng hindi inaasahang mga pagbabago. Pag-alis ng mga File Para mag-alis ng isang file mula sa Git, kailangan mong alisin ito mula sa iyong nasubaybayan na mga file (mas tama, tanggalin ito mula sa iyong staging na lawak) at pagkatapos i-commit. Ang git rm na utos ay ginagawa yan, at inaalis din ang file mula sa iyong tinatrabahong direktoryo para hindi mo makikita ito bilang hindi nasubaybayan na file sa susunod. Kung alisin mo lamang ang file mula sa iyong tinatrabahong direktoryo, nagpapakita ito sa ilalim ng “Ang mga pagbabago ay hindi na-stage para i-commit” (yan ay, unstaged ) lawak ng iyong git status na 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") Pagkatapos, kung ikaw ay nagpatakbo ng git rm , ito ay magsi-stage sa pag-alis ng file: $ 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 Sa susunod na ikaw ay mag-commit, ang file ay mawawala at hindi na masubaybayan. Kung ikaw ay nakapagbago ng isang file at idinagdag na ito sa staging na lawak, dapat mong pilitin ang pagtanggal kasama ang -f na opsyon. Ito ay isang tampok na kaligtasan para maiwasan ang aksidenteng pag-alis ng datos na hindi pa naitala sa isang snapshot at hindi na ito makuha muli mula sa Git. Isa pang kapaki-pakinabang na bagay na gusto mong gawin ay ang pagpanatili ng file sa iyong tinatrabahong tree ngunit alisin ito mula sa iyong staging na lawak. Sa ibang salita, baka gusto mong panatilihin ang file sa iyong hard drive ngunit walang Git na nagsubaybay nito ngayon. Ito ay partikular na magagamit kung ikaw ay nakalimot na magdagdag na kung ano sa iyong .gitignore na file at aksidenteng na-staged ito, tulad ng isang malaking log file o isang bugkos ng .a na naipon na mga file. Para gawin ito, gamitin ang --cached na opsyon: $ git rm --cached README Maaari mong ipasa ang mga file, mga direktoryo, at ang file-glob na mga palatandaan sa git rm na utos. Ibig sabihin na maaari kang gumawa ng mga bagay na tulad nito: $ git rm log/\*.log Tandaan ang backslash ( \ ) na nasa harap sa * . Ito ay kinakailangan dahil ang Git ay gagawang kanyang sariling filename na pagpapalawak bilang karagdagan sa iyong filename expansion sa shell. This command removes all files that have the .log extension in the log/ directory. O, maaari kang gumawa ng isang bagay na tulad nito: $ git rm \*~ Ang utos na ito ay nag-aalis ng lahat ng mga file na ang mga pangalan ay nagtatapos nang may ~ . Paggalaw ng mga File Hindi tulad ng maraming iba pang mga sistema ng VCS, ang Git ay hindi malinaw na nagsubaybay ng pagkilos ng file. Kung ikaw ay nagpalit ng pangalan sa Git, walang metadata ay naka-imbak sa Git na nagsasabi na iyong pinalitan ang pangalan ng file. Gayunpaman, ang Git ay medyo matalino sa pag-uunawa na pagkatapos ng katotohanan — haharapin natin ang pag-detect sa paggalaw ng file isang saglit. Kaya naman ito ay medyo nakakalito na ang Git ay may mv na utos. Kung gusto mong palitan ng pangalan ang isang file sa Git, maaari kang magpatakbo ng isang bagay na tulad nito: $ git mv file_from file_to at ito ay gumagana nang maayos. Sa katunayan, kung ikaw ay magpatakbo ng isang bagay na tulad nito at tumingin sa katayuan, iyong makikita na ang Git ay isinaalang-alang ang pagbago ng panglan ng 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 Gayunpaman, ito ay katumbas sa pagpapatakbo ng isang bagay na tulad nito: $ mv README.md README $ git rm README.md $ git add README Ang Git ay nakatukoy na ito ay isang pagpapahiwatig ng pagpalit ng pangalan, kaya hindi mahalaga na kung ikaw ay nakapalit ng pangalan sa file sa ganun na paraan o kasama ang mv na utos. Ang tanging tunay na kaibahan ay ang git mv ay isang utos sa halip na tatlo — ito ay isang kaginhawaang function. Higit na mahalaga, maaari kang gumamit ng anumang kasangkapan na gusto mo upang magpalit na pangalan sa isang file, at maipasa sa add/rm mamaya, bago ka mag-commit. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://www.linkedin.com/products/toon-boom-animation-inc-producer/?trk=products_seo_search | Producer | LinkedIn Skip to main content LinkedIn Toon Boom Animation 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 Producer Product Management Software by Toon Boom Animation See who's skilled in this Add as skill Contact us Report this product About Producer 20 provides real-time access to the progress of your animated features and series, making it easier to manage global production processes. Track tasks, assets, scenes, production progress, team management, efficiencies across departments, reporting and more. Plus, Producer seamlessly integrates with the software your team needs to get the job done including Storyboard Pro and Harmony. This product is intended for Technical Director Animation Director Media Products media viewer No more previous content Introducing Toon Boom Producer 20 With increasing global demand for original animated content, and productions being produced from different sites worldwide with more and more work from home, there is a growing need for tools that ensure efficient production development. Studios everywhere have relied on spreadsheets and DIY solutions to help keep teams aligned, and move productions forward along timelines and within budgets. Toon Boom Producer 20: 40-Minute Walkthrough Producer 20 provides real-time access to the progress of your animated features and series, making it easier to manage global production processes. Track tasks, assets, scenes, production progress, team management, efficiencies across departments, reporting and more. Plus, Producer seamlessly integrates with the software your team needs to get the job done including Storyboard Pro and Harmony. Brice Poisson and Mehma Sachdeva on using Toon Boom Producer MINTE is a leading creative studio based out of India, which provides preproduction and 2D animation service work for clients worldwide since September 2014. We interviewed Brice Poisson (CEO) and Mehma Sachdeva (Production Head) to learn how MINTE used Toon Boom Producer to manage their studio's production tasks. No more next content Similar products Productboard Productboard Product Management Software Aha! Academy Aha! Academy Product Management Software Product Portfolio Management Product Portfolio Management Product Management Software Dovetail Dovetail Product Management Software Interim Product Managers Interim Product Managers Product Management Software Aha! Discovery Aha! Discovery Product Management Software Sign in to see more Show more Show less Toon Boom Animation products Harmony Harmony Animation Software Storyboard Pro Storyboard Pro Animation Software 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:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_NI | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English (United States)) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 P | 2026-01-13T09:29:23 |
https://git-scm.com/book/id/v2/Git-Basics-Alias-Git | Git - 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. Memulai 1.1 Tentang Version Control 1.2 Sejarah Singkat Git 1.3 Dasar-dasar Git 1.4 Command Line 1.5 Memasang Git 1.6 Pengaturan Awal Git 1.7 Mendapatkan Bantuan 1.8 Kesimpulan 2. Git Basics 2.1 Mendapatkan Repository Git 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Alias Git 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git di Server 4.1 Protokol 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Ringkasan 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pengaturan dan Konfigurasi Akun 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Mengelola Organization 6.5 Scripting GitHub 6.6 Ringkasan 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Kostumisasi Git 8.1 Konfigurasi Git 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Ringkasan 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.7 Git Basics - Alias Git Alias Git Sebelum kita menyelesaikan bab tentang Git dasar ini, hanya ada satu tip kecil yang bisa membuat pengalaman Git Anda lebih sederhana, mudah, dan lebih familiar: alias. Kami tidak akan merujuk atau menganggap Anda telah menggunakannya di buku ini, tetapi Anda mungkin harus tahu cara menggunakannya. Git tidak secara otomatis menyimpulkan command Anda jika Anda mengetikkannya secara parsial. Jika Anda tidak ingin mengetik seluruh teks dari masing-masing command Git, Anda dapat dengan mudah membuat sebuah alias untuk setiap command menggunakan git config . Berikut adalah beberapa contoh yang mungkin ingin Anda siapkan: $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status Ini berarti, misalnya, sebagai ganti mengetik git commit , Anda hanya perlu mengetikkan git ci . Saat Anda terus menggunakan Git, Anda mungkin juga sering menggunakan command lain; jangan ragu untuk membuat alias baru. Teknik ini juga sangat berguna dalam membuat command yang menurut Anda harus ada. Misalnya, untuk memperbaiki masalah kegunaan yang Anda hadapi saat melakukan unstaging sebuah file, Anda dapat menambahkan alias unstage Anda sendiri ke Git: $ git config --global alias.unstage 'reset HEAD --' Ini akan membuat dua command yang setara dengan: $ git unstage fileA $ git reset HEAD fileA Hal ini tampaknya sedikit lebih jelas. Secara umum juga bisa dengan menambahkan command last , seperti ini: $ git config --global alias.last 'log -1 HEAD' Dengan cara ini, Anda bisa melihat commit terakhir dengan mudah: $ 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> Seperti yang Anda tahu, Git hanya mengganti command baru dengan alias apapun yang Anda inginkan. Namun, mungkin Anda ingin menjalankan command eksternal, bukan sub command Git. Dalam hal ini, Anda memulai command dengan karakter ! . Ini berguna jika Anda menulis alat Anda sendiri yang bekerja dengan repository Git. Kita bisa menunjukkan dengan alias git visual untuk menjalankan gitk : $ git config --global alias.visual "!gitk" prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:23 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#content-area | 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:23 |
https://git-scm.com/book/it/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. 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 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. . Figura 110. The “Your repositories” area. Figura 111. The “New repository” dropdown. This takes you to the “new repository” form: Figura 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. Nota 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. Figura 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. Figura 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. . Figura 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. Figura 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. Figura 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. Figura 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. Figura 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. Figura 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. Figura 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. . Figura 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 notification 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. Figura 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. Figura 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. Figura 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:23 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=en | 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-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 6.6 GitHub - Buod Buod Isa ka na ngayong GitHub user. Alam mo kung paano lumikha ng isang account, mamahala ng isang organisasyon, gumawa at mag-push sa mga repositoryo, mag-ambag sa mga proyekto ng ibang tao at tumanggap ng mga kontribusyon mula sa iba. Sa susunod na kabanata, matututo ka ng mas makapangyarihang mga gamit at mga tip para sa pakikitungo sa mga kumplikadong sitwasyon, kung saan tunay kang gagawin na isang master ng 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://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=lt | 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/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://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#param-num-of-posts-1 | 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/it/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. 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 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. Figura 49. The GitWeb web-based user interface. If you want to check out what GitWeb would look like for your project, Git comes with a command to fire up a temporary instance if you have a lightweight server on your system like lighttpd or webrick . On Linux machines, lighttpd is often installed, so you may be able to get it to run by typing git instaweb in your project directory. If you’re running a Mac, Leopard comes preinstalled with Ruby, so webrick may be your best bet. To start instaweb with a non-lighttpd handler, you can run it with the --httpd option. $ git instaweb --httpd=webrick [2009-02-21 10:02:21] INFO WEBrick 1.3.1 [2009-02-21 10:02:21] INFO ruby 1.8.6 (2008-03-03) [universal-darwin9.0] That starts up an HTTPD server on port 1234 and then automatically starts a web browser that opens on that page. It’s pretty easy on your part. When you’re done and want to shut down the server, you can run the same command with the --stop option: $ git instaweb --httpd=webrick --stop If you want to run the web interface on a server all the time for your team or for an open source project you’re hosting, you’ll need to set up the CGI script to be served by your normal web server. Some Linux distributions have a gitweb package that you may be able to install via apt or yum , so you may want to try that first. We’ll walk though installing GitWeb manually very quickly. First, you need to get the Git source code, which GitWeb comes with, and generate the custom CGI script: $ git clone git://git.kernel.org/pub/scm/git/git.git $ cd git/ $ make GITWEB_PROJECTROOT="/opt/git" prefix=/usr gitweb SUBDIR gitweb SUBDIR ../ make[2]: `GIT-VERSION-FILE' is up to date. GEN gitweb.cgi GEN static/gitweb.js $ sudo cp -Rf gitweb /var/www/ Notice that you have to tell the command where to find your Git repositories with the GITWEB_PROJECTROOT variable. Now, you need to make Apache use CGI for that script, for which you can add a VirtualHost: <VirtualHost *:80> ServerName gitserver DocumentRoot /var/www/gitweb <Directory /var/www/gitweb> Options ExecCGI +FollowSymLinks +SymLinksIfOwnerMatch AllowOverride All order allow,deny Allow from all AddHandler cgi-script cgi DirectoryIndex gitweb.cgi </Directory> </VirtualHost> Again, GitWeb can be served with any CGI or Perl capable web server; if you prefer to use something else, it shouldn’t be difficult to set up. At this point, you should be able to visit http://gitserver/ to view your repositories online. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:24 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#collect-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:24 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#collect-by-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://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#param-end-date-1 | 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 |
http://dig.ccmixter.org/free | Free for Commercial Use Toggle navigation donate to keep this library available! licenses tag search featured music for film music for games free for commercial use royalty free licensed 1 - 40 of 4,483 display 10 20 40 Free for Commercial Use Our artists count on you returning their generosity. It Really Helps when you filters × all licenses free for commercial use royalty free ccPlus license all time magic sort recent latest instrumental only reset filters Elephant in the room J.Lang Tags: drums , bass , instrumental , experimental , hip_hop , loops , remix , CBR I J U S T W A N N A SO SHA Tags: alternative , music_for_film , guitar , drums , female_vocals , electronic , synthesizer , piano , spoken_word , remix , ccplus Kung-Fu Glitch cdk Tags: experimental , chill , remix , CBR Conflict Opposition (deeplastik remix) Deeplastik Tags: electronic , remix The Stubble Field Break (Mana Mixed) Mana Junkie Tags: loops , downtempo , remix pushoutfromyourshore martinsea Tags: remix Pour des Chemins Facil (Small Mountain Remix) Ben Blohowiak Tags: reggaelike , reggaestyle , reggae , chansons , male_vocals , drums , bass , electronic , remix Gurd to Nark Returns Colin Mutchler Tags: remix , CBR phoenix urmymuse Tags: spoken_word , music_for_film , remix , guitars , are , the Tracing My Steps Stefan Kartenberg Tags: folk , remix , VBR It's Deep SackJo22 Tags: female_vocals , guitar , harmonies , remix , ccplus Dada Da Doom spinningmerkaba Tags: remix , a , Berlin , underground , bar , pulled You and I Admiral Bob Tags: chill , mellow , remix , ccplus bsides airtone Tags: chill , hip_hop , remix , in_web , CBR roboduck airtone Tags: chill , ambient , music_for_film , electronic , remix , mixup Dove SackJo22 Tags: ambient , jazz , spoken_word , poem , bass , downtempo , remix , mixup Chill, Relax coruscate Tags: downtempo , ambient , funky , music_for_film , trip_hop , remix , ccplus_stem , ccplus , CBR spacedust airtone Tags: acoustic , music_for_film , music_for_video , music_for_games , remix , mixup , ccplus_stem bluenotes airtone Tags: guitar , instrumental , bass , piano , jazz , music_for_film , music_for_video , remix , pell Tribute to Tobias Weber Stefan Kartenberg Tags: remix , (tobias_weber) , ballad , for , the , soul. , Hear blackSnow airtone Tags: music_for_film , music_for_video , remix , mixup , yin_of_yang Traveling Lights Zep Hurme Tags: female_vocals , drums , guitar , bass , remix , up , the , volume! , Zep Strong Man Zep Hurme Tags: remix , the , chart , pro , production , with , a , pulse , and Cyan Granite 7OOP3D Tags: synthesizer , electronic , guitar , male_vocals , remix , CBR Dirtbag Hans Atom Tags: retro , synth_pop , hymn , soft_pop , lofi , remix , CBR From Gurd To Nark Siobhan Dakay Tags: ambient , rising , experimental , electronic , remix , mixup , VBR Where the Moon Shines Bright Kara Square Tags: female_vocals , acoustic , folk , singer_songwriter , woodstock , moon , stars , uplifting , positive , remix , mixup , firefly sleepwalking airtone Tags: ambient , music_for_film , electronic , synthesizer , experimental , remix , ccplus_stem , ccplus , CBR Yesterdays Blues Radioontheshelf Tags: male_vocals , remix , mixup , magic_hours , Yesterday , & , The The night is calling Kraftamt Tags: music_for_film , instrumental , electronic , synthesizer , loops , ambient , electro , remix , mixup , come_together En Shenandoah Down With Ben Tags: remix , mixup , come_together , CBR , archive , With 0450am airtone Tags: chill , lofi , music_for_film , music_for_video , music_for_games , ambient , remix , CBR All along Hans Atom Tags: retro , synth_pop , lofi , operatic_synth_pop , remix , CBR , archive , and Come Inside, the Imagination is Shining Kirkoid Tags: loops , remix , CBR diffusion airtone Tags: music_for_film , ambient , chill , remix , pell Je ne peux pas le retenir Bluemillenium Tags: bass , clavinet , drums , female_vocals , funk , funky , guitar , infunktion , male_vocals , rhodes , r_n_b , remix , mixup We, the People Mr_Yesterday Tags: midi , cello , remix , mixup , firefly , CBR Wanderer (Take 2) Admiral Bob Tags: funk , jam , funky , guitar , electric , electric_guitar , telecaster , bass , rhodes , electric_piano , remix , mixup , firefly Soul Searching Jeris Tags: rhodes , male_vocals , guitar , remix , mixup , firefly , VBR Off-Grid Dreams Calling Sister Midnight Tags: remix , mixup Here Licenses Privacy Terms Donate(!) Credits There Everywhere Twitter YouTube Vimeo Facebook Instagram Resources GitHub Query API Forums Contact | 2026-01-13T09:29:24 |
https://git-scm.com/book/it/v2/Git-Basics-Git-Aliases | Git - Git Aliases About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Per Iniziare 1.1 Il Controllo di Versione 1.2 Una Breve Storia di Git 1.3 Cos’é Git? 1.4 La riga di comando 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Chiedere aiuto 1.8 Sommario 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Sommario 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendice A: Git in altri contesti A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Riassunto A2. Appendice B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendice C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.7 Git Basics - Git Aliases Git Aliases Before we finish this chapter on basic Git, there’s just one little tip that can make your Git experience simpler, easier, and more familiar: aliases. We won’t refer to them or assume you’ve used them later in the book, but you should probably know how to use them. Git doesn’t automatically infer your command if you type it in partially. If you don’t want to type the entire text of each of the Git commands, you can easily set up an alias for each command using git config . Here are a couple of examples you may want to set up: $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status This means that, for example, instead of typing git commit , you just need to type git ci . As you go on using Git, you’ll probably use other commands frequently as well; don’t hesitate to create new aliases. This technique can also be very useful in creating commands that you think should exist. For example, to correct the usability problem you encountered with unstaging a file, you can add your own unstage alias to Git: $ git config --global alias.unstage 'reset HEAD --' This makes the following two commands equivalent: $ git unstage fileA $ git reset HEAD fileA This seems a bit clearer. It’s also common to add a last command, like this: $ git config --global alias.last 'log -1 HEAD' This way, you can see the last commit easily: $ 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> As you can tell, Git simply replaces the new command with whatever you alias it for. However, maybe you want to run an external command, rather than a Git subcommand. In that case, you start the command with a ! character. This is useful if you write your own tools that work with a Git repository. We can demonstrate by aliasing git visual to run 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://www.linkedin.com/uas/login?session_redirect=%2Fproducts%2Feasi-spoom&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: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-%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 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:24 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#posts-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://www.linkedin.com/uas/login?session_redirect=%2Fservices%2Fproducts%2Feasi-spoom%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:24 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_PR | 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://www.linkedin.com/products/easi-spoom/?trk=products_seo_search#main-content | Spoom | LinkedIn Skip to main content LinkedIn Easi 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 Spoom Strategic Planning Software by Easi See who's skilled in this Add as skill Learn more Report this product About From now on, follow only the KPIs that really matter. Link operations to strategy and bring true business value to those executing the change. Using clear cascading strategy maps, you ensure that silos are broken and that initiatives, KPIs and related data can be linked across departments. Move from isolated business intelligence initiatives to motivated teams driven by strategy. Spoom gives you the bigger picture allowing you to spot opportunities, to minimize risks and act proactively on your strategic course. This product is intended for Chief Executive Officer Chief Financial Officer Chief Operating Officer Marketing Director Chief Information Officer Sales Manager Manager Team Lead Project Manager Human Resources Manager Media Products media viewer No more previous content Spoom - Aligns vision, data & teams - Strategy Execution Software Spoom's Strategy Map for cascading impacts Balanced Scorecard - manage and steer your team Track KPIs, Milestones, OKRs from any data source following your needs Transparency is key in strategy execution & planning 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 Easi products Adfinity Adfinity Enterprise Accounting Software 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:24 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#param-url-5 | 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://www.linkedin.com/products/easi-spoom?similarProducts=true&trk=products_details_guest_similar_products_section_sign_in | Spoom | LinkedIn Skip to main content LinkedIn Easi 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 Spoom Strategic Planning Software by Easi See who's skilled in this Add as skill Learn more Report this product About From now on, follow only the KPIs that really matter. Link operations to strategy and bring true business value to those executing the change. Using clear cascading strategy maps, you ensure that silos are broken and that initiatives, KPIs and related data can be linked across departments. Move from isolated business intelligence initiatives to motivated teams driven by strategy. Spoom gives you the bigger picture allowing you to spot opportunities, to minimize risks and act proactively on your strategic course. This product is intended for Chief Executive Officer Chief Financial Officer Chief Operating Officer Marketing Director Chief Information Officer Sales Manager Manager Team Lead Project Manager Human Resources Manager Media Products media viewer No more previous content Spoom - Aligns vision, data & teams - Strategy Execution Software Spoom's Strategy Map for cascading impacts Balanced Scorecard - manage and steer your team Track KPIs, Milestones, OKRs from any data source following your needs Transparency is key in strategy execution & planning 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 Easi products Adfinity Adfinity Enterprise Accounting Software 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:24 |
http://dig.ccmixter.org/film | Instrumental Music for Film and Video Toggle navigation donate to keep this library available! licenses tag search featured music for film music for games free for commercial use royalty free licensed 1 - 40 of 1,481 display 10 20 40 Instrumental Music for Film and Video Our artists count on you returning their generosity. It Really Helps when you filters × all licenses free for commercial use royalty free ccPlus license all time magic sort recent latest instrumental only reset filters ECHO Ant.Survila Tags: instrumental , drums , electronic , synthesizer , loops , remix , non_commercial , CBR Javomatics Martijn de Boer (NiGiD) Tags: bass , drums , funk , funky , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , uptempo , remix , ccplus February (Halfway There Remix) Ben Blohowiak Tags: rock , alternative , music_for_film , instrumental , guitar , drums , bass , electronic , synthesizer , remix , non_commercial Gramophone Of Lament coruscate Tags: alternative , music_for_film , instrumental , hip_hop , downtempo , ambient , funky , remix , ccplus_stem , ccplus Je suis un Phoenix Bluemillenium Tags: electronic , bass , synthesizer , experimental , ambient , remix , CBR Lesser Tact Improvisation Martijn de Boer (NiGiD) Tags: bass , fretless , folk , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , moody , melancholical , melancholic , duo Falling Season Fresh_Morning_Duet Tags: electronic , instrumental , guitar , synthesizer , remix , Blohowiak , Fresh , Morning Reconstruct Darkroom Tags: drums , synthesizer , chill , remix , ccplus_stem , CBR The Fade Out coruscate Tags: alternative , electronic , synthesizer , experimental , chill , hip_hop , downtempo , spoken_word , electro , funky , music_for_film , jazz , remix Sixeight 06 (6806 Remix) Ben Blohowiak Tags: electronic , glitch , drums , bass , synthesizer , instrumental , experimental , piano , music_for_film , techno , remix , non_commercial SONIC DIVE Ant.Survila Tags: instrumental , drums , bass , electronic , synthesizer , loops , piano , remix , nc_sampling_plus Strange Sam Martijn de Boer (NiGiD) Tags: bass , fretless , folk , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , moody , melancholical , melancholic , duo Imaginary Lunch Martijn de Boer (NiGiD) Tags: bass , fretless , jazz , jazzy , music_for_video , music_for_film , background_music , uptempo , instrumental , blues , bluesy , remix reImaginedInstrumental airtone Tags: guitar , synthesizer , electronic , piano , music_for_film , remix , CBR Stormcreeper (regains her spirit Remix) Ben Blohowiak Tags: downtempo , chill , guitar , synthesizer , experimental , instrumental , piano , ambient , remix , CBR bittersweet MalreDeszik Tags: rock , music_for_film , remix , CBR , CBR Chillermore Groove Martijn de Boer (NiGiD) Tags: bass , fretless , folk , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , moody , melancholical , melancholic , duo , duet Improspective Shades Martijn de Boer (NiGiD) Tags: bass , synthesizer , drums , funk , funky , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , moody , melancholical Free Mister Rabbit Martijn de Boer (NiGiD) Tags: bass , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , blues , remix Peace, Love & Unity Bocrew Tags: experimental , instrumental , synthesizer , music_for_film , bocrew , ambient , remix , Calling , Sister , Midnight Magic of Cymbals (Sigil Remix) Ben Blohowiak Tags: electronic , rock , alternative , drums , bass , synthesizer , experimental , piano , funky , remix , CBR TreeTones J.Lang Tags: instrumental , bass , loops , remix Bunkers Blues Martijn de Boer (NiGiD) Tags: bass , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , blues , remix , ccplus Untamed and Unanswered Martijn de Boer (NiGiD) Tags: bass , fretless , folk , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , moody , melancholical , melancholic , vibraphone , strings The Big Squeezer Martijn de Boer (NiGiD) Tags: bass , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , moody , melancholical , melancholic , joy , latin , bossa_nova , duo It Was (ReUp) Bocrew Tags: experimental , instrumental , synthesizer , music_for_film , bocrew , ambient , radio refractions airtone Tags: synthesizer , chill , music_for_film , remix Faithful Acting Martijn de Boer (NiGiD) Tags: bass , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , moody , melancholical , melancholic , remix , ccplus K36 graffiti Crew Bocrew Tags: experimental , chill , instrumental , ambient , remix , Siroko Stimulation Games Martijn de Boer (NiGiD) Tags: bass , fretless , folk , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , moody , melancholical , melancholic , duo When Things Were Love Martijn de Boer (NiGiD) Tags: bass , fretless , folk , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , moody , melancholical , melancholic , duo Baby Stops Martijn de Boer (NiGiD) Tags: bass , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , moody , melancholical , melancholic , joy , duo , remix Redwater Groove Martijn de Boer (NiGiD) Tags: bass , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , moody , melancholical , melancholic , joy , duo , remix Always Say Never Martijn de Boer (NiGiD) Tags: bass , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , duet , duo , blues , moody , melancholy , noir , game_music Nostalgic Reflections Ant.Survila Tags: instrumental , chill , loops , piano , ambient , remix , non_commercial , CBR , archive , zip Improspective Shades Martijn de Boer (NiGiD) Tags: bass , synthesizer , drums , funk , funky , jazz , jazzy , lounge , improvisation , music_for_video , music_for_film , background_music , downtempo , instrumental , moody , melancholical soulcraft airtone Tags: chill , acoustic , remix , ccplus_stem , ccplus , non_commercial , CBR Here's Your Chance (ReWorked) * J.Lang Tags: bass , electronic , instrumental , chill , hip_hop , loops , piano , downtempo , remix DEEP SEA ADVENTURE Ant.Survila Tags: instrumental , piano , loops , remix , non_commercial , soundtrack Changey - changed Beluga Ten Tags: chill , music_for_film , rock , guitar , drums , downtempo , ambient , multiple_formats , laid_back , casual , atmospheric , remix Here Licenses Privacy Terms Donate(!) Credits There Everywhere Twitter YouTube Vimeo Facebook Instagram Resources GitHub Query API Forums Contact | 2026-01-13T09:29:24 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=ko | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Pla | 2026-01-13T09:29:24 |
https://git-scm.com/book/es/v2/GitHub-Mantenimiento-de-un-proyecto | Git - Mantenimiento de un proyecto 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 6.3 GitHub - Mantenimiento de un proyecto Mantenimiento de un proyecto Ahora que ya sabes cómo ayudar a un proyecto, veamos el otro lado: cómo puedes crear, administrar y mantener tu propio proyecto. Creación de un repositorio Vamos a crear un nuevo repositorio para compartir nuestro código en él. Comienza pulsando el botón “New repository” en el lado derecho de tu página principal, o bien desde el botón {plus} en la barra de botones cercano a tu nombre de usuario, tal como se ve en Desplegable “New repository”. . Figura 110. La zona “Your repositories”. Figura 111. Desplegable “New repository”. Esto te llevará al formulario para crear un nuevo repositorio: Figura 112. Formulario para crear repositorio. Todo lo que tienes que hacer aquí es darle un nombre al proyecto; el resto de campos es totalmente opcional. Por ahora, pulsa en el botón “Create Repository” y listo: se habrá creado el repositorio en GitHub, con el nombre <usuario>/<proyecto> Dado que no tiene todavía contenido, GitHub te mostrará instrucciones para crear el repositorio Git, o para conectarlo a un proyecto Git existente. No entraremos aquí en esto; si necesitas refrescarlo, revisa el capítulo [ch02-git-basics] . Ahora que el proyecto está alojado en GitHub, puedes dar la URL a cualquiera con quien quieras compartirlo. Cada proyecto en GitHub es accesible mediante HTTPS como https://github.com/<usuario>/<proyecto> , y también con SSH con la dirección git@github.com:<usuario>/<proyecto> . Git puede obtener y enviar cambios en ambas URL, ya que tienen control de acceso basado en las credenciales del usuario. Nota Suele ser preferible compartir la URL de tipo HTTPS de los proyectos públicos, puesto que así el usuario no necesitará una cuenta GitHub para clonar el proyecto. Si das la dirección SSH, los usuarios necesitarán una cuenta GitHub y subir una clave SSH para acceder. Además, la URL HTTPS es exactamente la misma que usamos para ver la página web del proyecto. Añadir colaboradores Si estás trabajando con otras personas y quieres darle acceso de escritura, necesitarás añadirlas como “colaboradores”. Si Ben, Jeff y Louise se crean cuentas en GitHub, y quieres darles acceso de escritura a tu repositorio, los tienes que añadir al proyecto. Al hacerlo le darás permiso de “push”, que significa que tendrán tanto acceso de lectura como de escritura en el proyecto y en el repositorio Git. Figura 113. Enlace a ajustes del repositorio. Selecciona “Collaborators” del menú del lado izquierdo. Simplemente, teclea el usuario en la caja y pulsa en “Add collaborator.” Puedes repetir esto las veces que necesites para dar acceso a otras personas. Recuerda que si el proyecto está en un repositorio privado gratuito, solo podrás dar accesos a tres colaboradores. Si necesitas quitar un acceso, pulsa en la “X” del lado derecho del usuario. Figura 114. Colaboradores del repositorio. Gestión de los Pull Requests Ahora que tienes un proyecto con algo de código, y probablemente algunos colaboradores con acceso de escritura, veamos qué pasa cuando alguien te hace un Pull Request. Los Pull Requests pueden venir de una rama en una bifurcación del repositorio, o pueden venir de una rama del mismo repositorio. La única diferencia es que, en el primer caso procede de gente que no tiene acceso de escritura a tu proyecto y quiere integrar en el tuyo cambios interesantes, mientras que en el segundo caso procede de gente con acceso de escritura al repositorio. En los siguientes ejemplos, supondremos que eres “tonychacon” y has creado un nuevo proyecto para Arduino llamado “fade”. Notificaciones por correo electrónico Cuando alguien realiza un cambio en el código y te crea un Pull Request, debes recibir una notificación por correo electrónico avisándote, con un aspecto similar a Notificación por correo de nuevo Pull Request. . Figura 115. Notificación por correo de nuevo Pull Request. Hay algunas cosas a destacar en este correo. En primer lugar, te dará un pequeño diffstat (es decir, una lista de archivos cambiados y en qué medida). Además, trae un enlace al Pull Request y algunas URL que puedes usar desde la línea de comandos. Si observas la línea que dice git pull <url> patch-1 , es una forma simple de fusionar una rama remota sin tener que añadirla localmente. Lo vimos esto rápidamente en Recuperando ramas remotas . Si lo deseas, puedes crear y cambiar a una rama y luego ejecutar el comando para fusionar los cambios del Pull Request. Las otras URL interesantes son las de .diff y .patch , que como su nombre lo indica, proporcionan “diff unificados” y formatos de parche del Pull Request. Técnicamente, podrías fusionar con algo como: $ curl https://github.com/tonychacon/fade/pull/1.patch | git am Colaboración en el Pull Request Como hemos visto en El Flujo de Trabajo en GitHub , puedes participar en una discusión con la persona que generó el Pull Request. Puedes comentar líneas concretas de código, comentar commits completos o comentar el Pull Request en sí mismo, utilizando donde quieras el formato Markdown. Cada vez que alguien comenta, recibirás nuevas notificaciones por correo, lo que te permite vigilar todo lo que pasa. Cada correo tendrá un enlace a la actividad que ha tenido lugar y, además, puedes responder al comentario simplemente contestando al correo. Figura 116. Las respuestas a correos se incluyen en el hilo de discusión. Una vez que el código está como quieres y deseas fusionarlo, puedes copiar el código y fusionarlo localmente, mediante la sintaxis ya conocida de git pull <url> <branch> , o bien añadiendo el fork como nuevo remoto, bajándotelo y luego fusionándolo. Si la fusión es trivial, también puedes pulsar el botón “Merge” en GitHub. Esto realizará una fusión “sin avance rápido”, creando un commit de fusión incluso si era posible una fusión con avance rápido. Esto significa que cada vez que pulses el botón Merge, se creará un commit de fusión. Como verás en Botón Merge e instrucciones para fusionar manualmente un Pull Request. , GitHub te da toda esta información si pulsas en el enlace de ayuda. Figura 117. Botón Merge e instrucciones para fusionar manualmente un Pull Request. Si decides que no quieres fusionar, también puedes cerrar el Pull Request y la persona que lo creó será notificada. Referencias de Pull Request Si tienes muchos Pull Request y no quieres añadir un montón de remotos o hacer muchos cada vez, hay un pequeño truco que GitHub te permite. Es un poco avanzado y lo veremos en detalle después en Las especificaciones para hacer referencia a… (refspec) , pero puede ser bastante útil. En GitHub tenemos que las ramas de Pull Request son una especie de pseudo-ramas del servidor. De forma predeterminada no las obtendrás cuando hagas un clonado, pero hay una forma algo oscura de acceder a ellos. Para demostrarlo, usaremos un comando de bajo nivel (conocido como de “fontanería”, sabremos más sobre esto en Fontanería y porcelana ) llamado ls-remote . Este comando no se suele usar en el día a día de Git pero es útil para ver las referencias presentes en el servidor. Si ejecutamos este comando sobre el repositorio “blink” que hemos estado usando antes, obtendremos una lista de ramas, etiquetas y otras referencias del repositorio. $ 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 Por supuesto, si estás en tu repositorio y tecleas git ls-remote origin podrás ver algo similar pero para el remoto etiquetado como origin . Si el repositorio está en GitHub y tienes Pull Requests abiertos, tendrás estas referencias con el prefijo refs/pull . Básicamente, son ramas, pero ya que no están bajo refs/heads/ , no las obtendrás normalmente cuando clonas o te bajas el repositorio del servidor, ya que el proceso de obtención las ignora. Hay dos referencias por cada Pull Request, la que termina en /head apunta exactamente al último commit de la rama del Pull Request. Así si alguien abre un Pull Request en el repositorio y su rama se llama bug-fix apuntando al commit a5a775 , en nuestro repositorio no tendremos una rama bug-fix (puesto que está en el fork) pero tendremos el pull/<pr#>/head apuntando a a5a775 . Esto significa que podemos obtener fácilmente cada Pull Request sin tener que añadir un montón de remotos. Ahora puedes obtenerlo directamente. $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD Esto dice a Git, “Conecta al remoto origin y descarga la referencia llamada refs/pull/958/head .” Git obedece y descarga todo lo necesario para construir esa referencia, y deja un puntero al commit que quieres bajo .git/FETCH_HEAD . Puedes realizar operaciones como git merge FETCH_HEAD aunque el mensaje del commit será un poco confuso. Además, si estás revisando un montón de Pull Requests, se convertirá en algo tedioso. Hay también una forma de obtener todos los Pull Requests, y mantenerlos actualizados cada vez que conectas al remoto. Para ello abre el archivo .git/config y busca la línea origin . Será similar a esto: [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* La línea que comienza con fetch = es un “refspec.” Es una forma de mapear nombres del remoto con nombres de tu copia local. Este caso concreto dice a Git, que "las cosas en el remoto bajo refs/heads deben ir en mi repositorio bajo refs/remotes/origin ." Puedes modificar esta sección añadiendo otra refspec: [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* Con esta última línea decimos a Git, “Todas las referencias del tipo refs/pull/123/head deben guardarse localmente como refs/remotes/origin/pr/123 .” Ahora, si guardas el archivo y ejecutas un git fetch tendremos: $ 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 # … Ya tienes todos los Pull Request en local de forma parecida a las ramas; son solo-lectura y se actualizan cada vez que haces un fetch. Pero hace muy fácil probar el código de un Pull Request en local: $ 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' La referencia refs/pull/#/merge de GitHub representa el “commit” que resultaría si pulsamos el botón “merge”. Esto te permite probar la fusión del Pull Request sin llegar a pulsar dicho botón. Pull Requests sobre Pull Requests No solamente se puede abrir Pull Requests en la rama master , también se pueden abrir sobre cualquier rama de la red. De hecho, puedes poner como objetivo otro Pull Request. Si ves que un Pull Request va en la buena dirección y tienes una idea para hacer un cambio que depende de él, o bien no estás seguro de que sea una buena idea, o no tienes acceso de escritura en la rama objetivo, puedes abrir un Pull Request directamente. Cuando vas a abrir el Pull Request, hay una caja en la parte superior de la página que especifica qué rama quieres usar y desde qué rama quieres hacer la petición. Si pulsas el botón “Edit” en el lado derecho de la caja, puedes cambiar no solo las ramas sino también la bifurcación. Figura 118. Cambio manual de la rama o del fork en un pull request. Aquí puedes fácilmente especificar la fusión de tu nueva rama en otro Pull Request o en otrá bifurcación del proyecto. Menciones y notificaciones GitHub tiene un sistema de notificaciones que resulta útil cuando necesitas pedir ayuda, o necesitas la opinión de otros usuarios o equipos concretos. En cualquier comentario, si comienzas una palabra anteponiendo el carácter @ , intentará auto-completar nombres de usuario de personas que sean colaboradores o responsables en el proyecto. Figura 119. Empieza tecleando @ para mencionar a alguien. También puedes mencionar a un usuario que no esté en la lista desplegable, pero normalmente el autocompletado lo hará más rápido. Una vez que envías un comentario con mención a un usuario, el usuario citado recibirá una notificación. Es decir, es una forma de implicar más gente en una conversación. Esto es muy común en los Pull Requests para invitar a terceros a que participen en la revisión de una incidencia o un Pull Request. Si alguien es mencionado en un Pull Request o incidencia, quedará además “suscrito” y recibirá desde este momento las notificaciones que genere su actividad. Del mismo modo, el usuario que crea la incidencia o el Pull Request queda automáticamente “suscrito” para recibir las notificaciones, disponiendo todos de un botón “Unsubscribe” para dejar de recibirlas. Figura 120. Quitar suscripción de un pull request o incidencia. Página de notificaciones Cuando decimos “notificaciones”, nos referimos a una forma por la que GitHub intenta contactar contigo cuando tienen lugar eventos, y éstas pueden ser configuradas de diferentes formas. Si te vas al enlace “Notification center” de la página de ajustes, verás las diferentes opciones disponibles. Figura 121. Opciones de Notification center. Para cada tipo, puedes elegir tener notificaciones de “Email” o de “Web”, y puedes elegir tener una de ellas, ambas o ninguna. Notificaciones Web Las notificaciones web se muestran en la página de Github. Si las tienes activas verás un pequeño punto azul sobre el icono de Notificaciones en la parte superior de la pantalla, en Centro de notificaciones. . Figura 122. Centro de notificaciones. Si pulsas en él, verás una lista de todos los elementos sobre los que se te notifica, agrupados por proyecto. Puedes filtrar para un proyecto específico pulsando en su nombre en el lado izquierdo. También puedes reconocer (marcar como leída) una notificación pulsando en el icono de check en una notificación, o reconocerlas todas pulsando en el icono de check de todo el grupo. Hay también un botón “mute” para silenciarlas, que puedes pulsar para no recibir nuevas notificaciones de ese elemento en el futuro. Todas estas características son útiles para manejar un gran número de notificaciones. Muchos usuarios avanzados de GitHub suelen desactivar las notificaciones por correo y manejarlas todas mediante esta pantalla. Notificaciones por correo Las notificaciones por correo electrónico son la otra manera de gestionar notificaciones con GitHub. Si las tienes activas, recibirás los correos de cada notificación. Vimos ya algún ejemplo en Comentarios enviados en notificaciones de correo y Notificación por correo de nuevo Pull Request. . Los correos también serán agrupados correctamente en conversaciones, con lo que estará bien que uses un cliente de correo que maneje las conversaciones. En las cabeceras de estos correos se incluyen también algunos metadatos, que serán útiles para crear filtros y reglas adecuados. Por ejemplo, si miramos las cabeceras de los correos enviados a Tony en el correo visto en Notificación por correo de nuevo Pull Request. , veremos que se envió la siguiente información: 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 Vemos en primer lugar que la información de la cabecera Message-Id nos da los datos que necesitamos para identificar usuario, proyecto y demás en formato <usuario>/<proyecto>/<tipo>/<id> . Si se tratase de una incidencia, la palabra “pull” habría sido reemplazada por “issues”. Las cabeceras List-Post y List-Unsubscribe permiten a clientes de correo capaces de interpretarlas, ayudarnos a solicitar dejar de recibir nuevas notificaciones de ese tema. Esto es similar a pulsar el botón “mute” que vimos en la versión web, o en “Unsubscribe” en la página de la incidencia o el Pull Request. También merece la pena señalar que si tienes activadas las notificaciones tanto en la web como por correo, y marcas como leído el correo en la web también se marcará como leído, siempre que permitas las imágenes en el cliente de correo. Archivos especiales Hay dos archivos especiales que GitHub detecta y maneja si están presentes en el repositorio. README En primer lugar tenemos el archivo README , que puede estar en varios formatos. Puede estar con el nombre README , README.md , README.asciidoc y alguno más. Cuando GitHub detecta su presencia en el proyecto, lo muestra en la página principal, con el renderizado que corresponda a su formato. En muchos casos este archivo se usa para mostrar información relevante a cualquiera que sea nuevo en el proyecto o repositorio. Esto incluye normalmente cosas como: Para qué es el proyecto Cómo se configura y se instala Ejemplo de uso Licencia del código del proyecto Cómo participar en su desarrollo Puesto que GitHub hace un renderizado del archivo, puedes incluir imágenes o enlaces en él para facilitar su comprensión. CONTRIBUTING El otro archivo que GitHub reconoce es CONTRIBUTING . Si tienes un archivo con ese nombre y cualquier extensión, GitHub mostrará algo como Apertura de un Pull Request cuando existe el archivo CONTRIBUTING. cuando se intente abrir un Pull Request. Figura 123. Apertura de un Pull Request cuando existe el archivo CONTRIBUTING. La idea es que indiques cosas a considerar a la hora de recibir un Pull Request. La gente lo debe leer a modo de guía sobre cómo abrir la petición. Administración del proyecto Por lo general, no hay muchas cosas que administrar en un proyecto concreto, pero sí un par de cosas que pueden ser interesantes. Cambiar la rama predeterminada Si usas como rama predeterminada una que no sea “master”, por ejemplo para que sea objetivo de los Pull Requests, puedes cambiarla en las opciones de configuración del repositorio, en donde pone “Options”. Figura 124. Cambio de la rama predeterminada del proyecto. Simplemente cambia la rama predeterminada en la lista desplegable, y ésta será la elegida para la mayoría de las operaciones, así mismo será la que sea visible al principio (“checked-out”) cuando alguien clona el repositorio. Transferencia de un proyecto Si quieres transferir la propiedad de un proyecto a otro usuario u organización en GitHub, hay una opción para ello al final de “Options” llamada “Transfer ownership”. Figura 125. Transferir propiedad de un proyecto. Esto es útil si vas a abandonar el proyecto y quieres que alguien continúe, o bien se ha vuelto muy grande y prefieres que se gestione desde una organización. Esta transferencia, supone un cambio de URL. Para evitar que nadie se pierda, genera una redirección web en la URL antigua. Esta redirección funciona también con las operaciones de clonado o de copia desde 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://git-scm.com/book/ms/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. 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 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. 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 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://www.linkedin.com/products/easi-adfinity/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_image-click | Adfinity | LinkedIn Skip to main content LinkedIn Easi 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 Adfinity Enterprise Accounting Software by Easi See who's skilled in this Add as skill Learn more Report this product About Adfinity (previously named EASI Financials) is an accounting & purchase management software for mid-sized and larger companies. The strong points of Adfinity are the analytical accounting, the paperless aspect, the strong reporting capabilities, and the ease of use. Clients will win time in their daily management & gain competitive advantage thanks to insights into their financial situation. Adfinity will help them to reduce the use of paper to a very strict minimum and digitize and automate a maximum of accounting and financial processes within their company. Adfinity is suited for financial departments in many markets, mainly services, construction, transport, public sector, hospitals & health care & real estate. For the real estate market, we have a specific application called Adfinity Real Estate. Which is Adfinity, completed with a pack of features, tailored specifically to the needs of real estate companies. Media Products media viewer No more previous content Dashboard See all your financial data in our homepage dashboard. Deep dive into the numbers to see what they mean and where they are coming from. Budget control & reporting Gain complete control over expenses and revenue thanks to our budget control feature. Budget preparation Our integrated budget preparation feature helps you save time in preparing the budget. No need to plan meetings and constant back and forward discussions over Excel files - whether they are up-to-date or not-. Adfinity does the job with an integrated module that helps you to plan, prepare and discuss budgets. Digitalized approval cycle With Adfinity, thanks to our thee-way-match feature and OCR, you can digitalize all sorts of flows which need approval. Like purchase and stock management or invoicing approval. OCR Invoice, contracts and documents can be recognized by our OCR system. You just need to scan the papers or upload them digitally, and Adfinity does the rest by filling in the properties in your accounting system with ease. No more next content Featured customers of Adfinity AVA Retail 1,195 followers EAGLESTONE Belgium Real Estate 7,082 followers Batipro Wholesale Building Materials 809 followers Home Invest Belgium Real Estate 5,846 followers Herfurth Group Transportation, Logistics, Supply Chain and Storage 3,673 followers Inclusio SA Real Estate 2,245 followers Keolis Group Ground Passenger Transportation 148,157 followers CENTRE HOSPITALIER CHRETIEN Medical Practices 68 followers Covalux Automotive 1,172 followers epiCura Individual and Family Services 12,916 followers ALINSO GROUP Real Estate 4,103 followers Genista Construction 3,352 followers Befimmo Real Estate 12,631 followers OH Leuven Spectator Sports 7,522 followers RSC Anderlecht Spectator Sports 25,088 followers Dockx Rental Motor Vehicle Manufacturing 1,451 followers Pur Natur nv Dairy Product Manufacturing 914 followers Chaussures Maniet ! Luxus Retail 2,921 followers Dovy Keukens Furniture and Home Furnishings Manufacturing 4,166 followers CM - Christelijke Mutualiteit Hospitals and Health Care 48,545 followers Gezinsbond Public Policy Offices 3,704 followers Show more Show less Similar products PwC Bookkeeping Connect PwC Bookkeeping Connect Enterprise Accounting Software QuickBooks Desktop Enterprise QuickBooks Desktop Enterprise Enterprise Accounting Software Xero Xero Enterprise Accounting Software Odoo Accounting Odoo Accounting Enterprise Accounting Software Workday Financial Management Workday Financial Management Enterprise Accounting Software Foodics Accounting Foodics Accounting Enterprise Accounting Software Sign in to see more Show more Show less Easi products Spoom Spoom Strategic Planning Software 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:24 |
https://docs.brightdata.com/api-reference/web-scraper-api/synchronous-requests#content-area | 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.linkedin.com/products/easi-adfinity/?trk=products_details_guest_other_products_by_org_section_product_link_result-card_full-click | Adfinity | LinkedIn Skip to main content LinkedIn Easi 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 Adfinity Enterprise Accounting Software by Easi See who's skilled in this Add as skill Learn more Report this product About Adfinity (previously named EASI Financials) is an accounting & purchase management software for mid-sized and larger companies. The strong points of Adfinity are the analytical accounting, the paperless aspect, the strong reporting capabilities, and the ease of use. Clients will win time in their daily management & gain competitive advantage thanks to insights into their financial situation. Adfinity will help them to reduce the use of paper to a very strict minimum and digitize and automate a maximum of accounting and financial processes within their company. Adfinity is suited for financial departments in many markets, mainly services, construction, transport, public sector, hospitals & health care & real estate. For the real estate market, we have a specific application called Adfinity Real Estate. Which is Adfinity, completed with a pack of features, tailored specifically to the needs of real estate companies. Media Products media viewer No more previous content Dashboard See all your financial data in our homepage dashboard. Deep dive into the numbers to see what they mean and where they are coming from. Budget control & reporting Gain complete control over expenses and revenue thanks to our budget control feature. Budget preparation Our integrated budget preparation feature helps you save time in preparing the budget. No need to plan meetings and constant back and forward discussions over Excel files - whether they are up-to-date or not-. Adfinity does the job with an integrated module that helps you to plan, prepare and discuss budgets. Digitalized approval cycle With Adfinity, thanks to our thee-way-match feature and OCR, you can digitalize all sorts of flows which need approval. Like purchase and stock management or invoicing approval. OCR Invoice, contracts and documents can be recognized by our OCR system. You just need to scan the papers or upload them digitally, and Adfinity does the rest by filling in the properties in your accounting system with ease. No more next content Featured customers of Adfinity AVA Retail 1,195 followers EAGLESTONE Belgium Real Estate 7,082 followers Batipro Wholesale Building Materials 809 followers Home Invest Belgium Real Estate 5,846 followers Herfurth Group Transportation, Logistics, Supply Chain and Storage 3,673 followers Inclusio SA Real Estate 2,245 followers Keolis Group Ground Passenger Transportation 148,157 followers CENTRE HOSPITALIER CHRETIEN Medical Practices 68 followers Covalux Automotive 1,172 followers epiCura Individual and Family Services 12,916 followers ALINSO GROUP Real Estate 4,103 followers Genista Construction 3,352 followers Befimmo Real Estate 12,631 followers OH Leuven Spectator Sports 7,522 followers RSC Anderlecht Spectator Sports 25,088 followers Dockx Rental Motor Vehicle Manufacturing 1,451 followers Pur Natur nv Dairy Product Manufacturing 914 followers Chaussures Maniet ! Luxus Retail 2,921 followers Dovy Keukens Furniture and Home Furnishings Manufacturing 4,166 followers CM - Christelijke Mutualiteit Hospitals and Health Care 48,545 followers Gezinsbond Public Policy Offices 3,704 followers Show more Show less Similar products PwC Bookkeeping Connect PwC Bookkeeping Connect Enterprise Accounting Software QuickBooks Desktop Enterprise QuickBooks Desktop Enterprise Enterprise Accounting Software Xero Xero Enterprise Accounting Software Odoo Accounting Odoo Accounting Enterprise Accounting Software Workday Financial Management Workday Financial Management Enterprise Accounting Software Foodics Accounting Foodics Accounting Enterprise Accounting Software Sign in to see more Show more Show less Easi products Spoom Spoom Strategic Planning Software 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:24 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=gsw | 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://www.linkedin.com/products/hellosmartsuite-smartsuite-product-management-solutions/?trk=products_seo_search | SmartSuite | Product Management Solutions | LinkedIn Skip to main content LinkedIn SmartSuite 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 SmartSuite | Product Management Solutions Product Management Software by SmartSuite See who's skilled in this Add as skill Learn more Report this product About SmartSuite for Product Management allows businesses to turn their product vision into reality faster by managing every development process in one place. Create a product roadmap, plan requirements, manage your sprints, assign tasks to your team and deliver high-quality products on time and under budget. Monitor everything with real-time dashboards, flexible views, and powerful reports. Get Started with a free trial - no credit card required. This product is intended for Product Manager Product Development Specialist Software Engineer Engineering Manager Project Manager Quality Assurance Manager Product Marketing Manager Vice President of Engineering Vice President of Products Media Products media viewer No more previous content SmartSuite for Product Development / Management Product Roadmaps Track Requirements Agile SCRUM - Daily Standups Sprint Planning No more next content Similar products Productboard Productboard Product Management Software Aha! Academy Aha! Academy Product Management Software Product Portfolio Management Product Portfolio Management Product Management Software Producer Producer Product Management Software Dovetail Dovetail Product Management Software Interim Product Managers Interim Product Managers Product Management Software Sign in to see more Show more Show less SmartSuite products SmartSuite | Compliance Solutions SmartSuite | Compliance Solutions Governance, Risk Management, and Compliance (GRC) Software SmartSuite | Creative Design Solutions SmartSuite | Creative Design Solutions Product Lifecycle Management (PLM) Software SmartSuite | Customer Support Solutions SmartSuite | Customer Support Solutions Customer Success Software SmartSuite | Event Planning Solutions SmartSuite | Event Planning Solutions Event Management Software SmartSuite | Governance, Risk and Compliance Solutions SmartSuite | Governance, Risk and Compliance Solutions Governance, Risk Management, and Compliance (GRC) Software SmartSuite | Human Resources and Recruiting Solutions SmartSuite | Human Resources and Recruiting Solutions Human Resources Management Systems (HRMS) SmartSuite | Information Technology Solutions SmartSuite | Information Technology Solutions IT Asset Management Software SmartSuite | Professional Services Delivery Solutions SmartSuite | Professional Services Delivery Solutions Professional Services Automation (PSA) Software SmartSuite | Software Development Solutions SmartSuite | Software Development Solutions Requirements 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:24 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=kk | 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://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/pinterest#param-end-date | 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://www.linkedin.com/products/easi-spoom/ | Spoom | LinkedIn Skip to main content LinkedIn Easi 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 Spoom Strategic Planning Software by Easi See who's skilled in this Add as skill Learn more Report this product About From now on, follow only the KPIs that really matter. Link operations to strategy and bring true business value to those executing the change. Using clear cascading strategy maps, you ensure that silos are broken and that initiatives, KPIs and related data can be linked across departments. Move from isolated business intelligence initiatives to motivated teams driven by strategy. Spoom gives you the bigger picture allowing you to spot opportunities, to minimize risks and act proactively on your strategic course. This product is intended for Chief Executive Officer Chief Financial Officer Chief Operating Officer Marketing Director Chief Information Officer Sales Manager Manager Team Lead Project Manager Human Resources Manager Media Products media viewer No more previous content Spoom - Aligns vision, data & teams - Strategy Execution Software Spoom's Strategy Map for cascading impacts Balanced Scorecard - manage and steer your team Track KPIs, Milestones, OKRs from any data source following your needs Transparency is key in strategy execution & planning 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 Easi products Adfinity Adfinity Enterprise Accounting Software 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:24 |
https://git-scm.com/book/pt-br/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. 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 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 to create a brand-new Git repository, or connect an existing Git project. We won’t belabor this here; if you need a refresher, check out [ch02-git-basics] . Now that your project is hosted on GitHub, you can give the URL to anyone you want to share your project with. Every project on GitHub is accessible over HTTPS as https://github.com/<user>/<project_name> , and over SSH as git@github.com:<user>/<project_name> . Git can fetch from and push to both of these URLs, but they are access-controlled based on the credentials of the user connecting to them. Note It is often preferable to share the HTTPS based URL for a public project, since the user does not have to have a GitHub account to access it for cloning. Users will have to have an account and an uploaded SSH key to access your project if you give them the SSH URL. The HTTPS one is also exactly the same URL they would paste into a browser to view the project there. Adding Collaborators If you’re working with other people who you want to give commit access to, you need to add them as “collaborators”. If Ben, Jeff, and Louise all sign up for accounts on GitHub, and you want to give them push access to your repository, you can add them to your project. Doing so will give them “push” access, which means they have both read and write access to the project and Git repository. Click the “Settings” link at the bottom of the right-hand sidebar. Figure 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 O fluxo do GitHub , 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 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 Encanamento e Porcelana ) 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 Comentários enviados como notificações pelo email 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:24 |
https://docs.brightdata.com/api-reference/web-scraper-api/social-media-apis/instagram#param-end-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:24 |
https://git-scm.com/book/bg/v2/%d0%9a%d0%bb%d0%be%d0%bd%d0%be%d0%b2%d0%b5-%d0%b2-Git-%d0%9d%d0%b0%d0%ba%d1%80%d0%b0%d1%82%d0%ba%d0%be-%d0%b7%d0%b0-%d1%80%d0%b0%d0%b7%d0%ba%d0%bb%d0%be%d0%bd%d0%b5%d0%bd%d0%b8%d1%8f%d1%82%d0%b0 | Git - Накратко за разклоненията About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Начало 1.1 За 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 3.1 Клонове в Git - Накратко за разклоненията Почти всички VCS системи разполагат с поддръжка на разклонения на версиите на кода под някаква форма. Разклоняването на кода означава, че вие се отделяте от основната линия на разработка (във ваш собствен клон, branch) и продължавате да работите без да се намесвате в тази основна линия. В множеството VCS системи това е процес, който изисква много ресурси и често сте принудени да копирате цялата си директория със сорс код, което може да е бавно при големи проекти. Някои хора определят branching модела на Git като неговата “най-силна черта” и в действителност това е едно от нещата, които помагат на Git да изпъква сред другите VCS системи. Кое е толкова специално? Начинът, по който Git имплементира клоновете код е изключително олекотен, което прави branching операциите почти мигновени - това важи със същата сила и за превключването напред и назад по различните клонове код без оглед на мащаба на проекта. За разлика от другите VCS системи, Git окуражава работните процеси съдържащи чести разклонявания и сливания - дори по няколко пъти на ден. Ако успеете да овладеете тази страна на Git, ще разполагате с един мощен и уникален инструмент, който значително ще подобри и улесни методите ви на разработка. Накратко за разклоненията (Под клон, разклонение и branch ще имаме предвид едно и също нещо.) За да разберем как в действителност Git реализира разклоненията, трябва да се върнем стъпка назад и да си припомним как Git съхранява своите данни. Както може би помните от Какво е Git , Git не съхранява информацията си като серии от промени или разлики, а вместо това пази серии от моментното състояние на проекта - snapshots . Когато правите къмит, Git съхранява един commit обект, който съдържа указател към snapshot-а на индексираното съдържание (това, което е в индексната област). Този обект също така съдържа името и имейла на автора, къмит съобщението и също така - указатели към къмита или къмитите, които са правени директно преди текущия къмит (тоест, неговите родител/родители): първоначалният къмит няма родители, нормалният къмит има един родител, а къмитът създаден в резултат от сливане на няколко клона има множество родители. За да илюстрираме това, нека допуснем, че имате директория с три файла и сте ги индексирали и къмитнали. Процесът по индексирането на файловете (staging) изчислява чексума за всеки от файловете (това е SHA-1 хеш стрингът за който говорихме по-рано в Какво е Git ), записва версията на всеки файл в хранилището (Git третира файловете като blob-обекти) и добавя чексумите в индексната област (staging area): $ git add README test.rb LICENSE $ git commit -m 'Initial commit' След като изпълните git commit , Git изчислява чексума за всяка поддиректория (в този случай само основната директория на проекта) и ги съхранява като дървовиден обект в Git хранилището. След това Git създава commit-обект, който съдържа метаданните и указател към root-дървото на проекта, така че да може да пресъздаде snapshot-а (тоест йерархията от файлове и директории) по-късно, когато е необходимо. Вашето Git хранилище сега съдържа 5 обекта: по един blob за всеки от трите файла, едно дърво описващо съдържанието на директорията и указващо кой файл под формата на кой blob се съхранява, и един къмит с указател към това основно дърво и всички метаданни за къмита. Фигура 9. Един къмит и неговото дърво Ако направите някакви промени и къмитнете отново, следващият къмит ще съхранява указател към къмита направен веднага преди него. Фигура 10. Къмити и родителски къмити Разклонението код (branch) в Git е просто олекотен, променлив указател към един от тези къмити. Името на разклонението по подразбиране за Git е master . Когато започнете да правите къмити, вие разполагате с master branch, който сочи към последния къмит, който сте направили. Всеки път, когато къмитвате, той автоматично се премества и сочи към последния къмит. Забележка “master” клонът в Git не бива да се разглежда като специален такъв. Той е подобен на всички останали клонове. Единствената причина почти всяко хранилище да има master клон е, че командата git init го създава по подразбиране и повечето хора не си правят труда да му сменят името. Фигура 11. branch и неговата commit история Създаване на ново разклонение Какво се случва, когато създадете нов клон? Git просто създава нов указател за вас, който да може да се премества. Да кажем, че създавате клон с име testing . Това се прави с командата git branch : $ git branch testing Това създава нов указател към същия къмит, на който сте в момента. Фигура 12. Два клона сочещи към една и съща серия къмити Как Git знае в кой клон сте в даден момент? Системата си пази специален указател, който се нарича HEAD . Отбележете, че това е съвсем различно от HEAD концепциите в други VCS от рода на Subversion или CVS. В Git, това е указател към текущия локален клон от хранилището ви. В този случай, вие още сте в master клона. Това е така, защото git branch командата само създаде новия клон, но не превключи към него. Фигура 13. HEAD указател сочещ към текущия branch Можете лесно да видите това изпълнявайки командата git log --decorate , която отпечатва накъде сочат указателите на разклоненията. $ git log --oneline --decorate f30ab (HEAD -> master, testing) Add feature #32 - ability to add new formats to the central interface 34ac2 Fix bug #1328 - stack overflow under certain conditions 98ca9 Initial commit Виждате master и testing клоновете веднага до f30ab -къмита. Превключване на разклонения За да превключите към съществуващ клон, изпълнете командата git checkout . Нека превключим към testing клона: $ git checkout testing Това премества HEAD указателя и сега той сочи към testing клона. Фигура 14. HEAD сочи към текущия клон Какво означава това? Нека направим още един къмит: $ vim test.rb $ git commit -a -m 'made a change' Фигура 15. HEAD клонът се премества напред при направен къмит Това е интересно, защото сега вашият testing клон се премести напред, но master клонът все още сочи към къмита, в който бяхте когато изпълнихте git checkout за да превключите разклоненията. Нека се върнем отново на master клона: $ git checkout master Забележка git log не показва всички клонове постоянно Ако изпълните git log сега, може да се зачудите къде е изчезнал току що създадения "testing" клон, понеже той няма да се покаже в изхода. Клонът не е изчезнал, Git просто не знае, че се интересувате от него и се опитва да ви покаже това, което той мисли, че търсите. С други думи, по подразбиране, git log ще показва само историята на къмитите в клона, който е активен в момента. Ако желаете историята на конкретен клон, ще трябва да го укажете изрично git log testing . За да покажете всички клонове, използвайте git log --all . Фигура 16. HEAD се премества когато превключвате Тази команда направи две неща. Тя премести HEAD указателя обратно към точката на master клона - и също така върна обратно статуса на всички файлове в работната ви директория така че те сега съдържат това, което са съдържали в момента на последния къмит в master клона. Това също означава, че промените които предстои да правите занапред от тази точка на проекта, ще произлизат от по-стара негова версия. Практически - връщането в master клона заличи всички промени от testing клона в работната директория и сега можете да тръгнете в различна посока. Забележка Превключването между клоновете променя файловете в работната директория Важно е да се посочи, че когато превключвате клонове в Git, файловете в работната директория ще се променят. Ако превключите към по-ранен клон, вашата работна директория ще се превърти назад във времето и ще съдържа това, което е имала последния път когато сте направили къмит в този клон. Ако Git не може да направи това безпроблемно - то превключването няма да бъде позволено въобще. Нека направим няколко промени и да къмитнем отново: $ vim test.rb $ git commit -a -m 'made other changes' Сега историята на проекта се отклони (виж Разклонена история ). Вие създадохте и превключихте към нов клон, направихте промени по кода в него, превключихте към основния клон и направихте други промени. И двата вида промени са изолирани в отделни разклонения: можете да превключвате между тези разклонения и да ги слеете в едно, когато сте готови. Направихте всичко това с прости команди като branch , checkout , и commit . Фигура 17. Разклонена история Можете лесно да видите това и с командата git log . Ако изпълните git log --oneline --decorate --graph --all , това ще отпечата историята на вашите къмити, показвайки къде са вашите branch указатели и как се е разклонила историята на проекта. $ git log --oneline --decorate --graph --all * c2b9e (HEAD, master) Made other changes | * 87ab2 (testing) Made a change |/ * f30ab Add feature #32 - ability to add new formats to the central interface * 34ac2 Fix bug #1328 - stack overflow under certain conditions * 98ca9 initial commit of my project Понеже клонът в Git на практика е обикновен файл съдържащ 40-символна SHA-1 чексума на къмита, към който клонът сочи, създаването и изтриването на разклонения в Git почти не изисква ресурси. Създаването на нов клон е толкова бързо и просто колкото е записа на 41 байта във файл (40-те символа от чексумата и символ за нов ред). Това рязко контрастира с начина, по който повечето стари VCS системи управляват разклоненията, защото те копират всички файлове на проекта ви в отделна директория. При тях това може да отнеме много секунди и дори минути, според размера на проекта, докато при Git се прави почти мигновено. Също така, понеже записваме родителите когато къмитваме, намирането на правилната базова точка за сливане се осъществява автоматично за нас и е много лесно. Тези функции окуражават разработчиците да създават и използват разклонения колкото може по-често. Нека видим защо е добре да го правим. Забележка Създаване на нов клон и превключване към него автоматично Често се случва да искате да превключите веднага към новосъздаден клон — това може да стане на една стъпка с командата 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://git-scm.com/book/fa/v2/%d8%a7%d9%86%d8%b4%d8%b9%d8%a7%d8%a8%e2%80%8c%da%af%db%8c%d8%b1%db%8c-%d8%af%d8%b1-%da%af%db%8c%d8%aa-Git-Branching-%d8%b4%d8%a7%d8%ae%d9%87%e2%80%8c%d9%87%d8%a7-%d8%af%d8%b1-%db%8c%da%a9-%d9%86%da%af%d8%a7%d9%87-Branches-in-a-Nutshell | Git - شاخهها در یک نگاه (Branches in a Nutshell) About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. شروع به کار (getting started) 1.1 درباره ورژن کنترل (About Version Control) 1.2 تاریخچه کوتاهی از گیت (A Short History of Git) 1.3 گیت چیست؟ (What is Git) 1.4 نصب گیت (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 3.1 انشعابگیری در گیت (Git Branching) - شاخهها در یک نگاه (Branches in a Nutshell) تقریباً همهٔ سیستمهای کنترل نسخه نوعی پشتیبانی از شاخهبندی دارند. شاخهبندی یعنی از خط اصلی توسعه جدا میشوید و به کار ادامه میدهید بدون اینکه آن خط اصلی را دستکاری کنید. در بسیاری از ابزارهای کنترل نسخه، این فرایند نسبتاً پرهزینه است و اغلب نیاز دارد یک کپی جدید از پوشهٔ کد منبع خود بسازید که برای پروژههای بزرگ ممکن است زمان زیادی ببرد. برخیها مدل شاخهبندی گیت را «ویژگی قاتل» آن مینامند و بیشک این ویژگی گیت را در جامعهٔ سیستمهای کنترل نسخه متمایز میکند. چه چیزی آن را ویژه میکند؟ شیوهٔ کار شاخهها در گیت فوقالعاده سبک است، بنابراین عملیات شاخهبندی تقریباً لحظهای انجام میشود و جابهجایی بین شاخهها هم عموماً به همان سرعت انجام میگیرد. برخلاف بسیاری از سیستمهای دیگر، گیت جریانهای کاریای را تشویق میکند که اغلب شاخه میزنند و ادغام میکنند، حتی چند بار در طول روز. درک و تسلط بر این قابلیت ابزار قدرتمند و منحصربهفردی در اختیار شما میگذارد و میتواند کل شیوهٔ توسعهٔ شما را تغییر دهد. شاخهها در یک نگاه (Branches in a Nutshell) برای درک واقعی نحوهی شاخهبندی در گیت، باید یک قدم به عقب برداریم و بررسی کنیم گیت دادههای خود را چگونه ذخیره میکند. همانطور که ممکن است از گیت چیست؟ (What is Git) به یاد داشته باشید، گیت دادهها را به صورت یک سری تغییرات یا تفاوتها ذخیره نمیکند، بلکه به صورت یک سری تصویر لحظهای ذخیره میکند. وقتی شما یک کامیت میزنید، گیت یک شیء کامیت ذخیره میکند که شامل اشارهگری به تصویر لحظهای محتوایی است که آماده کردهاید. این شیء همچنین شامل نام و ایمیل نویسنده، پیامی که تایپ کردهاید، و اشارهگرهایی به کامیت یا کامیتهایی است که مستقیماً قبل از این کامیت آمدهاند (والد یا والدین آن): صفر والد برای کامیت اولیه، یک والد برای کامیت معمولی، و چند والد برای کامیتی که نتیجه ادغام دو یا چند شاخه است. برای تجسم این موضوع، فرض کنید دایرکتوریای دارید که شامل سه فایل است و همه را آماده کرده و کامیت میکنید. آماده کردن فایلها یک مقدار چکسام برای هر فایل محاسبه میکند (هش SHA-1 که در گیت چیست؟ (What is Git) ذکر شد)، آن نسخه از فایل را در مخزن گیت ذخیره میکند (گیت به آنها blob میگوید) و آن چکسام را به منطقه آمادهسازی اضافه میکند: $ git add README test.rb LICENSE $ git commit -m 'Initial commit' وقتی با اجرای دستور git commit کامیت را ایجاد میکنید، گیت چکسام هر زیرشاخه (در این مورد فقط دایرکتوری اصلی پروژه) را محاسبه کرده و آنها را به شکل یک شیء درختی (tree) در مخزن گیت ذخیره میکند. سپس گیت یک شیء کامیت ایجاد میکند که شامل فراداده و اشارهگری به درخت ریشه پروژه است تا بتواند آن تصویر لحظهای را در صورت نیاز بازسازی کند. اکنون مخزن گیت شما شامل پنج شیء است: سه blob (هر کدام نمایانگر محتوای یکی از سه فایل)، یک tree که محتوای دایرکتوری را لیست میکند و مشخص میکند کدام نام فایل به کدام blob ذخیره شده است، و یک commit با اشارهگری به آن درخت ریشه و تمام فرادادههای کامیت. نمودار 9. A commit and its tree اگر تغییراتی ایجاد کنید و دوباره کامیت بزنید، کامیت بعدی اشارهگری به کامیتی که بلافاصله قبل از آن آمده است ذخیره میکند. نمودار 10. Commits and their parents یک شاخه در گیت صرفاً یک اشارهگر سبک و قابل انتقال به یکی از این کامیتها است. نام پیشفرض شاخه در گیت master است. وقتی شروع به ایجاد کامیت میکنید، شاخه master به آخرین کامیتی که زدهاید اشاره دارد. هر بار که کامیت میزنید، اشارهگر شاخه master به طور خودکار جلو میرود. یادداشت شاخه “master” در گیت شاخهای ویژه نیست. این دقیقاً مانند هر شاخه دیگری است. تنها دلیل اینکه تقریباً هر مخزنی یکی دارد این است که دستور git init آن را به طور پیشفرض ایجاد میکند و بیشتر افراد زحمت تغییر آن را به خود نمیدهند. نمودار 11. A branch and its commit history ایجاد یک شاخه جدید (Creating a New Branch) وقتی یک شاخه جدید ایجاد میکنید چه اتفاقی میافتد؟ خب، این کار یک اشارهگر جدید برای شما ایجاد میکند تا جابجا کنید. فرض کنید میخواهید شاخه جدیدی به نام testing بسازید. این کار را با دستور git branch انجام میدهید: $ git branch testing این اشارهگر جدیدی به همان کامیتی که در حال حاضر روی آن هستید ایجاد میکند. نمودار 12. Two branches pointing into the same series of commits چگونه گیت میداند شما الان روی کدام شاخه هستید؟ گیت یک اشارهگر ویژه به نام HEAD نگه میدارد. توجه داشته باشید که این بسیار متفاوت از مفهوم HEAD در سایر سیستمهای کنترل نسخه مانند Subversion یا CVS است. در گیت، این اشارهگری به شاخه محلی است که در حال حاضر روی آن هستید. در این مورد، شما هنوز روی master هستید. دستور git branch فقط یک شاخه جدید ایجاد کرد — ولی به آن شاخه سوئیچ نکرد. نمودار 13. HEAD pointing to a branch شما میتوانید این موضوع را با اجرای دستور ساده git log ببینید که نشان میدهد اشارهگرهای شاخه کجا هستند. این گزینه --decorate نام دارد. $ git log --oneline --decorate f30ab (HEAD -> master, testing) Add feature #32 - ability to add new formats to the central interface 34ac2 Fix bug #1328 - stack overflow under certain conditions 98ca9 Initial commit شما میتوانید شاخههای master و testing را ببینید که درست کنار کامیت f30ab قرار دارند. تغییر شاخه (Switching Branches) برای تغییر به یک شاخه موجود، دستور git checkout را اجرا کنید. بیایید به شاخه جدید testing سوئیچ کنیم: $ git checkout testing این باعث میشود HEAD به شاخه testing اشاره کند. نمودار 14. HEAD points to the current branch اهمیت این چیست؟ خب، بیایید یک کامیت دیگر بزنیم: $ vim test.rb $ git commit -a -m 'Make a change' نمودار 15. The HEAD branch moves forward when a commit is made این جالب است، چون اکنون شاخه testing جلو رفته اما شاخه master هنوز به کامیتی اشاره دارد که هنگام اجرای git checkout روی آن بودید. بیایید برگردیم به شاخه master: $ git checkout master یادداشت git log doesn’t show all the branches all the time اگر همین الان دستور git log را اجرا کنید، ممکن است تعجب کنید که شاخه “testing” که تازه ساختید کجا رفته است، چون در خروجی نمایش داده نمیشود. شاخه ناپدید نشده؛ گیت فقط نمیداند شما علاقهمند به آن شاخه هستید و سعی دارد چیزی را نشان دهد که فکر میکند شما علاقه دارید. به عبارت دیگر، به طور پیشفرض، git log فقط تاریخچه کامیتهای زیر شاخهای که روی آن قرار دارید را نشان میدهد. برای نمایش تاریخچه کامیتهای شاخه مورد نظر باید صراحتاً آن را مشخص کنید: git log testing . برای نمایش تمام شاخهها، گزینه --all را به دستور git log اضافه کنید. نمودار 16. HEAD moves when you checkout آن دستور دو کار انجام داد. اشارهگر HEAD را برگرداند تا به شاخه master اشاره کند و فایلهای دایرکتوری کاری شما را به تصویر لحظهایای که master اشاره دارد برگرداند. این همچنین یعنی تغییراتی که از این نقطه به بعد انجام میدهید از نسخه قدیمیتر پروژه انحراف خواهد داشت. در واقع کارهایی که در شاخه testing انجام داده بودید را عقب برد تا بتوانید مسیر متفاوتی بروید. یادداشت Switching branches changes files in your working directory مهم است بدانید وقتی در گیت بین شاخهها جابجا میشوید، فایلهای دایرکتوری کاری شما تغییر خواهند کرد. اگر به شاخهای قدیمیتر سوئیچ کنید، دایرکتوری کاری شما بازمیگردد تا شبیه آخرین باری شود که روی آن شاخه کامیت زده بودید. اگر گیت نتواند این کار را به صورت تمیز انجام دهد، اصلاً اجازه نمیدهد سوئیچ کنید. بیایید چند تغییر ایجاد کنیم و دوباره کامیت بزنیم: $ vim test.rb $ git commit -a -m 'Make other changes' اکنون تاریخچه پروژه شما انحراف پیدا کرده است ببینید) Divergent history ). شما یک شاخه ساختید و روی آن کار کردید، سپس برگشتید به شاخه اصلی و کار دیگری انجام دادید. هر دو تغییر در شاخههای جداگانه ایزوله شدهاند: میتوانید بین شاخهها جابجا شوید و وقتی آماده بودید آنها را ادغام کنید. و همه این کارها را با دستورات سادهی branch ، checkout و commit انجام دادید. نمودار 17. Divergent history شما همچنین میتوانید این موضوع را به راحتی با دستور git log ببینید. اگر دستور git log --oneline --decorate --graph --all را اجرا کنید، تاریخچه کامیتها را چاپ میکند و نشان میدهد اشارهگرهای شاخه کجا هستند و تاریخچه شما چگونه انحراف یافته است. $ git log --oneline --decorate --graph --all * c2b9e (HEAD, master) Make other changes | * 87ab2 (testing) Make a change |/ * f30ab Add feature #32 - ability to add new formats to the central interface * 34ac2 Fix bug #1328 - stack overflow under certain conditions * 98ca9 Initial commit of my project | چون یک شاخه در گیت در واقع یک فایل ساده است که مقدار چکسام 40 حرفی SHA-1 کامیتی که به آن اشاره دارد را نگه میدارد، ایجاد و حذف شاخه بسیار کم هزینه است. ساختن یک شاخه جدید همانقدر سریع و ساده است که 41 بایت (40 کاراکتر و یک خط جدید) را در یک فایل بنویسیم. این برخلاف روش اکثر ابزارهای کنترل نسخه قدیمیتر است که برای ایجاد شاخه باید همه فایلهای پروژه را در دایرکتوری دوم کپی کنند. این کار ممکن است چند ثانیه یا حتی چند دقیقه طول بکشد، بسته به اندازه پروژه، در حالی که در گیت این فرایند همیشه فوری است. همچنین چون ما والدین را هنگام کامیت ثبت میکنیم، یافتن پایه مناسب برای ادغام خودکار انجام شده و معمولاً بسیار آسان است. این ویژگیها توسعهدهندگان را تشویق میکند تا اغلب شاخه بسازند و استفاده کنند. بیایید ببینیم چرا باید این کار را انجام دهید یادداشت Creating a new branch and switching to it at the same time معمولاً وقتی یک شاخه جدید ایجاد میکنید، میخواهید همزمان روی آن سوئیچ کنید — این کار با یک عملیات با دستور git checkout -b <newbranchname> انجام پذیر است. یادداشت از نسخه 2.23 گیت به بعد میتوانید از git switch به جای git checkout استفاده کنید برای: سوئیچ به شاخه موجود: git switch testing-branch . ساختن یک شاخه جدید و سوئیچ به آن: git switch -c new-branch . گزینه -c مخفف create است، همچنین میتوانید گزینه کامل آن یعنی: --create استفاده کنید. بازگشت به شاخهای که قبلاً روی آن بودید: git switch - . prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:24 |
https://git-scm.com/book/sl/v2/GitHub-Vzdr%c5%beevanje-projekta | Git - Vzdrževanje projekta 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 6.3 GitHub - Vzdrževanje projekta Vzdrževanje projekta Sedaj, ko smo domači s prispevanjem projektu, poglejmo drugo stran: ustvarjanje, vzdrževanje in administriranje vašega lastnega projekta. Ustvarjanje novega repozitorija Ustvarimo nov repozitorij, da delimo kodo vašega projekta. Začnite s klikom na gumb »New repository« na desni strani plošče ali z gumbom + na vrhnji orodni vrstici zraven vašega uporabniškega imena, kot je prikazano na sliki Spustni seznam »New repository« . Slika 109. Področje »Your repositories« Slika 110. Spustni seznam »New repository« To vas popelje na obrazec »new repository«: Slika 111. Obrazec »new repository« Vse kar morate v resnici tu narediti, je ponuditi ime projekta; preostanek polj je v celoti neobvezen. Za sedaj, samo kliknite na gumb »Create Repository« in že imate nov repozitorij na GitHubu imenovan <user>/<project_name> . Ker še nimate kode, vam bo GitHub prikazal navodila, kako ustvariti popolnoma nov repozitorij Git ali povezati obstoječi projekt Git. Tega tu ne bomo poudarjali; če potrebujete osvežitev, preverite poglavje Osnove Git . Sedaj, ko vaš projekt gostuje na GitHubu, lahko daste URL komurkoli, s komer želite deliti svoj projekt. Vsak projekt na GitHubu je dostopen preko HTTPS kot https://github.com/<user>/<project_name> in preko SSH kot git@github.com:<user>/<project_name> . Git lahko prenese in potisne na oba od teh URL-jev, vendar sta osnovana na nadzoru dostopa poverilnic uporabnika, ki se povezuje z njimi. Opomba Pogostokrat je bolje deliti HTTPS osnovan URL za javni projekt, saj uporabniku ni treba imeti računa GitHub, da dostopa do njega za kloniranje. Uporabniki bodo morali imeti račun in naložiti ključ SSH za dostop do vašega projekta, če jim daste SSH URL. HTTPS URL je tudi točno tak URL, kot bi ga prilepili v brskalnik, da si tam pogledajo projekt. Dodajanje sodelavcev Če delate z drugimi ljudmi, ki jim želite dati dostop potrjevanja, jih morate dodati kot »sodelavce«. Če se Ben, Jeff in Louise vsi prijavijo za račune na GitHubu in jim želite dati dostop potiskanja do svojega repozitorija, jih lahko dodate k svojemu projektu. To jim bo dalo dostop »push«, kar pomeni, da imajo tako pravice branja kot tudi pisanja za projekt in repozitorij Git. Kliknite na povezavo »Settings« na dnu orodne vrstice desne strani. Slika 112. Povezava nastavitev repozitorija Nato izberite »Collaborators« iz menija na levi strani. Nato samo vpišite uporabniško ime v prostor in kliknite »Add collaborator«. To lahko ponovite kolikorkrat želite, da daste dostop vsakomur, komur želite. Če morate odstraniti dostop, samo kliknite »X« na desni strani vrstice. Slika 113. Prostor za sodelavce repozitorija Upravljanje zahtevkov potega Sedaj, ko imate projekt z nekaj kode v njem in morda celo nekaj sodelavcev, ki imajo tudi dostop potiskanja, pojdimo skozi, kaj narediti, ko dobite zahtevek potega. Zahtevki potegov lahko pridejo ali iz veje v vejitvi vašega projekta ali pa pridejo iz druge veje v istem repozitoriju. Edina razlika je, da so tisti v vejitvi pogostokrat od ljudi, kjer ne morete potiskati v njihovo vejo in oni ne morejo potiskati v vašo, kjer z internimi zahtevki potegov v splošnem obe strani lahko dostopata do veje. Za te primere, predpostavimo, da ste »tonychacon« in ste ustvarili nov kodni projekt Arduino imenovan »fade«. E-poštna obvestila Nekdo pride zraven in naredi spremembe v vaši kodi ter vam pošlje zahtevek potega. Morali bi dobiti e-pošto, ki vas obvesti o novem zahtevku potega in videti bi morala biti nekako kot na sliki E-poštno obvestilo o novem zahtevku potega . Slika 114. E-poštno obvestilo o novem zahtevku potega Tam se opazi nekaj stvari o tej e-pošti. Dalo vam bo majhen status razlik (angl. diffstat ) — seznam datotek, ki so se spremenile v zahtevku potega in za koliko. Da vam povezavo na zahtevek potega na GitHubu. Da vam tudi nekaj URL-jev, ki jih lahko uporabite iz ukazne vrstice. Če opazite vrstico, ki pravi git pull <url> patch-1 , je to enostaven način za združevanje v oddaljeno vejo brez potrebe po dodajanju daljave. Skozi to smo šli na hitro v razdelku Izvlečenje oddaljenih vej . Če želite, lahko ustvarite in preklopite na tematsko vejo ter nato poženete ta ukaz za združitev sprememb zahtevka potega. Druga zanimiva URL-ja sta .diff in .patch , ki, kot ste že ugotovili, ponujata enotno razliko in različici popravkov zahtevka potega. Tehnično bi lahko združili zahtevek potega dela z nečim takim: $ curl https://github.com/tonychacon/fade/pull/1.patch | git am Sodelovanje na zahtevku potega Kot smo pokrili v Potek GitHub , imate lahko sedaj pogovor z osebo, ki je odprla zahtevek potega. Lahko komentirate na določenih vrsticah kode, komentirate na celotnih potrditvah ali komentirate na celotnem zahtevku potega, povsod z uporabo GitHub Flavored Markdowna. Vsakič, ko nekdo drug komentira na zahtevku potega, boste prejeli e-poštno obvestilo, da veste, da se dogaja dejavnost. Vsako obvestilo bo imelo povezavo na zahtevek potega, kjer se dejavnost dogaja, in lahko se tudi neposredno odzovete na e-pošto, da komentirate na temi zahtevka potega. Slika 115. Odzivi na e-pošte so vključeni v niti Ko je enkrat koda na mestu, ki ga želite, in želite to kodo združiti, lahko povlečete kodo in jo združite lokalno s sintakso git pull <url> <branch> , ki smo jo videli prej, ali pa dodate vejitev kot daljavo in jo prenesete ter združite. Če je združevanje trivialno, lahko samo tudi pritisnete gumb »Merge« na strani GitHub. To bo naredilo združitev »non-fast-forward« in ustvarilo potrditev združitve, tudi če fast-forward združevanje ni možno. To pomeni, da ne glede na kaj, vsakič, ko pritisnete gumb za združitev, se ustvari potrditev združitve. Kot lahko vidite na sliki Gumb za združevanje in navodila za ročno združitev zahtevka potega , vam da GitHub vse te informacije, če kliknete na povezavo namiga. Slika 116. Gumb za združevanje in navodila za ročno združitev zahtevka potega Če se odločite, da ga ne želite združiti, lahko tudi samo zaprete zahtevek potega in oseba, ki je to odprla, bo obveščena. Reference zahtevkov potega Če se spopadate z velikim številom zahtevkov potega in ne želite dodati več daljav, ali vsakič izvajati enkratnega vlečenja, obstaja trik, ki vam ga omogoča GitHub. To je nekoliko bolj napreden trik, o katerem bomo podrobneje razpravljali v Refspec , vendar pa je lahko zelo uporaben. GitHub dejansko oglašuje veje zahtevkov potega za določen repozitorij, kot nekakšne psevdo-veje na strežniku. Privzeto jih ne dobite pri kloniranju, vendar so tam na zakrit način, in do njih lahko dostopate zelo enostavno. Za prikaz tega bomo uporabili nizkonivojski ukaz (pogosto imenovan kot ukaz »napeljave«, o katerem bomo več brali v Napeljava in keramika ), ki se imenuje ls-remote . Ta ukaz se običajno ne uporablja pri vsakodnevnih operacijah Git, vendar je koristen, da nam prikaže, katere reference so na voljo na strežniku. Če ta ukaz poženemo na repozitoriju »blink«, ki smo ga uporabljali prej, bomo dobili seznam vseh vej, oznak in drugih referenc v repozitoriju. $ 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 Seveda, če ste v svojem repozitoriju in zaženete git ls-remote origin ali kateri koli drug oddaljen repozitorij, ki ga želite izpisati, vam bo prikazalo nekaj podobnega temu. Če se repozitorij nahaja na GitHubu in imate odprte zahtevke potegov, boste dobili te reference, ki imajo predpone refs/pull/ . To so v bistvu veje, vendar ker niso pod refs/heads/ , jih običajno ne dobite, ko klonirate ali prenesete podatke s strežnika — postopek prenašanja jih običajno ignorira. Za vsak zahtevek potega sta dve referenci — tista, ki se konča s /head , kaže na natančno isto potrditev kot zadnja potrditev na veji zahtevka potega. Če torej nekdo odpre zahtevek potega v našem repozitoriju in je njegova veja poimenovana bug-fix ter kaže na potrditev a5a775 , potem v našem repozitoriju ne bomo imeli veje bug-fix (ker je to v njegovi vejitvi), ampak bomo imeli pull/<pr#>/head , ki kaže na a5a775 . To pomeni, da lahko precej enostavno povlečete vse veje zahtevka potega v enem zamahu, ne da bi morali dodati kup daljav. Sedaj lahko na primer prenesete referenco neposredno. $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD To Gitu sporoči: »Poveži se z oddaljenim repozitorijem origin in prenesi sklic z imenom refs/pull/958/head .« Git ubogljivo izvrši ukaz in prenese vse, kar potrebujete za sestavo tega sklica, ter postavi kazalec na potrditev, ki jo želite, pod .git/FETCH_HEAD . Nato lahko z git merge FETCH_HEAD nadaljujete v vejo, v kateri jo želite preizkusiti, vendar je sporočilo združitve videti nekoliko čudno. Če pregledujete veliko zahtevkov potegov, je to tudi dolgočasno. Obstaja tudi način, kako prenesti vse zahtevke potegov in jih vedno posodobiti, ko se povežete z daljavo. Odprite .git/config v priljubljenem urejevalniku in poiščite daljavo origin . Videti bi moralo biti nekako tako: [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* Ta vrstica, ki se začne z fetch = , je »refspec«. To je način za preslikavo imen na daljavi z imeni v vašem lokalnem direktoriju .git . Ta posebni ukaz sporoči Gitu: »Stvari na daljavi, ki so pod refs/heads , naj bodo v mojem lokalnem repozitoriju pod refs/remotes/origin .« To področje lahko spremenite in dodate nov refspec: [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* Ta zadnja vrstica sporoči Gitu: »Vse sklice, ki so videti kot refs/pull/123/head , naj se lokalno shrani kot refs/remotes/origin/pr/123 «. Če zdaj shranite to datoteko in izvedete 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 # … Zdaj so vsi oddaljeni zahtevki potegov predstavljeni lokalno s sklici, ki se obnašajo podobno kot sledilne veje; so samo za branje in se posodobijo ob prejemu ukaza za pridobitev. To močno olajša preizkušanje kode iz zahtevka potega lokalno: $ 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' Ostri opazovalci bodo opazili head na koncu oddaljenega dela refspeca. Na strani GitHuba obstaja tudi referenca refs/pull/#/merge , ki predstavlja potrditev, ki bi se zgodila, če bi pritisnili gumb »merge« na spletnem mestu. To vam omogoča preizkus združevanja, še preden pritisnete gumb. Zahtevki potegov na zahtevku potega Ne samo, da lahko odprete zahtevke potegov, ki ciljajo na glavno vejo ali vejo master , dejansko lahko odprete zahtevek potega, ki cilja na katero koli vejo v omrežju. Pravzaprav lahko ciljate tudi drug zahtevek potega. Če vidite zahtevek potega, ki se premika v pravo smer, in imate idejo za spremembo, ki je od nje odvisna, ali se vam zdi dobra ideja, ali pa nimate dostopa za potiskanje v ciljno vejo, lahko neposredno na njem odprete zahtevek potega. Ko odprete zahtevek potega, je na vrhu strani polje, ki določa, katero vejo zahtevate, da se vanjo povleče in katero vejo zahtevate, da se iz nje povleče. Če kliknete gumb »Edit« desno od tega polja, lahko spremenite ne samo veje, temveč tudi vejitev. Slika 117. Ročno spremenite ciljno vejitev in vejo zahtevka potega Tukaj lahko dokaj enostavno določite, da se vaša nova veja združi v drug zahtevek potega ali drugo vejitev projekta. Omenjanje in obvestila GitHub ima tudi precej priročen sistem obvestil, ki vam lahko pride prav, ko imate vprašanja, ali potrebujete povratne informacije od določenih posameznikov ali ekip. V vsakem komentarju lahko začnete vpisovati znak @ , ki se bo začel samodokončanje z imeni in uporabniškimi imeni ljudi, ki so sodelavci ali sodelujoči na projektu. Slika 118. Začnite vpisovati @, da nekoga omenite Omenite lahko tudi uporabnika, ki ga ni v tem spustnem seznamu, vendar pogostokrat samodokončanje lahko postopek poenostavi. Ko objavite komentar z omembo uporabnika, bo ta uporabnik obveščen. To pomeni, da je to lahko zelo učinkovit način, da ljudi vključite v pogovore, namesto da morajo nenehno preverjati. Na GitHubu pogostokrat na zahtevkih potegov ljudje v svoje ekipe ali v svoje podjetje povabijo druge ljudi, da pregledajo težavo ali zahtevek potega. Če je nekdo omenjen na zahtevku potega ali težavi, bo nanjo »naročen« in bo še naprej prejemal obvestila ob vsaki dejavnosti na njej. Naročeni boste tudi, če ste jo odprli, če spremljate repozitorij, ali če nekaj komentirate. Če ne želite več prejemati obvestil, lahko na strani kliknete gumb »Unsubscribe«, da prenehate prejemati posodobitve o njej. Slika 119. Odjava od težave ali zahtevka potega Stran z obvestili Ko govorimo o »obvestilih« v zvezi z GitHubom, mislimo na poseben način, kako GitHub poskuša stopiti v stik z vami, ko se zgodijo določeni dogodki, in obstaja nekaj načinov, kako jih lahko konfigurirate. Če odprete zavihek »Notifications center« na strani z nastavitvami, lahko vidite nekatere možnosti, ki so vam na voljo. Slika 120. Možnosti centra za obvestila Dve izbiri sta, da prejmete obvestila po »e-pošti« in prek »spletnega vmesnika« in lahko izberete ali oboje, nobenega ali pa eno ali drugo možnost za aktivno sodelovanje in dejavnost na projektih, ki jih spremljate. Spletna obvestila Spletna obvestila obstajajo samo na GitHubu in jih lahko preverite samo tam. Če imate to možnost izbrano v svojih nastavitvah in se sproži obvestilo za vas, boste na vrhu zaslona, kot prikazano na sliki Center za obvestila , videli majhno modro piko nad ikono obvestil. Slika 121. Center za obvestila Če nanjo kliknete, boste videli seznam vseh elementov, o katerih ste bili obveščeni, razvrščenih po projektih. Filtrirate lahko obvestila za določen projekt, če kliknete njegovo ime v levem stranskem meniju. Obvestilo lahko potrdite s klikom na ikono kljukice poleg katerega koli obvestila, ali pa potrdite vsa obvestila v projektu s klikom na kljukico na vrhu skupine. Poleg vsake kljukice je tudi gumb za izklop, s katerim lahko prenehate prejemati nadaljnja obvestila o tem elementu. Vsi ti pripomočki so zelo uporabni za obvladovanje velikega števila obvestil. Mnogi napredni uporabniki GitHuba bodo popolnoma izklopili obvestila po elektronski pošti in vsa svoja obvestila upravljali preko tega zaslona. E-poštna obvestila E-poštna obvestila so drug način, s katerimi lahko upravljate obvestila preko GitHuba. Če imate to funkcijo vklopljeno, boste prejeli e-poštna obvestila za vsako obvestilo. Videli smo primere tega na sliki Komentarji poslani kot e-poštna obvestila in E-poštno obvestilo o novem zahtevku potega . E-poštna sporočila bodo tudi pravilno urejena, kar je lepo, če uporabljate e-poštni odjemalec z nitmi. V glavah e-poštnih sporočil, ki jih GitHub pošilja, je tudi precejšnje število metapodatkov, kar je lahko zelo koristno za nastavitev prilagojenih filtrov in pravil. Na primer, če si ogledamo dejanske glave e-pošte, ki jih GitHub pošilja Tonyju v e-poštnem sporočilu, prikazanem na sliki E-poštno obvestilo o novem zahtevku potega , bomo med poslano informacijo videli: 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 Obstaja nekaj zanimivih stvari. Če želite poudariti ali preusmeriti e-pošto na ta določeni projekt ali celo zahtevati potrditev povratne informacije za točno ta projekt ali celo zahtevek potega, vam podatki v Message-ID ponujajo vse podatke v formatu <uporabnik>/<projekt>/<vrsta>/<id> . Če bi bila to na primer težava, bi bilo polje <vrsta> »issues« namesto »pull«. Polji List-Post in List-Unsubscribe pomenita, da lahko, če imate poštni odjemalec, ki ju razume, enostavno pošljete sporočilo na seznam ali se »odjavite« iz niti. To bi bilo bistveno enako kot klikanje gumba »mute« na spletni različici obvestila ali »Unsubscribe« na strani težave ali zahtevka potega. Prav tako velja omeniti, da če imate omogočene obvestila prek e-pošte in spleta ter preberete različico obvestila prek e-pošte, bo spletna različica prav tako označena kot prebrana, če ima vaš poštni odjemalec omogočene slike. Posebne datoteke Obstaja nekaj posebnih datotek, ki jih bo GitHub opazil, če so prisotne v vašem repozitoriju. README Prva posebna datoteka je datoteka README , ki ima lahko skoraj katerikoli format, ki ga GitHub prepozna kot besedilo. Na primer, lahko gre za README , README.md , README.asciidoc itd. Če GitHub v vaši izvorni kodi opazi datoteko README , jo bo prikazal na začetni strani projekta. Številne ekipe uporabljajo to datoteko za shranjevanje vseh pomembnih informacij o projektu za nekoga, ki se prvič srečuje z repozitorijem ali projektom. To običajno vključuje stvari, kot so: Za kaj je projekt namenjen Kako ga konfigurirati in namestiti Primer uporabe ali zagona Licenca, pod katero je projekt na voljo Kako prispevati projektu Ker bo GitHub to datoteko prikazal, jo lahko razširite tudi z vključevanjem slik ali povezav za dodatno razumljivost. CONTRIBUTING Druga posebna datoteka, ki jo GitHub prepozna, je datoteka CONTRIBUTING . Če imate datoteko z imenom CONTRIBUTING s katero koli končnico datoteke, bo GitHub prikazal, kar je vidno na sliki Odpiranje zahtevka potega, ko datoteka CONTRIBUTING že obstaja , ko kdo odpre zahtevek potega. Slika 122. Odpiranje zahtevka potega, ko datoteka CONTRIBUTING že obstaja Ideja je, da lahko določite specifične stvari, ki jih želite, ali jih ne želite v zahtevku potega, ki je poslan v vaš projekt. Na ta način bodo ljudje morda prebrali smernice, preden odprejo zahtevek potega. Projektna administracija Splošno gledano, ni veliko upravljavskih stvari, ki jih lahko naredite z enim projektom, vendar obstajajo nekateri elementi, ki bi vas lahko zanimali. Sprememba privzete veje Če uporabljate drugo vejo od veje »master« kot privzeto, in želite, da ljudje privzeto vidijo to vejo ali odprejo zahtevke potegov nanjo, lahko to spremenite na strani nastavitev vašega repozitorija pod zavihkom »Options«. Slika 123. Spremenite privzeto vejo za projekt Preprosto spremenite privzeto vejo v spustnem meniju in ta bo privzeta za vse glavne operacije od takrat naprej, vključno z vejo, ki je privzeto izvlečena, ko nekdo klonira repozitorij. Prenos projekta Če želite prenesti projekt na drug uporabniški račun ali organizacijo na GitHubu, obstaja možnost »Prenos lastništva« (angl. Transfer ownership ) na dnu istega zavihka »Options« v nastavitvah vašega repozitorija, ki vam to omogoča. Slika 124. Prenesite projekt drugemu uporabniku ali organizaciji GitHub To je koristno, če zapuščate projekt in ga želi prevzeti nekdo drug, ali če se vaš projekt širi in ga želite premakniti v organizacijo. To ne premakne samo repozitorija skupaj z vsemi njegovimi opazovalci in zvezdicami na drugo mesto, ampak tudi nastavi preusmeritev iz vašega URL-ja na novo mesto. Prav tako bo preusmerilo klone in pridobivanja iz Gita, ne samo spletnih zahtevkov. 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=et | 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://docs.brightdata.com/api-reference/web-scraper-api/synchronous-requests#body-input | 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.youtube.com/channel/UCU7QBXVX4gcePOcEyha7yng | ccMixter - 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, 사업자정보 , 불법촬영물 신고 크리에이터들이 유튜브 상에 게시, 태그 또는 추천한 상품들은 판매자들의 약관에 따라 판매됩니다. 유튜브는 이러한 제품들을 판매하지 않으며, 그에 대한 책임을 지지 않습니다. (function() {window.ytAtR = '\x7b\x22responseContext\x22:\x7b\x22serviceTrackingParams\x22:\x5b\x7b\x22service\x22:\x22CSI\x22,\x22params\x22:\x5b\x7b\x22key\x22:\x22c\x22,\x22value\x22:\x22WEB\x22\x7d,\x7b\x22key\x22:\x22cver\x22,\x22value\x22:\x222.20260109.01.00\x22\x7d,\x7b\x22key\x22:\x22yt_li\x22,\x22value\x22:\x220\x22\x7d,\x7b\x22key\x22:\x22GetAttestationChallenge_rid\x22,\x22value\x22:\x220xa5de0dd15f6c89f3\x22\x7d\x5d\x7d,\x7b\x22service\x22:\x22GFEEDBACK\x22,\x22params\x22:\x5b\x7b\x22key\x22:\x22logged_in\x22,\x22value\x22:\x220\x22\x7d,\x7b\x22key\x22:\x22visitor_data\x22,\x22value\x22:\x22CgtvdjZ2RzZzTDFLWSjyoJjLBjIKCgJLUhIEGgAgPQ%3D%3D\x22\x7d\x5d\x7d,\x7b\x22service\x22:\x22GUIDED_HELP\x22,\x22params\x22:\x5b\x7b\x22key\x22:\x22logged_in\x22,\x22value\x22:\x220\x22\x7d\x5d\x7d,\x7b\x22service\x22:\x22ECATCHER\x22,\x22params\x22:\x5b\x7b\x22key\x22:\x22client.version\x22,\x22value\x22:\x222.20260109\x22\x7d,\x7b\x22key\x22:\x22client.name\x22,\x22value\x22:\x22WEB\x22\x7d\x5d\x7d\x5d,\x22mainAppWebResponseContext\x22:\x7b\x22loggedOut\x22:true\x7d,\x22webResponseContextExtensionData\x22:\x7b\x22hasDecorated\x22:true\x7d\x7d,\x22challenge\x22:\x22a\x3d6\\u0026a2\x3d10\\u0026b\x3dhM8zTXjzjpRrMCFfsUwK9DJtFvk\\u0026c\x3d1768296562\\u0026d\x3d1\\u0026t\x3d21600\\u0026c1a\x3d1\\u0026c6a\x3d1\\u0026c6b\x3d1\\u0026hh\x3dqb4VUsRM4kv7TXxzWYSrwjHPIO0pA3B6x6ssCFJbTPQ\x22,\x22bgChallenge\x22:\x7b\x22interpreterUrl\x22:\x7b\x22privateDoNotAccessOrElseTrustedResourceUrlWrappedValue\x22:\x22\/\/www.google.com\/js\/th\/VQRLE1nj_w3YOUr9bDT-SZkrXPV28X05Wh6hb2M3ukQ.js\x22\x7d,\x22interpreterHash\x22:\x22VQRLE1nj_w3YOUr9bDT-SZkrXPV28X05Wh6hb2M3ukQ\x22,\x22program\x22:\x22McjFqXs649hVgnMaoJ6ETqbvnbpjohwh+BdDKy0J\/vqG+QHvtPTlDB9dkEBwNy+U3oLBDpx7HdfRhqrGYeXGCKrir3uJEUnfz4sMM5mBQrMsS7JH0rpSq\/KtthIZZz9RmyKZBrmMWBQMfUm8wM658YN\/OFLKBq8KD8QKQGVb0HCV1HYWepvgsYenQH+DFabTBH5R3wufbvWWJKFrs+rf1+0PH214zM9Cn89BTkA3hw5bp3ZoOJLMq32cRFsgFEMlU0BE0qxavo00EkTtUydqEWJKaEq6wixQC9uhcYJIz9E6ZSC1TAJJNMnR5k1EyacoI4h1+BKarpVGgIllC88hp\/TmRuxak5Wtqod6JgTwKatPZtZk6L3P7J7M+ZPmM4Av6lu\/OKF1NTWJHh9uiPaePCQLniUpvEclGTFUq7nVLpPqe9f10AskKJrHbY4jVjN2UI013VrEEIl9eESmRmG+TCei6XTuMsXkb0hdaqUXU08tXrSFtOlVM3U\/6EBA5LdskUN+ZfdupNkPO1y12\/oKzVdzutFl0l716u52EaYb59sOJCiEzRhE5OI0LMFLrh2+tbdre7B1sG9jMRvEYqhnAOP9QVXJGtnJcXJO7fC+T2Vj2kP58gXv74b3uRRnv1mx+4rvRAtkBExnLTF3gnGvuzD4Egr9vsRAOwEyjJIfdDJVWD4RStdUOE5JgPyJC\/52ol1oeAujVfHKw0G7UZRL0AP6CE\/1Sr4NyPlmAvZO93mNBO5N5oLsymwxC857pUlg7UnW1mpuvtOThRbdAmim4OFjLzRf5ztm5tig1pDPd3wX\/9DDysbSzKRZUJGQ\/FjUnzAYiGseDpunnkSBtPxmTQrc89M6f93pGCDfL90iJYHSEbNbPn43Bya04DkXc0Ekz371AufLPf5ixIeLyWHSmRDw55gPX4Ju1zG4MhNs+c8CY9I9J2XO3blMhCsqzDwW4DhWL5iE+f90B6Qd1jWtvWXY6ngtAZYhC0G\/x5rrrT8tzbfy\/IFqrqQmXCYDRith\/8uBE1CPomjO1hizWEWUaMBvGKGAsOoIB6hZZ6gRtA96wuSdVvU58SVdXIKMTQbWrEXr+omdUV\/aT\/z94PAXORAE6FJgVe1qMKSUUAaMQFFoR5cMLuxw6MP8p+taaNNY4\/UvZFRQiHE\/laSChCqt3WqoAAUdojxV\/YRIx3M+SHGCLtdmlMFk7tQ40Ucfdaecf0OvOvL5T4PaabP7Z+01MeTxAwYWr\/0W35y+Qu+AISZhDRDLcYs0P3efFKUQow4urnLJcpghH\/2TKkwt+WfxHygIaOL85bfPt2FR34l19XQkzv6NUhd9b\/C\/3KwzZgmJnTnQiVcZQ7SSjIxVL73U9Oagl46GLKvXlQnqUhdBdagOzb2XCbIqpqmOXoXQSVulrDHn6l7rqmaIXh94r9vj1r3zXxMWKn1AqxCb1W483fZ62Rxu33wq6HrbEhwEzp24fmwbeBiwHe0Q\/PV0SzWd+bQsTersnxIUtHiJ5gWMPPsqxZe5tMKhznfGvQt2upfCFN2\/IL+ipCHrZ6IVGfTSbDBTHNS+LV2usMyBtEb4u1tMCSLqRMUw9tyTNnZP7qkIIZo1gkpdYdAGqCI6yOeR+C8CVTtXkP2aZXgmMUhVFmem0TC6DY1HucAULyF26FUsMR2SANKJ9pO0lo8P+25Y74m4iXTZarrxxtv5lHMtaz3VvKJkJNdRNoQd++SLB2cIdRQZldGL9nMu4T8Srq4WYKgZq3RLy\/yWek18+U4W+V+gXP8BX3FnLhpPRJ5iofx\/Wzsk6AFL7gZdjSd5N22hCtKxPffBzkkRW7UwaTCOXYr5+zFYBx1wKFmhF5S60Fwx7VeyNOikIZPL+1FPuoA5ZNWv8emm46RvJUqbC0DVmwLjXtmD725a4pmthH6BMM9K8Gsper0w0guqOjf07I\/sKAGuGqv5u1K0JsDyGl0nV2tnj74cMVUs6Njwt6NhW7Di8f1dYs7R9vQmLVFUBL32ilJHHAZJLOJa8VFDE3QzbD5Tt0yolGPvzbVEkPEiLYoPkcpki9K30ZMzCzE5xLjrlXEY8Hi6sn4Czt5eLikmwghfIkWgyhyC3m0on6SYXf+dbR9GYuOd8O6PUVZrtC8pkpbPQuI58FoerwlE3X8wcW1e03vE5EKKvXpNbz5Sgdyu0A+WtVdtN1dttmkrHCj9EIHoaKc\/TeqoSMpeueCLR464s1zaJNjzJKvXusWi32duyN2+XvRMTLL40+7hiMUoyHswm8Qtnq+VbXHhgpClZHBrNoR\/CqdVynzfg4U0ha579Zj3TNRBKG5bX8WyfHKJhwiQuBHfNhGNS6AwVD\/mrrM4fy9\/jMdr2OiZzu3iQ\/ehlZ98A+qwGXOhcUkQmojs7+EZvkLLGf7+vdvs0drSYzm2l8HRadYafs\/GzxVSkegYfqOjOjaHCuN10xR6RPfR8w4ZKbqogxOgAFrWm1nJVcLN+P0WduANIBpAxL9pQAtoKEYC7Fth8xMUnmWO3hxPB47WG5+PbzjNwsf0AZC4bPUGts7h3IPdg\/OBgoI7lLcegUB9GoB0qL4\/\/zUnk3IjYRl0jA97BYv3joThqDn7Zd4c8qKBF3Ss5Ovw4PMEgvk7oEeeI1WxLGe4rP9bg7LZ0mVenOEs2Wd5in9+gJ\/cR+JUlkUYA9uhWdQjbqqZ0AEdHXGtVjkQo4oC5jVs\/1OAILFjdNEAqAD4qc8AUlQ4R2dV\/bDckmpDtHImjG5xkyw9e39+j24QG2M9fT3bi+oEiI70cbLrm7WiNHsBB9gD6QcRQYiekroxMrBzsTSGQvG8HvrX2kgnKmjIM7J4nm5vcwvzCYEbrtzp9UpgqGZ3zIVA3UgaIR\/WKunRGxrRA9vUBrIMtNDkjHbrti4Y1YVos4hKSORRsoCnf2DY+CtG3Spg1N0PXch6A4OwueISJkSB9EUpdiLeqXdnJXZBcYiB+Qmk0YKhUuJ0G\/ClZRhFn5eaiLKUEcJiiNP8KWdVUfZaEfxfVXyQcxdqsEdaHPD+\/9+ADfDyOKxV+RlWSGTfagJJVKTTNHN\/u9hUxC8iM06I0GFZjJ5V9Tq4KjJjE+z0NX2ELS1u7EL0p0p9Lgp\/YloNOFKjitP1HQG9oTucQ28fqtJTfzy65Ynxb1gfTMvvtd8Qimc\/lwDiWL+WllHjmjUXEYmER1z+\/zc3GMURh\/hwsmGpAh3aaZJiu8oEMJLGDdG0jvZbaVInJRnk6F7VrZFqgrk5ga9KIpWgiHmU+guUq4\/TuhogGkYi4psLzrL4tbz7SFZhU | 2026-01-13T09:29:24 |
https://git-scm.com/book/tl/v2/Mga-Pangunahing-Kaalaman-sa-Git-Pag-Undo-ng-mga-Bagay | Git - Pag-Undo ng mga Bagay 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.4 Mga Pangunahing Kaalaman sa Git - Pag-Undo ng mga Bagay Pag-Undo ng mga Bagay Sa anumang yugto, baka gusto mong i-undo ang isang bagay. Dito, susuriin natin ang iilang mga pangunahing mga kasangkapan para sa pag-undo ng mga pagbabago na ginawa mo. Mag-ingat ka, dahil hindi mo laging i-undo ang ilan sa mga undo na ito. Ito ay isa sa ilang mga lugar sa Git na kung saan maaari kang mawalan ng trabaho kung mali ang pagkagawa mo nito. Isa sa mga karaniwang mga undo ay magaganap kapag gumawa ka ng commit na masyadong maaga at marahil kalimutan na magdagdag ng ilang mga file, o ikaw ay gumulo sa iyong commit na mensahe. Kung nais mong gawing muli ang commit na iyon, gawin ang karagdagang mga pagbabago na nakalimutan mo, i-yugto sila, at commit uli gamit ang --amend option: $ git commit --amend Ang utos na ito ay kumukuha ng iyong staging na lugar at ginagamit ito para sa commit. Kung wala kang pagbabago mula noong iyong huling commit (halimbawa, agad mong pinatakbo ang utos na ito pagkatapos ng iyong nakaraan na commit), pagkatapos ang iyong snapshot ay magiging eksaktong magkatulad, at lahat ng iyong babaguhin ay ang iyong commit na mensahe. Ang parehong commit-mensahe na editor ay nag-aapoy, ngunit naglalaman na ito ng mensahe sa nakaraan mong commit. Maaari mong i-edit ang mensahe na katulad palagi, ngunit ito ay nag-overwrite ng iyong huling commit. Bilang isang halimbawa, kung mag-commit ka at pagkatapos ay mapagtanto mong nakalimutan ang yugto sa mga pagbabago sa isang file na nais mong idagdag sa commit na ito, maaari mong gawin ang isang bagay na tulad nito: $ git commit -m 'initial commit' $ git add forgotten_file $ git commit --amend Nagtatapos ka ng may isang solong commit — ang pangalawang commit ay pumapalit sa mga resulta ng una. Mahalagang unawaan na kapag binabago mo ang iyong huling commit, hindi ka masyadong nag-aayos nito bilang kapalit na ganap na may bago, pinagbuti na commit na nagpapatuloy sa lumang commit na wala sa daan at inilalagay ang bagong commit sa lugar na ito. Mabisa, ito ay kung ang dating commit ay hindi nangyari, at ito ay hindi nagpapakita ng iyong kasaysayan ng repositoryo. Ang malinaw na halaga sa pagbabago ng mga commit ay gumawa ng mga menor na mga pagpapabuti sa iyong huling commit, wala nang kalat sa iyong kasaysayan ng repositoryo na may commit na mga mensahe ng form, “Oops, forgot to add a file” o “Darn, fixing a typo in last commit”. Hindi pagyuyugto ng isang Yugtong File Ang susunod na dalawang seksyon ay ipinapakita kung papaano magtrabaho sa iyong yugtong lugar at tinatrabahong direktoryo na mga pagbabago. Ang ganda ng bahagi ay ang utos upang matukoy ang kalagayan ng dalawang lugar na iyon na nagpapaalala rin sa iyo kung papaano magbabago sa kanila. Halimbawa, sabihin natin na ang nabago na dalawang file at nais na gawin ang commit na sila bilang dalawang hiwalay na pagbabago, ngunit hindi mo sinasadya ang pag-type ng git add * at yugto silang pareho. Paano ka mag-unstage sa isa sa dalawa? Ang git status na utos na nagpapaalala sa iyo: $ git add * $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README modified: CONTRIBUTING.md Sa baba ng “Changes to be committed” na teksto, sinasabi nito ang paggamit git reset HEAD <file>... sa unstage. Kaya, gamitin natin ang payo na iyon upang i-unstage ang CONTRIBUTING.md na file: $ git reset HEAD CONTRIBUTING.md Unstaged changes after reset: M CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Ang utos ay medyo kakaiba, ngunit ito ay gumagana. Ang CONTRIBUTING.md na file ay binago ngunit muling na unstaged. Totoo iyon na ang git reset ay maaaring isang mapanganib na utos, lalo na kung ibinigay mo ang --hard na flag. Gayunpaman, sa senaryo na inilarawan sa itaas, ang file sa iyong tinatrabahong direktoryo ay hindi hinawakan, kaya medyo ligtas. Sa ngayon ito ay salamangka ng pagsang-ayon ay ang lahat na iyong kailangan na malaman tungkol sa git reset na utos. Puntahan natin ang mas detalye na tungkol sa ano ang reset na gagawin at kung papaano ito i-master upang gawin talaga ang kawili-wiling mga bagay sa Ang Reset Demystified . Ang Pagbalik sa Pagbago ng Binagong File Paano kung napagtanto mo na ayaw mong panatilihin ang iyong pagbabago sa CONTRIBUTING.md na file? Paano mo napadali ang pagbalik sa pagbago nito — ibalik ito pabalik sa kung ano ang mukha nito bago ka huling na-commit (o nagsimula na naka-clone, o gayunpaman nakuha mo ito sa iyong tinatrabaho na direktoryo)? Sa kabutihang palad, git status nagsasabi sa iyo kung paano gawin iyon, din. Sa huling halimbawa ng output, ang unstaged na lugar ay mukhang ganito: 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 Ito ay nagsasabi sa iyo ng medyo malinaw kung papaano itiwalag ang mga pagbabago na iyong ginawa. Gawin natin ang sinasabi nito: $ git checkout -- CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Nakikita mo na ang mga pagbabago ay naibalik na. Ito ay mahalagang maunawaan na ang git checkout -- <file> ay isang delikadong utos. Anumang mga pagbabago na iyong ginawa sa file ay mawawala — Ang Git ay naka-kopya ng ibang file sa ganito. Huwag kailanman gumamit sa utos maliban kung ikaw ay talagang alam na hindi mo gusto ang file. Kung nais mong panatilihin ang pagbabago na nagawa mo sa file na iyon ngunit kailangan mo pa rin na lumabas daanan sa ngayon, pupunta tayo sa stashing at branching sa Pag-branch ng Git ; ang mga ito ay pangkalahatang mas mahusay na paraan upang pumunta. Tandaan, kahit ano ang na-commit sa Git ay maaaring halos palaging mababawi. Kahit na ang mga commit na nasa branch na natanggal na o mga commit ay napalitan na ng --amend ang commit ay pwedeng mababawi (tingnan Pagbalik ng Datos para sa pagbawi ng datos). Gayunpaman, anumang bagay ang iyong mawala na hindi pa na-commit ay malamang hindi na makikita muli. 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/be/v2/Git-Basics-Git-Aliases | Git - Git Aliases About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Першыя крокі 1.1 About Version Control 1.2 A Short History of Git 1.3 What is Git? 1.4 The Command Line 1.5 Installing Git 1.6 First-Time Git Setup 1.7 Getting Help 1.8 Падсумаваньне 2. Git Basics 2.1 Getting a Git Repository 2.2 Recording Changes to the Repository 2.3 Viewing the Commit History 2.4 Undoing Things 2.5 Working with Remotes 2.6 Tagging 2.7 Git Aliases 2.8 Summary 3. Git Branching 3.1 Branches in a Nutshell 3.2 Basic Branching and Merging 3.3 Branch Management 3.4 Branching Workflows 3.5 Remote Branches 3.6 Rebasing 3.7 Summary 4. Git on the Server 4.1 The Protocols 4.2 Getting Git on a Server 4.3 Generating Your SSH Public Key 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Summary 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Дадатак A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Summary A2. Дадатак B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Дадатак C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.7 Git Basics - Git Aliases Git Aliases Before we move on to the next chapter, we want to introduce a feature that can make your Git experience simpler, easier, and more familiar: aliases. For clarity’s sake, we won’t be using them anywhere else in this book, but if you go on to use Git with any regularity, aliases are something you should know about. Git doesn’t automatically infer your command if you type it in partially. If you don’t want to type the entire text of each of the Git commands, you can easily set up an alias for each command using git config . Here are a couple of examples you may want to set up: $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status This means that, for example, instead of typing git commit , you just need to type git ci . As you go on using Git, you’ll probably use other commands frequently as well; don’t hesitate to create new aliases. This technique can also be very useful in creating commands that you think should exist. For example, to correct the usability problem you encountered with unstaging a file, you can add your own unstage alias to Git: $ git config --global alias.unstage 'reset HEAD --' This makes the following two commands equivalent: $ git unstage fileA $ git reset HEAD -- fileA This seems a bit clearer. It’s also common to add a last command, like this: $ git config --global alias.last 'log -1 HEAD' This way, you can see the last commit easily: $ 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> As you can tell, Git simply replaces the new command with whatever you alias it for. However, maybe you want to run an external command, rather than a Git subcommand. In that case, you start the command with a ! character. This is useful if you write your own tools that work with a Git repository. We can demonstrate by aliasing git visual to run 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://www.linkedin.com/products/programmersbeyondit-prodgy/?trk=products_seo_search | Prodgy | LinkedIn Skip to main content LinkedIn Programmers 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 Prodgy Product Management Software by Programmers See who's skilled in this Add as skill Request demo Report this product About Meet Prodgy, the AI Agents platform designed to transform the way teams run Product Ops. From Discovery to Delivery, Prodgy automates the entire process while connecting seamlessly with the tools you already use — Jira, DevOps, Slack, Teams, and more. With a unified knowledge base at its core, Prodgy empowers organizations to accelerate product development, enhance collaboration, and deliver real impact faster. Media Products media viewer No more previous content AI Agents for Product Ops It's time to automate, optimize, and accelerate your outcomes! With Prodgy, you connect your tools and supercharge product development with greater efficiency and accuracy. Transform your Product Ops with Prodgy, the AI Agents platform by Programmers! AI for product operations Your Product Ops doesn’t have to be slow. With Prodgy, AI agents trained on your business accelerate launches, automate critical processes, and maintain governance. More speed, less rework. Experience what it means to scale with intelligence. Automate Product Ops with AI Your time is valuable. With Prodgy’s AI agents, you can automate backlogs, user stories, and documentation directly in Jira, DevOps, Teams, and more. Less rework, more delivery — all without leaving your product flow. No more next content Similar products Productboard Productboard Product Management Software Aha! Academy Aha! Academy Product Management Software Product Portfolio Management Product Portfolio Management Product Management Software Producer Producer Product Management Software Dovetail Dovetail Product Management Software Interim Product Managers Interim Product Managers Product Management Software Sign in to see more 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:24 |
https://www.linkedin.com/products/stratsys-strategic-planning/?trk=products_seo_search#main-content | Stratsys platform for compliance and efficiency | LinkedIn Skip to main content LinkedIn Stratsys 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 Stratsys platform for compliance and efficiency Strategic Planning Software by Stratsys See who's skilled in this Add as skill Learn more Report this product About Stratsys offers a SaaS platform that streamlines compliance in business-critical areas such as sustainability, GRC and governance for medium to large organizations in the Nordics. Unlike other compliance tools, Stratsys takes it a step further to move organizations from reporting to action and effectively allocate responsibilities internally. For many organizations, coordination and lack of structure is a challenge, which can lead to the whole business not working towards the same goal. With Stratsys, you can easily solve these problems by bringing your work together in one place. From sustainability, risk management, quality management and much more. This product is intended for Sustainability Manager Chief Information Security Officer Head of Sustainability Sustainability Specialist Information Technology Security Specialist Information Technology Security Manager Risk Manager Chief Technology Officer Media Products media viewer No more previous content Stratsys platform Compliance made smart Samla arbetet kring regulatoriska krav i en plattform Tips på hur organisationer kan hantera de ökade regulatoriska kraven No more next content Featured customers of Stratsys platform for compliance and efficiency Stena AB Maritime 21,445 followers Vectura Real Estate 6,487 followers ALEKTUM GROUP Financial Services 6,083 followers Elenia Electric Power Transmission, Control, and Distribution 7,310 followers Avanza Bank Financial Services 88,349 followers Aleris Hospitals and Health Care 17,509 followers Svenska kraftnät Utilities 55,492 followers Vattenfall Utilities 325,018 followers MAX Burgers Restaurants 16,961 followers Länsförsäkringar Insurance 86,859 followers Bostads AB Mimer Real Estate 3,889 followers Domstolsverket Courts of Law 12,337 followers Stockholms stad Government Administration 112,744 followers Region Stockholm Government Administration 61,413 followers Pensionsmyndigheten Government Administration 18,947 followers Region Gävleborg Government Administration 10,577 followers Returpack / Pantamera Wholesale Recyclable Materials 2,262 followers Peab Construction 122,975 followers Trafikverket Government Administration 123,777 followers Göteborgs Stad Government Administration 72,231 followers JM Construction 56,642 followers Show more Show less 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 Dataport Consulting Dataport Consulting Strategic Planning Software Sign in to see more 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:24 |
https://git-scm.com/book/uz/v2/Git-%d1%81%d0%b5%d1%80%d0%b2%d0%b5%d1%80%d0%b4%d0%b0-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 The Protocols 4.2 Getting Git on a Server 4.3 Sizning SSH ochiq (public) kalitingizni generatsiyalash 4.4 Setting Up the Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Third Party Hosted Options 4.10 Хулосалар 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Account Setup and Configuration 6.2 Contributing to a Project 6.3 Maintaining a Project 6.4 Managing an organization 6.5 Scripting GitHub 6.6 Summary 7. Git Tools 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Qism modullar (Submodule) 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 Summary 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. Appendix A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. Appendix B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 4.7 Git серверда - 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="/opt/git" prefix=/usr gitweb SUBDIR gitweb SUBDIR ../ make[2]: `GIT-VERSION-FILE' is up to date. GEN gitweb.cgi GEN static/gitweb.js $ sudo cp -Rf gitweb /var/www/ Notice that you have to tell the command where to find your Git repositories with the GITWEB_PROJECTROOT variable. Now, you need to make Apache use CGI for that script, for which you can add a VirtualHost: <VirtualHost *:80> ServerName gitserver DocumentRoot /var/www/gitweb <Directory /var/www/gitweb> Options ExecCGI +FollowSymLinks +SymLinksIfOwnerMatch AllowOverride All order allow,deny Allow from all AddHandler cgi-script cgi DirectoryIndex gitweb.cgi </Directory> </VirtualHost> Again, GitWeb can be served with any CGI or Perl capable web server; if you prefer to use something else, it shouldn’t be difficult to set up. At this point, you should be able to visit http://gitserver/ to view your repositories online. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:24 |
https://www.linkedin.com/products/productplan/?trk=products_seo_search | ProductPlan | LinkedIn Skip to main content LinkedIn ProductPlan 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 ProductPlan Product Management Software by ProductPlan See who's skilled in this Add as skill Learn more Report this product About ProductPlan is the easiest way to build and share beautiful product roadmaps. Get started today with a free trial and 20+ roadmap templates. Media Products media viewer No more previous content No more next content Similar products Productboard Productboard Product Management Software Aha! Academy Aha! Academy Product Management Software Product Portfolio Management Product Portfolio Management Product Management Software Producer Producer Product Management Software Dovetail Dovetail Product Management Software Interim Product Managers Interim Product Managers Product Management Software Sign in to see more 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:24 |
https://git-scm.com/book/tl/v2/Git-sa-Server-GitLab | Git - GitLab About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 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.8 Git sa Server - GitLab GitLab Bagaman, ang GitWeb ay masyadong simple. Kung ikaw ay naghahanap na isang mas moderno, puno ng mga tampok na Git server, mayroong iilang open source na solusyon na maaari mong i-install sa halip. Dahil ang GitLab ang isa sa mga sikat, tatalakayin natin ang pag-install at paggamit nito bilang halimbawa. Ito ay mas mahirap kumpara sa opsyon ng GitWeb at maaaring mangangailangan ng mas maraming pagpapanatili, pero ito ay mas puno ng mga tapok na opsyon. Pag-install Ang GitLab ay isang database-backed na aplikasyon sa web, kaya subsob ka sa pag-install nito kumpara sa ibang mga server ng Git. Sa kabutihang-palad, ang proseso na ito ay maayos na nakadokumento at sinuportahan. Mayroong iilang mga pamamaraan para magawa mo ang pag-install ng GitLab. Para mapagana at mapatakbo ang isang bagay nang mabilisan, maaaring i-download ang isang birtwal na imahe ng makina or isang one-click na installer mula sa https://bitnami.com/stack/gitlab , at i-tweak ang pagsasaayos upang matugma sa iyong partikular na environment. Isang magandang tampok na sinali ng Bitnami ay isang login screen (ma-access sa pamamagitan ng pag-type ng alt+→); sinasabi nito sayo ang IP address at default username at password para sa na-install na GitLab. Figure 50. Ang login screen sa birtwal na makina ng Bitnami GitLab. Para sa iba pang bagay, sundin ang gabay sa Komunidad na Edisyon ng Gitlab readme, na mahahanap sa https://gitlab.com/gitlab-org/gitlab-ce/tree/master . Doon makakahanap ka ng tulong para sa pag-install ng GitLab gamit ang mga resipe ng chef, isang birtwal na makina sa Digital Ocean, at RPM at DEB na mga pakete (kung saan, sa pagsulat na ito, ay nasa beta). Mayroon ding “unofficial” na pag-gabay sa pagpapagana sa GitLab gamit ang hindi kilala na mga operating system at mga database, isang ganap na manu-manong pag-install na iskrip, at marami pang ibang mga paksa. Administrasyon Ang administrasyon sa interface ng GitLab ay maaaring ma access sa web. Simpleng tukuyin lamang ang iyong browser sa hostname at IP address kung saan naka-install ang GitLab, at mag-login bilang admin na user. Ang default na username ay admin@local.host , at ang default na password ay 5iveL!fe (na kung saan ikaw ay sasabihan na baguhin sa sandali na maka-log in ka). Kapag naka-log in na, pindutin ang “Admin area” na icon sa menu sa itaas na kanan na bahagi ng pahina. Figure 51. Ang “Admin area” na aytem sa menu ng GitLab. Mga Gumagamit Ang mga gumagamit sa GitLab ay mga account na tumutugma sa mga tao. Ang mga account ng mga gumagamit ay hindi gaano kakumplikado; higit sa lahat ito ay koleksyon ng mga personal na impormasyon na nakalakip sa datos ng login. Ang bawat account ng gumagamit ay may sariling namespace , na kung saan ay isang lohikal na pagpapangkat ng mga proyekto na nabibilang sa gumagamit na iyon. Kung ang user jane ay may proyekto na nakapangalan na proyekto , ang url ng proyekto na iyon ay http://server/jane/proyekto . Figure 52. Ang screen ng administrasyon na gumagamit sa GitLab. Mayroong dalawang paraan sa pagtanggal ng isang user. Sa “Blocking” pinipigilan ang isang gumagamit mula sa pag-login sa instansya ng GitLab, ngunit lahat ng datos sa ilalim ng namespace ng gumagamit ay mapapanatili, at ang mga commit na naka-sign ng email address ng gumagamit ay mag-link pa rin pabalik sa kanilang profile. Sa kabilang kamay, ang ‘`Destroying’ ay ganap na tinatanggal sa database at filesystem. Lahat ng mga proyekto at datos sa kanilang namespace ay tinatanggal, at anumang mga grupo na pagmamay-ari nila ay matatangal rin. Ito ay malinaw naman na isang mas permanente at mas nakakasira na galaw, at ang paggamit nito ay bihira. Mga Grupo Ang isang grupo sa GitLab ay pagtitipon ng mga proyekto, kasama ang mga datos tungkol sa kung paano ma-access ng gumagamit ang proyektong iyon. Bawat grupo ay may sariling namespace ng proyekto (tulad ng mga gumagamit), kaya kung ang grupo ng pagsasanay ay may pryoyektong materyales , ang url na iyon ay http://server/pagsasanay/materyales . Figure 53. Ang screen sa administrasyon ng grupo sa GitLab. Ang bawat grupo ay nauugnay sa ilang bilang ng mga gumagamit, bawat isa ay may antas ng mga pahintulot para sa mga proyekto ng grupo at ang grupo mismo. Ang saklaw nito ay nagmumula sa “Guest” (mga isyu at pag-chat lamang) hanggang “Owner” (buong kontrol sa grupo, mga miyembro nito, at mga proyekto nito). Masyadong marami ang mga klase ng pahintulot para malista dito, ngunit mayroong kapaki-pakinabang na link sa screen ng administrasyon ang GitLab. Mga Proyekto Halos lahat ng proyekto sa GitLab ay tumutugma sa isang repositoryo sa Git. Bawat proyekto ay nabibiling sa isang namespace, maski isang gumagamit o isang grupo. Kung ang proyekto ay nabibilang sa isang gumagamit, ang may-ari ng proyekto ay may direktang kontrol kung sino ang may access sa proyekto; kung ang proyekto ay nabibilang sa isang grupo, ang user-level na pahintulot ng grupo ang eepekto. Bawat proyekto ay may antas rin ng kakayahang makita, kung saan ay may kapangyarahin sa pag-kontrol kung sino ang may access sa pagbasa sa mga pahina at repositoryo ng proyektong iyon. Kung ang proyekto ay Private , ang may-ari ng proyekto ay dapat tahasang magbigay ng access sa partikular na gumagamit. Ang isang Internal na proyekto ay makikita ng sinuman na gumagamit na naka-log, at ang isang Public na proyekto ay makikita ng sinuman. Tandaan na ang mga ito ay kumokontrol sa git fetch na access pati na rin ang access sa web UI ng proyekto na iyon. Mga Hook Sinuportahan din ng GitLab ang mga hook, pareho sa antas ng proyekto o sistema. Para sa alinman sa mga ito, ang GitLab na server ay magsasagawa ng isang HTTP POST kasama ang iilang naglalarawang JSON sa tuwing may nagaganap na kaganapan na may kaugnayan. Ito ay isang mahusay na paraan upang i-kontekta ang iyong mga repositoryo sa Git at instansya ng GitLab sa ibang bahagi ng iyong pag-automate ng pag-unlad, tulad ng mga server ng CI, mga chat room, o mga kagamitan sa pag-deploy. Pangunahing Paggamit Ang unang bagay na gusto mong gawin gamit ang GitLab ay lumikha ng isang bagong proyekto. Ito ay ginagawa sa pamamagitan ng pag-click sa “+” na icon sa toolbar. Tatanungin ka para sa pangalan ng proyekto, kung saan na namespace ito nabibilang, at kung ano ang antas ng kakayahang makita nito. Karamihan sa mga iyong tinukoy dito ay hindi permanente, at maaaring muling maayos sa sunod sa pamamagitan ng interface sa mga setting. I-click ang “Create Project”, at tapos ka na. Kapag umiiral na ang proyekto, malamang ay gugustuhin mong kumonekta sa isang lokal na repositoryo sa Git. Bawat proyekto ay naa-access sa HTTPS o SSH, alinman ay maaaring gamiting upang i-configure ang isang remote na Git. Ang mga URL ay makikita sa itaas sa pahina ng home page ng proyekto. Para sa umiiral na lokal na repositoryo, ang utos na ito ay lilikha ng isang remote na nakapangalan na gitlab sa naka-host na lokasyon: $ git remote add gitlab https://server/namespace/project.git Kung wala kang lokal na kopya sa repositoryo, maaari mong gawin ito: $ git clone https://server/namespace/project.git Ang web UI ay nagbibigay ng access sa ilang mga kapaki-pakinabang na tanawin sa repositoryo mismo. Bawat home page ng proyekto ay nagpapakita ng kamakailang mga gawain, at mga link sa tuktok ay dadalhin ka mga tanawin ng mga file ng proyekto at ang commit log. Pakikipagtulungan Ang pinakasimpleng paraan ng pakikipagtulungan sa isang proyekto ng GitLab ay sa pamamagitan ng pagbigay access sa ibang gumagamit na direktang mag-push sa repositoryo ng Git. Maaari kang magdagdag ng miyembro sa proyekto sa pamamagitan ng pagpunta sa “Members” na seksyon ng mga setting ng proyekto, at pag-uugnay sa bagong gumagamit ng antas ng pag-access (ang iba’t ibang mga antas ng pag-access ay tinalakay ng kaunti sa Mga Grupo ). Sa pamamagitan ng pagbigay sa isang gumagamit ng antas ng pag-access na “Developer” o mataas pa, ang user na iyon ay maaaring mag push ng direkta ng mga commit at mga branch sa repositoryo ng walang parusa. Isa pa, ang isang mas decoupled na paraan ng kolaborasyon ay sa pamamagitan ng paggamit ng mga merge na request. Ang tampok na ito ay nagbibigay daan para sa sinumang gumagamit na nakakakita sa proyekto na mag-ambag sa isang kontrolado na paraan. Ang mga gumagamit na may direktang access ay maaaring gumawa ng branch, mag-push ng mga commit sa branch na iyon, at mag open ng isang merge na request mula sa kanilang branch pabalik sa master o anumang ibang branch. Ang mga gumagamit na walang pahintulot na mag-push sa isang repositoryo ay maaaring mag “fork” nito (gumawa ng sariling kopya), mag push ng mga commit sa iyong kopya, at mag bukas ng isang merge na request mula sa kanilang fork pabalik sa pangunahing proyekto. Ang modelong ito ay nagpapahintulot sa mga may-ari na magkaroon ng buong kontrol kung ano ang pumapasok sa repositoryo at kailan, habang nagpapahintulot sa mga kontribusyon mula sa hindi pinagkakatiwalaan na mga gumagamit. Ang mga merge na request at mga isyu ay ang mga pangunahing yunit ng matagal na nabubuhay na diskusyon sa GitLab. Bawat merge na request ay nagpapahintulot ng bawat linya na diskusyon sa iminungkahi na pagbabago (na sumusuporta sa isang magaan na klase ng pagsusuri sa code), pati na rin ang isang thread para sa pangkalahatang talakayan. Parehong maaaring italaga sa mga gumagamit, o organisado sa mga milestones. Ang seksyon na ito ay nakatuon sa mga may kaugnayan sa Git na tampok ng GitLab, pero bilang isang ganap na proyekto, nagbibigay ito ng marami pang iba na mga tampok upang makatulong sa inyong koponon na magtulungan, tulad ng mga wiki sa proyekto at mga kagamitan para sa pagpapanatili ng sistema. Isang benepisyo ng GitLab ay, kapag ang server ay naka-set up na, bihira mo na kailangan baguhin ang file ng pagsasaayos o i-access ang server gamit ang SSH; karamihan sa administrasyon at pangunahing paggamit ay maaaring matupad sa pamamagitan ng interface sa browser. 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/de/v2/Git-Grundlagen-Git-Aliases | Git - Git Aliases About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Erste Schritte 1.1 Was ist Versionsverwaltung? 1.2 Kurzer Überblick über die Historie von Git 1.3 Was ist Git? 1.4 Die Kommandozeile 1.5 Git installieren 1.6 Git Basis-Konfiguration 1.7 Hilfe finden 1.8 Zusammenfassung 2. Git Grundlagen 2.1 Ein Git-Repository anlegen 2.2 Änderungen nachverfolgen und im Repository speichern 2.3 Anzeigen der Commit-Historie 2.4 Ungewollte Änderungen rückgängig machen 2.5 Mit Remotes arbeiten 2.6 Taggen 2.7 Git Aliases 2.8 Zusammenfassung 3. Git Branching 3.1 Branches auf einen Blick 3.2 Einfaches Branching und Merging 3.3 Branch-Management 3.4 Branching-Workflows 3.5 Remote-Branches 3.6 Rebasing 3.7 Zusammenfassung 4. Git auf dem Server 4.1 Die Protokolle 4.2 Git auf einem Server einrichten 4.3 Erstellung eines SSH-Public-Keys 4.4 Einrichten des Servers 4.5 Git-Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Von Drittanbietern gehostete Optionen 4.10 Zusammenfassung 5. Verteiltes Git 5.1 Verteilter Arbeitsablauf 5.2 An einem Projekt mitwirken 5.3 Ein Projekt verwalten 5.4 Zusammenfassung 6. GitHub 6.1 Einrichten und Konfigurieren eines Kontos 6.2 Mitwirken an einem Projekt 6.3 Ein Projekt betreuen 6.4 Verwalten einer Organisation 6.5 Skripte mit GitHub 6.6 Zusammenfassung 7. Git Tools 7.1 Revisions-Auswahl 7.2 Interaktives Stagen 7.3 Stashen und Bereinigen 7.4 Deine Arbeit signieren 7.5 Suchen 7.6 Den Verlauf umschreiben 7.7 Reset entzaubert 7.8 Fortgeschrittenes Merging 7.9 Rerere 7.10 Debuggen mit Git 7.11 Submodule 7.12 Bundling 7.13 Replace (Ersetzen) 7.14 Anmeldeinformationen speichern 7.15 Zusammenfassung 8. Git einrichten 8.1 Git Konfiguration 8.2 Git-Attribute 8.3 Git Hooks 8.4 Beispiel für Git-forcierte Regeln 8.5 Zusammenfassung 9. Git und andere VCS-Systeme 9.1 Git als Client 9.2 Migration zu Git 9.3 Zusammenfassung 10. Git Interna 10.1 Basisbefehle und Standardbefehle (Plumbing and Porcelain) 10.2 Git Objekte 10.3 Git Referenzen 10.4 Packdateien (engl. Packfiles) 10.5 Die Referenzspezifikation (engl. Refspec) 10.6 Transfer Protokolle 10.7 Wartung und Datenwiederherstellung 10.8 Umgebungsvariablen 10.9 Zusammenfassung A1. Anhang A: Git in anderen Umgebungen A1.1 Grafische Schnittstellen A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Zusammenfassung A2. Anhang B: Git in deine Anwendungen einbetten A2.1 Die Git-Kommandozeile A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Anhang C: Git Kommandos A3.1 Setup und Konfiguration A3.2 Projekte importieren und erstellen A3.3 Einfache Snapshot-Funktionen A3.4 Branching und Merging A3.5 Projekte gemeinsam nutzen und aktualisieren A3.6 Kontrollieren und Vergleichen A3.7 Debugging A3.8 Patchen bzw. Fehlerkorrektur A3.9 E-mails A3.10 Externe Systeme A3.11 Administration A3.12 Basisbefehle 2nd Edition 2.7 Git Grundlagen - Git Aliases Git Aliases Bevor wir dieses Kapitel über Basic Git abschließen, gibt es noch einen kurzen Tipp, der deine Arbeit mit Git einfacher, leichter und verständlicher machen kann: Aliase. Der Klarheit halber werden wir sie nirgendwo anders in diesem Buch verwenden, aber wenn du Git in Zukunft regelmäßig verwendest, dann sind Aliase etwas, das du kennen solltest. Git erkennt nicht automatisch deinen abgesetzten Befehl, wenn du ihn nur teilweise eingibst. Wenn du nicht den gesamten Text jedes Git-Befehls eingeben möchtest, könntest du mit Hilfe von git config einfach ein Alias für jeden Befehl einrichten. Hier sind ein paar Beispiele, die du einrichten sollten: $ git config --global alias.co checkout $ git config --global alias.br branch $ git config --global alias.ci commit $ git config --global alias.st status Das bedeutet, dass du z.B. anstelle von git commit einfach git ci eingeben kannst. Je mehr du Git verwendest, wirst du vermutlich noch andere Befehle häufiger verwenden; scheue dich nicht, neue Aliase zu erstellen. Diese Technik kann auch sehr nützlich sein, um Befehle zu erstellen, von denen du glaubst, dass sie vorhanden sein sollten. Um beispielsweise ein Usability-Problem zu beheben, auf das du beim Entfernen einer Datei aus der Staging-Area stößt, kannst du Git deinen eigenen Unstage-Alias hinzufügen: $ git config --global alias.unstage 'reset HEAD --' Dadurch sind die folgenden beiden Befehle gleichwertig: $ git unstage fileA $ git reset HEAD -- fileA Das macht denn Sinn des aliasing hoffentlich klarer. Es ist auch üblich, einen last (dt. letzten) Befehl hinzuzufügen, so wie hier: $ git config --global alias.last 'log -1 HEAD' Auf diese Weise kannst du den letzten Commit leicht auffinden: $ 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> Wie du siehst, ersetzt Git den neuen Befehl einfach durch den Alias, den du ihn geben hast. Vielleicht möchtest du jedoch eher einen externen Befehl als einen Git-Subbefehl ausführen. In diesem Fall starte den Befehl mit einem Ausrufezeichen ( ! ). Das ist hilfreich, wenn du deine eigenen Tools schreibst, die mit einem Git-Repository arbeiten. Hier ein Beispiel, in dem wir git visual mit gitk aliasen: $ 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/pinterest#param-posts-to-not-include | 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://www.linkedin.com/products/productboard/?trk=products_seo_search | Productboard | LinkedIn Skip to main content LinkedIn Productboard 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 Productboard Product Management Software by Productboard See who's skilled in this Add as skill Learn more Report this product About Productboard is the leading customer-centric product management platform that empowers teams to get the right products to market, faster. It provides a complete solution for product teams to understand user needs, prioritize what to build next, align everyone on the roadmap, and engage with their customers. Productboard is easy to use, enables company-wide collaboration, and integrates into existing workflows. Over 6,000 organizations around the world use Productboard to build excellent products. Get started with a two week free trial! This product is intended for Product Manager Executive Sales Executive Product Marketing Manager Product Designer Software Engineering Manager Head of Product Product Owner Customer Success Manager User Experience Researcher Media Products media viewer No more previous content Introducing Productboard Productboard is a customer-driven product management system that empowers teams to get the right products to market, faster. Productboard Prioritization Prioritize the features your customers need See which features customers need the most. Standardize your prioritization framework and ensure product objectives support company goals. Productboard Roadmaps Align everyone around the roadmap Share beautiful product roadmaps tailored for different audiences that always stay up-to-date. Improve cross-functional collaboration. Productboard Portal Validate feature ideas, share updates, and capture new ideas from your customers on a public Portal to build products that drive revenue. Productboard Insights Define your product vision with customer feedback Consolidate customer feedback from any source into a single repository. Identify trends around what users really need. No more next content Featured customers of Productboard Delivery Hero Technology, Information and Internet 319,520 followers PSafe US IT Services and IT Consulting 1,635 followers Microsoft Software Development 27,296,747 followers Revenue.io Software Development 14,963 followers BigCommerce Software Development 151,491 followers Cloudinary Technology, Information and Internet 61,404 followers Metromile Insurance 14,402 followers Lessonly (now Seismic Learning) Software Development 19,197 followers Dashlane Computer and Network Security 30,408 followers Zendesk Software Development 648,235 followers DANA Indonesia IT Services and IT Consulting 247,500 followers Slack Technology, Information and Internet 1,714,426 followers Tray.ai Software Development 22,953 followers Avast Computer and Network Security 43,160 followers Fastly Software Development 64,600 followers UiPath Software Development 510,737 followers 1-800 Contacts Retail Health and Personal Care Products 6,757 followers OutSystems Software Development 175,871 followers HERE Technologies IT Services and IT Consulting 265,055 followers Amplitude Software Development 103,066 followers Show more Show less Similar products Aha! Academy Aha! Academy Product Management Software Product Portfolio Management Product Portfolio Management Product Management Software Producer Producer Product Management Software Dovetail Dovetail Product Management Software Interim Product Managers Interim Product Managers Product Management Software Aha! Discovery Aha! Discovery Product Management Software Sign in to see more 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:24 |
https://git-scm.com/book/tl/v2/Pagsisimula-Pagkuha-ng-Tulong | Git - Pagkuha ng Tulong About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Pagsisimula 1.1 Tungkol sa Bersyon Kontrol 1.2 Isang Maikling Kasaysayan ng Git 1.3 Pangunahing Kaalaman sa Git 1.4 Ang Command Line 1.5 Pag-install ng Git 1.6 Unang Beses na Pag-Setup ng Git 1.7 Pagkuha ng Tulong 1.8 Buod 2. Mga Pangunahing Kaalaman sa Git 2.1 Pagkuha ng Repositoryo ng Git 2.2 Pagtatala ng mga Pagbabago sa Repositoryo 2.3 Pagtitingin sa Kasaysayan ng Commit 2.4 Pag-Undo ng mga Bagay 2.5 Paggawa gamit ang mga Remote 2.6 Pag-tag 2.7 Mga Alyas sa Git 2.8 Buod 3. Pag-branch ng Git 3.1 Mga Branch sa Maikling Salita 3.2 Batayan ng Pag-branch at Pag-merge 3.3 Pamamahala ng Branch 3.4 Mga Daloy ng Trabaho sa Pag-branch 3.5 Remote na mga Branch 3.6 Pag-rebase 3.7 Buod 4. Git sa Server 4.1 Ang Mga Protokol 4.2 Pagkuha ng Git sa isang Server 4.3 Ang paglikha ng iyong Pampublikong Susi ng SSH 4.4 Pag-Setup ng Server 4.5 Git Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Mga Opsyon ng Naka-host sa Third Party 4.10 Buod 5. Distributed Git 5.1 Distributed Workflows 5.2 Contributing to a Project 5.3 Maintaining a Project 5.4 Summary 6. GitHub 6.1 Pag-setup at pagsasaayos ng Account 6.2 Pag-aambag sa isang Proyekto 6.3 Pagpapanatili ng isang Proyekto 6.4 Pamamahala ng isang organisasyon 6.5 Pag-iiskrip sa GitHub 6.6 Buod 7. Mga Git na Kasangkapan 7.1 Pagpipili ng Rebisyon 7.2 Staging na Interactive 7.3 Pag-stash at Paglilinis 7.4 Pag-sign sa Iyong Trabaho 7.5 Paghahanap 7.6 Pagsulat muli ng Kasaysayan 7.7 Ang Reset Demystified 7.8 Advanced na Pag-merge 7.9 Ang Rerere 7.10 Pagdebug gamit ang Git 7.11 Mga Submodule 7.12 Pagbibigkis 7.13 Pagpapalit 7.14 Kredensyal na ImbakanCredential Storage 7.15 Buod 8. Pag-aangkop sa Sariling Pangangailagan ng Git 8.1 Kompigurasyon ng Git 8.2 Mga Katangian ng Git 8.3 Mga Hook ng Git 8.4 An Example Git-Enforced Policy 8.5 Buod 9. Ang Git at iba pang mga Sistema 9.1 Git bilang isang Kliyente 9.2 Paglilipat sa Git 9.3 Buod 10. Mga Panloob ng GIT 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 Ang Refspec 10.6 Transfer Protocols 10.7 Pagpapanatili At Pagbalik ng Datos 10.8 Mga Variable sa Kapaligiran 10.9 Buod A1. Appendix A: Git in Other Environments A1.1 Grapikal Interfaces A1.2 Git in Visual Studio A1.3 Git sa Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git sa Powershell A1.7 Summary A2. Appendix B: Pag-embed ng Git sa iyong Mga Aplikasyon A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. Appendix C: Mga Kautusan ng Git A3.1 Setup at Config A3.2 Pagkuha at Paglikha ng Mga Proyekto A3.3 Pangunahing Snapshotting A3.4 Branching at Merging A3.5 Pagbabahagi at Pagbabago ng mga Proyekto A3.6 Pagsisiyasat at Paghahambing A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Pagtutuberong mga Utos 2nd Edition 1.7 Pagsisimula - Pagkuha ng Tulong Pagkuha ng Tulong Kung kakailanganin mo ng tulong habang gumagamit ng Git, mayroong dalawang magkaparehong pamamaraan para makakuha ka ng komprehensibong manual na pahina (manpage) na tulong para sa kahit anong mga command sa Git: $ git help <verb> $ man git-<verb> Halimbawa, maaari kang kumuha ng manpage na tulong para sa git config na command sa pamamagitan ng pagpapatakbo ng $ git help config Ang mga utos na ito ay maganda dahil maaari mo itong magamit kahit saan, kahit na offline. Kung ang mga manpages at ang aklat na ito ay hindi sapat at nangangailangan ka ng personal na tulong, maaaring mong subukan ang #git o #github na channel sa Freenode IRC server (irc.freenode.net). Ang mga channel na ito ay palaging napupuno ng daan-daang mga tao na may napakaraming nalalaman tungkol sa Git at kadalasan sila ay gustong makatulong. Bukod pa dito, kung hindi mo kailangan ang buong manpage na tulong, at nangangailangan ka lang ng madaliang refresher sa mga magagamit na mga opsyon para sa isang Git na command, maaari kang maghingi ng mas pinaikling “tulong” na output gamit ang -h o --help na mga opsyon, gaya ng: $ git add -h usage: git add [<options>] [--] <pathspec>... -n, --dry-run dry run -v, --verbose be verbose -i, --interactive interactive picking -p, --patch select hunks interactively -e, --edit edit current diff and apply -f, --force allow adding otherwise ignored files -u, --update update tracked files -N, --intent-to-add record only the fact that the path will be added later -A, --all add changes from all tracked and untracked files --ignore-removal ignore paths removed in the working tree (same as --no-all) --refresh don't add, only refresh the index --ignore-errors just skip files which cannot be added because of errors --ignore-missing check if - even missing - files are ignored in dry run --chmod <(+/-)x> override the executable bit of the listed files 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.linkedin.com/products/stratsys-strategic-planning?similarProducts=true&trk=products_details_guest_similar_products_section_sign_in | Stratsys platform for compliance and efficiency | LinkedIn Skip to main content LinkedIn Stratsys 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 Stratsys platform for compliance and efficiency Strategic Planning Software by Stratsys See who's skilled in this Add as skill Learn more Report this product About Stratsys offers a SaaS platform that streamlines compliance in business-critical areas such as sustainability, GRC and governance for medium to large organizations in the Nordics. Unlike other compliance tools, Stratsys takes it a step further to move organizations from reporting to action and effectively allocate responsibilities internally. For many organizations, coordination and lack of structure is a challenge, which can lead to the whole business not working towards the same goal. With Stratsys, you can easily solve these problems by bringing your work together in one place. From sustainability, risk management, quality management and much more. This product is intended for Sustainability Manager Chief Information Security Officer Head of Sustainability Sustainability Specialist Information Technology Security Specialist Information Technology Security Manager Risk Manager Chief Technology Officer Media Products media viewer No more previous content Stratsys platform Compliance made smart Samla arbetet kring regulatoriska krav i en plattform Tips på hur organisationer kan hantera de ökade regulatoriska kraven No more next content Featured customers of Stratsys platform for compliance and efficiency Stena AB Maritime 21,445 followers Vectura Real Estate 6,487 followers ALEKTUM GROUP Financial Services 6,083 followers Elenia Electric Power Transmission, Control, and Distribution 7,310 followers Avanza Bank Financial Services 88,349 followers Aleris Hospitals and Health Care 17,509 followers Svenska kraftnät Utilities 55,492 followers Vattenfall Utilities 325,018 followers MAX Burgers Restaurants 16,961 followers Länsförsäkringar Insurance 86,859 followers Bostads AB Mimer Real Estate 3,889 followers Domstolsverket Courts of Law 12,337 followers Stockholms stad Government Administration 112,744 followers Region Stockholm Government Administration 61,413 followers Pensionsmyndigheten Government Administration 18,947 followers Region Gävleborg Government Administration 10,577 followers Returpack / Pantamera Wholesale Recyclable Materials 2,262 followers Peab Construction 122,975 followers Trafikverket Government Administration 123,777 followers Göteborgs Stad Government Administration 72,231 followers JM Construction 56,642 followers Show more Show less 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 Dataport Consulting Dataport Consulting Strategic Planning Software Sign in to see more 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:24 |
https://www.linkedin.com/products/aha-labs-inc--aha-discovery/?trk=products_seo_search | Aha! Discovery | 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! Discovery Product Management Software by Aha! See who's skilled in this Add as skill Get started Report this product About Aha! Discovery is the new way to manage customer interviews — centralize meeting transcripts, uncover key product insights, and link them to your roadmap. This product is intended for Product Manager User Experience Researcher User Experience Designer Media Products media viewer No more previous content Aha! Discovery - Analyze customer interviews Review transcripts with AI. Quickly derive valuable learnings, quotes, and new ideas from customer interviews to inform your product discovery efforts. Aha! Discovery - Validate plans with customer feedback Turn insights into action. Create a customer-informed roadmap through productive conversations with your users. Aha! Discovery - Learn from your customers Manage user interviews. Capture the voice of the customer the old-fashioned way — talk to them to understand their challenges and uncover key insights. Aha! Discovery - Centralize customer research Organize your product discovery work. Manage all types of research — from initiative validation to feature feedback prioritization and usability testing — in one place. No more next content Similar products Productboard Productboard Product Management Software Aha! Academy Aha! Academy Product Management Software Product Portfolio Management Product Portfolio Management Product Management Software Producer Producer Product Management Software Dovetail Dovetail Product Management Software Interim Product Managers Interim Product Managers Product 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! Ideas Aha! Ideas Idea Management Software Aha! Knowledge Aha! Knowledge Knowledge 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:24 |
https://git-scm.com/book/tl/v2/Git-sa-Server-GitLab | Git - GitLab About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 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.8 Git sa Server - GitLab GitLab Bagaman, ang GitWeb ay masyadong simple. Kung ikaw ay naghahanap na isang mas moderno, puno ng mga tampok na Git server, mayroong iilang open source na solusyon na maaari mong i-install sa halip. Dahil ang GitLab ang isa sa mga sikat, tatalakayin natin ang pag-install at paggamit nito bilang halimbawa. Ito ay mas mahirap kumpara sa opsyon ng GitWeb at maaaring mangangailangan ng mas maraming pagpapanatili, pero ito ay mas puno ng mga tapok na opsyon. Pag-install Ang GitLab ay isang database-backed na aplikasyon sa web, kaya subsob ka sa pag-install nito kumpara sa ibang mga server ng Git. Sa kabutihang-palad, ang proseso na ito ay maayos na nakadokumento at sinuportahan. Mayroong iilang mga pamamaraan para magawa mo ang pag-install ng GitLab. Para mapagana at mapatakbo ang isang bagay nang mabilisan, maaaring i-download ang isang birtwal na imahe ng makina or isang one-click na installer mula sa https://bitnami.com/stack/gitlab , at i-tweak ang pagsasaayos upang matugma sa iyong partikular na environment. Isang magandang tampok na sinali ng Bitnami ay isang login screen (ma-access sa pamamagitan ng pag-type ng alt+→); sinasabi nito sayo ang IP address at default username at password para sa na-install na GitLab. Figure 50. Ang login screen sa birtwal na makina ng Bitnami GitLab. Para sa iba pang bagay, sundin ang gabay sa Komunidad na Edisyon ng Gitlab readme, na mahahanap sa https://gitlab.com/gitlab-org/gitlab-ce/tree/master . Doon makakahanap ka ng tulong para sa pag-install ng GitLab gamit ang mga resipe ng chef, isang birtwal na makina sa Digital Ocean, at RPM at DEB na mga pakete (kung saan, sa pagsulat na ito, ay nasa beta). Mayroon ding “unofficial” na pag-gabay sa pagpapagana sa GitLab gamit ang hindi kilala na mga operating system at mga database, isang ganap na manu-manong pag-install na iskrip, at marami pang ibang mga paksa. Administrasyon Ang administrasyon sa interface ng GitLab ay maaaring ma access sa web. Simpleng tukuyin lamang ang iyong browser sa hostname at IP address kung saan naka-install ang GitLab, at mag-login bilang admin na user. Ang default na username ay admin@local.host , at ang default na password ay 5iveL!fe (na kung saan ikaw ay sasabihan na baguhin sa sandali na maka-log in ka). Kapag naka-log in na, pindutin ang “Admin area” na icon sa menu sa itaas na kanan na bahagi ng pahina. Figure 51. Ang “Admin area” na aytem sa menu ng GitLab. Mga Gumagamit Ang mga gumagamit sa GitLab ay mga account na tumutugma sa mga tao. Ang mga account ng mga gumagamit ay hindi gaano kakumplikado; higit sa lahat ito ay koleksyon ng mga personal na impormasyon na nakalakip sa datos ng login. Ang bawat account ng gumagamit ay may sariling namespace , na kung saan ay isang lohikal na pagpapangkat ng mga proyekto na nabibilang sa gumagamit na iyon. Kung ang user jane ay may proyekto na nakapangalan na proyekto , ang url ng proyekto na iyon ay http://server/jane/proyekto . Figure 52. Ang screen ng administrasyon na gumagamit sa GitLab. Mayroong dalawang paraan sa pagtanggal ng isang user. Sa “Blocking” pinipigilan ang isang gumagamit mula sa pag-login sa instansya ng GitLab, ngunit lahat ng datos sa ilalim ng namespace ng gumagamit ay mapapanatili, at ang mga commit na naka-sign ng email address ng gumagamit ay mag-link pa rin pabalik sa kanilang profile. Sa kabilang kamay, ang ‘`Destroying’ ay ganap na tinatanggal sa database at filesystem. Lahat ng mga proyekto at datos sa kanilang namespace ay tinatanggal, at anumang mga grupo na pagmamay-ari nila ay matatangal rin. Ito ay malinaw naman na isang mas permanente at mas nakakasira na galaw, at ang paggamit nito ay bihira. Mga Grupo Ang isang grupo sa GitLab ay pagtitipon ng mga proyekto, kasama ang mga datos tungkol sa kung paano ma-access ng gumagamit ang proyektong iyon. Bawat grupo ay may sariling namespace ng proyekto (tulad ng mga gumagamit), kaya kung ang grupo ng pagsasanay ay may pryoyektong materyales , ang url na iyon ay http://server/pagsasanay/materyales . Figure 53. Ang screen sa administrasyon ng grupo sa GitLab. Ang bawat grupo ay nauugnay sa ilang bilang ng mga gumagamit, bawat isa ay may antas ng mga pahintulot para sa mga proyekto ng grupo at ang grupo mismo. Ang saklaw nito ay nagmumula sa “Guest” (mga isyu at pag-chat lamang) hanggang “Owner” (buong kontrol sa grupo, mga miyembro nito, at mga proyekto nito). Masyadong marami ang mga klase ng pahintulot para malista dito, ngunit mayroong kapaki-pakinabang na link sa screen ng administrasyon ang GitLab. Mga Proyekto Halos lahat ng proyekto sa GitLab ay tumutugma sa isang repositoryo sa Git. Bawat proyekto ay nabibiling sa isang namespace, maski isang gumagamit o isang grupo. Kung ang proyekto ay nabibilang sa isang gumagamit, ang may-ari ng proyekto ay may direktang kontrol kung sino ang may access sa proyekto; kung ang proyekto ay nabibilang sa isang grupo, ang user-level na pahintulot ng grupo ang eepekto. Bawat proyekto ay may antas rin ng kakayahang makita, kung saan ay may kapangyarahin sa pag-kontrol kung sino ang may access sa pagbasa sa mga pahina at repositoryo ng proyektong iyon. Kung ang proyekto ay Private , ang may-ari ng proyekto ay dapat tahasang magbigay ng access sa partikular na gumagamit. Ang isang Internal na proyekto ay makikita ng sinuman na gumagamit na naka-log, at ang isang Public na proyekto ay makikita ng sinuman. Tandaan na ang mga ito ay kumokontrol sa git fetch na access pati na rin ang access sa web UI ng proyekto na iyon. Mga Hook Sinuportahan din ng GitLab ang mga hook, pareho sa antas ng proyekto o sistema. Para sa alinman sa mga ito, ang GitLab na server ay magsasagawa ng isang HTTP POST kasama ang iilang naglalarawang JSON sa tuwing may nagaganap na kaganapan na may kaugnayan. Ito ay isang mahusay na paraan upang i-kontekta ang iyong mga repositoryo sa Git at instansya ng GitLab sa ibang bahagi ng iyong pag-automate ng pag-unlad, tulad ng mga server ng CI, mga chat room, o mga kagamitan sa pag-deploy. Pangunahing Paggamit Ang unang bagay na gusto mong gawin gamit ang GitLab ay lumikha ng isang bagong proyekto. Ito ay ginagawa sa pamamagitan ng pag-click sa “+” na icon sa toolbar. Tatanungin ka para sa pangalan ng proyekto, kung saan na namespace ito nabibilang, at kung ano ang antas ng kakayahang makita nito. Karamihan sa mga iyong tinukoy dito ay hindi permanente, at maaaring muling maayos sa sunod sa pamamagitan ng interface sa mga setting. I-click ang “Create Project”, at tapos ka na. Kapag umiiral na ang proyekto, malamang ay gugustuhin mong kumonekta sa isang lokal na repositoryo sa Git. Bawat proyekto ay naa-access sa HTTPS o SSH, alinman ay maaaring gamiting upang i-configure ang isang remote na Git. Ang mga URL ay makikita sa itaas sa pahina ng home page ng proyekto. Para sa umiiral na lokal na repositoryo, ang utos na ito ay lilikha ng isang remote na nakapangalan na gitlab sa naka-host na lokasyon: $ git remote add gitlab https://server/namespace/project.git Kung wala kang lokal na kopya sa repositoryo, maaari mong gawin ito: $ git clone https://server/namespace/project.git Ang web UI ay nagbibigay ng access sa ilang mga kapaki-pakinabang na tanawin sa repositoryo mismo. Bawat home page ng proyekto ay nagpapakita ng kamakailang mga gawain, at mga link sa tuktok ay dadalhin ka mga tanawin ng mga file ng proyekto at ang commit log. Pakikipagtulungan Ang pinakasimpleng paraan ng pakikipagtulungan sa isang proyekto ng GitLab ay sa pamamagitan ng pagbigay access sa ibang gumagamit na direktang mag-push sa repositoryo ng Git. Maaari kang magdagdag ng miyembro sa proyekto sa pamamagitan ng pagpunta sa “Members” na seksyon ng mga setting ng proyekto, at pag-uugnay sa bagong gumagamit ng antas ng pag-access (ang iba’t ibang mga antas ng pag-access ay tinalakay ng kaunti sa Mga Grupo ). Sa pamamagitan ng pagbigay sa isang gumagamit ng antas ng pag-access na “Developer” o mataas pa, ang user na iyon ay maaaring mag push ng direkta ng mga commit at mga branch sa repositoryo ng walang parusa. Isa pa, ang isang mas decoupled na paraan ng kolaborasyon ay sa pamamagitan ng paggamit ng mga merge na request. Ang tampok na ito ay nagbibigay daan para sa sinumang gumagamit na nakakakita sa proyekto na mag-ambag sa isang kontrolado na paraan. Ang mga gumagamit na may direktang access ay maaaring gumawa ng branch, mag-push ng mga commit sa branch na iyon, at mag open ng isang merge na request mula sa kanilang branch pabalik sa master o anumang ibang branch. Ang mga gumagamit na walang pahintulot na mag-push sa isang repositoryo ay maaaring mag “fork” nito (gumawa ng sariling kopya), mag push ng mga commit sa iyong kopya, at mag bukas ng isang merge na request mula sa kanilang fork pabalik sa pangunahing proyekto. Ang modelong ito ay nagpapahintulot sa mga may-ari na magkaroon ng buong kontrol kung ano ang pumapasok sa repositoryo at kailan, habang nagpapahintulot sa mga kontribusyon mula sa hindi pinagkakatiwalaan na mga gumagamit. Ang mga merge na request at mga isyu ay ang mga pangunahing yunit ng matagal na nabubuhay na diskusyon sa GitLab. Bawat merge na request ay nagpapahintulot ng bawat linya na diskusyon sa iminungkahi na pagbabago (na sumusuporta sa isang magaan na klase ng pagsusuri sa code), pati na rin ang isang thread para sa pangkalahatang talakayan. Parehong maaaring italaga sa mga gumagamit, o organisado sa mga milestones. Ang seksyon na ito ay nakatuon sa mga may kaugnayan sa Git na tampok ng GitLab, pero bilang isang ganap na proyekto, nagbibigay ito ng marami pang iba na mga tampok upang makatulong sa inyong koponon na magtulungan, tulad ng mga wiki sa proyekto at mga kagamitan para sa pagpapanatili ng sistema. Isang benepisyo ng GitLab ay, kapag ang server ay naka-set up na, bihira mo na kailangan baguhin ang file ng pagsasaayos o i-access ang server gamit ang SSH; karamihan sa administrasyon at pangunahing paggamit ay maaaring matupad sa pamamagitan ng interface sa browser. 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=es_AR | Freedom World - Apps on Google Play Games Apps Books Kids google_logo Play Games Apps Books Kids none search help_outline Sign in with Google play_apps Library & devices payment Payments & subscriptions reviews My Play activity redeem Offers Play Pass Personalization in Play settings Settings Privacy Policy • Terms of Service Games Apps Books Kids Freedom World Bitazza Company Limited 100K+ Downloads Rated for 3+ info Install Share Add to wishlist About this app arrow_forward Freedom World – Chat, Make Friends, Earn Points, and Redeem Real Rewards! Freedom World is an all-in-one community platform that lets you chat, connect, and make new friends easily through a user-friendly chat app. Enjoy a variety of fun missions to collect “Freedom Shards” and redeem them for real rewards – no extra cost. The more you engage, the more you get! One app, endless fun – community, games, and rewards in one place! Whether you're looking to chat, find friends with similar interests, or enjoy rewarding activities, Freedom World is the app for you! Join interest-based communities – finance, gaming, lifestyle, restaurants, top shops, and more – and easily connect and chat with new people through our smooth chat and social feed features. Plus, enjoy live streaming to keep up with real-time content and entertainment. Complete fun missions to collect Freedom Shards and exchange them for exclusive prizes – from in-app rewards to gift cards and real products. Every shard you earn has real value! 🎮 Battle on with “The Scape” – our strategy card game Fight, train your tactics, and collect shards to redeem rewards. Complete daily missions and start earning right away! 💡 Why choose Freedom World? ■ Make new friends – chat, play, and connect based on shared interests ■ Smooth, user-friendly chat and messaging system ■ Join communities that match your interests – from gaming and finance to lifestyle ■ Enjoy live streaming – stay updated with knowledge or entertainment in real time ■ Collect Freedom Shards and redeem real rewards – no hidden costs ■ Join branded missions and campaigns – the more you join, the more you earn 🎁 What kind of rewards can you get? Use the points you collect from chatting, playing games, or engaging with communities to redeem: ■ Gift cards from leading stores ■ Limited edition items ■ Discount codes ■ Everyday essentials ■ And many more rewards, updated regularly! Whether you're here to make friends, chat, share stories, or earn and redeem points – Freedom World has everything you need to have fun every day. Download now and start your shard-earning journey today! Updated on Nov 20, 2025 Social Data safety arrow_forward Safety starts with understanding how developers collect and share your data. Data privacy and security practices may vary based on your use, region, and age. The developer provided this information and may update it over time. No data shared with third parties Learn more about how developers declare sharing This app may collect these data types Personal info, Financial info, and App info and performance Data is encrypted in transit You can request that data be deleted See details What’s new Bug fixes and Improvements flag Flag as inappropriate App support expand_more public Website email Support email support@freedom.world shield Privacy Policy About the developer BITAZZA COMPANY LIMITED hamidreza.momeni@bitazza.com 2922/280 New Phetchaburi Road 24 Floor HUAI KHWANG 10310 Thailand +49 1590 1400651 Similar apps arrow_forward TCG Card Value Scanner - Shiny Shiny Cardboard LLC Ronin Wallet Sky Mavis Pte. Ltd. 4.0 star Wombat - Powered by PlayMind PlayMind 5.0 star Ledger Wallet™ crypto app Ledger 4.7 star Tykr: Confident Investing Tykr LLC Seeking Alpha: News & Analysis SeekingAlpha 4.6 star flag Flag as inappropriate Google Play Play Pass Play Points Gift cards Redeem Refund policy Kids & family Parent Guide Family sharing Terms of Service Privacy About Google Play Developers Google Store All prices include VAT. South Korea (English (United States)) 상호명: Google LLC. | 대표자: Sundar Pichai | 주소: 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | 고객센터: 080-085-1500 (무료) / gpk-usersupport@google.com | 호스팅 서비스 제공: Google LLC. | 사업자정보 Google Play에 등록된 앱과 게임은 각 개발자가 제공하고 판매하는 것이며, Google LLC가 개발자로 표시된 앱과 게임 이외에 Pla | 2026-01-13T09:29:24 |
https://www.linkedin.com/products/getproductpeople-interim-product-managers/?trk=products_seo_search | Interim Product Managers | LinkedIn Skip to main content LinkedIn Product People 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 Interim Product Managers Product Management Software by Product People See who's skilled in this Add as skill Learn more Report this product About Our Interim/Fractional Product Managers/Owners, Product Ops, or Product Leaders cover parental leaves, scale your Product Management team quickly, or lead key initiatives while bridging the gap until a full-time employee joins. We onboard fast, align teams and deliver outcomes. We’re not recruiters. We don’t source candidates, this would be a conflict of interest with our interim work. Our in-house Product Managers acting as Interims in your company can appraise/create a hiring process and onboard your hires once they join. We’re not a freelance marketplace. We play long-term games with long-term people. Our team is full-time on our payroll. They join us via a 7-step recruitment process. We tender to their career growth with coaching and 360 feedback every 3 months. We’re not a software development agency. We specialize in Interim Product Management (including Product Ops). If you need developers or designers, we can connect you to a few firms we’ve worked with. This product is intended for Chief Product Officer Vice President of Product Management Director of Product Management Senior Product Manager Product Manager Technical Product Manager Product Data Manager Program Manager Project Management Officer Product Owner Media Products media viewer No more previous content What We Do: Interim Product Managers What We Don't Do Use Cases We Cover Personal Intro Mirela Mus, Founder & CPO at Product People No more next content Featured customers of Interim Product Managers TIER Mobility Software Development 57,032 followers Freenow Internet Marketplace Platforms 69,124 followers Zalando Retail 398,930 followers Alira Health Pharmaceutical Manufacturing 53,394 followers Emma – The Sleep Company Retail 75,723 followers Sastrify Software Development 34,853 followers Freeletics Wellness and Fitness Services 17,791 followers WeShare is now MILES Transportation/Trucking/Railroad 6,670 followers Back Market Internet Marketplace Platforms 92,882 followers Zenhomes Internet Publishing 1,296 followers Curalie Hospitals and Health Care 2,018 followers Rotageek Software Development 3,396 followers Blinkist E-Learning Providers 56,485 followers ARIVE Technology, Information and Internet 6,956 followers Pliant Financial Services 13,638 followers Douglas Retail 106,680 followers Ometria Technology, Information and Internet 31,216 followers NiCE Cognigy Software Development 49,156 followers ImmoScout24 Software Development 30,100 followers Omio Software Development 75,635 followers OneFootball Software Development 61,169 followers Show more Show less Similar products Productboard Productboard Product Management Software Aha! Academy Aha! Academy Product Management Software Product Portfolio Management Product Portfolio Management Product Management Software Producer Producer Product Management Software Dovetail Dovetail Product Management Software Aha! Discovery Aha! Discovery Product Management Software Sign in to see more 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:24 |
https://git-scm.com/book/ru/v2/%d0%9e%d1%81%d0%bd%d0%be%d0%b2%d1%8b-Git-%d0%97%d0%b0%d0%bf%d0%b8%d1%81%d1%8c-%d0%b8%d0%b7%d0%bc%d0%b5%d0%bd%d0%b5%d0%bd%d0%b8%d0%b9-%d0%b2-%d1%80%d0%b5%d0%bf%d0%be%d0%b7%d0%b8%d1%82%d0%be%d1%80%d0%b8%d0%b9 | Git - Запись изменений в репозиторий About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Введение 1.1 О системе контроля версий 1.2 Краткая история Git 1.3 Что такое Git? 1.4 Командная строка 1.5 Установка Git 1.6 Первоначальная настройка Git 1.7 Как получить помощь? 1.8 Заключение 2. Основы Git 2.1 Создание Git-репозитория 2.2 Запись изменений в репозиторий 2.3 Просмотр истории коммитов 2.4 Операции отмены 2.5 Работа с удалёнными репозиториями 2.6 Работа с тегами 2.7 Псевдонимы в Git 2.8 Заключение 3. Ветвление в Git 3.1 О ветвлении в двух словах 3.2 Основы ветвления и слияния 3.3 Управление ветками 3.4 Работа с ветками 3.5 Удалённые ветки 3.6 Перебазирование 3.7 Заключение 4. Git на сервере 4.1 Протоколы 4.2 Установка Git на сервер 4.3 Генерация открытого SSH ключа 4.4 Настраиваем сервер 4.5 Git-демон 4.6 Умный HTTP 4.7 GitWeb 4.8 GitLab 4.9 Git-хостинг 4.10 Заключение 5. Распределённый Git 5.1 Распределённый рабочий процесс 5.2 Участие в проекте 5.3 Сопровождение проекта 5.4 Заключение 6. GitHub 6.1 Настройка и конфигурация учётной записи 6.2 Внесение собственного вклада в проекты 6.3 Сопровождение проекта 6.4 Управление организацией 6.5 Создание сценариев GitHub 6.6 Заключение 7. Инструменты Git 7.1 Выбор ревизии 7.2 Интерактивное индексирование 7.3 Припрятывание и очистка 7.4 Подпись 7.5 Поиск 7.6 Перезапись истории 7.7 Раскрытие тайн reset 7.8 Продвинутое слияние 7.9 Rerere 7.10 Обнаружение ошибок с помощью Git 7.11 Подмодули 7.12 Создание пакетов 7.13 Замена 7.14 Хранилище учётных данных 7.15 Заключение 8. Настройка Git 8.1 Конфигурация Git 8.2 Атрибуты Git 8.3 Хуки в Git 8.4 Пример принудительной политики Git 8.5 Заключение 9. Git и другие системы контроля версий 9.1 Git как клиент 9.2 Переход на Git 9.3 Заключение 10. Git изнутри 10.1 Сантехника и Фарфор 10.2 Объекты Git 10.3 Ссылки в Git 10.4 Pack-файлы 10.5 Спецификации ссылок 10.6 Протоколы передачи данных 10.7 Обслуживание репозитория и восстановление данных 10.8 Переменные окружения 10.9 Заключение A1. Приложение A: Git в других окружениях A1.1 Графические интерфейсы A1.2 Git в Visual Studio A1.3 Git в Visual Studio Code A1.4 Git в Eclipse A1.5 Git в IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.6 Git в Sublime Text A1.7 Git в Bash A1.8 Git в Zsh A1.9 Git в PowerShell A1.10 Заключение A2. Приложение B: Встраивание Git в ваши приложения A2.1 Git из командной строки A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Приложение C: Команды Git A3.1 Настройка и конфигурация A3.2 Клонирование и создание репозиториев A3.3 Основные команды A3.4 Ветвление и слияния A3.5 Совместная работа и обновление проектов A3.6 Осмотр и сравнение A3.7 Отладка A3.8 Внесение исправлений A3.9 Работа с помощью электронной почты A3.10 Внешние системы A3.11 Администрирование A3.12 Низкоуровневые команды 2nd Edition 2.2 Основы Git - Запись изменений в репозиторий Запись изменений в репозиторий Итак, у вас имеется настоящий Git-репозиторий и рабочая копия файлов для некоторого проекта. Вам нужно делать некоторые изменения и фиксировать «снимки» состояния (snapshots) этих изменений в вашем репозитории каждый раз, когда проект достигает состояния, которое вам хотелось бы сохранить. Запомните, каждый файл в вашем рабочем каталоге может находиться в одном из двух состояний: под версионным контролем (отслеживаемые) и нет (неотслеживаемые). Отслеживаемые файлы — это те файлы, которые были в последнем снимке состояния проекта; они могут быть неизменёнными, изменёнными или подготовленными к коммиту. Если кратко, то отслеживаемые файлы — это те файлы, о которых знает Git. Неотслеживаемые файлы — это всё остальное, любые файлы в вашем рабочем каталоге, которые не входили в ваш последний снимок состояния и не подготовлены к коммиту. Когда вы впервые клонируете репозиторий, все файлы будут отслеживаемыми и неизменёнными, потому что Git только что их извлёк и вы ничего пока не редактировали. Как только вы отредактируете файлы, Git будет рассматривать их как изменённые, так как вы изменили их с момента последнего коммита. Вы индексируете эти изменения, затем фиксируете все проиндексированные изменения, а затем цикл повторяется. Рисунок 8. Жизненный цикл состояний файлов Определение состояния файлов Основной инструмент, используемый для определения, какие файлы в каком состоянии находятся — это команда git status . Если вы выполните эту команду сразу после клонирования, вы увидите что-то вроде этого: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working tree clean Это означает, что у вас чистый рабочий каталог, другими словами — в нём нет отслеживаемых изменённых файлов. Git также не обнаружил неотслеживаемых файлов, в противном случае они бы были перечислены здесь. Наконец, команда сообщает вам на какой ветке вы находитесь и сообщает вам, что она не расходится с веткой на сервере. Пока что это всегда ветка master , ветка по умолчанию; в этой главе это не важно. В главе Ветвление в Git будут рассмотрены ветки и ссылки более детально. Примечание В 2020 году GitHub изменил имя ветки по умолчанию с master на main , другие же git-хостинг платформы последовали этому примеру. Поэтому, вы можете обнаружить, что ветка по умолчанию для новых репозиториев — main , а не master . Более того, имя ветки по умолчанию можно изменить (как вы видели в Настройка ветки по умолчанию ), поэтому вам может встретиться и другое имя. При этом Git продолжает использовать имя master , поэтому далее в книге мы используем именно его. Предположим, вы добавили в свой проект новый файл, простой файл README . Если этого файла раньше не было, и вы выполните git status , вы увидите свой неотслеживаемый файл вот так: $ echo 'My Project' > README $ git status On branch master Your branch is up-to-date with 'origin/master'. Untracked files: (use "git add <file>..." to include in what will be committed) README nothing added to commit but untracked files present (use "git add" to track) Понять, что новый файл README неотслеживаемый можно по тому, что он находится в секции «Untracked files» в выводе команды status . Статус Untracked означает, что Git видит файл, которого не было в предыдущем снимке состояния (коммите); Git не станет добавлять его в ваши коммиты, пока вы его явно об этом не попросите. Это предохранит вас от случайного добавления в репозиторий сгенерированных бинарных файлов или каких-либо других, которые вы и не думали добавлять. Мы хотели добавить README, так давайте сделаем это. Отслеживание новых файлов Для того чтобы начать отслеживать (добавить под версионный контроль) новый файл, используется команда git add . Чтобы начать отслеживание файла README , вы можете выполнить следующее: $ git add README Если вы снова выполните команду status , то увидите, что файл README теперь отслеживаемый и добавлен в индекс: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git restore --staged <file>..." to unstage) new file: README Вы можете видеть, что файл проиндексирован, так как он находится в секции «Changes to be committed». Если вы выполните коммит в этот момент, то версия файла, существовавшая на момент выполнения вами команды git add , будет добавлена в историю снимков состояния. Как вы помните, когда вы ранее выполнили git init , затем вы выполнили git add (файлы) — это было сделано для того, чтобы добавить файлы в вашем каталоге под версионный контроль. Команда git add принимает параметром путь к файлу или каталогу, если это каталог, команда рекурсивно добавляет все файлы из указанного каталога в индекс. Индексация изменённых файлов Давайте модифицируем файл, уже находящийся под версионным контролем. Если вы измените отслеживаемый файл CONTRIBUTING.md и после этого снова выполните команду git status , то результат будет примерно следующим: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Файл CONTRIBUTING.md находится в секции «Changes not staged for commit» — это означает, что отслеживаемый файл был изменён в рабочем каталоге, но пока не проиндексирован. Чтобы проиндексировать его, необходимо выполнить команду git add . Это многофункциональная команда, она используется для добавления под версионный контроль новых файлов, для индексации изменений, а также для других целей, например для указания файлов с исправленным конфликтом слияния. Вам может быть понятнее, если вы будете думать об этом как «добавить этот контент в следующий коммит», а не как «добавить этот файл в проект». Выполним git add , чтобы проиндексировать CONTRIBUTING.md , а затем снова выполним git status : $ git add CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Теперь оба файла проиндексированы и войдут в следующий коммит. В этот момент вы, предположим, вспомнили одно небольшое изменение, которое вы хотите сделать в CONTRIBUTING.md до коммита. Вы открываете файл, вносите и сохраняете необходимые изменения и вроде бы готовы к коммиту. Но давайте-ка ещё раз выполним git status : $ vim CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Что за чёрт? Теперь CONTRIBUTING.md отображается как проиндексированный и непроиндексированный одновременно. Как такое возможно? Такая ситуация наглядно демонстрирует, что Git индексирует файл в точности в том состоянии, в котором он находился, когда вы выполнили команду git add . Если вы выполните коммит сейчас, то файл CONTRIBUTING.md попадёт в коммит в том состоянии, в котором он находился, когда вы последний раз выполняли команду git add , а не в том, в котором он находится в вашем рабочем каталоге в момент выполнения git commit . Если вы изменили файл после выполнения git add , вам придётся снова выполнить git add , чтобы проиндексировать последнюю версию файла: $ git add CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Сокращённый вывод статуса Вывод команды git status довольно всеобъемлющий и многословный. Git также имеет флаг вывода сокращённого статуса, так что вы можете увидеть изменения в более компактном виде. Если вы выполните git status -s или git status --short вы получите гораздо более упрощённый вывод: $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt Новые неотслеживаемые файлы помечены ?? слева от них, файлы добавленные в отслеживаемые помечены A , отредактированные файлы помечены M и так далее. В выводе содержится два столбца — в левом указывается статус файла, а в правом модифицирован ли он после этого. К примеру в нашем выводе, файл README модифицирован в рабочем каталоге, но не проиндексирован, а файл lib/simplegit.rb модифицирован и проиндексирован. Файл Rakefile модифицирован, проиндексирован и ещё раз модифицирован, таким образом на данный момент у него есть те изменения, которые попадут в коммит, и те, которые не попадут. Игнорирование файлов Зачастую, у вас имеется группа файлов, которые вы не только не хотите автоматически добавлять в репозиторий, но и видеть в списках неотслеживаемых. К таким файлам обычно относятся автоматически генерируемые файлы (различные логи, результаты сборки программ и т. п.). В таком случае, вы можете создать файл .gitignore . с перечислением шаблонов соответствующих таким файлам. Вот пример файла .gitignore : $ cat .gitignore *.[oa] *~ Первая строка предписывает Git игнорировать любые файлы заканчивающиеся на «.o» или «.a» — объектные и архивные файлы, которые могут появиться во время сборки кода. Вторая строка предписывает игнорировать все файлы заканчивающиеся на тильду ( ~ ), которая используется во многих текстовых редакторах, например Emacs, для обозначения временных файлов. Вы можете также включить каталоги log, tmp или pid; автоматически создаваемую документацию; и т. д. и т. п. Хорошая практика заключается в настройке файла .gitignore до того, как начать серьёзно работать, это защитит вас от случайного добавления в репозиторий файлов, которых вы там видеть не хотите. К шаблонам в файле .gitignore применяются следующие правила: Пустые строки, а также строки, начинающиеся с # , игнорируются. Стандартные шаблоны являются глобальными и применяются рекурсивно для всего дерева каталогов. Чтобы избежать рекурсии используйте символ слеш (/) в начале шаблона. Чтобы исключить каталог добавьте слеш (/) в конец шаблона. Можно инвертировать шаблон, использовав восклицательный знак (!) в качестве первого символа. Glob-шаблоны представляют собой упрощённые регулярные выражения, используемые командными интерпретаторами. Символ ( * ) соответствует 0 или более символам; последовательность [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 в корневом каталоге, но не файл в subdir/TODO /TODO # Игнорировать все файлы в каталоге build/ build/ # Игнорировать файл doc/notes.txt, но не файл doc/server/arch.txt doc/*.txt # Игнорировать все .txt файлы в каталоге doc/ doc/**/*.txt Подсказка GitHub поддерживает довольно полный список примеров .gitignore файлов для множества проектов и языков https://github.com/github/gitignore это может стать отправной точкой для .gitignore в вашем проекте. Примечание В простейшем случае репозиторий будет иметь один файл .gitignore в корневом каталоге, правила из которого будут рекурсивно применяться ко всем подкаталогам. Так же возможно использовать .gitignore файлы в подкаталогах. Правила из этих файлов будут применяться только к каталогам, в которых они находятся. Например, репозиторий исходного кода ядра Linux содержит 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 you patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's Эта команда сравнивает содержимое вашего рабочего каталога с содержимым индекса. Результат показывает ещё не проиндексированные изменения. Если вы хотите посмотреть, что вы проиндексировали и что войдёт в следующий коммит, вы можете выполнить 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 you patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's Примечание Git Diff во внешних инструментах Мы будем продолжать использовать команду git diff различными способами на протяжении всей книги. Существует ещё один способ просматривать эти изменения, если вы предпочитаете графический просмотр или внешнюю программу просмотра различий, вместо консоли. Выполнив команду git difftool вместо git diff , вы сможете просмотреть изменения в файле с помощью таких программ как emerge, vimdiff и других (включая коммерческие продукты). Выполните git difftool --tool-help чтобы увидеть какие из них уже установлены в вашей системе. Коммит изменений Теперь, когда ваш индекс находится в таком состоянии, как вам и хотелось, вы можете зафиксировать свои изменения. Запомните, всё, что до сих пор не проиндексировано — любые файлы, созданные или изменённые вами, и для которых вы не выполнили git add после редактирования — не войдут в этот коммит. Они останутся изменёнными файлами на вашем диске. В нашем случае, когда вы в последний раз выполняли git status , вы видели что всё проиндексировано, и вот, вы готовы к коммиту. Простейший способ зафиксировать изменения — это набрать git commit : $ git commit Эта команда откроет выбранный вами текстовый редактор. Примечание Редактор устанавливается переменной окружения EDITOR — обычно это vim или emacs, хотя вы можете установить любой другой с помощью команды git config --global core.editor , как было показано в главе Введение ). В редакторе будет отображён следующий текст (это пример окна Vim): # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # new file: README # modified: CONTRIBUTING.md # ~ ~ ~ ".git/COMMIT_EDITMSG" 9L, 283C Вы можете видеть, что комментарий по умолчанию для коммита содержит закомментированный результат работы команды git status и ещё одну пустую строку сверху. Вы можете удалить эти комментарии и набрать своё сообщение или же оставить их для напоминания о том, что вы фиксируете. Примечание Для ещё более подробного напоминания, что же именно вы поменяли, можете передать аргумент -v в команду git commit . Это приведёт к тому, что в комментарий будет также помещена дельта/diff изменений, таким образом вы сможете точно увидеть все изменения которые вы совершили. Когда вы выходите из редактора, Git создаёт для вас коммит с этим сообщением, удаляя комментарии и вывод команды diff . Есть и другой способ — вы можете набрать свой комментарий к коммиту в командной строке вместе с командой commit указав его после параметра -m , как в следующем примере: $ git commit -m "Story 182: fix benchmarks for speed" [master 463dc4f] Story 182: fix benchmarks for speed 2 files changed, 2 insertions(+) create mode 100644 README Итак, вы создали свой первый коммит! Вы можете видеть, что коммит вывел вам немного информации о себе: на какую ветку вы выполнили коммит ( master ), какая контрольная сумма SHA-1 у этого коммита ( 463dc4f ), сколько файлов было изменено, а также статистику по добавленным/удалённым строкам в этом коммите. Запомните, что коммит сохраняет снимок состояния вашего индекса. Всё, что вы не проиндексировали, так и висит в рабочем каталоге как изменённое; вы можете сделать ещё один коммит, чтобы добавить эти изменения в репозиторий. Каждый раз, когда вы делаете коммит, вы сохраняете снимок состояния вашего проекта, который позже вы можете восстановить или с которым можно сравнить текущее состояние. Игнорирование индексации Несмотря на то, что индекс может быть удивительно полезным для создания коммитов именно такими, как вам и хотелось, он временами несколько сложнее, чем вам нужно в процессе работы. Если у вас есть желание пропустить этап индексирования, Git предоставляет простой способ. Добавление параметра -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 включает все файлы. Это удобно, но будьте осторожны: флаг -a может включить в коммит нежелательные изменения. Удаление файлов Для того чтобы удалить файл из Git, вам необходимо удалить его из отслеживаемых файлов (точнее, удалить его из вашего индекса) а затем выполнить коммит. Это позволяет сделать команда git rm , которая также удаляет файл из вашего рабочего каталога, так что в следующий раз вы не увидите его как «неотслеживаемый». Если вы просто удалите файл из своего рабочего каталога, он будет показан в секции «Changes not staged for commit» (изменённые, но не проиндексированные) вывода команды git status : $ rm PROJECTS.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add/rm <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) deleted: PROJECTS.md no changes added to commit (use "git add" and/or "git commit -a") Затем, если вы выполните команду git rm , удаление файла попадёт в индекс: $ git rm PROJECTS.md rm 'PROJECTS.md' $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) deleted: PROJECTS.md После следующего коммита файл исчезнет и больше не будет отслеживаться. Если вы изменили файл и уже проиндексировали его, вы должны использовать принудительное удаление с помощью параметра -f . Это сделано для повышения безопасности, чтобы предотвратить ошибочное удаление данных, которые ещё не были записаны в снимок состояния и которые нельзя восстановить из Git. Другая полезная штука, которую вы можете захотеть сделать — это удалить файл из индекса, оставив его при этом в рабочем каталоге. Другими словами, вы можете захотеть оставить файл на жёстком диске, но перестать отслеживать изменения в нём. Это особенно полезно, если вы забыли добавить что-то в файл .gitignore и по ошибке проиндексировали, например, большой файл с логами, или кучу промежуточных файлов компиляции. Чтобы сделать это, используйте опцию --cached : $ git rm --cached README В команду git rm можно передавать файлы, каталоги или шаблоны. Это означает, что вы можете сделать что-то вроде: $ git rm log/\*.log Обратите внимание на обратный слеш ( \ ) перед * . Он необходим из-за того, что Git использует свой собственный обработчик имён файлов вдобавок к обработчику вашего командного интерпретатора. Эта команда удаляет все файлы, имеющие расширение .log и находящиеся в каталоге log/ . Или же вы можете сделать вот так: $ git rm \*~ Эта команда удаляет все файлы, имена которых заканчиваются на ~ . Перемещение файлов В отличие от многих других систем контроля версий, 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 . Единственное отличие состоит лишь в том, что 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://git-scm.com/book/de/v2/Git-auf-dem-Server-Zusammenfassung | Git - Zusammenfassung About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Erste Schritte 1.1 Was ist Versionsverwaltung? 1.2 Kurzer Überblick über die Historie von Git 1.3 Was ist Git? 1.4 Die Kommandozeile 1.5 Git installieren 1.6 Git Basis-Konfiguration 1.7 Hilfe finden 1.8 Zusammenfassung 2. Git Grundlagen 2.1 Ein Git-Repository anlegen 2.2 Änderungen nachverfolgen und im Repository speichern 2.3 Anzeigen der Commit-Historie 2.4 Ungewollte Änderungen rückgängig machen 2.5 Mit Remotes arbeiten 2.6 Taggen 2.7 Git Aliases 2.8 Zusammenfassung 3. Git Branching 3.1 Branches auf einen Blick 3.2 Einfaches Branching und Merging 3.3 Branch-Management 3.4 Branching-Workflows 3.5 Remote-Branches 3.6 Rebasing 3.7 Zusammenfassung 4. Git auf dem Server 4.1 Die Protokolle 4.2 Git auf einem Server einrichten 4.3 Erstellung eines SSH-Public-Keys 4.4 Einrichten des Servers 4.5 Git-Daemon 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 Von Drittanbietern gehostete Optionen 4.10 Zusammenfassung 5. Verteiltes Git 5.1 Verteilter Arbeitsablauf 5.2 An einem Projekt mitwirken 5.3 Ein Projekt verwalten 5.4 Zusammenfassung 6. GitHub 6.1 Einrichten und Konfigurieren eines Kontos 6.2 Mitwirken an einem Projekt 6.3 Ein Projekt betreuen 6.4 Verwalten einer Organisation 6.5 Skripte mit GitHub 6.6 Zusammenfassung 7. Git Tools 7.1 Revisions-Auswahl 7.2 Interaktives Stagen 7.3 Stashen und Bereinigen 7.4 Deine Arbeit signieren 7.5 Suchen 7.6 Den Verlauf umschreiben 7.7 Reset entzaubert 7.8 Fortgeschrittenes Merging 7.9 Rerere 7.10 Debuggen mit Git 7.11 Submodule 7.12 Bundling 7.13 Replace (Ersetzen) 7.14 Anmeldeinformationen speichern 7.15 Zusammenfassung 8. Git einrichten 8.1 Git Konfiguration 8.2 Git-Attribute 8.3 Git Hooks 8.4 Beispiel für Git-forcierte Regeln 8.5 Zusammenfassung 9. Git und andere VCS-Systeme 9.1 Git als Client 9.2 Migration zu Git 9.3 Zusammenfassung 10. Git Interna 10.1 Basisbefehle und Standardbefehle (Plumbing and Porcelain) 10.2 Git Objekte 10.3 Git Referenzen 10.4 Packdateien (engl. Packfiles) 10.5 Die Referenzspezifikation (engl. Refspec) 10.6 Transfer Protokolle 10.7 Wartung und Datenwiederherstellung 10.8 Umgebungsvariablen 10.9 Zusammenfassung A1. Anhang A: Git in anderen Umgebungen A1.1 Grafische Schnittstellen A1.2 Git in Visual Studio A1.3 Git in Visual Studio Code A1.4 Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git in Sublime Text A1.6 Git in Bash A1.7 Git in Zsh A1.8 Git in PowerShell A1.9 Zusammenfassung A2. Anhang B: Git in deine Anwendungen einbetten A2.1 Die Git-Kommandozeile A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Anhang C: Git Kommandos A3.1 Setup und Konfiguration A3.2 Projekte importieren und erstellen A3.3 Einfache Snapshot-Funktionen A3.4 Branching und Merging A3.5 Projekte gemeinsam nutzen und aktualisieren A3.6 Kontrollieren und Vergleichen A3.7 Debugging A3.8 Patchen bzw. Fehlerkorrektur A3.9 E-mails A3.10 Externe Systeme A3.11 Administration A3.12 Basisbefehle 2nd Edition 4.10 Git auf dem Server - Zusammenfassung Zusammenfassung Du hast mehrere Möglichkeiten, ein entferntes Git-Repository in Betrieb zu nehmen, damit du mit anderen zusammenarbeiten und deine Arbeit teilen kannst. Der Betrieb eines eigenen Servers gibt dir viel Kontrolle und ermöglicht es dir, den Server innerhalb deiner eigenen Firewall zu betreiben. Ein solcher Server benötigt jedoch in der Regel einen angemessenen Teil deiner Zeit für Einrichtung und Wartung. Wenn du deine Daten auf einem gehosteten Server ablegst, macht es dir dein Leben wesentlich einfacher. Du musst aber die Möglichkeit haben, deinen Code auf fremden Servern zu speichern. Einige Unternehmen erlauben das nicht. Es sollte ziemlich einfach sein festzustellen, welche Lösung oder Kombination von Lösungen für dich und dein Unternehmen am besten geeignet ist. 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/synchronous-requests#authorization-authorization | 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/gr/v2/%ce%a4%ce%b1-%ce%b8%ce%b5%ce%bc%ce%b5%ce%bb%ce%b9%cf%8e%ce%b4%ce%b7-%cf%83%cf%84%ce%bf%ce%b9%cf%87%ce%b5%ce%af%ce%b1-%cf%84%ce%bf%cf%85-Git-%ce%9a%ce%b1%cf%84%ce%b1%ce%b3%cf%81%ce%b1%cf%86%ce%ae-%ce%b1%ce%bb%ce%bb%ce%b1%ce%b3%cf%8e%ce%bd-%cf%83%cf%84%ce%bf-%ce%b1%cf%80%ce%bf%ce%b8%ce%b5%cf%84%ce%ae%cf%81%ce%b9%ce%bf | Git - Καταγραφή αλλαγών στο αποθετήριο About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Ξεκινώντας με το Git 1.1 Σχετικά με τον έλεγχο εκδόσεων 1.2 Σύντομο ιστορικό του Git 1.3 Τι είναι το Git; 1.4 Η γραμμή εντολών 1.5 Εγκατάσταση του Git 1.6 Ρύθμιση του Git για πρώτη φορά 1.7 Χρησιμοποιώντας τη βοήθεια 1.8 Ανακεφαλαίωση 2. Τα θεμελιώδη στοιχεία του Git 2.1 Απόκτηση αποθετηρίου Git 2.2 Καταγραφή αλλαγών στο αποθετήριο 2.3 Χρησιμοποιώντας το ιστορικό υποβολών 2.4 Αναιρέσεις (undoing) 2.5 Δουλεύοντας με απομακρυσμένα αποθετήρια 2.6 Ετικέτες 2.7 Συντομεύεσεις στο Git 2.8 Ανακεφαλαίωση 3. Διακλαδώσεις στο Git 3.1 Οι κλάδοι με λίγα λόγια 3.2 Βασικές έννοιες διακλαδώσεων και συγχωνεύσεων 3.3 Διαχείριση κλάδων 3.4 Ροές εργασίας με διακλαδώσεις 3.5 Απομακρυσμένοι κλάδοι 3.6 Αλλαγή βάσης (rebasing) 3.7 Ανακεφαλαίωση 4. Το Git στον διακομιστή 4.1 Τα πρωτόκολλα 4.2 Εγκατάσταση του Git σε διακομιστή 4.3 Δημιουργία δημόσιου κλειδιού SSH 4.4 Στήσιμο του διακομιστή 4.5 Δαίμονες του Git 4.6 Έξυπνο HTTP 4.7 GitWeb 4.8 GitLab 4.9 Επιλογές φιλοξενίας από τρίτους 4.10 Ανακεφαλαίωση 5. Κατανεμημένο Git 5.1 Κατανεμημένες ροές εργασίας 5.2 Συνεισφέροντας σε ένα έργο 5.3 Συντήρηση ενός έργου 5.4 Ανακεφαλαίωση 6. GitHub 6.1 Δημιουργία λογαριασμού και ρύθμισή του 6.2 Συνεισφορά σε έργο 6.3 Συντήρηση ενός έργου 6.4 Διαχείριση οργανισμώνν 6.5 Συγγραφή script στο GitHub 6.6 Ανακεφαλαίωση 7. Εργαλεία του Git 7.1 Επιλογή αναθεώρησης 7.2 Διαδραστική εργασία με το στάδιο καταχώρισης 7.3 Αποθέματα και Καθαρισμός 7.4 Υπογραφή της δουλειάς μας 7.5 Αναζήτηση 7.6 Η ιστορία ξαναγράφεται 7.7 Απομυθοποίηση της reset 7.8 Προχωρημένη Συγχώνευση 7.9 Rerere 7.10 Αποσφαλμάτωση με το Git 7.11 Υπομονάδες 7.12 Δεμάτιασμα δεδομένων 7.13 Replace 7.14 Αποθήκευση διαπιστευτηρίων 7.15 Ανακεφαλαίωση 8. Εξατομίκευση του Git 8.1 Διαμόρφωση Git 8.2 Γνωρίσματα του Git 8.3 Τα άγκιστρα του Git 8.4 Ένα παράδειγμα επιβολής πολιτικής από το Git 8.5 Ανακεφαλαίωση 9. Το Git και άλλα συστήματα 9.1 Το Git ως πελάτης 9.2 Μετανάστευση στο Git 9.3 Ανακεφαλαίωση 10. Εσωτερική λειτουργία του Git 10.1 Διοχετεύσεις και πορσελάνες 10.2 Αντικείμενα του Git 10.3 Αναφορές του Git 10.4 Πακετάρισμα αρχείων 10.5 Τα refspec 10.6 Πρωτόκολλα μεταφοράς 10.7 Διατήρηση και ανάκτηση δεδομένων 10.8 Μεταβλητές περιβάλλοντος 10.9 Ανακεφαλαίωση A1. Appendix A: Το Git σε άλλα περιβάλλοντα A1.1 Γραφικές διεπαφές A1.2 Το Git στο Visual Studio A1.3 Git στο Visual Studio Code A1.4 Git στο IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.5 Git στο Sublime Text A1.6 Το Git στο Bash A1.7 Το Git στο Zsh A1.8 Το Git στο Powershell A1.9 Ανακεφαλαίωση A2. Appendix B: Ενσωμάτωση του Git στις εφαρμογές μας A2.1 Γραμμή εντολών Git A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Appendix C: Εντολές Git A3.1 Ρύθμιση και διαμόρφωση A3.2 Λήψη και δημιουργία έργων A3.3 Βασική λήψη στιγμιοτύπων A3.4 Διακλάδωση και συγχώνευση A3.5 Κοινή χρήση και ενημέρωση έργων A3.6 Επιθεώρηση και σύγκριση A3.7 Αποσφαλμάτωση A3.8 Επιθέματα A3.9 Ηλεκτρονικό ταχυδρομείο A3.10 Εξωτερικά Συστήματα A3.11 Διοίκηση A3.12 Εντολές διοχέτευσης 2nd Edition 2.2 Τα θεμελιώδη στοιχεία του Git - Καταγραφή αλλαγών στο αποθετήριο Καταγραφή αλλαγών στο αποθετήριο Σε αυτό το σημείο, θα πρέπει να έχουμε ένα αξιόπιστο αποθετήριο Git στο τοπικό μηχάνημά μας και μια ενημερωμένη έκδοση των αρχείων του έργου μπροστά μας. Συνήθως, η διαδικασία που ακολουθεί είναι να κάνουμε μερικές αλλαγές στο έργο και να υποβάλλουμε στιγμιότυπα (snapshots) αυτών των αλλαγών στο αποθετήριό μας όποτε το έργο φτάνει σε μια κατάσταση που θέλουμε να καταγράψουμε. Θυμόμαστε ότι κάθε αρχείο στον κατάλογο που εργαζόμαστε μπορεί να βρίσκεται σε δύο καταστάσεις: παρακολουθούμενο (tracked) ή μη-παρακολουθούμενο . Τα παρακολουθούμενα αρχεία είναι αυτά που βρίσκονταν στο τελευταίο στιγμιότυπο καθώς και αρχεία που μόλις έχουν τοποθετηθεί στο στάδιο καταχώρησης· μπορεί να είναι μη τροποποιημένα, τροποποιημένα ή στο στάδιο καταχώρησης (staged). Εν συντομία, τα παρακολουθούμενα αρχεία είναι τα αρχεία που το Git γνωρίζει για αυτά. Τα μη-παρακολουθούμενα αρχεία είναι όλα τα υπόλοιπα — τα αρχεία στον κατάλογο εργασίας που δεν βρίσκονταν στο τελευταίο στιγμιότυπο, και δεν βρίσκονται ούτε στο στάδιο καταχώρησης. Όταν κλωνοποιούμε για πρώτη φορά ένα αποθετήριο, όλα τα αρχεία θα είναι παρακολουθούμενα και ατροποποίητα επειδή το Git μόλις τα έχει ενημερώσει (check out) και δεν τα έχουμε επεξεργαστεί ακόμα. Καθώς επεξεργαζόμαστε τα αρχεία, το Git θα τα αναγνωρίζει ως τροποποιημένα, αφού θα έχουν αλλάξει από την τελευταία μας υποβολή (commit). Όσο εργαζόμαστε, τοποθετούμε επιλεκτικά κάποια τροποποιημένα αρχεία στο στάδιο καταχώρησης, στη συνέχεια υποβάλλουμε όλες τις αλλαγές των αρχείων και επαναλαμβάνουμε τη διαδικασία ξανά και ξανά. Figure 8. Ο κύκλος ζωής της κατάστασης των αρχείων μας Έλεγχος της κατάστασης των αρχείων μας Το βασικό εργαλείο που χρησιμοποιoύμε για να προσδιορίσουμε την τρέχουσα κατάσταση των αρχείων είναι η εντολή git status . Αν την εκτελέσουμε αμέσως μόλις έχουμε κλωνοποιήσει ένα αποθετήριο, θα δούμε ένα μήνυμα παρόμοιο με το παρακάτω: $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working tree clean Αυτό σημαίνει ότι έχουμε ένα καθαρό κατάλογο εργασίας· με άλλα λόγια, κανένα από τα παρακολουθούμενα αρχεία μας δεν έχουν τροποποιηθεί. Επίσης το Git δεν βλέπει κανένα μη-παρακολουθούμενο αρχείο, αλλιώς θα τα παρέθετε στο παραπάνω μήνυμα. Τέλος, η εντολή αυτή μας ενημερώνει σε ποιον κλάδο βρίσκομαστε καθώς και ότι δεν έχει αποκλίσει από τον αντίστοιχο κλάδο που βρίσκεται στον διακομιστή. Προς το παρόν ο κλάδος αυτός είναι ο master , που είναι και ο προεπιλεγμένος· δεν θα μας απασχολήσει εδώ. Η ενότητα Διακλαδώσεις στο Git θα εξετάσει πιο αναλυτικά τους κλάδους και τις αναφορές. Note Το GitHub άλλαξε το προεπιλεγμένο όνομα κλάδου από master σε main στα μέσα του 2020, κάτι που μιμήθηκαν και άλλοι διακομιστές Git. Συνεπώς, ενδεχομένως θα δείτε ότι το προεπιλεμγένο όνομα κλάδου σε κάποια πιο καινούρια αποθετήρια είναι main και όχι master . Επιπλέον, το προεπιλεγμένο όνομα βρόχου μπορεί να τροποποιηθεί (όπως είδαμε στην ενότητα Το προεπιλεγμένο όνομα κλάδου μας ), συνεπώς ίσως δέιτε κάποιο άλλο όνομα για τον προεπιλεγμένο κλάδο. Πάντως, το ίδιο το Git χρησιμοποιεί το όνομα master ως προεπιλεγμένο, συνεπώς αυτό θα χρησιμοποιήσουμε κι εμείς σε αυτό το βιβλίο. Ας υποθέσουμε ότι έχουμε προσθέσει ένα νέο αρχείο στο έργο μας, ένα απλό αρχείο README . Αν το αρχείο αυτό δεν προϋπήρχε και εκτελέσουμε την εντολή git status , θα δούμε το μη-παρακολουθούμενο αρχείο μας ως εξής: $ echo 'My Project' > README $ git status On branch master Your branch is up-to-date with 'origin/master'. Untracked files: (use "git add <file>..." to include in what will be committed) README nothing added to commit but untracked files present (use "git add" to track) Βλέπουμε ότι το αρχείο README είναι μη-παρακολουθούμενο διότι βρίσκεται κάτω από τον τίτλο “Untracked files” στο πάνω μέρος του αποτελέσματος της εντολής. Μη-παρακολουθούμενο ουσιαστικά σημαίνει ότι το Git βλέπει ένα αρχείο το οποίο δεν υπήρχε στο προηγούμενο στιγμιότυπο (υποβολή, commit) και που δεν έχει τοποθετηθεί ακόμα στο στάδιο καταχώρησης· το Git δεν θα συμπεριλάβει το αρχείο αυτό στα επόμενα στιγμιότυπα που θα υποβάλλουμε, αν δεν το ζητήσουμε ρητά. Αυτό γίνεται ώστε να μην συμπεριλάβουμε κατά λάθος στο έργο μας αρχεία τα οποία δεν θέλουμε να συμπεριλάβουμε, για παράδειγμα εκτελέσιμα αρχεία. Σε αυτή την περίπτωση, θέλουμε να συμπεριλάβουμε το αρχείο README στο έργο μας, οπότε ας ξεκινήσουμε να παρακολουθούμε το αρχείο. Παρακολούθηση νέων αρχείων Για να αρχίσουμε να παρακολουθούμε ένα καινούριο αρχείο, χρησιμοποιoύμε την εντολή git add . Για να αρχίσουμε να παρακολουθούμε το αρχείο READΜE , εκτελούμε: $ git add README Αν τώρα εκτελέσουμε την εντολή git status για να δούμε την τρέχουσα κατάσταση, θα δούμε ότι το αρχείο README πλέον παρακολουθείται και έχει τοποθετηθεί στο στάδιο καταχώρησης ώστε να είναι έτοιμο να υποβληθεί: $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git restore --staged <file>..." to unstage) new file: README Καταλαβαίνουμε ότι το αρχείο αυτό πλέον έχει τοποθετηθεί στο στάδιο καταχώρησης διότι βρίσκεται κάτω από τον τίτλο “Changes to be committed”. Αν σε αυτό το σημείο υποβάλλουμε τα αρχεία μας, η έκδοση του αρχείου README που θα αποθηκευτεί στο στιγμιότυπο θα είναι αυτή που υπήρχε όταν εκτελέσαμε την εντολή 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 έχει πολλές λειτουργίες· τη χρησιμοποιoύμε για να ξεκινήσουμε την παρακολούθηση καινούργιων αρχείων, για να τοποθετήσουμε αρχεία στο στάδιο καταχώρησης αλλά και για άλλες λειτουργίες όπως το να επισημάνουμε αρχεία που προέρχονται από συγκρούσεις συγχώνευσης (merge conflicts) ως επιλυμένα. Μπορούμε να σκεφτούμε την εντολή ως “πρόσθεσε αυτό το περιεχόμενο στην επόμενη υποβολή” αντί για “πρόσθεσε αυτό το αρχείο στο έργο”. Ας εκτελέσουμε την εντολή git add , ώστε να καταχωρήσουμε το αρχείο “CONTRIBUTING.md” και έπειτα ας τρέξουμε την εντολή git status ξανά: $ git add CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Και τα δύο αρχεία πλέον βρίσκονται στο στάδιο καταχώρησης και θα συμπεριληφθούν στην επόμενη υποβολή μας. Ας υποθέσουμε τώρα ότι θυμηθήκαμε άλλη μία μικρή αλλαγή που θέλουμε να κάνουμε στο αρχείο CONTRIBUTING.md πριν το υποβάλλουμε. Το ανοίγουμε ξανά, κάνουμε την αλλαγή που θέλουμε και είμαστε έτοιμοι για την υποβολή. Παρόλα αυτά ας εκτελέσουμε git status για άλλη μια φορά: $ vim CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Τι στην ευχή συμβαίνει; Το αρχείο CONTRIBUTING.md εμφανίζεται και ως αρχείο τοποθετημένο στο στάδιο καταχώρησης, αλλά και ως αρχείο που δεν έχει τοποθετηθεί στο στάδιο καταχώρησης. Πώς είναι αυτό δυνατόν; Αυτό που συμβαίνει είναι ότι το Git τοποθετεί στο στάδιο καταχώρησης ένα αρχείο ακριβώς όπως είναι τη στιγμή που εκτελούμε την εντολή git add . Αν υποβάλλουμε το στιγμιότυπο τώρα, η έκδοση του αρχείου CONTRIBUTING.md που θα συμπεριληφθεί στην υποβολή είναι αυτή που υπήρχε όταν εκτελέσαμε την εντολή git add (και όχι η τωρινή έκδοση του αρχείου). Γενικά, αν τροποποιήσουμε ένα αρχείο αφότου έχουμε εκτελέσει την εντολή git 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 Σύντομο Status Αν και το αποτέλεσμα της εντολής git status είναι αρκετά περιεκτικό, οι πληροφορίες αυτές είναι λίγο φλύαρες. Το Git διαθέτει μια σημαία για πιο συνοπτική περιγραφή της κατάστασης των αλλαγών. Αν εκτελέσουμε git status -s ή git status --short θα έχουμε ένα πιο απλοποιημένο αποτέλεσμα. $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt Τα καινούργια αρχεία που δεν παρακολουθούνται ακόμα ακολουθούνται με ένα ?? , τα καινούρια αρχεία που έχουν καταχωρηθεί με A , τα τροποποιημένα αρχεία με M κ.ο.κ. Υπάρχουν δύο στήλες στην έξοδο· η αριστερή στήλη περιγράφει την κατάσταση του σταδίου καταχώρησης και η δεξιά στήλη την κατάσταση του δένδρου εργασίας. Έτσι, για παράδειγμα, στην προήγουμενη έξοδο το αρχείο README έχει τροποποιηθεί στον κατάλογο εργασίας, αλλά δεν έχει ακόμα τοποθετηθεί στο στάδιο καταχώρησης, ενώ το αρχείο lib/simplegit.rb είναι και τροποποιημένο και έχει τοποθετηθεί στο στάδιο καταχώρησης. Το αρχείο Rakefile έχει τροποποιηθεί, τοποθετηθεί στο στάδιο καταχώρησης και στη συνέχεια τροποποιήθηκε ξανά, που σημαίνει ότι υπάρχουν κάποιες αλλαγές που έχουν τοποθετηθεί στο στάδιο καταχώρησης και άλλες που δεν έχουν τοποθετηθεί στο στάδιο καταχώρησης. Αγνόηση αρχεία Συμβαίνει συχνά, να υπάρχει μια κατηγορία αρχείων που δεν θέλουμε να προσθέτει αυτόματα το Git, ούτε καν να φαίνονται ως μη-παρακολουθούμενα. Αυτά είναι συνήθως αρχεία που δημιουργούνται αυτόματα όπως αρχεία .log ή αρχεία που δημιουργούνται κατά τη μεταγλώττιση. Σε αυτές τις περιπτώσεις μπορούμε να δημιουργήσουμε ένα αρχείο με όνομα .gitignore , στο οποίο να καταγράψουμε τα μοτίβα των ονομάτων αυτών των αρχείων. Να ένα παράδειγμα αρχείου .gitignore : $ cat .gitignore *.[oa] *~ Η πρώτη γραμμή λέει στο Git να αγνοεί όλα τα αρχεία που τελειώνουν σε “.o” ή “.a” — αρχεία που είναι συνήθως αποτέλεσμα της μεταγλώττισης τους κώδικά μας. Η δεύτερη γραμμή λέει στο Git να αγνοεί όλα τα αρχεία που τελειώνουν με τον χαρακτήρα ( ~ ), το οποίο χρησιμοποιείται από πολλούς επεξεργαστές κειμένου, όπως τον Emacs, για να δηλώσει τα προσωρινά αρχεία. Μπορούμε επίσης να συμπεριλάβουμε καταλόγους που περιλαμβάνουν αρχεία καταγραφής· προσωρινούς καταλόγους· αυτόματες δημιουργίες τεκμηρίωσεων· κ.ο.κ. Γενικά είναι καλή ιδέα να ρυθμίσουμε το αρχείο .gitignore νωρίς ώστε να μην υποβάλλουμε κατά λάθος αρχεία που δεν θέλουμε να βρίσκονται στο αποθετήριό μας. Οι κανόνες για τα μοτίβα που μπορούμε να δηλώσουμε στο αρχείο .gitignore είναι οι εξής: Οι κενές γραμμές ή οι γραμμές που ξεκινούν με # αγνοούνται. Μπορούμε να χρησιμοποιήσουμε τα κλασικά μοτίβα για ονόματα αρχείων (glob patterns) που εφαρμόζονται αναδρομικά. Μπορούμε να ξεκινήσουμε τα μοτίβα μας με slash ( / ) ώστε να αποφύγουμε την αναδρομικότητα Μπορούμε να τελειώσουμε τα μοτίβα μας με slash ( / ) ώστε να ορίσουμε έναν κατάλογο. Μπορούμε να αντιστρέψουμε ένα μοτίβο χρησιμοποιώντας ένα θαυμαστικό ( ! ) στην αρχή του. Τα μοτίβα αυτά μοιάζουν με απλοποιημένες κανονικές εκφράσεις (regular expressions) που χρησιμοποιούν τα κέλυφοι (shells). Ένας αστερίσκος ( * ) αντιστοιχεί σε μηδέν ή περισσότερους χαρακτήρες· το [abc] αντιστοιχεί σε οποιονδήποτε χαρακτήρα βρίσκεται μέσα στις αγκύλες (σε αυτή την περίπτωση a , b και c )· το σύμβολο του αγγλικού ερωτηματικού ( ? ) αντιστοιχεί σε έναν και μόνο χαρακτήρα· και οι αγκύλες που περιέχουν χαρακτήρες που διαχωρίζονται με παύλα ( [0-9] ) αντιστοιχίζονται σε όλους τους χαρακτήρες που υπάρχουν μεταξύ τους (σε αυτή την περίπτωση, όλους τους αριθμούς από το 0 μέχρι το 9). Μπορούμε επίσης να χρησιμοποιήσουμε δύο αστερίσκους για να αντιστοιχίσουμε εμφωλευμένους καταλόγους· η έκφραση a/**/z αντιστοιχεί στους καταλόγους a/z , a/b/z , a/b/c/z κ.ο.κ. Ορίστε άλλο ένα παράδειγμα ενός αρχείου .gitignore : # αγνόησε όλα τα αρχεία .a *.a # αλλά να παρακολουθείς το lib.a, παρά το ότι αγνοείς τα αρχεία .a !lib.a # αγνόησε μόνο το αρχείο TODO στον τρέχοντα κατάλογο, όχι το subdir/TODO /TODO # αγνόησε όλα τα αρχεία σε οποιονδήποτε κατάλογο με όνομα build build/ # αγνόησε το doc/notes.txt, αλλά όχι το doc/server/arch.txt doc/*.txt # αγνόησε όλα τα αρχεία .pdf στον φάκελο doc/ και όλους τους υποφακέλους του doc/**/*.pdf Tip Αν θέλετε κάποια παραδείγματα για να ξεκινήσετε, το GitHub διατηρεί μια λίστα με παραδείγματαα αρχείων .gitignore για πολλές γλώσσες προγραμματισμού στη διεύθυνση https://github.com/github/gitignore . Note Στην απλούστερη περίπτωση, ένα αποθετήριο έχει μόνο ένα αρχείο .gitignore στον κατάλογο root, το οποίο εφαρμόζεται αναδρομικά σε όλο το αποθετήριο. Όμως είναι δυνατό να έχετε επιπρόσθετα αρχεία .gitignore σε υποφακέλους. Οι κανόνες σε αυτά τα εμφωλευμένα αρχεία .gitignore εφαρμόζονται μόνο σε αρχεία του φακέλου στον οποίο βρίσκονται. Το αποθετήριο με τον πηγαίο κώδικα του πυρήνα του Linux έχει 206 αρχεία .gitignore . Περισσότερες λεπτομέρειες σχετικά με πολλαπλά αρχεία .gitignore είναι πέρα από τους σκοπούς αυτού του βιβλίου· βλ. man gitignore για περισσότερες λεπτομέρειες. Προβολή των καταχωρημένων και μη-καταχωρημένων αλλαγών Αν η εντολή git status είναι πολύ αόριστη για μας και θέλουμε να δούμε ακριβώς τι έχουμε αλλάξει (και όχι μόνο ποια αρχεία έχουν αλλάξει), μπορούμε να χρησιμοποιήσουμε την εντολή git diff . Θα καλύψουμε την εντολή αυτή πιο αναλυτικά αργότερα, αλλά το πιθανότερο είναι ότι θα τη χρησιμοποιoύμε πιο συχνά για να απαντήσουμε σε αυτές τις δύο ερωτήσεις: Τι έχουμε αλλάξει και δεν έχουμε ακόμα τοποθετήσει στο στάδιο καταχώρησης; Και τι έχουμε τοποθετήσει στο στάδιο καταχώρησης και είναι έτοιμο να υποβληθεί; Ενώ η εντολή git status απαντά σε αυτές τις ερωτήσεις πολύ γενικά, απαριθμώντας τα ονόματα των αρχείων, η εντολή git diff θα μας δείξει ακριβώς ποιες γραμμές προστέθηκαν ή αφαιρέθηκαν — με άλλα λόγια το επίθεμα (patch) όπως ήταν. Έστω λοιπόν ότι έχουμε επεξεργαστεί και τοποθετήσει στο στάδιο καταχώρησης το αρχείο 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 Note Χρήση της git diff από Εξωτερικό εργαλείο Θα συνεχίσουμε να χρησιμοποιούμε την εντολή git diff με διάφορους τρόπους στο βιβλίο. Αν όμως θέλουμε να βλέπουμε τις διαφορές μεταξύ των αρχείων με κάποιο γραφικό εργαλείο (και όχι μέσα από τη γραμμή εντολών), υπάρχει και άλλος τρόπος. Αν εκτελέσετε την εντολή git difftool αντί για git diff μπορείτε να δείτε τις διαφορές των αρχείων με προγράμματα όπως τα emerge, vimdiff και άλλα (συμπεριλαμβανομένων και εμπορικών λογισμικών). Εκτελείτε την εντολή git difftool --tool-help για να δείτε ποια προγράμματα είναι διαθέσιμα στο σύστημά σας. Υποβολή των αλλαγών Τώρα που ο προθάλαμός μας περιέχει τις αλλαγές που θέλουμε, είμαστε έτοιμοι να τις υποβάλλουμε (commit). Θυμόμαστε ότι όλα τα μη καταχωρημένα αρχεία, δηλαδή όσα αρχεία έχουμε δημιουργήσει ή τροποποιήσει και για τα οποία δεν εκτελέσαμε την εντολή git add , δεν θα συμπεριληφθούν σε αυτή την υποβολή. Θα παραμείνουν ως τροποποιημένα αρχεία στον δίσκο μας. Σε αυτή την περίπτωση, έστω ότι την τελευταία φορά που εκτελέσαμε την εντολή git status , είδαμε ότι τα πάντα είχαν τοποθετηθεί στο στάδιο καταχώρησης και συνεπώς είμαστε έτοιμοι να υποβάλλουμε τις αλλαγές μας. Ο απλούστερος τρόπος για να υποβάλλουμε αλλαγές είναι να πληκτρολογήσουμε git commit : $ git commit Όταν το κάνουμε, θα ξεκινήσει ο προεπιλεγμένος επεξεργαστής κειμένου μας. Note Αυτός είναι καθορισμένος από τη μεταβλητή περιβάλλοντος (environment variable) της γραμμής εντολών, $EDITOR — συνήθως vim ή emacs, αλλά μπορείτε να χρησιμοποιήσετε την εντολή git config --global core.editor ώστε να χρησιμοποιήσετε τον επεξεργαστή κειμένου της αρεσκείας σας, όπως είδαμε στο Ξεκινώντας με το Git . Ο επεξεργαστής κειμένου μας θα εμφανίσει το παρακάτω κείμενο (αυτό το παράδειγμα είναι οθόνη του Vim): # Please enter the commit message for your changes. Lines starting # with '#' will be ignored, and an empty message aborts the commit. # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # new file: README # modified: CONTRIBUTING.md # ~ ~ ~ ".git/COMMIT_EDITMSG" 9L, 283C Βλέπουμε ότι το προεπιλεγμένο μήνυμα υποβολής περιέχει το τελευταίο αποτέλεσμα της εντολής git status μέσα σε σχόλια και μια κενή γραμμή στην αρχή. Μπορούμε να αφαιρέσουμε τα σχόλια αυτά και να γράψουμε το δικό μας μήνυμα υποβολής ή να τα αφήσουμρ ως έχουν ώστε να μας βοηθήσουν αργότερα να θυμηθούμε ποια αρχεία υποβάλλουμε. Note Για να έχετε μια ακόμα πιο ρητή υπενθύμιση των αλλαγών που έχετε κάνει, μπορείτε να χρησιμοποιήσετε την επιλογή -v στην εντολή git commit . Με τον τρόπο αυτό, θα εισάγετε τις αλλαγές σας στον επεξεργαστή κειμένου ώστε να δείτε ακριβώς ποιες αλλαγές θα υποβάλλετε. Αφού κλείσουμε τον επεξεργαστή κειμένου, το Git θα δημιουργήσει την υποβολή μας με το παραπάνω μήνυμα (τα σχόλια θα αφαιρεθούν). Εναλλακτικά, μπορούμε να γράψουμε το μήνυμα υποβολής μας μαζί με την εντολή commit , μετά τη σημαία -m ως εξής: $ git commit -m "Story 182: fix benchmarks for speed" [master 463dc4f] Story 182: fix benchmarks for speed 2 files changed, 2 insertions(+) create mode 100644 README Μόλις κάναμε την πρώτη μας υποβολή! Βλέπουμε ότι η υποβολή αυτή μας έχει δώσει κάποιες πληροφορίες: τον κλάδο στον οποίο υποβάλλαμε τις αλλαγές μας ( master ), το άθροισμα ελέγχου SHA-1 (SHA-1 checksum) της υποβολής ( 463dc4f ), πόσα αρχεία τροποποιήθηκαν, καθώς και στατιστικά για το πόσες γραμμές προστέθηκαν και αφαιρέθηκαν σε αυτή την υποβολή. Θυμόμαστε ότι η υποβολή αλλαγών καταγράφει το στιγμιότυπο το οποίο είχαμε εκείνη τη στιγμή στο στάδιο καταχώρησης. Οτιδήποτε δεν είχαμε τοποθετήσει στο στάδιο καταχώρησης, παραμένει εκεί τροποποιημένο και μπορούμε να το υποβάλλουμε αργότερα με άλλο ένα commit. Κάθε φορά που πραγματοποιούμε μια υποβολή, καταγράφουμε ένα στιγμιότυπο του έργου μας, στο οποίο μπορούμε να επανέλθουμε αργότερα ή να το συγκρίνουμε με κάποιο παλιότερο στιγμιότυπο του έργου μας. Παραλείποντας το στάδιο καταχώρησης Παρόλο που το στάδιο καταχώρησης είναι πολύ χρήσιμο για να κόβουμε και να ράβουμε τις υποβολές μας όπως ακριβώς θέλουμε, ενίοτε είναι πιο περίπλοκος από όσο χρειάζεται να είναι στην εργασία μας. Αν θέλουμε να παραλείψουμε το στάδιο καταχώρηςη, το Git παρέχει μια απλή συντόμευση. Αν προσθέσουμε την επιλογή -a στην εντολή git commit αναγκάζουμε το Git να τοποθετεί αυτόματα όλα τα αρχεία υπό παρακολούθηση πριν κάνει το commit, επιτρέποντάς μας έτσι να παραλείψουμε την εντολή 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 , η οποία επίσης θα διαγράψει το αρχείο από τον κατάλογο εργασίας μας, ώστε να μην εμφανίζεται ως μη-παρακολουθούμενο αρχείο. Αν απλά διαγράψουμε το αρχείο από τον κατάλογο εργασίας μας, θα εμφανίζεται κάτω από την κατηγορία “Changed but not updated” ( 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 Την επόμενη φορά που θα κάνουμε commit, το αρχείο θα έχει διαγραφεί και δεν θα βρίσκεται υπό παρακολούθηση. Αν είχαμε τροποποιήσει το αρχείο ή το είχαμε ήδη τοποθετήσει στο στάδιο καταχώρησης, θα πρέπει να εξαναγκάσουμε τη διαγραφή του με την επιλογή -f . Πρόκειται για μια λειτουργικότητα ασφαλείας του Git, προκειμένου να αποτρέψει αφαίρεση δεδομένων από σφάλμα που δεν έχουν ακόμα καταγραφεί σε κάποιο στιγμιότυπο και δεν μπορούν να ανακτηθούν από το Git. Κάτι άλλο που μπορεί να θέλουμε να κάνουμε, είναι να κρατήσουμε το αρχείο στον κατάλογο εργασίας μας, αλλά να το αφαιρέσουμε από το στάδιο καταχώρησης. Με άλλα λόγια, ίσως θέλουμε να κρατήσουμε το αρχείο στον σκληρό μας δίσκο, αλλά να μην βρίσκεται πλέον υπό παρακολούθηση από το Git. Αυτό είναι ιδιαίτερα χρήσιμο αν είχαμε ξεχάσει να προσθέσουμε κάτι στο αρχείο .gitignore και το τοποθετήσαμε στο στάδιο καταχώρησης κατά λάθος, όπως για παράδειγμα μεγάλα αρχεία .log ή αρχεία .a που προέκυψαν από μεταγλώττιση. Για να το κάνουμε αυτό, χρησιμοποιoύμε την επιλογή --cached : $ git rm --cached README Μπορούμε να χρησιμοποιήσουμε την παραπάνω εντολή με αρχεία, καταλόγους και μοτίβα glob αρχείων. Αυτό σημαίνει ότι μπορούμε να εκτελέσουμε εντολές όπως: $ git rm log/\*.log Παρατηρήστε το backslash ( \ ) μπροστά από τον αστερίσκο, * . Είναι απαραίτητο, επειδή το Git χρησιμοποιεί κι αυτό ανάπτυξη των ονομάτων των αρχείων (file name expansion), επιπρόσθετα με την ανάπτυξη των ονομάτων των αρχείων του κελύφους. Η παραπάνω εντολή αφαιρεί όλα τα αρχεία που έχουν την κατάληξη .log στον κατάλογο log/ . Επίσης, θα μπορούσαμε να κάνουμε κάτι τέτοιο: $ git rm \*~ Η εντολή αυτή αφαιρεί όλα τα αρχεία που τελειώνουν με τον χαρακτήρα ~ . Μετακίνηση αρχείων Σε αντίθεση με άλλα συστήματα ελέγχου έκδοσης, το Git δεν παρακολουθεί τις μετακινήσεις αρχείων από μόνο του. Αν μετονομάσουμε ένα α� | 2026-01-13T09:29:24 |
https://www.fuse.io/fr/node-sale | Node Sale Fuse Turns Six: Future-Proofing the Entire Network Network Intro to Fuse EVM-compatible, Layer-2 Blockchain Get Fuse Explore the ways to get the native Fuse Network token Ecosystem Web3 Tools for Business Ignite Apply for Funding & Grants Tools Staking Stake FUSE for Rewards Bridge Bridge Assets To & From Fuse Safe Leading Platform to Manage Digital Assets Products Fuse Ember Integrate Web3 in Minutes Edison AI Agent Integrate Web3 in Minutes Gaming Coming soon... FuseBox Integrate Web3 in Minutes Case Studies Real World Case Studies Mystic Valley Freedom Wallet Sanduk Zneakrz Developers Documentation Build on Fuse RPC Providers Build crypto apps that scale Fuse Explorer Query Transactions & Activity Network Status Network performance and status Developers Documentation Build on Fuse RPC Providers Build crypto apps that scale Fuse Explorer Query Transactions & Activity Network Status Network performance and status Tools Ecosystem Web3 Tools for Business NFTs Mint Digital Collectibles on Artrific Community Support & Contribute Telegram Youtube LinkedIn Twitter Github Discord Governance Shape the Future of Fuse About Fuse Blog Latest news and updates Brand Kit Brand assets Jobs Explore opportunities Network Products Developers Ecosystem About Intro to Fuse EVM-compatible, Layer-2 Blockchain Ignite Apply for Funding & Grants Staking Stake FUSE for Rewards Bridge Bridge Assets To & From Fuse Safe Leading Platform to Manage Digital Assets Edison AI Agent Integrate Web3 in Minutes FuseBox Integrate Web3 in Minutes Case studies Real World Case Studies Real world case studies Mystic Valley Ticketing and Event Payments Freedom Wallet Bridging RWAs for Businesses Sanduk Send and receive digital dollars Zneakrz Frictionless e-commerce Documentation Learn about Fuse and get started with guides and tools for building on Fuse RPC Providers Build crypto apps that scale Fuse Explorer Query Transactions & Activity Network Status Network performance and status Get Started Quick Start Fuse Basics FuseBox Tutorials Explore our APIs Smart Wallets API Trade API Notifications API GraphQL API Ecosystem Web3 Tools for Business Community Support & Contribute Governance Shape the Future of Fuse Telegram Youtube LinkedIn Github Twitter Discord Get Fuse Explore the ways to get the native Fuse Network token Fuse Blog Latest news and updates Brand Kit Brand assets Jobs Explore opportunities EN FR JP CN Docs Ember Points Fuse Console The Fuse Ember Node Sale Is Live! As we prepare to launch zkEVM-powered Fuse Ember L2 in Q2 2025, we’re offering 12,000 exclusive node licenses. Nodes will secure the network, processing up to 9,000 transactions per second, while earning a share of ecosystem fees and early adopter incentives. As a node operator, you’ll also play a key role in governance towards the future of blockchain-powered business payments. It’s a chance to own a stake in a growing ecosystem built for real-world adoption. Once these 12,000 licenses are gone, the window closes. Buy Ember Node Find out more about Fuse Ember Global Payments. Effortless Integration. 1 9000 TPS and 0.0001$ fees 2 AI agents for businesses 3 ZK payments for mainstream usage 4 Vertically integrated open source stack 5 Full Mobile compatibility 6 Recurring payments The blockchain for businesses 9000 TPS and 0.0001$ fees AI agents for businesses ZK payments for mainstream usage Vertically integrated open source stack Full Mobile compatibility Recurring payments Node Sale Pricing Node sale participants will purchase NFTs that grant them a share of Fuse Ember emissions and fees, plus governance voting rights. The NFT will be non-transferable for the first year. The first 2,000 nodes will be sold at a discounted price of $315, with successive tranches rising to $2,500. Node sale and tiers information Benefits Of Running An Ember Node Earn a share of 10% of network fees and FuseBox subscriptions Receive additional yield from LST, LRT, and RWA tokens staked on the platform. Receive a percentage of 42 million FUSE Collect airdrop rewards for three years, with 20 million FUSE allocated for year 1 and no vesting schedule. Early tiers ensure a greater ROI Total rewards are split evenly across all active nodes. Tier 1 nodes are exclusively limited to FUSE holders Tier 1 participants will be able to purchase a maximum of 100 nodes each. Community-driven governance Play your part in shaping the future of the Fuse network. Buybacks using 10% of node sale funds Locking Treasury funds and staking FUSE will further help to drive a deflationary economy. Get whitelisted now! Enter your ERC-20 wallet address to be whitelisted and email to be notified when the sale starts. Join Whitelist Thanks, we’ll keep you updated! Oops! Something went wrong while submitting the form. Secure Your Stake In The Future Of Fuse Ember L2 Unlock a world of rewards, participate in governance, and enjoy the benefits of our revolutionary business payments infrastructure. It's time to take your place at the forefront of innovation. Buy Ember Node Backers and partners Big vision requires long term partners Read more about our Plans Fuse migration to Fuse Ember and node sale details and tiers New proposed tokenomics for the transition New proposed staking model Frequently Asked Questions How to purchase a Node License? The process will consist of 3 stages: Whitelist application: users can register for whitelist to get priority access. Whitelisting will start in November 2024. Leave your email to be notified. Whitelist Sale: only whitelisted users can participate in the sale. Nodes are sold on first come, first served basis. Public Sale: the sale is open to all users. What is whitelist? This is a list of wallets that have expressed their desire to buy a node before the sale starts. These participants will receive priority access to buy the node before the public sale starts. What is a Node License and why does it matter? When you participate in the Node Sale, you’re purchasing a Node License : an NFT that grants you the right to operate a Data Availability (DA) Node on Fuse Ember. These nodes play a vital role in the network’s architecture, handling tasks like: Securing data availability Processing transactions efficiently Ensuring the network remains fast, secure, and decentralized If you don’t want to run a node yourself, you can delegate your license to an active operator and still earn passive rewards while they handle the operations. How to get whitelisted? A whitelisting form will be published on this page in November 2024. Leave your email to be notified. What are the rewards and incentives for Node Operators? Node operators are key players in the Fuse Ember ecosystem, and the rewards reflect that: Share in 30% of network fees and FuseBox subscriptions Receive a share of rewards from staked Real-World Assets (RWAs) and Liquid Staking Tokens (LSTs) Voting power to help shape protocol decisions The earlier you join, the greater your rewards, thanks to tiered pricing that favors early participants. Does entering the whitelist guarantee that I can definitely purchase a node? No. The priority sale of nodes to whitelisted participants will be on a first come, first served basis.If all nodes allocated to whitelisted users are sold out, you will be able to participate in the public sale. Leave your email to be notified. How do I participate in the Node Sale? Visit our Node Sale homepage: https://www.fuse.io/node-sale . Register on the NodeOps Console: https://console.nodeops.xyz/bootstrap-event/fuse . Prepare Your Funds: Ensure you have FUSE, USDC, USDT, or wETH on the Fuse network. You can bridge assets to Fuse using https://console.fuse.io/bridge . Purchase your Node License. Your NFT will be non-transferable for the first year. Start earning: Operate your DA Node or delegate it to an active operator. How many nodes will be available in total? A total of 12,000 nodes will be available for purchase in the Fuse Ember network. How much do nodes cost? Nodes are priced in tiers, rising in price as each tier sells out. Early adopters are rewarded with a higher potential ROI. Tier Allocation Table Tier Allocation Price (USD) T1 2,000 $350 T2 1,300 $600 T3 1,250 $850 T4 1,125 $1,000 T5 1,100 $1,250 T6 1,075 $1,500 T7 1,065 $1,750 T8 1,055 $2,000 T9 1,030 $2,250 T10 1,000 $2,500 Can I buy multiple nodes? Yes, each participant can buy any number of nodes. Which jurisdictions can participate in the Node Sale? Residents from FATF-sanctioned jurisdictions (including North Korea, Iran, and Myanmar) are prohibited from participating. Additional restrictions may apply in other regions. Please check whether you are eligible. How will the node licenses be distributed? The node license is an NFT. NFTs will be sent to the buyer's wallet immediately after the license is paid. How will node licenses be distributed? The node license is an NFT. NFTs will be sent to the buyer's wallet immediately after the license fee is paid. NFTs cannot be transferred for the first year. How to run a node? Running and managing nodes on the Fuse Ember network will be done through the NodeOps console. How do I run a node? Running and managing nodes on the Fuse Ember network will be carried out through the NodeOps console . How can I delegate my NFT license? If you don’t want to run your own node, you can delegate your license to another node operator using the Fuse Ember Delegation portal . YouTube Github Twitter Telegram Discord Docs Getting started Fuse Network Mobile Stack Voltage Finance Web3 Glossary Charge Under the hood Explorer Documentation Fuse Staking Governance Service Status General Brand Kits Jobs Ambassador Program FAQ Subscribe to our newsletter © 2024 Fuse. All Rights Reserved | 2026-01-13T09:29:24 |
https://git-scm.com/book/sv/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. 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 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. . Figur 110. The “Your repositories” area. Figur 111. The “New repository” dropdown. This takes you to the “new repository” form: Figur 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 to create a brand-new Git repository, or connect an existing Git project. We won’t belabor this here; if you need a refresher, check out Grunder i Git . Now that your project is hosted on GitHub, you can give the URL to anyone you want to share your project with. Every project on GitHub is accessible over HTTPS as https://github.com/<user>/<project_name> , and over SSH as git@github.com:<user>/<project_name> . Git can fetch from and push to both of these URLs, but they are access-controlled based on the credentials of the user connecting to them. Notera It is often preferable to share the HTTPS based URL for a public project, since the user does not have to have a GitHub account to access it for cloning. Users will have to have an account and an uploaded SSH key to access your project if you give them the SSH URL. The HTTPS one is also exactly the same URL they would paste into a browser to view the project there. Adding Collaborators If you’re working with other people who you want to give commit access to, you need to add them as “collaborators”. If Ben, Jeff, and Louise all sign up for accounts on GitHub, and you want to give them push access to your repository, you can add them to your project. Doing so will give them “push” access, which means they have both read and write access to the project and Git repository. Click the “Settings” link at the bottom of the right-hand sidebar. Figur 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. Figur 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. . Figur 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 Checka ut fjärrgrenar . 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. Figur 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. Figur 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. Figur 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. Figur 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. Figur 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. Figur 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. . Figur 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. Figur 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. Figur 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. Figur 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:24 |
https://git-scm.com/book/fa/v2/%d9%85%d9%82%d8%af%d9%85%d8%a7%d8%aa-%da%af%db%8c%d8%aa-git-basics-chapter-%d9%86%d8%a7%d9%85-%d9%85%d8%b3%d8%aa%d8%b9%d8%a7%d8%b1-%da%af%db%8c%d8%aa-Git-Aliases | Git - نام مستعار گیت (Git Aliases) About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. شروع به کار (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 2.7 مقدمات گیت (git basics chapter) - نام مستعار گیت (Git Aliases) نام مستعار گیت (Git Aliases) نام مستعار 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 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> همانطور که می بینید، گیت به سادگی فرمان جدید را با هر نام دیگری که برای آن انتخاب کرده اید، جایگزین می کند. با این حال، شاید شما می خواهید یک دستور خارجی را اجرا کنید، نه یک زیر دستور گیت. در این حالت، شما دستور را با ! شروع می کنید! شخصیت خوبیه اگر شما ابزار خود را که با یک مخزن گیت کار می کنند بنویسید این کار مفید است. ما می توانیم با استفاده از aliasing `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://git-scm.com/book/es/v2/Fundamentos-de-Git-Guardando-cambios-en-el-Repositorio | Git - Guardando cambios en el Repositorio 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.2 Fundamentos de Git - Guardando cambios en el Repositorio Guardando cambios en el Repositorio Ya tienes un repositorio Git y un checkout o copia de trabajo de los archivos de dicho proyecto. El siguiente paso es realizar algunos cambios y confirmar instantáneas de esos cambios en el repositorio cada vez que el proyecto alcance un estado que quieras conservar. Recuerda que cada archivo de tu repositorio puede tener dos estados: rastreados y sin rastrear. Los archivos rastreados ( tracked files en inglés) son todos aquellos archivos que estaban en la última instantánea del proyecto; pueden ser archivos sin modificar, modificados o preparados. Los archivos sin rastrear son todos los demás - cualquier otro archivo en tu directorio de trabajo que no estaba en tu última instantánea y que no está en el área de preparación ( staging area ). Cuando clonas por primera vez un repositorio, todos tus archivos estarán rastreados y sin modificar pues acabas de sacarlos y aun no han sido editados. Mientras editas archivos, Git los ve como modificados, pues han sido cambiados desde su último commit . Luego preparas estos archivos modificados y finalmente confirmas todos los cambios preparados, y repites el ciclo. Figura 8. El ciclo de vida del estado de tus archivos. Revisando el Estado de tus Archivos La herramienta principal para determinar qué archivos están en qué estado es el comando git status . Si ejecutas este comando inmediatamente después de clonar un repositorio, deberías ver algo como esto: $ git status On branch master nothing to commit, working directory clean Esto significa que tienes un directorio de trabajo limpio - en otras palabras, que no hay archivos rastreados y modificados. Además, Git no encuentra archivos sin rastrear, de lo contrario aparecerían listados aquí. Finalmente, el comando te indica en cuál rama estás y te informa que no ha variado con respecto a la misma rama en el servidor. Por ahora, la rama siempre será “master”, que es la rama por defecto; no le prestaremos atención de momento. [ch03-git-branching] tratará en detalle las ramas y las referencias. Supongamos que añades un nuevo archivo a tu proyecto, un simple README. Si el archivo no existía antes y ejecutas git status , verás el archivo sin rastrear de la siguiente manera: $ echo 'My Project' > README $ git status On branch master Untracked files: (use "git add <file>..." to include in what will be committed) README nothing added to commit but untracked files present (use "git add" to track) Puedes ver que el archivo README está sin rastrear porque aparece debajo del encabezado “Untracked files” (“Archivos no rastreados” en inglés) en la salida. Sin rastrear significa que Git ve archivos que no tenías en el commit anterior. Git no los incluirá en tu próximo commit a menos que se lo indiques explícitamente. Se comporta así para evitar incluir accidentalmente archivos binarios o cualquier otro archivo que no quieras incluir. Como tú sí quieres incluir README, debes comenzar a rastrearlo. Rastrear Archivos Nuevos Para comenzar a rastrear un archivo debes usar el comando git add . Para comenzar a rastrear el archivo README, puedes ejecutar lo siguiente: $ git add README Ahora si vuelves a ver el estado del proyecto, verás que el archivo README está siendo rastreado y está preparado para ser confirmado: $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Puedes ver que está siendo rastreado porque aparece luego del encabezado “Cambios a ser confirmados” (“Changes to be committed” en inglés). Si confirmas en este punto, se guardará en el historial la versión del archivo correspondiente al instante en que ejecutaste git add . Anteriormente cuando ejecutaste git init , ejecutaste luego git add (files) - lo cual inició el rastreo de archivos en tu directorio. El comando git add puede recibir tanto una ruta de archivo como de un directorio; si es de un directorio, el comando añade recursivamente los archivos que están dentro de él. Preparar Archivos Modificados Vamos a cambiar un archivo que esté rastreado. Si cambias el archivo rastreado llamado “CONTRIBUTING.md” y luego ejecutas el comando git status , verás algo parecido a esto: $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md El archivo “CONTRIBUTING.md” aparece en una sección llamada “Changes not staged for commit” (“Cambios no preparado para confirmar” en inglés) - lo que significa que existe un archivo rastreado que ha sido modificado en el directorio de trabajo pero que aún no está preparado. Para prepararlo, ejecutas el comando git add . git add es un comando que cumple varios propósitos - lo usas para empezar a rastrear archivos nuevos, preparar archivos, y hacer otras cosas como marcar archivos en conflicto por combinación como resueltos. Es más útil que lo veas como un comando para “añadir este contenido a la próxima confirmación” más que para “añadir este archivo al proyecto”. Ejecutemos git add para preparar el archivo “CONTRIBUTING.md” y luego ejecutemos git status : $ git add CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Ambos archivos están preparados y formarán parte de tu próxima confirmación. En este momento, supongamos que recuerdas que debes hacer un pequeño cambio en CONTRIBUTING.md antes de confirmarlo. Abres de nuevo el archivo, lo cambias y ahora estás listos para confirmar. Sin embargo, ejecutemos git status una vez más: $ vim CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md ¡¿Pero qué…?! Ahora CONTRIBUTING.md aparece como preparado y como no preparado. ¿Cómo es posible? Resulta que Git prepara un archivo de acuerdo al estado que tenía cuando ejecutas el comando git add . Si confirmas ahora, se confirmará la versión de CONTRIBUTING.md que tenías la última vez que ejecutaste git add y no la versión que ves ahora en tu directorio de trabajo al ejecutar git status . Si modificas un archivo luego de ejecutar git add , deberás ejecutar git add de nuevo para preparar la última versión del archivo: $ git add CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Estado Abreviado Si bien es cierto que la salida de git status es bastante explícita, también es verdad que es muy extensa. Git ofrece una opción para obtener un estado abreviado, de manera que puedas ver tus cambios de una forma más compacta. Si ejecutas git status -s o git status --short , obtendrás una salida mucho más simplificada. $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt Los archivos nuevos que no están rastreados tienen un ?? a su lado, los archivos que están preparados tienen una A y los modificados una M . El estado aparece en dos columnas - la columna de la izquierda indica el estado preparado y la columna de la derecha indica el estado sin preparar. Por ejemplo, en esa salida, el archivo README está modificado en el directorio de trabajo pero no está preparado, mientras que lib/simplegit.rb está modificado y preparado. El archivo Rakefile fue modificado, preparado y modificado otra vez por lo que existen cambios preparados y sin preparar. Ignorar Archivos A veces, tendrás algún tipo de archivo que no quieres que Git añada automáticamente o más aun, que ni siquiera quieras que aparezca como no rastreado. Este suele ser el caso de archivos generados automáticamente como trazas o archivos creados por tu sistema de compilación. En estos casos, puedes crear un archivo llamado .gitignore que liste patrones a considerar. Este es un ejemplo de un archivo .gitignore : $ cat .gitignore *.[oa] *~ La primera línea le indica a Git que ignore cualquier archivo que termine en “.o” o “.a” - archivos de objeto o librerías que pueden ser producto de compilar tu código. La segunda línea le indica a Git que ignore todos los archivos que terminen con una tilde ( ~ ), la cual es usada por varios editores de texto como Emacs para marcar archivos temporales. También puedes incluir cosas como trazas, temporales, o pid directamente; documentación generada automáticamente; etc. Crear un archivo .gitignore antes de comenzar a trabajar es generalmente una buena idea, pues así evitas confirmar accidentalmente archivos que en realidad no quieres incluir en tu repositorio Git. Las reglas sobre los patrones que puedes incluir en el archivo .gitignore son las siguientes: Ignorar las líneas en blanco y aquellas que comiencen con # . Emplear patrones glob estándar que se aplicarán recursivamente a todo el directorio del repositorio local. Los patrones pueden comenzar en barra ( / ) para evitar recursividad. Los patrones pueden terminar en barra ( / ) para especificar un directorio. Los patrones pueden negarse si se añade al principio el signo de exclamación ( ! ). Los patrones glob son una especie de expresión regular simplificada usada por los terminales. Un asterisco ( * ) corresponde a cero o más caracteres; [abc] corresponde a cualquier caracter dentro de los corchetes (en este caso a, b o c); el signo de interrogación ( ? ) corresponde a un caracter cualquiera; y los corchetes sobre caracteres separados por un guión ( [0-9] ) corresponde a cualquier caracter entre ellos (en este caso del 0 al 9). También puedes usar dos asteriscos para indicar directorios anidados; a/**/z coincide con a/z , a/b/z , a/b/c/z , etc. Aquí puedes ver otro ejemplo de un archivo .gitignore : # ignora los archivos terminados en .a *.a # pero no lib.a, aun cuando había ignorado los archivos terminados en .a en la línea anterior !lib.a # ignora unicamente el archivo TODO de la raiz, no subdir/TODO /TODO # ignora todos los archivos del directorio build/ build/ # ignora doc/notes.txt, pero no este: doc/server/arch.txt doc/*.txt # ignora todos los archivos .txt del directorio doc/ doc/**/*.txt Sugerencia GitHub mantiene una extensa lista de archivos .gitignore adecuados a docenas de proyectos y lenguajes en https://github.com/github/gitignore , en caso de que quieras tener un punto de partida para tu proyecto. Ver los Cambios Preparados y No Preparados Si el comando git status es muy impreciso para ti - quieres ver exactamente que ha cambiado, no solo cuáles archivos lo han hecho - puedes usar el comando git diff . Hablaremos sobre git diff más adelante, pero lo usarás probablemente para responder estas dos preguntas: ¿Qué has cambiado pero aun no has preparado? y ¿Qué has preparado y está listo para confirmar? A pesar de que git status responde a estas preguntas de forma muy general listando el nombre de los archivos, git diff te muestra las líneas exactas que fueron añadidas y eliminadas, es decir, el parche. Supongamos que editas y preparas el archivo README de nuevo y luego editas CONTRIBUTING.md pero no lo preparas. Si ejecutas el comando git status , verás algo como esto: $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Para ver qué has cambiado pero aun no has preparado, escribe git diff sin más parámetros: $ git diff diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,8 @@ branch directly, things can get messy. Please include a nice description of your changes when you submit your PR; if we have to read the whole diff to figure out why you're contributing in the first place, you're less likely to get feedback and have your change -merged in. +merged in. Also, split your changes into comprehensive chunks if you patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's Este comando compara lo que tienes en tu directorio de trabajo con lo que está en el área de preparación. El resultado te indica los cambios que has hecho pero que aun no has preparado. Si quieres ver lo que has preparado y será incluido en la próxima confirmación, puedes usar git diff --staged . Este comando compara tus cambios preparados con la última instantánea confirmada. $ 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 Es importante resaltar que al llamar a git diff sin parámetros no verás los cambios desde tu última confirmación - solo verás los cambios que aun no están preparados. Esto puede ser confuso porque si preparas todos tus cambios, git diff no te devolverá ninguna salida. Pasemos a otro ejemplo, si preparas el archivo CONTRIBUTING.md y luego lo editas, puedes usar git diff para ver los cambios en el archivo que ya están preparados y los cambios que no lo están. Si nuestro ambiente es como este: $ git add CONTRIBUTING.md $ echo 'test line' >> CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md Puedes usar git diff para ver qué está sin preparar $ 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 y git diff --cached para ver que has preparado hasta ahora (--staged y --cached son 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 you patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's Nota Git Diff como Herramienta Externa A lo largo del libro, continuaremos usando el comando git diff de distintas maneras. Existe otra forma de ver estas diferencias si prefieres utilizar una interfaz gráfica u otro programa externo. Si ejecutas git difftool en vez de git diff , podrás ver los cambios con programas de este tipo como Araxis, emerge, vimdiff y más. Ejecuta git difftool --tool-help para ver qué tienes disponible en tu sistema. Confirmar tus Cambios Ahora que tu área de preparación está como quieres, puedes confirmar tus cambios. Recuerda que cualquier cosa que no esté preparada - cualquier archivo que hayas creado o modificado y que no hayas agregado con git add desde su edición - no será confirmado. Se mantendrán como archivos modificados en tu disco. En este caso, digamos que la última vez que ejecutaste git status verificaste que todo estaba preparado y que estás listo para confirmar tus cambios. La forma más sencilla de confirmar es escribiendo git commit : $ git commit Al hacerlo, arrancará el editor de tu preferencia. (El editor se establece a través de la variable de ambiente $EDITOR de tu terminal - usualmente es vim o emacs, aunque puedes configurarlo con el editor que quieras usando el comando git config --global core.editor tal como viste en [ch01-introduction] ). El editor mostrará el siguiente texto (este ejemplo corresponde a una pantalla de 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 # Changes to be committed: # new file: README # modified: CONTRIBUTING.md # ~ ~ ~ ".git/COMMIT_EDITMSG" 9L, 283C Puedes ver que el mensaje de confirmación por defecto contiene la última salida del comando git status comentada y una línea vacía encima de ella. Puedes eliminar estos comentarios y escribir tu mensaje de confirmación, o puedes dejarlos allí para ayudarte a recordar qué estás confirmando. (Para obtener una forma más explícita de recordar qué has modificado, puedes pasar la opción -v a git commit . Al hacerlo se incluirá en el editor el diff de tus cambios para que veas exactamente qué cambios estás confirmando). Cuando sales del editor, Git crea tu confirmación con tu mensaje (eliminando el texto comentado y el diff). Otra alternativa es escribir el mensaje de confirmación directamente en el comando commit utilizando la opción -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 ¡Has creado tu primera confirmación (o commit )! Puedes ver que la confirmación te devuelve una salida descriptiva: indica cuál rama has confirmado ( master ), que checksum SHA-1 tiene el commit ( 463dc4f ), cuántos archivos han cambiado y estadísticas sobre las líneas añadidas y eliminadas en el commit . Recuerda que la confirmación guarda una instantánea de tu área de preparación. Todo lo que no hayas preparado sigue allí modificado; puedes hacer una nueva confirmación para añadirlo a tu historial. Cada vez que realizas un commit , guardas una instantánea de tu proyecto la cual puedes usar para comparar o volver a ella luego. Saltar el Área de Preparación A pesar de que puede resultar muy útil para ajustar los commits tal como quieres, el área de preparación es a veces un paso más complejo de lo que necesitas para tu flujo de trabajo. Si quieres saltarte el área de preparación, Git te ofrece un atajo sencillo. Añadiendo la opción -a al comando git commit harás que Git prepare automáticamente todos los archivos rastreados antes de confirmarlos, ahorrándote el paso de git add : $ git status On branch master Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md no changes added to commit (use "git add" and/or "git commit -a") $ git commit -a -m 'added new benchmarks' [master 83e38c7] added new benchmarks 1 file changed, 5 insertions(+), 0 deletions(-) Fíjate que en este caso no fue necesario ejecutar git add sobre el archivo CONTRIBUTING.md antes de confirmar. Eliminar Archivos Para eliminar archivos de Git, debes eliminarlos de tus archivos rastreados (o mejor dicho, eliminarlos del área de preparación) y luego confirmar. Para ello existe el comando git rm , que además elimina el archivo de tu directorio de trabajo de manera que no aparezca la próxima vez como un archivo no rastreado. Si simplemente eliminas el archivo de tu directorio de trabajo, aparecerá en la sección “Changes not staged for commit” (esto es, sin preparar ) en la salida de 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") Ahora, si ejecutas git rm , entonces se prepara la eliminación del archivo: $ git rm PROJECTS.md rm 'PROJECTS.md' $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) deleted: PROJECTS.md Con la próxima confirmación, el archivo habrá desaparecido y no volverá a ser rastreado. Si modificaste el archivo y ya lo habías añadido al índice, tendrás que forzar su eliminación con la opción -f . Esta propiedad existe por seguridad, para prevenir que elimines accidentalmente datos que aun no han sido guardados como una instantánea y que por lo tanto no podrás recuperar luego con Git. Otra cosa que puedas querer hacer es mantener el archivo en tu directorio de trabajo pero eliminarlo del área de preparación. En otras palabras, quisieras mantener el archivo en tu disco duro pero sin que Git lo siga rastreando. Esto puede ser particularmente útil si olvidaste añadir algo en tu archivo .gitignore y lo preparaste accidentalmente, algo como un gran archivo de trazas a un montón de archivos compilados .a . Para hacerlo, utiliza la opción --cached : $ git rm --cached README Al comando git rm puedes pasarle archivos, directorios y patrones glob. Lo que significa que puedes hacer cosas como $ git rm log/\*.log Fíjate en la barra invertida ( \ ) antes del asterisco * . Esto es necesario porque Git hace su propia expansión de nombres de archivo, aparte de la expansión hecha por tu terminal. Este comando elimina todos los archivo que tengan la extensión .log dentro del directorio log/ . O también puedes hacer algo como: $ git rm \*~ Este comando elimina todos los archivos que acaben con ~ . Cambiar el Nombre de los Archivos Al contrario que muchos sistemas VCS, Git no rastrea explícitamente los cambios de nombre en archivos. Si renombras un archivo en Git, no se guardará ningún metadato que indique que renombraste el archivo. Sin embargo, Git es bastante listo como para detectar estos cambios luego que los has hecho - más adelante, veremos cómo se detecta el cambio de nombre. Por esto, resulta confuso que Git tenga un comando mv . Si quieres renombrar un archivo en Git, puedes ejecutar algo como $ git mv file_from file_to y funcionará bien. De hecho, si ejecutas algo como eso y ves el estado, verás que Git lo considera como un renombramiento de archivo: $ git mv README.md README $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Sin embargo, eso es equivalente a ejecutar algo como esto: $ mv README.md README $ git rm README.md $ git add README Git se da cuenta que es un renombramiento implícito, así que no importa si renombras el archivo de esa manera o a través del comando mv . La única diferencia real es que mv es un solo comando en vez de tres - existe por conveniencia. De hecho, puedes usar la herramienta que quieras para renombrar un archivo y luego realizar el proceso rm/add antes de confirmar. 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#collect-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://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=ky | 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/fa/v2/%da%af%db%8c%d8%aa-%d9%87%d8%a7%d8%a8-GitHub-%d9%86%da%af%d9%87%d8%af%d8%a7%d8%b1%db%8c-%db%8c%da%a9-%d9%be%d8%b1%d9%88%da%98%d9%87-Maintaining-a-Project | Git - نگهداری یک پروژه (Maintaining a Project) About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. شروع به کار (getting started) 1.1 درباره ورژن کنترل (About Version Control) 1.2 تاریخچه کوتاهی از گیت (A Short History of Git) 1.3 گیت چیست؟ (What is Git) 1.4 نصب گیت (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 6.3 گیت هاب (GitHub) - نگهداری یک پروژه (Maintaining a Project) نگهداری یک پروژه (Maintaining a Project) حالا که در مشارکت در یک پروژه راحت شدهایم، بیایید به سمت دیگر قضیه نگاه کنیم: ایجاد، نگهداری و مدیریت پروژهی خودتان. ایجاد یک مخزن جدید (Creating a New Repository) بیایید یک مخزن جدید بسازیم تا کد پروژهمان را به اشتراک بگذاریم. با کلیک روی دکمهی «New repository» در سمت راست داشبورد شروع کنید، یا از دکمهی «+» در نوار ابزار بالای صفحه کنار نام کاربریتان استفاده کنید، همانطور که در The “New repository” dropdown دیده میشود. نمودار 109. The “Your repositories” area نمودار 110. The “New repository” dropdown این شما را به فرم “new repository” هدایت میکند: نمودار 111. The “new repository” form تنها کاری که واقعاً باید انجام دهید این است که نام پروژه را وارد کنید؛ بقیه فیلدها کاملاً اختیاری هستند. فعلاً فقط روی دکمهی «Create Repository» کلیک کنید، و همینطور — یک مخزن جدید روی گیتهاب با نام <user>/<project_name> دارید. از آنجا که هنوز هیچ کدی در این مخزن نیست، گیتهاب به شما دستورالعملهایی برای ساخت یک مخزن گیت کاملاً جدید یا اتصال یک پروژهی گیت موجود نشان میدهد. ما اینجا وارد جزئیات نمیشویم؛ اگر نیاز به بازخوانی دارید، بخش مقدمات گیت (git basics chapter) را مطالعه کنید. حالا که پروژهی شما روی گیتهاب میزبانی شده است، میتوانید آدرس URL آن را به هر کسی که میخواهید پروژه را با او به اشتراک بگذارید، بدهید. هر پروژهای روی گیتهاب از طریق HTTPS به صورت https://github.com/<user>/<project_name&gt ; و از طریق SSH به صورت git@github.com:<user>/<project_name> قابل دسترسی است. گیت میتواند از هر دو URL دریافت و ارسال کند، اما دسترسی به آنها بر اساس اعتبارنامههای کاربری که به آنها متصل میشوند کنترل میشود. یادداشت اغلب ترجیح داده میشود که URL مبتنی بر HTTPS را برای پروژههای عمومی به اشتراک بگذارید، چرا که کاربر برای کلون کردن نیازی به حساب کاربری گیتهاب ندارد. اگر URL SSH را بدهید، کاربران باید حساب کاربری و کلید SSH آپلود شده داشته باشند تا بتوانند به پروژه دسترسی پیدا کنند. همچنین، URL HTTPS همان آدرسی است که آنها میتوانند در مرورگر خود برای مشاهده پروژه وارد کنند. اضافه کردن همکاران (Adding Collaborators) اگر با افرادی کار میکنید که میخواهید دسترسی تعهد (commit) به آنها بدهید، باید آنها را به عنوان «collaborators» اضافه کنید. اگر بن، جف و لوئیس همه در گیتهاب حساب کاربری بسازند و شما بخواهید دسترسی push به مخزن خود بدهید، میتوانید آنها را به پروژه اضافه کنید. این کار به آنها دسترسی «push» میدهد، بدین معنا که هم به پروژه و مخزن گیت خواندن و نوشتن دارند. روی لینک “Setting” در پایین نوار کناری سمت راست کلیک کنید. نمودار 112. The repository settings link سپس از منوی سمت چپ «Collaborators» را انتخاب کنید. بعد، فقط نام کاربری را در کادر تایپ کنید و روی «Add collaborator» کلیک کنید. میتوانید این کار را به هر تعداد که دوست دارید تکرار کنید تا به همهی افراد دلخواه دسترسی بدهید. اگر نیاز به لغو دسترسی داشتید، فقط روی «X» در سمت راست ردیف آنها کلیک کنید. نمودار 113. The repository collaborators box مدیریت درخواستهای کشش (Managing Pull Requests) حالا که یک پروژه با مقداری کد دارید و شاید چند همکار که دسترسی push دارند، بیایید ببینیم وقتی خودتان یک Pull Request دریافت میکنید، چه کار باید بکنید. درخواستهای Pull میتوانند یا از یک شاخه در یک فورک مخزن شما بیایند یا از شاخهای دیگر در همان مخزن. تنها تفاوت این است که درخواستهای Pull در فورکها اغلب از افرادی هستند که شما نمیتوانید به شاخه آنها push کنید و آنها هم نمیتوانند به شاخه شما push کنند، در حالی که در درخواستهای Pull داخلی معمولاً هر دو طرف به شاخه دسترسی دارند. برای این مثالها فرض کنیم شما “tonychacon” هستید و یک پروژه کد آردوینو به نام «fade» ساختهاید. اعلانهای ایمیلی (Email Notifications) کسی میآید و تغییری در کد شما ایجاد میکند و یک Pull Request برای شما ارسال میکند. شما باید ایمیلی دریافت کنید که در مورد Pull Request جدید اطلاع دهد و این ایمیل باید چیزی شبیه به Email notification of a new Pull Request باشد. نمودار 114. Email notification of a new Pull Request چند نکته درباره این ایمیل وجود دارد که باید بدانید. این ایمیل یک خلاصه کوچک از تغییرات (diffstat) به شما میدهد — فهرستی از فایلهایی که در درخواست Pull تغییر کردهاند و میزان تغییرات آنها. همچنین یک لینک به درخواست Pull در گیتهاب به شما ارائه میکند. چند URL نیز دارد که میتوانید از طریق خط فرمان از آنها استفاده کنید. اگر به خطی که نوشته git pull <url> patch-1 دقت کنید، این یک روش ساده برای ادغام یک شاخه از راه دور بدون نیاز به اضافه کردن remote است. ما این موضوع را سریعاً در بررسی شاخههای ریموت (Checking Out Remote Branches) مرور کردیم. اگر بخواهید، میتوانید یک شاخه موضوعی (topic branch) ایجاد و به آن سوئیچ کنید و سپس این دستور را اجرا کنید تا تغییرات درخواست Pull را ادغام کنید. URLهای جالب دیگر، URLهای .diff و .patch هستند که همانطور که حدس میزنید، نسخههای unified diff و patch از درخواست Pull را ارائه میدهند. از نظر فنی، میتوانید کار درخواست Pull را با چیزی شبیه به این ادغام کنید: $ curl https://github.com/tonychacon/fade/pull/1.patch | git am همکاری روی درخواست کشش (Collaborating on the Pull Request) همانطور که در روند کاری گیتهاب (The GitHub Flow) توضیح دادیم، اکنون میتوانید با شخصی که درخواست Pull را باز کرده است گفتگو کنید. میتوانید روی خطوط خاصی از کد نظر بگذارید، روی کامیتهای کامل یا کل درخواست Pull نظر بدهید و در همه جا از Markdown با سبک GitHub استفاده کنید. هر بار که شخص دیگری روی درخواست Pull نظر میدهد، شما ایمیل اطلاعرسانی دریافت میکنید تا بدانید فعالیتی در حال انجام است. هر ایمیل شامل لینکی به درخواست Pull است که فعالیت در آنجا اتفاق میافتد و همچنین میتوانید مستقیماً به ایمیل پاسخ دهید و در همان رشته (thread) درخواست Pull نظر بگذارید. نمودار 115. Responses to emails are included in the thread وقتی کد به جایی رسید که راضی بودید و میخواهید آن را ادغام کنید، میتوانید کد را دانلود کرده و محلی ادغام کنید، یا با دستور git pull <url> <branch> که قبلاً دیدیم، یا با افزودن فورک به عنوان remote و گرفتن و ادغام آن. اگر ادغام ساده باشد، میتوانید به سادگی روی دکمه «Merge» در سایت گیتهاب کلیک کنید. این کار یک ادغام «non-fast-forward» انجام میدهد، یعنی یک کامیت ادغام ایجاد میکند حتی اگر ادغام fast-forward ممکن باشد. این یعنی هر بار که دکمه merge را میزنید، یک کامیت ادغام ساخته میشود. همانطور که در Merge button and instructions for merging a Pull Request manually میبینید، گیتهاب همه این اطلاعات را اگر روی لینک راهنما کلیک کنید، به شما نشان میدهد. نمودار 116. Merge button and instructions for merging a Pull Request manually اگر تصمیم گرفتید که نمیخواهید ادغام کنید، میتوانید فقط درخواست Pull را ببندید و شخصی که آن را باز کرده است، مطلع خواهد شد. رفرنسهای درخواست کشش (Pull Request Refs) گیتهاب در واقع شاخههای درخواست Pull را به عنوان شاخههای شبه (pseudo-branches) روی سرور تبلیغ میکند. به طور پیشفرض وقتی کلون میکنید آنها را دریافت نمیکنید، اما به شکلی پنهان وجود دارند و میتوانید به راحتی به آنها دسترسی پیدا کنید. برای نشان دادن این موضوع، از یک دستور سطح پایین (که اغلب به آن دستور «لولهکشی» یا plumbing گفته میشود و در ابزارها و دستورات سطح پایین (Plumbing and Porcelain) بیشتر درباره آن میخوانیم) به نام ls-remote استفاده میکنیم. این دستور معمولاً در عملیات روزمره گیت استفاده نمیشود اما مفید است برای اینکه به ما نشان دهد چه ارجاعاتی روی سرور وجود دارد. اگر این دستور را روی مخزن “blink” که قبلاً استفاده میکردیم اجرا کنیم، فهرستی از همه شاخهها، تگها و ارجاعات دیگر در مخزن به ما میدهد. $ git ls-remote https://github.com/schacon/blink 10d539600d86723087810ec636870a504f4fee4d HEAD 10d539600d86723087810ec636870a504f4fee4d refs/heads/master 6a83107c62950be9453aac297bb0193fd743cd6e refs/pull/1/head afe83c2d1a70674c9505cc1d8b7d380d5e076ed3 refs/pull/1/merge 3c8d735ee16296c242be7a9742ebfbc2665adec1 refs/pull/2/head 15c9f4f80973a2758462ab2066b6ad9fe8dcf03d refs/pull/2/merge a5a7751a33b7e86c5e9bb07b26001bb17d775d1a refs/pull/4/head 31a45fc257e8433c8d8804e3e848cf61c9d3166c refs/pull/4/merge البته، اگر در مخزن خود باشید و دستور git ls-remote origin یا هر ریموت دیگری که میخواهید بررسی کنید را اجرا کنید، چیزی مشابه این مشاهده خواهید کرد. اگر مخزن روی GitHub باشد و هر درخواست Pull (Pull Request) باز شدهای داشته باشید، این ارجاعات را خواهید دید که با refs/pull/ شروع میشوند. اینها اساساً شاخه هستند، اما چون زیر refs/heads/ نیستند، معمولاً هنگام کلون کردن یا fetch گرفتن از سرور به شما نمایش داده نمیشوند — فرایند fetch معمولاً آنها را نادیده میگیرد. برای هر درخواست Pull دو ارجاع وجود دارد — ارجاعی که به /head ختم میشود دقیقاً به همان کامیتی اشاره میکند که آخرین کامیت در شاخه درخواست Pull است. پس اگر کسی در مخزن ما یک درخواست Pull باز کند و شاخهاش به نام bug-fix باشد و به کامیت a5a775 اشاره کند، در مخزن خودمان شاخهای به نام bug-fix نخواهیم داشت (چون آن در فورک آنها است)، اما داشتن ارجاع pull/<pr#>/head که به a5a775 اشاره میکند، خواهیم داشت. این یعنی میتوانیم به آسانی همه شاخههای درخواست Pull را یکجا دریافت کنیم بدون اینکه مجبور باشیم تعداد زیادی ریموت اضافه کنیم. حالا، میتوانید کاری مانند دریافت مستقیم ارجاع را انجام دهید. $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD این به Git میگوید: « به ریموت `origin وصل شو، و ارجاع به نام refs/pull/958/head را دانلود کن. » Git با کمال میل این کار را انجام میدهد و همه چیز لازم برای ساختن آن ارجاع را دانلود میکند و اشارهگری به کامیتی که میخواهید را زیر `.git/FETCH_HEAD قرار میدهد. شما میتوانید بعد از آن با دستور git merge FETCH_HEAD این را در شاخهای که میخواهید تست کنید ادغام کنید، اما پیام کامیت ادغام کمی عجیب به نظر میرسد. همچنین، اگر تعداد زیادی درخواست Pull را بررسی میکنید، این کار خستهکننده میشود. یک روش هم برای دریافت تمام درخواستهای Pull و بهروزرسانی آنها هر بار که به ریموت وصل میشوید وجود دارد. فایل .git/config را در ویرایشگر مورد علاقهتان باز کنید و دنبال ریموت origin بگردید. باید چیزی شبیه به این باشد: [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* خطی که با fetch = شروع میشود، یک “refspec” است. روشی برای نگاشت نامها در ریموت با نامها در دایرکتوری محلی .git شماست. این refspec خاص به Git میگوید: «مواردی که در ریموت زیر refs/heads هستند باید در مخزن محلی من زیر refs/remotes/origin ذخیره شوند.» میتوانید این بخش را اصلاح کنید و یک refspec دیگر اضافه کنید: [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* خط آخر به Git میگوید: «تمام ارجاعهایی که شبیه refs/pull/123/head هستند باید به صورت محلی مانند refs/remotes/origin/pr/123 ذخیره شوند.» حالا اگر آن فایل را ذخیره کنید و دستور git fetch را اجرا کنید: $ git fetch # … * [new ref] refs/pull/1/head -> origin/pr/1 * [new ref] refs/pull/2/head -> origin/pr/2 * [new ref] refs/pull/4/head -> origin/pr/4 # … اکنون همه درخواستهای Pull ریموت به صورت محلی با ارجاعهایی نمایش داده میشوند که مثل شاخههای پیگیری عمل میکنند؛ فقط خواندنی هستند و هر بار که fetch میکنید بهروزرسانی میشوند. این کار بسیار ساده میکند تا کد یک درخواست Pull را به صورت محلی تست کنید: $ git checkout pr/2 Checking out files: 100% (3769/3769), done. Branch pr/2 set up to track remote branch pr/2 from origin. Switched to a new branch 'pr/2' کسانی که با دقت نگاه میکنند متوجه head در انتهای بخش ریموت refspec خواهند شد. همچنین یک ارجاع refs/pull/#/merge در سمت GitHub وجود دارد که نشاندهنده کامیتی است که در صورت زدن دکمه “merge” در سایت حاصل میشود. این امکان را فراهم میکند که قبل از زدن دکمه، ادغام را تست کنید. درخواستهای کشش روی درخواستهای کشش (Pull Requests on Pull Requests) شما میتوانید نه تنها درخواستهای Pull را به شاخهی اصلی یا master ارسال کنید، بلکه در واقع میتوانید درخواست Pull را به هر شاخهای در شبکه هدف قرار دهید. در واقع، حتی میتوانید یک درخواست Pull را هدف بگیرید. اگر درخواست Pull ای را دیدید که در مسیر درستی حرکت میکند و ایدهای برای تغییر دارید که به آن وابسته است، یا مطمئن نیستید که ایدهی خوبی باشد، یا دسترسی برای ارسال مستقیم به شاخه هدف را ندارید، میتوانید مستقیماً درخواست Pull را به آن ارسال کنید. وقتی میخواهید درخواست Pull باز کنید، در بالای صفحه جعبهای وجود دارد که مشخص میکند شما درخواست ادغام از کدام شاخه به کدام شاخه را دارید. اگر روی دکمهی “Edit” در سمت راست آن جعبه کلیک کنید، میتوانید نه تنها شاخهها بلکه فورک مورد نظر را نیز تغییر دهید. نمودار 117. Manually change the Pull Request target fork and branch در اینجا میتوانید بهراحتی مشخص کنید که شاخه جدیدتان را به یک درخواست Pull دیگر یا فورک دیگری از پروژه ادغام کنید. ذکرها و اعلانها (Mentions and Notifications) گیتهاب همچنین سیستم اعلانهای بسیار خوبی دارد که وقتی سوالی دارید یا به بازخورد از افراد یا تیمهای خاص نیاز دارید، بسیار مفید است. در هر کامنت میتوانید کاراکتر @ را تایپ کنید و گیتهاب شروع به تکمیل خودکار نامها و نامکاربری افرادی میکند که همکار یا مشارکتکننده در پروژه هستند. نمودار 118. Start typing @ to mention someone همچنین میتوانید کاربری را که در آن لیست نیست، به صورت دستی ذکر کنید، اما اغلب تکمیل خودکار کار را سریعتر میکند. پس از ارسال کامنت با ذکر کاربر، آن کاربر مطلع خواهد شد. این یعنی این روش میتواند بسیار مؤثر باشد برای جلب توجه افراد به مکالمات، به جای اینکه آنها را مجبور به رصد کردن کنید. اغلب در درخواستهای Pull در گیتهاب، افراد دیگر اعضای تیم یا شرکت خود را برای بررسی یک Issue یا Pull Request وارد گفتگو میکنند. اگر کسی در یک درخواست Pull یا Issue ذکر شود، به آن مورد “subscribed” میشود و هر بار که فعالیتی روی آن انجام شود، اعلان دریافت خواهد کرد. شما هم به مواردی که باز کردهاید، یا مخزن را دنبال میکنید، یا در آن نظر دادهاید، بهطور خودکار عضو میشوید. اگر دیگر نمیخواهید اعلان دریافت کنید، دکمهی “Unsubscribe” در صفحه وجود دارد که میتوانید با کلیک روی آن، دریافت بهروزرسانیها را متوقف کنید. نمودار 119. Unsubscribe from an Issue or Pull Request صفحه اعلانها (The Notifications Page) وقتی دربارهی “اعلانها” در گیتهاب صحبت میکنیم، منظورمان روشی خاص است که گیتهاب برای اطلاعرسانی به شما هنگام رخ دادن رویدادها دارد و شما میتوانید آنها را به چند روش مختلف تنظیم کنید. اگر به تب “Notification center” در صفحه تنظیمات بروید، میتوانید برخی از گزینههای موجود را ببینید. نمودار 120. Notification center options دو گزینه اصلی دریافت اعلانها از طریق “ایمیل” و “وب” هستند و میتوانید برای زمانی که در فعالیتها شرکت میکنید و فعالیت روی مخازنی که دنبال میکنید، هر دو، هیچکدام یا یکیشان را انتخاب کنید. اعلانهای وب (Web Notifications) اعلانهای وب فقط در گیتهاب وجود دارند و فقط میتوانید آنها را در گیتهاب مشاهده کنید. اگر این گزینه را در تنظیمات خود فعال کرده باشید و اعلان جدیدی برای شما ایجاد شود، یک نقطهی کوچک آبی روی آیکون اعلانها در بالای صفحه ظاهر میشود، همانطور که در Notification center دیده میشود. نمودار 121. Notification center با کلیک روی آن، فهرستی از تمام مواردی که اعلان دریافت کردهاید، به تفکیک پروژه نمایش داده میشود. میتوانید با کلیک روی نام پروژه در نوار کناری سمت چپ، اعلانهای یک پروژه خاص را فیلتر کنید. همچنین میتوانید با کلیک روی آیکون تیک کنار هر اعلان، آن را تأیید کنید، یا تمام اعلانهای یک پروژه را با کلیک روی تیک بالای گروه تأیید نمایید. دکمهی سایلنت (بیصدا) نیز کنار هر تیک وجود دارد که اگر کلیک کنید، دیگر اعلانهای آن مورد خاص را دریافت نخواهید کرد. تمام این ابزارها برای مدیریت تعداد زیادی اعلان بسیار کاربردی هستند. بسیاری از کاربران حرفهای گیتهاب، اعلانهای ایمیل را کاملاً غیرفعال میکنند و تمام اعلانهای خود را از طریق این صفحه مدیریت میکنند. اعلانهای ایمیل (Email Notifications) اعلانهای ایمیل روش دیگری برای دریافت اعلانها از طریق گیتهاب هستند. اگر این گزینه را فعال کنید، برای هر اعلان یک ایمیل دریافت خواهید کرد. ما نمونههایی از این اعلانها را در Comments sent as email notifications و Email notification of a new Pull Request دیدیم. ایمیلها همچنین بهصورت موضوعبندی شده (Threaded) ارسال میشوند، که اگر از کلاینت ایمیل با پشتیبانی از این قابلیت استفاده کنید، بسیار مناسب است. علاوه بر این، مقدار قابل توجهی از فراداده (metadata) در هدرهای ایمیلهایی که گیتهاب ارسال میکند وجود دارد، که برای تنظیم فیلترها و قوانین سفارشی بسیار مفید است. برای مثال، اگر به هدرهای ایمیل واقعی که به تونی در ایمیل نشان دادهشده در Email notification of a new Pull Request ارسال شده نگاه کنیم، اطلاعات زیر در میان دادههای ارسالی دیده میشود: To: tonychacon/fade <fade@noreply.github.com> Message-ID: <tonychacon/fade/pull/1@github.com> Subject: [fade] Wait longer to see the dimming effect better (#1) X-GitHub-Recipient: tonychacon List-ID: tonychacon/fade <fade.tonychacon.github.com> List-Archive: https://github.com/tonychacon/fade List-Post: <mailto:reply+i-4XXX@reply.github.com> List-Unsubscribe: <mailto:unsub+i-XXX@reply.github.com>,... X-GitHub-Recipient-Address: tchacon@example.com چند نکته جالب در اینجا وجود دارد. اگر بخواهید ایمیلها را به این پروژه خاص یا حتی درخواست پول (Pull Request) مشخصی هدایت یا برجسته کنید، اطلاعات موجود در `Message-ID` تمام دادهها را به فرمت `<user>/<project>/<type>/<id>` در اختیار شما قرار میدهد. برای مثال، اگر این یک مسئله (Issue) بود، فیلد `<type>` به جای "`pull`" مقدار "`issues`" را داشت. فیلدهای List-Post و List-Unsubscribe به این معنا هستند که اگر کلاینت ایمیل شما این قابلیتها را پشتیبانی کند، به راحتی میتوانید به لیست ایمیل ارسال کنید یا از دریافت این موضوع خاص لغو اشتراک کنید. این عملکرد عملاً معادل کلیک روی دکمه “mute” در نسخه وب اعلان یا گزینه “Unsubscribe” در صفحه Issue یا Pull Request است. همچنین شایان ذکر است که اگر اعلانهای ایمیل و وب هر دو فعال باشند و شما نسخه ایمیلی اعلان را بخوانید، نسخه وب نیز به عنوان خوانده شده علامتگذاری میشود، البته به شرطی که در کلاینت ایمیل خود اجازه نمایش تصاویر را داده باشید. فایلهای ویژه (Special Files) چند فایل ویژه وجود دارند که اگر در مخزن شما باشند، گیتهاب آنها را تشخیص میدهد. فایل معرفی (README) اولین فایل README است که میتواند تقریباً هر فرمتی داشته باشد که گیتهاب به عنوان متن قابل خواندن بشناسد. مثلاً میتواند README ، README.md ، README.asciidoc و غیره باشد. اگر گیتهاب فایل README را در سورس شما ببیند، آن را در صفحه اصلی پروژه نمایش میدهد. بسیاری از تیمها از این فایل استفاده میکنند تا تمام اطلاعات مرتبط با پروژه را برای کسی که تازه با مخزن یا پروژه آشنا شده، ارائه دهند. معمولاً این اطلاعات شامل موارد زیر است: هدف پروژه چیست چگونه آن را پیکربندی و نصب کنیم نمونهای از نحوه استفاده یا اجرای آن مجوزی که پروژه تحت آن عرضه شده است نحوه مشارکت در پروژه از آنجا که گیتهاب این فایل را نمایش میدهد، میتوانید تصاویر یا لینکهایی در آن بگنجانید تا فهم آن آسانتر شود. مشارکت (CONTRIBUTING) فایل ویژه دیگری که گیتهاب آن را تشخیص میدهد، فایل CONTRIBUTING است. اگر فایل CONTRIBUTING با هر پسوندی داشته باشید، گیتهاب زمانی که کسی درخواست پول جدیدی باز میکند، Opening a Pull Request when a CONTRIBUTING file exists را نمایش میدهد. نمودار 122. Opening a Pull Request when a CONTRIBUTING file exists ایده این است که شما میتوانید قواعد خاصی که میخواهید یا نمیخواهید در یک Pull Request به پروژه شما ارسال شود را مشخص کنید. به این ترتیب، افراد احتمالاً قبل از باز کردن درخواست پول، دستورالعملها را مطالعه خواهند کرد. مدیریت پروژه (Project Administration) به طور کلی امکانات مدیریتی زیادی برای یک پروژه واحد وجود ندارد، اما چند مورد ممکن است برای شما جالب باشد. تغییر شاخه پیشفرض (Changing the Default Branch) اگر شاخهای غیر از “master” را به عنوان شاخه پیشفرض که میخواهید افراد روی آن درخواست پول باز کنند یا به صورت پیشفرض ببینند، استفاده میکنید، میتوانید این تنظیم را در صفحه تنظیمات مخزن خود زیر تب “Options” تغییر دهید. نمودار 123. Change the default branch for a project به سادگی شاخه پیشفرض را در منوی کشویی تغییر دهید و از آن پس تمام عملیات اصلی با آن شاخه به عنوان پیشفرض انجام خواهد شد، از جمله شاخهای که هنگام کلون کردن مخزن به صورت پیشفرض بررسی میشود. انتقال یک پروژه (Transferring a Project) اگر بخواهید پروژهای را به کاربر یا سازمان دیگری در گیتهاب منتقل کنید، گزینهای با عنوان “Transfer ownership” در پایین همان تب “Options” در صفحه تنظیمات مخزن شما وجود دارد که این امکان را فراهم میکند. نمودار 124. Transfer a project to another GitHub user or Organization این قابلیت زمانی مفید است که شما پروژه را رها میکنید و کسی میخواهد آن را به عهده بگیرد، یا پروژه شما بزرگتر شده و میخواهید آن را به یک سازمان منتقل کنید. این کار نه تنها مخزن را همراه با تمام دنبالکنندگان و ستارههای آن به مکان جدید منتقل میکند، بلکه یک ریدایرکت از URL قبلی شما به مکان جدید نیز ایجاد میکند. همچنین این ریدایرکت شامل کلونها و دریافتها از طریق گیت میشود، نه فقط درخواستهای وب. 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-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:24 |
https://git-scm.com/book/zh-tw/v2/Git-%e5%9f%ba%e7%a4%8e-%e7%b4%80%e9%8c%84%e8%ae%8a%e6%9b%b4%e5%88%b0%e7%89%88%e6%9c%ac%e5%ba%ab%e4%b8%ad | Git - 紀錄變更到版本庫中 About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 開始 1.1 關於版本控制 1.2 Git 的簡史 1.3 Git 基礎要點 1.4 命令列 1.5 Git 安裝教學 1.6 初次設定 Git 1.7 取得說明文件 1.8 摘要 2. Git 基礎 2.1 取得一個 Git 倉儲 2.2 紀錄變更到版本庫中 2.3 檢視提交的歷史記錄 2.4 復原 2.5 與遠端協同工作 2.6 標籤 2.7 Git Aliases 2.8 總結 3. 使用 Git 分支 3.1 簡述分支 3.2 分支和合併的基本用法 3.3 分支管理 3.4 分支工作流程 3.5 遠端分支 3.6 衍合 3.7 總結 4. 伺服器上的 Git 4.1 通訊協定 4.2 在伺服器上佈署 Git 4.3 產生你的 SSH 公鑰 4.4 設定伺服器 4.5 Git 常駐程式 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第3方 Git 託管方案 4.10 總結 5. 分散式的 Git 5.1 分散式工作流程 5.2 對專案進行貢獻 5.3 維護一個專案 5.4 Summary 6. GitHub 6.1 建立帳戶及設定 6.2 參與一個專案 6.3 維護專案 6.4 Managing an organization 6.5 Scripting GitHub 6.6 總結 7. Git 工具 7.1 Revision Selection 7.2 Interactive Staging 7.3 Stashing and Cleaning 7.4 Signing Your Work 7.5 Searching 7.6 Rewriting History 7.7 Reset Demystified 7.8 Advanced Merging 7.9 Rerere 7.10 Debugging with Git 7.11 Submodules 7.12 Bundling 7.13 Replace 7.14 Credential Storage 7.15 總結 8. Customizing Git 8.1 Git Configuration 8.2 Git Attributes 8.3 Git Hooks 8.4 An Example Git-Enforced Policy 8.5 Summary 9. Git and Other Systems 9.1 Git as a Client 9.2 Migrating to Git 9.3 Summary 10. Git Internals 10.1 Plumbing and Porcelain 10.2 Git Objects 10.3 Git References 10.4 Packfiles 10.5 The Refspec 10.6 Transfer Protocols 10.7 Maintenance and Data Recovery 10.8 Environment Variables 10.9 Summary A1. 附錄 A: Git in Other Environments A1.1 Graphical Interfaces A1.2 Git in Visual Studio A1.3 Git in Eclipse A1.4 Git in Bash A1.5 Git in Zsh A1.6 Git in Powershell A1.7 Summary A2. 附錄 B: Embedding Git in your Applications A2.1 Command-line Git A2.2 Libgit2 A2.3 JGit A3. 附錄 C: Git Commands A3.1 Setup and Config A3.2 Getting and Creating Projects A3.3 Basic Snapshotting A3.4 Branching and Merging A3.5 Sharing and Updating Projects A3.6 Inspection and Comparison A3.7 Debugging A3.8 Patching A3.9 Email A3.10 External Systems A3.11 Administration A3.12 Plumbing Commands 2nd Edition 2.2 Git 基礎 - 紀錄變更到版本庫中 紀錄變更到版本庫中 現在你的手上有了一個貨真價實的 Git 版本庫和這個專案中所有檔案的檢出（checkout）或工作複本（working copy）， 每當你修改檔案到一個你想記錄它的階段時，你就需要提交（commit）這些變更的快照到版本庫中。 請記住，你工作目錄下的每個檔案不外乎兩種狀態：已追蹤、未追蹤。 「已追蹤」檔案是指那些在上次快照中的檔案：它們的狀態可能是「未修改」、「已修改」、「已預存（staged）」； 「未追蹤」則是其它以外的檔案——在工作目錄中，卻不包含在上次的快照中，也不在預存區（staging area）中的任何檔案； 當你第一次克隆（clone）一個版本庫時，所有檔案都是「已追蹤」且「未修改」，因為 Git 剛剛檢出它們並且你尚未編輯過任何檔案。 隨著你編輯某些檔案，Git 會視它們為「已修改」，因為自從上次提交以來你已經更動過它們； 你預存（stage）這些已修改檔案，然後提交所有已預存的修改內容，接著重覆這個循環。 圖表 8. 檔案狀態的生命週期。 檢查你的檔案狀態 git status 命令是用來偵測哪些檔案處在什麼樣的狀態下的主要工具； 如果你在克隆之後直接執行該命令，應該會看到類似以下內容： $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean 這意味著你有一個乾淨的工作目錄——換句話說，已追蹤的檔案沒有被修改； Git 也沒有看到任何未追蹤檔案，否則它們會在這裡被列出來； 最後，這個命令告訴你目前在哪一個分支上，也告訴你它和伺服器上的同名分支是同步的。 到目前為止，該分支一直都是預設的「master」，在這裡你先不用擔心它， [ch03-git-branching] 會詳細地介紹「分支（branch）」和「參照（reference）」。 假設你在專案中新增一個檔案，例如：一個簡單的 README 檔案； 如果該檔案先前並不存在，執行 git status 命令後，你會看到未追蹤檔案： $ echo 'My Project' > README $ git status On branch master Your branch is up-to-date with 'origin/master'. Untracked files: (use "git add <file>..." to include in what will be committed) README nothing added to commit but untracked files present (use "git add" to track) 你可以看到新增檔案 README 尚未被追蹤，因為它被列在輸出訊息的「Untracked files」欄位下方； 基本上「未追蹤」表示 Git 發現這個檔案在上次的快照（提交）中並不存在；Git 並不會將此檔案納入你的提交快照，除非你明確地告訴 Git 要這麼做； 它會這樣做是為了避免你意外地將一些二進位暫存檔或其它你並不想要的檔案納入版本控制。 讓我們開始追蹤 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 reset HEAD <file>..." to unstage) new file: README 由於它放在「Changes to be committed」欄位下方，你可以得知它已經被預存， 如果你在此時提交，在執行 git add 的當下所加進來的檔案版本就會被記錄在歷史快照中； 你或許會想到之前執行 git init 後也有執行過 git add (files) ——那就是開始追蹤目錄內的檔案。 git add 命令接受「檔案」或「目錄」做為路徑名稱；如果是目錄，該命令會用遞迴的方式加入那個目錄下所有的檔案。 預存修改過的檔案 讓我們修改一個已追蹤檔案； 假設你修改了一個先前已追蹤的檔案 CONTRIBUTING.md ，接著再次執行 git status ，你會看到類似以下文字： $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md CONTRIBUTING.md 檔案出現在「Changes not staged for commit」欄位下方——代表著位於工作目錄的已追蹤檔案已經被修改，但尚未預存； 要預存該檔案，你可執行 git add 命令； git add 是一個多重用途的指令——用來「開始追蹤」檔案、「預存」檔案以及做一些其它的事，像是「標記合併衝突（merge-conflicted）檔案為已解決」。 比起「把這個檔案加進專案」，把它想成「把檔案內容加入下一個提交中」會比較容易理解。 現在，讓我們執行 git add 將 CONTRIBUTING.md 檔案預存起來，並再度執行 git status ： $ git add CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md 這兩個檔案目前都被預存，而且將會成為你下次提交的內容； 此時，假設在提交前你想起要對 CONTRIBUTING.md 再做一個小修改， 你再次開啟檔案並修改它，然後準備提交； 然而，當我們再次執行 git status ： $ vim CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md 見鬼了？ 現在 CONTRIBUTING.md 同時被列在已預存「及」未預存。 這怎麼可能？ 原來 Git 在你執行 git add 命令時，的確將當時的檔案內容預存起來； 如果你現在提交，最後一次執行 git add 命令時，那個當下的 CONTRIBUTING.md 的版本會被提交，而不是在提交時你在工作目錄所看到的檔案版本被提交； 如果你在 git add 後修改檔案，你必需再次執行 git add 預存最新版的檔案： $ git add CONTRIBUTING.md $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) new file: README modified: CONTRIBUTING.md 簡潔的狀態輸出 雖然 git status 輸出內容相當全面，但也相當囉嗦； Git 另外提供一個簡潔輸出的選項，因此你可以以一種較精簡的方式來檢視你的修改； 如果你執行 git status -s 或 git status --short ，你可以從該命令得到一個相當簡單的輸出內容： $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt 未追蹤的新檔案在開頭被標示為 ?? 、被加入預存區的新檔案被標為 A 、已修改檔案則是 M 等等。 標記有二個欄位——左邊欄位用來指示「預存區」狀態，右邊欄位則是「工作目錄」狀態。 所以在這個範例中，在工作目錄中的檔案 README 是已修改的，但尚未被預存；而 lib/simplegit.rb 檔案則是已修改且已預存的； Rakefile 則是曾經修改過也預存過，但之後又再次修改，所以總共有二次修改，一個有預存一個沒有。 忽略不需要的檔案 通常你會有一類檔案不想讓 Git 自動加入，也不希望它們被顯示為未追蹤， 這些通常是自動產生的檔案，例如：日誌檔案或者編譯系統產生的檔案； 在這情況下，你可以新建一個名為 .gitignore 的檔案，在該檔中列舉符合這些檔名的模式（pattern）。 以下是一個 .gitignore 範例檔內容： $ cat .gitignore *.[oa] *~ 第一列告訴 Git 忽略任何副檔名為「.o」或「.a」的檔案，它們可能是編譯系統建置程式碼時所產生的目的檔及連結檔； 第二列告訴 Git 忽略所有檔名以波浪號（ ~ ）結尾的檔案，這種檔案通常被用在很多文字編輯器中，例如：Emacs 把它用在暫存檔； 你可能也想忽略 log、tmp、pid 目錄、自動產生的文件等等； 在你要開始做事之前將 .gitignore 設定好通常是一個不錯的主意，這樣你就不會意外地將實際上並不想追蹤的檔案提交到你的 Git 版本庫。 編寫 .gitignore 檔案的模式規則如下： 空白列，或者以 # 開頭的列會被忽略。 可使用標準的 Glob 模式。 以斜線（ / ）開頭以避免路徑遞迴。（譯注：只忽略特定路徑；如果不以斜線開頭，則不管同名檔案或同名資料夾在哪一層都會被忽略。） 以斜線（ / ）結尾代表是目錄。 以驚嘆號（ ! ）開頭表示將模式規則反向。 Glob 模式就像是 Shell 所使用的簡化版正規運算式（regular expressions）； 一個星號（ * ）匹配零個或多個字元、 [abc] 匹配中括弧內的其中一個字元（此例為 a、b、c）、問號（ ? ）匹配單一個字元、中括孤內的字以連字號連接（如： [0-9] ）用來匹配任何在該範圍內的字元（此例為 0 到 9）； 你也可以使用二個星號用來匹配巢狀目錄； a/**/z 將會匹配到 a/z 、 a/b/z 、 a/b/c/z 等等。 以下是另一個 .gitignore 範例檔案： # 不要追蹤檔名為 .a 結尾的檔案 *.a # 但是要追蹤 lib.a，即使上面已指定忽略所有的 .a 檔案 !lib.a # 只忽略根目錄下的 TODO 檔案，不包含子目錄下的 TODO /TODO # 忽略 build/ 目錄下所有檔案 build/ # 忽略 doc/notes.txt，但不包含 doc/server/arch.txt doc/*.txt # 忽略所有在 doc/ 目錄底下的 .pdf 檔案 doc/**/*.pdf 提示 如果你的專案想要有個好開頭，GitHub 在 https://github.com/github/gitignore 中針對幾十種專案和程式語言維護了一個相當完整、好用的 .gitignore 範例檔案列表。 檢視已預存及未預存的檔案 如果 git status 命令提供的資訊對你來說太過簡略——你要想精確地知道你修改了什麼，而不只是那些檔案被修改——你可以使用 git diff 命令； 稍後我們會更詳盡講解 git diff 命令，然而大部分你在使用它的時候只是為了瞭解兩個問題：已修改但尚未預存的內容是哪些？ 已預存而準備被提交的內容又有哪些？ 儘管 git status 命令透過列出檔名的方式大略回答了這些問題，但 git diff 可顯示檔案裡的哪些列被加入或刪除——如同以往地以補綴（patch）格式呈現。 假設你再次編輯並預存 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 外部差異比對工具 接下來我們還會在書中的其它地方以各種不同的用法來使用 git diff 命令； 如果你傾向於使用圖形或外部差異比對檢視工具，有另一種方法可以查看這些差異內容； 執行 git difftool 取代 git diff ，你可以用軟體工具檢視任何這類型的差異，像是 emerge、vimdiff 或其它更多的工具（包括商業化的產品）； 執行 git difftool --tool-help 以查看在你系統上有什麼可用的。 提交你的修改 現在你的預存區已被建構成你想要的，你可以開始提交你的變更； 記住：任何未預暫存的檔案——新增的、已修改的，自從你編輯它們卻尚未用 git add 預存的——將不會納入本次的提交中； 它們仍以「已修改」的身份存在磁碟中。 在目前情況下，假設你上次執行 git status 時，你看到所有檔案都已經被預存，因此你準備提交你的變更。 最簡單的提交方式是輸入 git commit ： $ git commit 這麼做會啟動你選定的編輯器 （由你的 Shell 的 $EDITOR 環境變數所指定——通常是 vim 或 emacs；你也可以如同 [ch01-introduction] 所介紹的，使用 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 選項； 這麼做連修改的差異內容也會被放到編輯器中，如此你便可以精確地看到你正在提交的修改內容。） 當你關閉編輯器，Git 會利用這些提交訊息（註解和差異內容會被濾除）產生新的提交。 另一種方式則是在 commit 命令的 -m 選項後方直接輸入提交訊息，如下： $ git commit -m "Story 182: Fix benchmarks for speed" [master 463dc4f] Story 182: Fix benchmarks for speed 2 files changed, 2 insertions(+) create mode 100644 README 現在你已經建立了你的第一個提交！ 你可從輸出訊息看到此提交相關資訊：提交到哪個分支（ master ）、提交的 SHA-1 校驗碼（ 463dc4f ）、有多少檔案被更動，以及統計此提交有多少列被新增和被移除。 記住：那個提交記錄了你放在預存區的快照。 任何你尚未預存的已修改檔案仍然安好地在那裡，你可以做另一次提交來把它加入到你的歷史中； 每一次提交時，你都正在對專案記錄一個快照，可以在之後用來「復原」或「比對」。 略過預存區 雖然「預存區」的用法讓你能夠很有技巧地且精確地提交你想記錄的內容而意外地好用，但有時候它也比你實際需要的工作流程要繁瑣得多； 如果你想跳過預存區，Git 提供了一個簡易的捷徑， 在 git commit 命令加上 -a 選項，使 Git 在提交前自動預存所有已追蹤的檔案，讓你略過 git add 步驟： $ git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md no changes added to commit (use "git add" and/or "git commit -a") $ git commit -a -m 'added new benchmarks' [master 83e38c7] added new benchmarks 1 file changed, 5 insertions(+), 0 deletions(-) 請留意這種使用情況：在提交之前，你並不需要執行 git add 來預存 CONTRIBUTING.md 檔案； 那是因為 -a 選項會納入所有已變更的檔案； 很方便，但請小心，有時候它會納入你並不想要的變更。 移除檔案 要從 Git 中刪除一個檔案，你需要將它從已追蹤檔案中移除（更準確地說，是從預存區中移除），然後再提交； git rm 命令可完成此工作，它同時也會將該檔案從工作目錄中移除，如此它之後也不會身為未追蹤檔案而被你看到。 如果你僅僅是將檔案從工作目錄中移除，那麼它會被列在 git status 輸出內容的「Changed but not updated」（也就是「未預存」）欄位下面： $ 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 你可將「檔案」、「目錄」、「file-glob 模式」做為參數傳給 git rm 命令， 那意味著你可以做類似下面的事： $ git rm log/\*.log 注意：星號 * 前面有反斜線（ \ ）； 這是必須的，因為 Git 在你的 Shell 檔名擴展（filename expansion）之上另外有自己的檔名擴展； 此命令會移除在 log/ 所有副檔名為 .log 的檔案。 或者你也可以做像下面的事： $ git rm \*~ 此命令會移除所有以 ~ 結尾的檔案。 移動檔案 Git 不像其它 VCS 系統，它並不會明確地追蹤檔案的移動； 如果你在 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 命令並沒有差別； 實際上唯一不同的是 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://git-scm.com/book/zh/v2/GitHub-%e7%bb%b4%e6%8a%a4%e9%a1%b9%e7%9b%ae | 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 6.3 GitHub - 维护项目 维护项目 现在我们可以很方便地向一个项目贡献内容，来看一下另一个方面的内容：创建、维护和管理你自己的项目。 创建新的版本库 让我们创建一个版本库来分享我们的项目。 通过点击面板右侧的“New repository”按钮，或者顶部工具条你用户名旁边的 + 按钮来开始我们的旅程。 参见 这是 “New repository” 下拉列表. 。 Figure 110. 这是 “Your repositories” 区域. Figure 111. 这是 “New repository” 下拉列表. 这会带你到 “new repository” 表单: Figure 112. 这是 “new repository” 表单. 这里除了一个你必须要填的项目名，其他字段都是可选的。 现在只需要点击 “Create Repository” 按钮，Duang!!! – 你就在 GitHub 上拥有了一个以 <user>/<project_name> 命名的新仓库了。 因为目前暂无代码，GitHub 会显示有关创建新版本库或者关联到一个已有的 Git 版本库的一些说明。 我们不会在这里详细说明此项，如果你需要复习，去看 Git 基础 。 现在你的项目就托管在 GitHub 上了，你可以把 URL 给任何你想分享的人。 GitHub 上的项目可通过 HTTP 或 SSH 访问，HTTPS 为 https://github.com/<user>/<project_name> ， SSH 为 git@github.com:<user>/<project_name> 。 Git 可以通过以上两种 URL 进行抓取和推送，但是用户的访问权限又因连接时使用的证书不同而异。 Note 通常对于公开项目可以优先分享基于 HTTPS 的 URL，因为用户克隆项目不需要有一个 GitHub 帐号。 如果你分享 SSH URL，用户必须有一个帐号并且上传 SSH 密钥才能访问你的项目。 HTTPS URL 与你贴到浏览器里查看项目用的地址是一样的。 添加合作者 如果你想与他人合作，并想给他们提交的权限，你需要把他们添加为 “Collaborators”。 如果 Ben，Jeff，Louise 都在 GitHub 上注册了，你想给他们推送的权限，你可以将他们添加到你的项目。 这样做会给他们 “推送” 权限，就是说他们对项目和 Git 版本库都有读写的权限。 点击边栏底部的 “Settings” 链接。 Figure 113. 版本库设置链接. 然后从左侧菜单中选择 “Collaborators” 。 然后，在输入框中填写用户名，点击 “Add collaborator.” 如果你想授权给多个人，你可以多次重复这个步骤。 如果你想收回权限，点击他们同一行右侧的 “X” Figure 114. 版本库合作者. 管理合并请求 现在你有一个包含一些代码的项目，可能还有几个有推送权限的合作者，下面来看当你收到合并请求时该做什么。 合并请求可以来自仓库副本的一个分支，或者同一仓库的另一个分支。 唯一的区别是 fork 过来的通常是和你不能互相推送的人，而内部的推送通常都可以互相访问。 作为例子，假设你是 “tonychacon” ，你创建了一个名为 “fade” 的 Arduino 项目. 邮件通知 有人来修改了你的代码，给你发了一个合并请求。 你会收一封关于合并请求的提醒邮件，它看起来像 新的合并请求的邮件通知. 。 Figure 115. 新的合并请求的邮件通知. 关于这个邮件有几个要注意的地方。 它会给你一个小的变动统计结果 — 一个包含合并请求中改变的文件和改变了多少的列表。 它还给你一个 GitHub 上进行合并请求操作的链接。 还有几个可以在命令行使用的 URL。 如果你注意到 git pull <url> patch-1 这一行，这是一种合并远程分支的简单方式，无需必须添加一个远程分支。 我们很快会在 检出远程分支 讲到它。 如果你愿意，你可以创建并切换到一个主题分支，然后运行这个命令把合并请求合并进来。 还有一些有趣的 URL，像 .diff 和 .patch ，就像你猜的那样，它们提供 diff 和 patch 的标准版本。 你可以技术性地用下面的方法合并“合并请求”： $ curl https://github.com/tonychacon/fade/pull/1.patch | git am 在合并请求上进行合作 就像我们在 GitHub 流程 中说过的，现在你可以跟开启合并请求的人进行会话。 你既可以对某些代码发表评论，也可以对整个提交或整个合并请求发表评论， 在任何地方都可以用 GitHub 风格的 Markdown。 每次有人在合并请求上发表了评论，你都会收到邮件，通知你哪里发生了改变。邮件里面包含一个链接，指向改变的位置，你可以直接在邮件中回复，相当于在合并请求上发表评论。 Figure 116. 回复邮件会包含在帖子（thread）中。 一旦代码符合了你的要求，你想把它合并进来，你可以把代码拉取下来在本地进行合并，也可以用我们之前提到过的 git pull <url> <branch> 语法，或者把 fork 添加为一个 remote，然后进行抓取和合并。 对于很琐碎的合并，你也可以用 GitHub 网站上的 “Merge” 按钮。 它会做一个 “non-fast-forward” 合并，即使可以快进（fast-forward）合并也会产生一个合并提交记录。 就是说无论如何，只要你点击 merge 按钮，就会产生一个合并提交记录。 你可以在 合并按钮和手工合并一个合并请求的指令. 看到，如果你点击提示链接，GitHub 会给你所有的这些信息。 Figure 117. 合并按钮和手工合并一个合并请求的指令. 如果你决定不合并它，你可以把合并请求关掉，开启合并请求的人会收到通知。 合并请求引用 如果你正在处理 许多 合并请求，不想添加一堆 remote 或者每次都要做一次拉取，这里有一个可以在 GitHub 上用的小技巧。 这是有点高级的技巧，但它相当有用，我们会在 引用规范 有更多的细节说明。 实际上 GitHub 在服务器上把合并请求分支视为一种 “假分支”。 默认情况下你克隆时不会得到它们，但它们还是隐式地存在，你可以很容易地访问到它们。 为了展示这个，我们要用到一个叫做 ls-remote 的低级命令（通常被叫做“plumbing”， 我们会在 底层命令与上层命令 读到更多相关内容）。 这个命令在日常 Git 操作中基本不会用到，但在显示服务器上有哪些引用（reference）时很管用。 如果在我们之前用过的 “blink” 版本库上使用这个命令，我们会得到一个版本库里所有的分支，标签和其它引用（reference）的列表。 $ git ls-remote https://github.com/schacon/blink 10d539600d86723087810ec636870a504f4fee4d HEAD 10d539600d86723087810ec636870a504f4fee4d refs/heads/master 6a83107c62950be9453aac297bb0193fd743cd6e refs/pull/1/head afe83c2d1a70674c9505cc1d8b7d380d5e076ed3 refs/pull/1/merge 3c8d735ee16296c242be7a9742ebfbc2665adec1 refs/pull/2/head 15c9f4f80973a2758462ab2066b6ad9fe8dcf03d refs/pull/2/merge a5a7751a33b7e86c5e9bb07b26001bb17d775d1a refs/pull/4/head 31a45fc257e8433c8d8804e3e848cf61c9d3166c refs/pull/4/merge 当然，如果你在你自己的版本库或其它你想检查的远程版本库中使用 git ls-remote origin ，它会显示相似的内容。 如果版本库在 GitHub 上并且有打开的合并请求，你会得到一些以 refs/pull/ 开头的引用。 它们实际上是分支，但因为它们不在 refs/heads/ 中，所以正常情况下你克隆时不会从服务器上得到它们 ——抓取过程正常情况下会忽略它们。 每个合并请求有两个引用——其中以 /head 结尾的引用指向的提交记录与合并请求分支中的最后一个提交记录是同一个。 所以如果有人在我们的版本库中开启了一个合并请求，他们的分支叫做 bug-fix ， 指向 a5a775 这个提交记录，那么在 我们的 版本库中我们没有 bug-fix 分支（因为那是在他们的 fork 中）， 但我们 可以 有一个 pull/<pr#>/head 指向 a5a775 。 这意味着我们可以很容易地拉取每一个合并请求分支而不用添加一堆远程仓库。 现在，你可以像直接抓取引用一样抓取那些分支或提交。 $ git fetch origin refs/pull/958/head From https://github.com/libgit2/libgit2 * branch refs/pull/958/head -> FETCH_HEAD 这告诉 Git： “连接到 origin 这个 remote，下载名字为 refs/pull/958/head 的引用。” Git 高高兴兴去执行，下载构建那个引用需要的所有内容，然后把指针指向 .git/FETCH_HEAD 下面你想要的提交记录。 然后你可以用 git merge FETCH_HEAD 把它合并到你想进行测试的分支，但那个合并的提交信息看起来有点怪。 然而，如果你需要审查 一大批 合并请求，这样操作会很麻烦。 还有一种方法可以抓取 所有的 合并请求，并且在你连接到远程仓库的时候保持更新。 用你最喜欢的编辑器打开 .git/config ，查找 origin 远程仓库。 看起来差不多像下面这样： [remote "origin"] url = https://github.com/libgit2/libgit2 fetch = +refs/heads/*:refs/remotes/origin/* 以 fetch = 开头的行是一个 “refspec.” 它是一种把 remote 的名称映射到你本地 .git 目录的方法。 这一条（就是上面的这一条）告诉 Git，“remote 上 refs/heads 下面的内容在我本地版本库中都放在 refs/remotes/origin 。” 你可以把这一段修改一下，添加另一个 refspec： [remote "origin"] url = https://github.com/libgit2/libgit2.git fetch = +refs/heads/*:refs/remotes/origin/* fetch = +refs/pull/*/head:refs/remotes/origin/pr/* 最后一行告诉 Git： “所有看起来像 refs/pull/123/head 的引用应该在本地版本库像 refs/remotes/origin/pr/123 一样存储” 现在，如果你保存那个文件，执行 git fetch ： $ git fetch # … * [new ref] refs/pull/1/head -> origin/pr/1 * [new ref] refs/pull/2/head -> origin/pr/2 * [new ref] refs/pull/4/head -> origin/pr/4 # … 现在所有的合并请求在本地像分支一样展现，它们是只读的，当你执行抓取时它们也会更新。 这让在本地测试合并请求中的代码变得超级简单： $ git 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' 你的鹰眼系统会发现在 refspec 的 remote 部分的结尾有个 head 。 在 GitHub 那边也有一个 refs/pull/#/merge 引用，它代表的是如果你在网站上按了 “merge” 按钮对应的提交记录。 这甚至让你可以在按按钮之前就测试这个合并。 合并请求之上的合并请求 你不仅可以在主分支或者说 master 分支上开启合并请求，实际上你可以在网络上的任何一个分支上开启合并请求。 其实，你甚至可以在另一个合并请求上开启一个合并请求。 如果你看到一个合并请求在向正确的方向发展，然后你想在这个合并请求上做一些修改或者你不太确定这是个好主意，或者你没有目标分支的推送权限，你可以直接在合并请求上开启一个合并请求。 当你开启一个合并请求时，在页面的顶端有一个框框显示你要合并到哪个分支和你从哪个分支合并过来的。 如果你点击那个框框右边的 “Edit” 按钮，你不仅可以改变分支，还可以选择哪个 fork。 Figure 118. 手工修改合并请求的目标. 这里你可以很简单地指明合并你的分支到哪一个合并请求或 fork。 提醒和通知 GitHub 内置了一个很好的通知系统，当你需要与别人或别的团队交流时用起来很方便。 在任何评论中你可以先输入一个 @ ，系统会自动补全项目中合作者或贡献者的名字和用户名。 Figure 119. 输入 @ 来提醒某人. 你也可以提醒不在列表中的用户，但是通常自动补全用起更快。 当你发布了一个带用户提醒的评论，那个用户会收到通知。 这意味着把人们拉进会话中要比让他们投票有效率得多。 对于 GitHub 上的合并请求，人们经常把他们团队或公司中的其它人拉来审查问题或合并请求。 如果有人收到了合并请求或问题的提醒，他们会“订阅”它，后面有新的活动发生他们都会持续收到提醒。 如果你是合并请求或者问题的发起方你也会被订阅上，比如你在关注一个版本库或者你评论了什么东西。 如果你不想再收到提醒，在页面上有个 “Unsubscribe” 按钮，点一下就不会再收到更新了。 Figure 120. 取消订阅一个问题或合并请求. 通知页面 当我们在这提到特指 GitHub 的 “notifications” ，指的是当 GitHub 上有事件发生时，它通知你的方式，这里有几种不同的方式来配置它们。 如果你打开配置页面的 “Notification center” 标签，你可以看到一些选项。 Figure 121. 通知中心选项. 有两个选项，通过“邮件（Email）”和通过“网页（Web）”，你可以选用一个或者都不选或者都选。 网页通知 网页通知只在 GitHub 上存在，你也只能在 GitHub 上查看。 如果你打开了这个选项并且有一个你的通知，你会在你屏幕上方的通知图标上看到一个小蓝点。参见 通知中心. 。 Figure 122. 通知中心. 如果你点击那个玩意儿，你会看到你被通知到的所有条目，按照项目分好了组。 你可以点击左边栏的项目名字来过滤项目相关的通知。 你可以点击通知旁边的对号图标把通知标为已读，或者点击组上面的图标把项目中 所有的 通知标为已读。 在每个对号图标旁边都有一个静音按钮，你可以点一下，以后就不会收到它相关的通知。 所有这些工具对于处理大量通知非常有用。 很多 GitHub 资深用户都关闭邮件通知，在这个页面上处理他们所有的通知。 邮件通知 邮件通知是你处理 GitHub 通知的另一种方式。 如果你打开这个选项，每当有通知时，你会收到一封邮件。 我们在 通过电子邮件发送的评论提醒 和 新的合并请求的邮件通知. 看到了一些例子。 邮件也会被合适地按话题组织在一起，如果你使用一个具有会话功能的邮件客户端那会很方便。 GitHub 在发送给你的邮件头中附带了很多元数据，这对于设置过滤器和邮件规则非常有帮助。 举个例子，我们来看一看在 新的合并请求的邮件通知. 中发给 Tony 的一封真实邮件的头部，我们会看到下面这些： To: tonychacon/fade <fade@noreply.github.com> Message-ID: <tonychacon/fade/pull/1@github.com> Subject: [fade] Wait longer to see the dimming effect better (#1) X-GitHub-Recipient: tonychacon List-ID: tonychacon/fade <fade.tonychacon.github.com> List-Archive: https://github.com/tonychacon/fade List-Post: <mailto:reply+i-4XXX@reply.github.com> List-Unsubscribe: <mailto:unsub+i-XXX@reply.github.com>，... X-GitHub-Recipient-Address: tchacon@example.com 这里有一些有趣的东西。如果你想高亮或者转发这个项目甚至这个合并请求相关的邮件， Message-ID 中的信息会以`<user>/<project>/<type>/<id>` 的格式展现所有的数据。 例如，如果这是一个问题（issue），那么 <type> 字段就会是 “issues” 而不是 “pull” 。 List-Post 和 List-Unsubscribe 字段表示如果你的邮件客户端能够处理这些，那么你可以很容易地在列表中发贴或取消对这个相关帖子的订阅。 那会很有效率，就像在页面中点击静音按钮或在问题/合并请求页面点击 “Unsubscribe” 一样。 值得注意的是，如果你同时打开了邮件和网页通知，那么当你在邮件客户端允许加载图片的情况下阅读邮件通知时，对应的网页通知也将会同时被标记为已读。 特殊文件 如果你的版本库中有一些特殊文件，GitHub 会提醒你。 README 第一个就是 README 文件，可以是几乎任何 GitHub 可以识别的格式。 例如，它可以是 README ， README.md ， README.asciidoc 。 如果 GitHub 在你的版本库中找到 README 文件，会把它在项目的首页渲染出来。 很多团队在这个文件里放版本库或项目新人需要了解的所有相关的信息。 它一般包含这些内容： 该项目的作用 如何配置与安装 有关如何使用和运行的例子 项目的许可证 如何向项目贡献力量 因为 GitHub 会渲染这个文件，你可以在文件里植入图片或链接让它更容易理解。 贡献 CONTRIBUTING 另一个 GitHub 可以识别的特殊文件是 CONTRIBUTING 。 如果你有一个任意扩展名的 CONTRIBUTING 文件，当有人开启一个合并请求时 GitHub 会显示 开启合并请求时有 CONTRIBUTING 文件存在. 。 Figure 123. 开启合并请求时有 CONTRIBUTING 文件存在. 这个的作用就是你可以在这里指出对于你的项目开启的合并请求你想要的／不想要的各种事情。 这样别人在开启合并请求之前可以读到这些指导方针。 项目管理 对于一个单个项目其实没有很多管理事务要做，但也有几点有趣的。 改变默认分支 如果你想用 “master” 之外的分支作为你的默认分支，其他人将默认会在这个分支上开启合并请求或进行浏览，你可以在你版本库的设置页面的 "options" 标签下修改。 Figure 124. 改变项目的默认分支. 简单地改变默认分支下拉列表中的选项，它就会作为所有主要操作的默认分支，他人进行克隆时该分支也将被默认检出。 移交项目 如果你想把一个项目移交给 GitHub 中的另一个人或另一个组织，还是设置页面的这个 “options” 标签下有一个 “Transfer ownership” 选项可以用来干这个。 Figure 125. 把项目移交给另一个 GitHub 用户或组织。 当你正准备放弃一个项目且正好有别人想要接手时，或者你的项目壮大了想把它移到一个组织里时，这就管用了。 这么做不仅会把版本库连带它所有的关注者和星标数都移到另一个地方，它还会将你的 URL 重定向到新的位置。 它也重定向了来自 Git 的克隆和抓取，而不仅仅是网页端请求。 prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:24 |
https://play.google.com/store/apps/details?id=com.bitazza.freedom.wallet&hl=es_VE | 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/fr/v2/Les-bases-de-Git-Enregistrer-des-modifications-dans-le-d%c3%a9p%c3%b4t | Git - Enregistrer des modifications dans le dépôt 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.2 Les bases de Git - Enregistrer des modifications dans le dépôt Enregistrer des modifications dans le dépôt Vous avez à présent un dépôt Git valide et une extraction ou copie de travail du projet. Vous devez faire quelques modifications et valider des instantanés de ces modifications dans votre dépôt chaque fois que votre projet atteint un état que vous souhaitez enregistrer. Souvenez-vous que chaque fichier de votre copie de travail peut avoir deux états : sous suivi de version ou non suivi. Les fichiers suivis sont les fichiers qui appartenaient déjà au dernier instantané ; ils peuvent être inchangés, modifiés ou indexés. En résumé, les fichiers suivis sont ceux que Git connaît. Tous les autres fichiers sont non suivis — tout fichier de votre copie de travail qui n’appartenait pas à votre dernier instantané et n’a pas été indexé. Quand vous clonez un dépôt pour la première fois, tous les fichiers seront sous suivi de version et inchangés car Git vient tout juste de les extraire et vous ne les avez pas encore édités. Au fur et à mesure que vous éditez des fichiers, Git les considère comme modifiés, car vous les avez modifiés depuis le dernier instantané. Vous indexez ces fichiers modifiés et vous enregistrez toutes les modifications indexées, puis ce cycle se répète. Figure 8. Le cycle de vie des états des fichiers. Vérifier l’état des fichiers L’outil principal pour déterminer quels fichiers sont dans quel état est la commande git status . Si vous lancez cette commande juste après un clonage, vous devriez voir ce qui suit : $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. rien à valider, la copie de travail est propre Ce message signifie que votre copie de travail est propre, en d’autres termes, aucun fichier suivi n’a été modifié. Git ne voit pas non plus de fichiers non-suivis, sinon ils seraient listés ici. Enfin, la commande vous indique sur quelle branche vous êtes. Pour l’instant, c’est toujours ``master'', qui correspond à la valeur par défaut ; nous ne nous en soucierons pas maintenant. Dans Les branches avec Git , nous parlerons plus en détail des branches et des références. Supposons que vous souhaitez ajouter un nouveau fichier au projet, un simple fichier LISEZMOI. Si le fichier n’existait pas auparavant, et si vous lancez git status , vous voyez votre fichier non suivi comme suit : $ echo 'Mon Projet' > LISEZMOI $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Fichiers non suivis: (utilisez "git add <fichier>..." pour inclure dans ce qui sera validé) LISEZMOI aucune modification ajoutée à la validation mais des fichiers non suivis sont présents (utilisez "git add" pour les suivre) Vous pouvez constater que votre nouveau fichier LISEZMOI n’est pas en suivi de version, car il apparaît dans la section « Fichiers non suivis » de l’état de la copie de travail. « non suivi » signifie simplement que Git détecte un fichier qui n’était pas présent dans le dernier instantané ; Git ne le placera sous suivi de version que quand vous lui indiquerez de le faire. Ce comportement permet de ne pas placer accidentellement sous suivi de version des fichiers binaires générés ou d’autres fichiers que vous ne voulez pas inclure. Mais vous voulez inclure le fichier LISEZMOI dans l’instantané, alors commençons à suivre ce fichier. Placer de nouveaux fichiers sous suivi de version Pour commencer à suivre un nouveau fichier, vous utilisez la commande git add . Pour commencer à suivre le fichier LISEZMOI , vous pouvez entrer ceci : $ git add LISEZMOI Si vous lancez à nouveau la commande git status , vous pouvez constater que votre fichier LISEZMOI est maintenant suivi et indexé : $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui seront validées : (utilisez "git restore --staged <fichier>..." pour désindexer) nouveau fichier : LISEZMOI Vous pouvez affirmer qu’il est indexé car il apparaît dans la section « Modifications qui seront validées ». Si vous validez à ce moment, la version du fichier à l’instant où vous lancez git add est celle qui sera dans l’historique des instantanés. Vous pouvez vous souvenir que lorsque vous avez précédemment lancé git init , vous avez ensuite lancé git add (fichiers) — c’était bien sûr pour commencer à placer sous suivi de version les fichiers de votre répertoire de travail. La commande git add accepte en paramètre un chemin qui correspond à un fichier ou un répertoire ; dans le cas d’un répertoire, la commande ajoute récursivement tous les fichiers de ce répertoire. Indexer des fichiers modifiés Maintenant, modifions un fichier qui est déjà sous suivi de version. Si vous modifiez le fichier sous suivi de version appelé CONTRIBUTING.md et que vous lancez à nouveau votre commande git status , vous verrez ceci : $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui seront validées : (utilisez "git reset HEAD <fichier>..." pour désindexer) nouveau fichier : LISEZMOI Modifications qui ne seront pas validées : (utilisez "git add <fichier>..." pour mettre à jour ce qui sera validé) (utilisez "git checkout -- <fichier>..." pour annuler les modifications dans la copie de travail) modifié : CONTRIBUTING.md Le fichier CONTRIBUTING.md apparaît sous la section nommée « Modifications qui ne seront pas validées » ce qui signifie que le fichier sous suivi de version a été modifié dans la copie de travail mais n’est pas encore indexé. Pour l’indexer, il faut lancer la commande git add . git add est une commande multi-usage — elle peut être utilisée pour placer un fichier sous suivi de version, pour indexer un fichier ou pour d’autres actions telles que marquer comme résolus des conflits de fusion de fichiers. Sa signification s’approche plus de « ajouter ce contenu pour la prochaine validation » que de « ajouter ce contenu au projet ». Lançons maintenant git add pour indexer le fichier CONTRIBUTING.md , et relançons la commande git status : $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui seront validées : (utilisez "git reset HEAD <fichier>..." pour désindexer) nouveau fichier : LISEZMOI modifié : CONTRIBUTING.md À présent, les deux fichiers sont indexés et feront partie de la prochaine validation. Mais supposons que vous souhaitiez apporter encore une petite modification au fichier CONTRIBUTING.md avant de réellement valider la nouvelle version. Vous l’ouvrez à nouveau, réalisez la petite modification et vous voilà prêt à valider. Néanmoins, vous lancez git status une dernière fois : $ vim CONTRIBUTING.md $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui seront validées : (utilisez "git reset HEAD <fichier>..." pour désindexer) nouveau fichier : LISEZMOI modifié : CONTRIBUTING.md Modifications qui ne seront pas validées : (utilisez "git add <fichier>..." pour mettre à jour ce qui sera validé) (utilisez "git checkout -- <fichier>..." pour annuler les modifications dans la copie de travail) modifié : CONTRIBUTING.md Que s’est-il donc passé ? À présent, CONTRIBUTING.md apparaît à la fois comme indexé et non indexé. En fait, Git indexe un fichier dans son état au moment où la commande git add est lancée. Si on valide les modifications maintenant, la version de CONTRIBUTING.md qui fera partie de l’instantané est celle correspondant au moment où la commande git add CONTRIBUTING.md a été lancée, et non la version actuellement présente dans la copie de travail au moment où la commande git commit est lancée. Si le fichier est modifié après un git add , il faut relancer git add pour prendre en compte l’état actuel de la copie de travail : $ git add CONTRIBUTING.md $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui seront validées : (utilisez "git reset HEAD <fichier>..." pour désindexer) nouveau fichier : LISEZMOI modifié : CONTRIBUTING.md Statut court Bien que git status soit informatif, il est aussi plutôt verbeux. Git a aussi une option de status court qui permet de voir les modifications de façon plus compacte. Si vous lancez git status -s ou git status --short , vous obtenez une information bien plus simple. $ git status -s M README MM Rakefile A lib/git.rb M lib/simplegit.rb ?? LICENSE.txt Les nouveaux fichiers qui ne sont pas suivis sont précédés de ?? , les fichiers nouveaux et indexés sont précédés de A , les fichiers modifiés de M et ainsi de suite. Il y a deux colonnes d’état - celle de gauche indique l’état de l’index et celle de droite l’état du dossier de travail. Donc l’exemple ci-dessus indique que le fichier README est modifié dans le répertoire de travail mais n’est pas encore indexé, tandis que le fichier lib/simplegit.rb est modifié et indexé. Le fichier Rakefile a été modifié, indexé puis modifié à nouveau, de sorte qu’il a des modifications à la fois indexées et non-indexées. Ignorer des fichiers Il apparaît souvent qu’un type de fichiers présent dans la copie de travail ne doit pas être ajouté automatiquement ou même ne doit pas apparaître comme fichier potentiel pour le suivi de version. Ce sont par exemple des fichiers générés automatiquement tels que les fichiers de journaux ou de sauvegardes produits par l’outil que vous utilisez. Dans un tel cas, on peut énumérer les patrons de noms de fichiers à ignorer dans un fichier .gitignore . Voici ci-dessous un exemple de fichier .gitignore : $ cat .gitignore *.[oa] *~ La première ligne ordonne à Git d’ignorer tout fichier se terminant en .o ou .a — des fichiers objet ou archive qui sont généralement produits par la compilation d’un programme. La seconde ligne indique à Git d’ignorer tous les fichiers se terminant par un tilde ( ~ ), ce qui est le cas des noms des fichiers temporaires pour de nombreux éditeurs de texte tels qu’Emacs. On peut aussi inclure un répertoire log , tmp ou pid , ou le répertoire de documentation générée automatiquement, ou tout autre fichier. Renseigner un fichier .gitignore avant de commencer à travailler est généralement une bonne idée qui évitera de valider par inadvertance des fichiers qui ne doivent pas apparaître dans le dépôt Git. Les règles de construction des patrons à placer dans le fichier .gitignore sont les suivantes : les lignes vides ou commençant par # sont ignorées ; les patrons standards de fichiers sont utilisables et seront appliqués récursivement dans tout l’arbre de travail ; si le patron commence par une barre oblique (`/), le patron n’est pas récursif ; si le patron se termine par une barre oblique ( / ), il indique un répertoire ; un patron commençant par un point d’exclamation ( ! ) indique des fichiers à inclure malgré les autres règles. Les patrons standards de fichiers sont des expressions régulières simplifiées utilisées par les shells. Un astérisque ( * ) correspond à un ou plusieurs caractères ; [abc] correspond à un des trois caractères listés dans les crochets, donc a ou b ou c ; un point d’interrogation ( ? ) correspond à un unique caractère ; des crochets entourant des caractères séparés par un tiret ( [0-9] ) correspond à un caractère dans l’intervalle des deux caractères indiqués, donc ici de 0 à 9. Vous pouvez aussi utiliser deux astérisques pour indiquer une série de répertoires inclus ; a/**/z correspond donc à a/z , a/b/z , a/b/c/z et ainsi de suite. Voici un autre exemple de fichier .gitignore : # pas de fichier .a *.a # mais suivre lib.a malgré la règle précédente !lib.a # ignorer uniquement le fichier TODO à la racine du projet /TODO # ignorer tous les fichiers dans le répertoire build build/ # ignorer doc/notes.txt, mais pas doc/server/arch.txt doc/*.txt # ignorer tous les fichiers .txt sous le répertoire doc/ doc/**/*.txt Astuce GitHub maintient une liste assez complète d’exemples de fichiers .gitignore correspondant à de nombreux types de projets et langages. Voir https://github.com/github/gitignore pour obtenir un point de départ pour votre projet. Note Dans un cas simple, un dépôt peut n’avoir qu’un unique fichier .gitignore à la racine de l’arbre de travail, qui s’applique récursivement dans le dépôt. Cependant, il est aussi possible d’avoir des fichiers .gitignore dans les sous-répertoires. Les règles dans ces fichiers .gitignore locaux ne s’appliquent qu’à partir du répertoire où ils se trouvent. Le dépôt des sources du noyau Linux contient 206 fichier .gitignore . Les détails de l’utilisation de multiples fichiers .gitignore dépassent l’objet de ce livre ; référez-vous à man gitignore pour plus d’information. Inspecter les modifications indexées et non indexées Si le résultat de la commande git status est encore trop vague — lorsqu’on désire savoir non seulement quels fichiers ont changé mais aussi ce qui a changé dans ces fichiers — on peut utiliser la commande git diff . Cette commande sera traitée en détail plus loin ; mais elle sera vraisemblablement utilisée le plus souvent pour répondre aux questions suivantes : qu’est-ce qui a été modifié mais pas encore indexé ? Quelle modification a été indexée et est prête pour la validation ? Là où git status répond de manière générale à ces questions, git diff montre les lignes exactes qui ont été ajoutées, modifiées ou effacées — le patch en somme. Supposons que vous éditez et indexez à nouveau le fichier LISEZMOI et que vous éditez CONTRIBUTING.md sans l’indexer. Si vous lancer la commande git status , vous allez voir une fois encore quelque chose comme : $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui seront validées : (utilisez "git reset HEAD <fichier>..." pour désindexer) nouveau fichier : LISEZMOI Modifications qui ne seront pas validées : (utilisez "git add <fichier>..." pour mettre à jour ce qui sera validé) (utilisez "git checkout -- <fichier>..." pour annuler les modifications dans la copie de travail) modifié : CONTRIBUTING.md Pour visualiser ce qui a été modifié mais pas encore indexé, tapez git diff sans autre 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 you patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's Cette commande compare le contenu du répertoire de travail avec la zone d’index. Le résultat vous indique les modifications réalisées mais non indexées. Si vous souhaitez visualiser les modifications indexées qui feront partie de la prochaine validation, vous pouvez utiliser git diff --cached (avec les versions 1.6.1 et supérieures de Git, vous pouvez aussi utiliser git diff --staged , qui est plus mnémotechnique). Cette commande compare les fichiers indexés et le dernier instantané : $ git diff --staged diff --git a/LISEZMOI b/LISEZMOI new file mode 100644 index 0000000..1e17b0c --- /dev/null +++ b/LISEZMOI @@ -0,0 +1 @@ +Mon Projet Il est important de noter que git diff ne montre pas les modifications réalisées depuis la dernière validation — seulement les modifications qui sont non indexées. Cela peut introduire une confusion car si tous les fichiers modifiés ont été indexés, git diff n’indiquera aucun changement. Par exemple, si vous indexez le fichier CONTRIBUTING.md et l’éditez ensuite, vous pouvez utiliser git diff pour visualiser les modifications indexées et non indexées de ce fichier. Si l’état est le suivant : $ git add CONTRIBUTING.md $ echo 'ligne de test' >> CONTRIBUTING.md $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui seront validées : (utilisez "git reset HEAD <fichier>..." pour désindexer) nouveau fichier : CONTRIBUTING.md Modifications qui ne seront pas validées : (utilisez "git add <fichier>..." pour mettre à jour ce qui sera validé) (utilisez "git checkout -- <fichier>..." pour annuler les modifications dans la copie de travail) modifié : CONTRIBUTING.md À présent, vous pouvez utiliser git diff pour visualiser les modifications non indexées : $ 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). +ligne de test et git diff --cached pour visualiser ce qui a été indexé jusqu’à maintenant : $ git diff --cached diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8ebb991..643e24f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,8 @@ branch directly, things can get messy. Please include a nice description of your changes when you submit your PR; if we have to read the whole diff to figure out why you're contributing in the first place, you're less likely to get feedback and have your change -merged in. +merged in. Also, split your changes into comprehensive chunks if you patch is +longer than a dozen lines. If you are starting to work on a particular area, feel free to submit a PR that highlights your work in progress (and note in the PR title that it's Note Git Diff dans un outil externe Nous allons continuer à utiliser la commande git diff de différentes manières par la suite. Il existe une autre manière de visualiser les différences si vous préférez un outil graphique ou externe. Si vous lancez git difftool au lieu de git diff , vous pourrez visualiser les différences grâce à une application telle que Araxis, emerge, vimdiff ou autre. Lancez git difftool --tool-help pour connaître les applications disponibles sur votre système. Valider vos modifications Maintenant que votre zone d’index est dans l’état désiré, vous pouvez valider vos modifications. Souvenez-vous que tout ce qui est encore non indexé — tous les fichiers qui ont été créés ou modifiés mais n’ont pas subi de git add depuis que vous les avez modifiés — ne feront pas partie de la prochaine validation. Ils resteront en tant que fichiers modifiés sur votre disque. Dans notre cas, la dernière fois que vous avez lancé git status , vous avez vérifié que tout était indexé, et vous êtes donc prêt à valider vos modifications. La manière la plus simple de valider est de taper git commit : $ git commit Cette action lance votre éditeur choisi. Note Ceci est paramétré par la variable d’environnement EDITOR de votre shell — habituellement vim ou Emacs, mais vous pouvez le paramétrer spécifiquement pour Git en utilisant la commande git config --global core.editor comme nous l’avons vu au Démarrage rapide ). L’éditeur affiche le texte suivant (par exemple, ici Vim) : # Veuillez saisir le message de validation pour vos modifications. Les lignes # commençant par '#' seront ignorées, et un message vide abandonne la validation. # Sur la branche master # Votre branche est à jour avec 'origin/master'. # # Modifications qui seront validées : # nouveau fichier : LISEZMOI # modifié : CONTRIBUTING.md # Vous constatez que le message de validation par défaut contient une ligne vide suivie en commentaire par le résultat de la commande git status . Vous pouvez effacer ces lignes de commentaire et saisir votre propre message de validation, ou vous pouvez les laisser en place pour vous aider à vous rappeler ce que vous êtes en train de valider. Note Pour un rappel plus explicite de ce que vous avez modifié, vous pouvez aussi passer l’option -v à la commande git commit . Cette option place le résultat du diff en commentaire dans l’éditeur pour vous permettre de visualiser exactement ce que vous avez modifié. Quand vous quittez l’éditeur (après avoir sauvegardé le message), Git crée votre commit avec ce message de validation (après avoir retiré les commentaires et le diff). Autrement, vous pouvez spécifier votre message de validation en ligne avec la commande git commit en le saisissant après l’option -m , comme ceci : $ 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 LISEZMOI À présent, vous avez créé votre premier commit ! Vous pouvez constater que le commit vous fournit quelques informations sur lui-même : sur quelle branche vous avez validé ( master ), quelle est sa somme de contrôle SHA-1 ( 463dc4f ), combien de fichiers ont été modifiés, et quelques statistiques sur les lignes ajoutées et effacées dans ce commit . Souvenez-vous que la validation enregistre l’instantané que vous avez préparé dans la zone d’index. Tout ce que vous n’avez pas indexé est toujours en état modifié ; vous pouvez réaliser une nouvelle validation pour l’ajouter à l’historique. À chaque validation, vous enregistrez un instantané du projet en forme de jalon auquel vous pourrez revenir ou avec lequel comparer votre travail ultérieur. Passer l’étape de mise en index Bien qu’il soit incroyablement utile de pouvoir organiser les commits exactement comme on l’entend, la gestion de la zone d’index est parfois plus complexe que nécessaire dans le cadre d’une utilisation normale. Si vous souhaitez éviter la phase de placement des fichiers dans la zone d’index, Git fournit un raccourci très simple. L’ajout de l’option -a à la commande git commit ordonne à Git de placer automatiquement tout fichier déjà en suivi de version dans la zone d’index avant de réaliser la validation, évitant ainsi d’avoir à taper les commandes git add : $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui ne seront pas validées : (utilisez "git add <fichier>..." pour mettre à jour ce qui sera validé) (utilisez "git checkout -- <fichier>..." pour annuler les modifications dans la copie de travail) modifié : CONTRIBUTING.md aucune modification n'a été ajoutée à la validation (utilisez "git add" ou "git commit -a") $ git commit -a -m 'added new benchmarks' [master 83e38c7] added new benchmarks 1 file changed, 5 insertions(+), 0 deletions(-) Notez bien que vous n’avez pas eu à lancer git add sur le fichier CONTRIBUTING.md avant de valider. Effacer des fichiers Pour effacer un fichier de Git, vous devez l’éliminer des fichiers en suivi de version (plus précisément, l’effacer dans la zone d’index) puis valider. La commande git rm réalise cette action mais efface aussi ce fichier de votre copie de travail de telle sorte que vous ne le verrez pas réapparaître comme fichier non suivi en version à la prochaine validation. Si vous effacez simplement le fichier dans votre copie de travail, il apparaît sous la section « Modifications qui ne seront pas validées » (c’est-à-dire, non indexé ) dans le résultat de git status : $ rm PROJECTS.md $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui ne seront pas validées : (utilisez "git add/rm <fichier>..." pour mettre à jour ce qui sera validé) (utilisez "git checkout -- <fichier>..." pour annuler les modifications dans la copie de travail) supprimé : PROJECTS.md aucune modification n'a été ajoutée à la validation (utilisez "git add" ou "git commit -a") Ensuite, si vous lancez git rm , l’effacement du fichier est indexé : $ git rm PROJECTS.md rm 'PROJECTS.md' Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui seront validées : (utilisez "git reset HEAD <fichier>..." pour désindexer) supprimé : PROJECTS.md Lors de la prochaine validation, le fichier sera absent et non-suivi en version. Si vous avez auparavant modifié et indexé le fichier, son élimination doit être forcée avec l’option -f . C’est une mesure de sécurité pour empêcher un effacement accidentel de données qui n’ont pas encore été enregistrées dans un instantané et qui seraient définitivement perdues. Un autre scénario serait de vouloir abandonner le suivi de version d’un fichier tout en le conservant dans la copie de travail. Ceci est particulièrement utile lorsqu’on a oublié de spécifier un patron dans le fichier .gitignore et on a accidentellement indexé un fichier, tel qu’un gros fichier de journal ou une série d’archives de compilation .a . Pour réaliser ce scénario, utilisez l’option --cached : $ git rm --cached LISEZMOI Vous pouvez spécifier des noms de fichiers ou de répertoires, ou des patrons de fichiers à la commande git rm . Cela signifie que vous pouvez lancer des commandes telles que : $ git rm log/\*.log Notez bien la barre oblique inverse ( \ ) devant * . Il est nécessaire d’échapper le caractère \* car Git utilise sa propre expansion de nom de fichier en addition de l’expansion du shell. Ce caractère d’échappement doit être omis sous Windows si vous utilisez le terminal système. Cette commande efface tous les fichiers avec l’extension .log présents dans le répertoire log/ . Vous pouvez aussi lancer une commande telle que : $ git rm \*~ Cette commande élimine tous les fichiers se terminant par ~ . Déplacer des fichiers À la différence des autres VCS, Git ne suit pas explicitement les mouvements des fichiers. Si vous renommez un fichier suivi par Git, aucune méta-donnée indiquant le renommage n’est stockée par Git. Néanmoins, Git est assez malin pour s’en apercevoir après coup — la détection de mouvement de fichier sera traitée plus loin. De ce fait, que Git ait une commande mv peut paraître trompeur. Si vous souhaitez renommer un fichier dans Git, vous pouvez lancer quelque chose comme : $ git mv nom_origine nom_cible et cela fonctionne. En fait, si vous lancez quelque chose comme ceci et inspectez le résultat d’une commande git status , vous constaterez que Git gère le renommage de fichier : $ git mv LISEZMOI.txt LISEZMOI $ git status Sur la branche master Votre branche est à jour avec 'origin/master'. Modifications qui seront validées : (utilisez "git reset HEAD <fichier>..." pour désindexer) renommé : LISEZMOI.txt -> LISEZMOI Néanmoins, cela revient à lancer les commandes suivantes : $ mv LISEZMOI.txt LISEZMOI $ git rm LISEZMOI.txt $ git add LISEZMOI Git trouve implicitement que c’est un renommage, donc cela importe peu si vous renommez un fichier de cette manière ou avec la commande mv . La seule différence réelle est que git mv ne fait qu’une commande à taper au lieu de trois — c’est une commande de convenance. Le point principal est que vous pouvez utiliser n’importe quel outil pour renommer un fichier, et traiter les commandes add / rm plus tard, avant de valider la modification. 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/zh/v2/Git-%e5%9f%ba%e7%a1%80-Git-%e5%88%ab%e5%90%8d | 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 协议 4.2 在服务器上搭建 Git 4.3 生成 SSH 公钥 4.4 配置服务器 4.5 Git 守护进程 4.6 Smart HTTP 4.7 GitWeb 4.8 GitLab 4.9 第三方托管的选择 4.10 总结 5. 分布式 Git 5.1 分布式工作流程 5.2 向一个项目贡献 5.3 维护项目 5.4 总结 6. GitHub 6.1 账户的创建和配置 6.2 对项目做出贡献 6.3 维护项目 6.4 管理组织 6.5 脚本 GitHub 6.6 总结 7. Git 工具 7.1 选择修订版本 7.2 交互式暂存 7.3 贮藏与清理 7.4 签署工作 7.5 搜索 7.6 重写历史 7.7 重置揭密 7.8 高级合并 7.9 Rerere 7.10 使用 Git 调试 7.11 子模块 7.12 打包 7.13 替换 7.14 凭证存储 7.15 总结 8. 自定义 Git 8.1 配置 Git 8.2 Git 属性 8.3 Git 钩子 8.4 使用强制策略的一个例子 8.5 总结 9. Git 与其他系统 9.1 作为客户端的 Git 9.2 迁移到 Git 9.3 总结 10. Git 内部原理 10.1 底层命令与上层命令 10.2 Git 对象 10.3 Git 引用 10.4 包文件 10.5 引用规范 10.6 传输协议 10.7 维护与数据恢复 10.8 环境变量 10.9 总结 A1. 附录 A: 在其它环境中使用 Git A1.1 图形界面 A1.2 Visual Studio 中的 Git A1.3 Visual Studio Code 中的 Git A1.4 IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine 中的 Git A1.5 Sublime Text 中的 Git A1.6 Bash 中的 Git A1.7 Zsh 中的 Git A1.8 PowerShell 中的 Git A1.9 总结 A2. 附录 B: 在你的应用中嵌入 Git A2.1 命令行 Git 方式 A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. 附录 C: Git 命令 A3.1 设置与配置 A3.2 获取与创建项目 A3.3 快照基础 A3.4 分支与合并 A3.5 项目分享与更新 A3.6 检查与比较 A3.7 调试 A3.8 补丁 A3.9 邮件 A3.10 外部系统 A3.11 管理 A3.12 底层命令 2nd Edition 2.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 。 随着你继续不断地使用 Git，可能也会经常使用其他命令，所以创建别名时不要犹豫。 在创建你认为应该存在的命令时这个技术会很有用。 例如，为了解决取消暂存文件的易用性问题，可以向 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://git-scm.com/book/ru/v2/%d0%9e%d1%81%d0%bd%d0%be%d0%b2%d1%8b-Git-%d0%9f%d1%80%d0%be%d1%81%d0%bc%d0%be%d1%82%d1%80-%d0%b8%d1%81%d1%82%d0%be%d1%80%d0%b8%d0%b8-%d0%ba%d0%be%d0%bc%d0%bc%d0%b8%d1%82%d0%be%d0%b2 | Git - Просмотр истории коммитов About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. Введение 1.1 О системе контроля версий 1.2 Краткая история Git 1.3 Что такое Git? 1.4 Командная строка 1.5 Установка Git 1.6 Первоначальная настройка Git 1.7 Как получить помощь? 1.8 Заключение 2. Основы Git 2.1 Создание Git-репозитория 2.2 Запись изменений в репозиторий 2.3 Просмотр истории коммитов 2.4 Операции отмены 2.5 Работа с удалёнными репозиториями 2.6 Работа с тегами 2.7 Псевдонимы в Git 2.8 Заключение 3. Ветвление в Git 3.1 О ветвлении в двух словах 3.2 Основы ветвления и слияния 3.3 Управление ветками 3.4 Работа с ветками 3.5 Удалённые ветки 3.6 Перебазирование 3.7 Заключение 4. Git на сервере 4.1 Протоколы 4.2 Установка Git на сервер 4.3 Генерация открытого SSH ключа 4.4 Настраиваем сервер 4.5 Git-демон 4.6 Умный HTTP 4.7 GitWeb 4.8 GitLab 4.9 Git-хостинг 4.10 Заключение 5. Распределённый Git 5.1 Распределённый рабочий процесс 5.2 Участие в проекте 5.3 Сопровождение проекта 5.4 Заключение 6. GitHub 6.1 Настройка и конфигурация учётной записи 6.2 Внесение собственного вклада в проекты 6.3 Сопровождение проекта 6.4 Управление организацией 6.5 Создание сценариев GitHub 6.6 Заключение 7. Инструменты Git 7.1 Выбор ревизии 7.2 Интерактивное индексирование 7.3 Припрятывание и очистка 7.4 Подпись 7.5 Поиск 7.6 Перезапись истории 7.7 Раскрытие тайн reset 7.8 Продвинутое слияние 7.9 Rerere 7.10 Обнаружение ошибок с помощью Git 7.11 Подмодули 7.12 Создание пакетов 7.13 Замена 7.14 Хранилище учётных данных 7.15 Заключение 8. Настройка Git 8.1 Конфигурация Git 8.2 Атрибуты Git 8.3 Хуки в Git 8.4 Пример принудительной политики Git 8.5 Заключение 9. Git и другие системы контроля версий 9.1 Git как клиент 9.2 Переход на Git 9.3 Заключение 10. Git изнутри 10.1 Сантехника и Фарфор 10.2 Объекты Git 10.3 Ссылки в Git 10.4 Pack-файлы 10.5 Спецификации ссылок 10.6 Протоколы передачи данных 10.7 Обслуживание репозитория и восстановление данных 10.8 Переменные окружения 10.9 Заключение A1. Приложение A: Git в других окружениях A1.1 Графические интерфейсы A1.2 Git в Visual Studio A1.3 Git в Visual Studio Code A1.4 Git в Eclipse A1.5 Git в IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine A1.6 Git в Sublime Text A1.7 Git в Bash A1.8 Git в Zsh A1.9 Git в PowerShell A1.10 Заключение A2. Приложение B: Встраивание Git в ваши приложения A2.1 Git из командной строки A2.2 Libgit2 A2.3 JGit A2.4 go-git A2.5 Dulwich A3. Приложение C: Команды Git A3.1 Настройка и конфигурация A3.2 Клонирование и создание репозиториев A3.3 Основные команды A3.4 Ветвление и слияния A3.5 Совместная работа и обновление проектов A3.6 Осмотр и сравнение A3.7 Отладка A3.8 Внесение исправлений A3.9 Работа с помощью электронной почты A3.10 Внешние системы A3.11 Администрирование A3.12 Низкоуровневые команды 2nd Edition 2.3 Основы Git - Просмотр истории коммитов Просмотр истории коммитов После того, как вы создали несколько коммитов или же клонировали репозиторий с уже существующей историей коммитов, вероятно вам понадобится возможность посмотреть что было сделано — историю коммитов. Одним из основных и наиболее мощных инструментов для этого является команда git log . Следующие несколько примеров используют очень простой проект «simplegit». Чтобы клонировать проект, используйте команду: $ git clone https://github.com/schacon/simplegit-progit Если вы запустите команду git log в каталоге клонированного проекта, вы увидите следующий вывод: $ git log commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 Change version number commit 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 16:40:33 2008 -0700 Remove unnecessary test commit a11bef06a3f659402fe7563abf99ad00de2209e6 Author: Scott Chacon <schacon@gee-mail.com> Date: Sat Mar 15 10:31:28 2008 -0700 Initial commit По умолчанию (без аргументов) git log перечисляет коммиты, сделанные в репозитории в обратном к хронологическому порядке — последние коммиты находятся вверху. Из примера можно увидеть, что данная команда перечисляет коммиты с их SHA-1 контрольными суммами, именем и электронной почтой автора, датой создания и сообщением коммита. Команда git log имеет очень большое количество опций для поиска коммитов по разным критериям. Рассмотрим наиболее популярные из них. Одним из самых полезных аргументов является -p или --patch , который показывает разницу (выводит патч ), внесённую в каждый коммит. Так же вы можете ограничить количество записей в выводе команды; используйте параметр -2 для вывода только двух записей: $ git log -p -2 commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 Change 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 Remove 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 Эта опция отображает аналогичную информацию но содержит разницу для каждой записи. Очень удобно использовать данную опцию для код ревью или для быстрого просмотра серии внесённых изменений. Так же есть возможность использовать серию опций для обобщения. Например, если вы хотите увидеть сокращённую статистику для каждого коммита, вы можете использовать опцию --stat : $ git log --stat commit ca82a6dff817ec66f44342007202690a93763949 Author: Scott Chacon <schacon@gee-mail.com> Date: Mon Mar 17 21:52:11 2008 -0700 Change 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 Remove 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 Initial commit README | 6 ++++++ Rakefile | 23 +++++++++++++++++++++++ lib/simplegit.rb | 25 +++++++++++++++++++++++++ 3 files changed, 54 insertions(+) Как вы видите, опция --stat печатает под каждым из коммитов список и количество изменённых файлов, а также сколько строк в каждом из файлов было добавлено и удалено. В конце можно увидеть суммарную таблицу изменений. Следующей действительно полезной опцией является --pretty . Эта опция меняет формат вывода. Существует несколько встроенных вариантов отображения. Опция oneline выводит каждый коммит в одну строку, что может быть очень удобным если вы просматриваете большое количество коммитов. К тому же, опции short , full и fuller делают вывод приблизительно в том же формате, но с меньшим или большим количеством информации соответственно: $ git log --pretty=oneline ca82a6dff817ec66f44342007202690a93763949 Change version number 085bb3bcb608e1e8451d4b2432f8ecbe6306e7e7 Remove unnecessary test a11bef06a3f659402fe7563abf99ad00de2209e6 Initial commit Наиболее интересной опцией является format , которая позволяет указать формат для вывода информации. Особенно это может быть полезным когда вы хотите сгенерировать вывод для автоматического анализа — так как вы указываете формат явно, он не будет изменён даже после обновления Git: $ git log --pretty=format:"%h - %an, %ar : %s" ca82a6d - Scott Chacon, 6 years ago : Change version number 085bb3b - Scott Chacon, 6 years ago : Remove unnecessary test a11bef0 - Scott Chacon, 6 years ago : Initial commit Полезные опции для git log --pretty=format отображает наиболее полезные опции для изменения формата. Таблица 1. Полезные опции для git log --pretty=format Опция Описания вывода %H Хеш коммита %h Сокращённый хеш коммита %T Хеш дерева %t Сокращённый хеш дерева %P Хеш родителей %p Сокращённый хеш родителей %an Имя автора %ae Электронная почта автора %ad Дата автора (формат даты можно задать опцией --date=option) %ar Относительная дата автора %cn Имя коммитера %ce Электронная почта коммитера %cd Дата коммитера %cr Относительная дата коммитера %s Содержание Вам наверное интересно, какая же разница между автором и коммитером . Автор — это человек, изначально сделавший работу, а коммитер — это человек, который последним применил эту работу. Другими словами, если вы создадите патч для какого-то проекта, а один из основных членов команды этого проекта применит этот патч, вы оба получите статус участника — вы как автор и основной член команды как коммитер. Более детально мы рассмотрим разницу в главе Распределённый Git . Опции oneline и format являются особенно полезными с опцией --graph команды log . С этой опцией вы сможете увидеть небольшой граф в формате ASCII, который показывает текущую ветку и историю слияний: $ 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 Add 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 Данный вывод будет нам очень интересен в следующей главе, где мы рассмотрим ветвление и слияние. Мы рассмотрели только несколько простых опций для форматирования вывода с помощью команды git log — на самом деле их гораздо больше. Наиболее распространённые опции для команды git log содержит описание как уже рассмотренных, так и нескольких новых опций, которые могут быть полезными в зависимости от нужного формата вывода. Таблица 2. Наиболее распространённые опции для команды git log Опция Описание -p Показывает патч для каждого коммита. --stat Показывает статистику изменённых файлов для каждого коммита. --shortstat Отображает только строку с количеством изменений/вставок/удалений для команды --stat. --name-only Показывает список изменённых файлов после информации о коммите. --name-status Показывает список файлов, которые добавлены/изменены/удалены. --abbrev-commit Показывает только несколько символов SHA-1 чек-суммы вместо всех 40. --relative-date Отображает дату в относительном формате (например, «2 weeks ago») вместо стандартного формата даты. --graph Отображает ASCII граф с ветвлениями и историей слияний. --pretty Показывает коммиты в альтернативном формате. Возможные варианты опций: oneline, short, full, fuller и format (с помощью последней можно указать свой формат). --oneline Сокращение для одновременного использования опций --pretty=oneline --abbrev-commit . Ограничение вывода В дополнение к опциям форматирования вывода, команда git log принимает несколько опций для ограничения вывода — опций, с помощью которых можно увидеть определённое подмножество коммитов. Вы уже видели одну из таких опций — это опция -2 , которая показывает только последние два коммита. В действительности вы можете использовать -<n> , где n — это любое натуральное число и представляет собой n последних коммитов. На практике вы не будете часто использовать эту опцию, потому что Git по умолчанию использует постраничный вывод и вы будете видеть только одну страницу за раз. Однако, опции для ограничения вывода по времени, такие как --since и --until , являются очень удобными. Например, следующая команда покажет список коммитов, сделанных за последние две недели: $ git log --since=2.weeks Это команда работает с большим количеством форматов — вы можете указать определённую дату вида 2008-01-15 или же относительную дату, например 2 years 1 day 3 minutes ago . Также вы можете фильтровать список коммитов по заданным параметрам. Опция --author даёт возможность фильтровать по автору коммита, а опция --grep искать по ключевым словам в сообщении коммита. Примечание Допускается указывать несколько параметров --author и --grep для поиска, которые позволят найти коммиты, соответствующие любому указанному --author и любому указанному --grep шаблону; однако, применение опции --all-match заставит искать коммиты соответствующие всем указанным --grep шаблонам. Следующим действительно полезным фильтром является опция -S , которая принимает аргумент в виде строки и показывает только те коммиты, в которых изменение в коде повлекло за собой добавление или удаление этой строки. Например, если вы хотите найти последний коммит, который добавил или удалил вызов определённой функции, вы можете запустить команду: $ git log -S function_name Последней полезной опцией, которую принимает команда git log как фильтр, является путь. Если вы укажете каталог или имя файла, вы ограничите вывод только теми коммитами, в которых были изменения этих файлов. Эта опция всегда указывается последней после двойного тире ( -- ), чтобы отделить пути от опций: $ git log -- path/to/file В таблице Опции для ограничения вывода команды git log вы можете увидеть эти и другие распространённые опции. Таблица 3. Опции для ограничения вывода команды git log Опция Описание -(n) Показывает только последние n коммитов. --since , --after Показывает только те коммиты, которые были сделаны после указанной даты. --until , --before Показывает только те коммиты, которые были сделаны до указанной даты. --author Показывает только те коммиты, в которых запись author совпадает с указанной строкой. --committer Показывает только те коммиты, в которых запись committer совпадает с указанной строкой. --grep Показывает только коммиты, сообщение которых содержит указанную строку. -S Показывает только коммиты, в которых изменение в коде повлекло за собой добавление или удаление указанной строки. Например, если вы хотите увидеть, в каких коммитах произошли изменения в тестовых файлах в исходном коде Git в октябре 2008 года, автором которых был Junio Hamano и которые не были коммитами слияния, вы можете запустить следующую команду: $ git log --pretty="%h - %s" --author='Junio C Hamano' --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 Из почти 40 000 коммитов в истории исходного кода Git, эта команда показывает только 6, которые соответствуют этим критериям. Подсказка Предотвращение отображения коммитов слияния В зависимости от используемого порядка работы, история коммитов в вашем репозитории может содержать большое количество коммитов слияния, которые сами по себе не очень информативны. Чтобы исключить их из вывода команды git 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:24 |
https://docs.brightdata.com/api-reference/web-scraper-api/synchronous-requests#how-it-works | 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/it/v2/Git-on-the-Server-GitLab | Git - GitLab About Trademark Learn Book Cheat Sheet Videos External Links Tools Command Line GUIs Hosting Reference Install Community This book is available in English . Full translation available in azərbaycan dili , български език , Deutsch , Español , فارسی , Français , Ελληνικά , 日本語 , 한국어 , Nederlands , Русский , Slovenščina , Tagalog , Українська , 简体中文 , Partial translations available in Čeština , Македонски , Polski , Српски , Ўзбекча , 繁體中文 , Translations started for Беларуская , Indonesian , Italiano , Bahasa Melayu , Português (Brasil) , Português (Portugal) , Svenska , Türkçe . The source of this book is hosted on GitHub. Patches, suggestions and comments are welcome. Chapters ▾ 1. 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 4.8 Git on the Server - GitLab GitLab GitWeb is pretty simplistic though. If you’re looking for a more modern, fully featured Git server, there are some several open source solutions out there that you can install instead. As GitLab is one of the more popular ones, we’ll cover installing and using it as an example. This is a bit more complex than the GitWeb option and likely requires more maintenance, but it is a much more fully featured option. Installation GitLab is a database-backed web application, so its installation is a bit more involved than some other git servers. Fortunately, this process is very well-documented and supported. There are a few methods you can pursue to install GitLab. To get something up and running quickly, you can download a virtual machine image or a one-click installer from https://bitnami.com/stack/gitlab , and tweak the configuration to match your particular environment. One nice touch Bitnami has included is the login screen (accessed by typing alt-→); it tells you the IP address and default username and password for the installed GitLab. Figura 50. The Bitnami GitLab virtual machine login screen. For anything else, follow the guidance in the GitLab Community Edition readme, which can be found at https://gitlab.com/gitlab-org/gitlab-ce/tree/master . There you’ll find assistance for installing GitLab using Chef recipes, a virtual machine on Digital Ocean, and RPM and DEB packages (which, as of this writing, are in beta). There’s also “unofficial” guidance on getting GitLab running with non-standard operating systems and databases, a fully-manual installation script, and many other topics. Administration GitLab’s administration interface is accessed over the web. Simply point your browser to the hostname or IP address where GitLab is installed, and log in as an admin user. The default username is admin@local.host , and the default password is 5iveL!fe (which you will be prompted to change as soon as you enter it). Once logged in, click the “Admin area” icon in the menu at the top right. Figura 51. The “Admin area” item in the GitLab menu. Users Users in GitLab are accounts that correspond to people. User accounts don’t have a lot of complexity; mainly it’s a collection of personal information attached to login data. Each user account comes with a namespace , which is a logical grouping of projects that belong to that user. If the user jane had a project named project , that project’s url would be http://server/jane/project . Figura 52. The GitLab user administration screen. Removing a user can be done in two ways. “Blocking” a user prevents them from logging into the GitLab instance, but all of the data under that user’s namespace will be preserved, and commits signed with that user’s email address will still link back to their profile. “Destroying” a user, on the other hand, completely removes them from the database and filesystem. All projects and data in their namespace is removed, and any groups they own will also be removed. This is obviously a much more permanent and destructive action, and its uses are rare. Groups A GitLab group is an assemblage of projects, along with data about how users can access those projects. Each group has a project namespace (the same way that users do), so if the group training has a project materials , its url would be http://server/training/materials . Figura 53. The GitLab group administration screen. Each group is associated with a number of users, each of which has a level of permissions for the group’s projects and the group itself. These range from “Guest” (issues and chat only) to “Owner” (full control of the group, its members, and its projects). The types of permissions are too numerous to list here, but GitLab has a helpful link on the administration screen. Projects A GitLab project roughly corresponds to a single git repository. Every project belongs to a single namespace, either a user or a group. If the project belongs to a user, the owner of the project has direct control over who has access to the project; if the project belongs to a group, the group’s user-level permissions will also take effect. Every project also has a visibility level, which controls who has read access to that project’s pages and repository. If a project is Private , the project’s owner must explicitly grant access to specific users. An Internal project is visible to any logged-in user, and a Public project is visible to anyone. Note that this controls both git “fetch” access as well as access to the web UI for that project. Hooks GitLab includes support for hooks, both at a project or system level. For either of these, the GitLab server will perform an HTTP POST with some descriptive JSON whenever relevant events occur. This is a great way to connect your git repositories and GitLab instance to the rest of your development automation, such as CI servers, chat rooms, or deployment tools. Basic Usage The first thing you’ll want to do with GitLab is create a new project. This is accomplished by clicking the “+” icon on the toolbar. You’ll be asked for the project’s name, which namespace it should belong to, and what its visibility level should be. Most of what you specify here isn’t permanent, and can be re-adjusted later through the settings interface. Click “Create Project”, and you’re done. Once the project exists, you’ll probably want to connect it with a local Git repository. Each project is accessible over HTTPS or SSH, either of which can be used to configure a Git remote. The URLs are visible at the top of the project’s home page. For an existing local repository, this command will create a remote named gitlab to the hosted location: $ git remote add gitlab https://server/namespace/project.git If you don’t have a local copy of the repository, you can simply do this: $ git clone https://server/namespace/project.git The web UI provides access to several useful views of the repository itself. Each project’s home page shows recent activity, and links along the top will lead you to views of the project’s files and commit log. Working Together The simplest way of working together on a GitLab project is by giving another user direct push access to the git repository. You can add a user to a project by going to the “Members” section of that project’s settings, and associating the new user with an access level (the different access levels are discussed a bit in Groups ). By giving a user an access level of “Developer” or above, that user can push commits and branches directly to the repository with impunity. Another, more decoupled way of collaboration is by using merge requests. This feature enables any user that can see a project to contribute to it in a controlled way. Users with direct access can simply create a branch, push commits to it, and open a merge request from their branch back into master or any other branch. Users who don’t have push permissions for a repository can “fork” it (create their own copy), push commits to that copy, and open a merge request from their fork back to the main project. This model allows the owner to be in full control of what goes into the repository and when, while allowing contributions from untrusted users. Merge requests and issues are the main units of long-lived discussion in GitLab. Each merge request allows a line-by-line discussion of the proposed change (which supports a lightweight kind of code review), as well as a general overall discussion thread. Both can be assigned to users, or organized into milestones. This section has focused mainly on the Git-related parts of GitLab, but it’s a fairly mature system, and provides many other features that can help your team work together. These include project wikis, discussion “walls”, and system maintenance tools. One benefit to GitLab is that, once the server is set up and running, you’ll rarely need to tweak a configuration file or access the server via SSH; most administration and general usage can be accomplished through the in-browser interface. prev | next About this site Patches, suggestions, and comments are welcome. Git is a member of Software Freedom Conservancy | 2026-01-13T09:29:24 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.