-
-
-
-
- A curated list of awesome, Slack-related things. -
- -*** - -An avid Slack user? A developer looking for awesome tools to build out an integration? Just looking for inspiration? This is a list of all the best things Slack. - - -## :pencil: Lists -- [Community-Built Libraries](https://api.slack.com/community) - Slack-curated list of community open-source libraries -- [Slack App Directory](https://slack.com/apps) - Official directory of publicly available Slack apps -- [Slack Emojis](https://emoji.gg) - Unofficial directory of custom emojis for Slack - -## :art: Themes - -- [Slack Themes](http://slackthemes.net/) - A Slack sidebar theme browser -- [Sweet Themes Are Made of These](http://sweetthemesaremadeofthe.se/) - Website for sharing Slack custom palettes - -## :hammer_and_wrench: Libraries and SDKs - -### C# - -- [margiebot](https://github.com/jammerware/margiebot) - A .NET library designed to make building bots for Slack fast, easy, and fun -- [Slack.Webhooks](https://github.com/nerdfury/Slack.Webhooks) - A library to work with Slack webhooks more easily -- [SlackAPI](https://github.com/Inumedia/SlackAPI) - A third-party implementation of Slack's API written in C# - -### Erlang - -- [slacker](https://github.com/julienXX/slacker) - Erlang Slack REST API wrapper - -### Go - -- [webhook](https://github.com/adnanh/webhook) - Easily run commands in response to HTTP webhook requests from Slack - -### Java - -- [java-slack-sdk](https://github.com/slackapi/java-slack-sdk) - Slack's official Java framework for building Slack apps -- [simple-slack-api](https://github.com/Ullink/simple-slack-api) - A Slack client library in Java - -### JavaScript/TypeScript - -- [bolt-js](https://github.com/slackapi/bolt-js) - Slack's official JavaScript framework for building Slack apps -- [jsx-slack](https://github.com/yhatt/jsx-slack) - Build JSON object for Slack Block Kit surfaces from JSX -- [node-slack-sdk](https://github.com/slackapi/node-slack-sdk) - Slack's official SDK for Node.js -- [slack-block-builder](https://github.com/raycharius/slack-block-builder) - Lightweight Node.js library for building Slack Block Kit UIs, with a declarative syntax inspired by SwiftUI - -### PHP - -- [SlackBundle](https://github.com/DZunke/SlackBundle) - SlackBundle for Symfony2 -- [slack-php-app-framework](https://github.com/slack-php/slack-php-app-framework) - Robust PHP framework for building Slack apps in PHP -- [slack-php-block-kit](https://github.com/jeremeamia/slack-block-kit) - Fluent interface for composing Slack Block Kit messages and modals in PHP -- [slack-php-socket-mode](https://github.com/slack-php/slack-php-socket-mode) - A Socket Mode implementation for [slack-php-app-framework](https://github.com/slack-php/slack-php-app-framework) -- [slack-php-slick](https://github.com/slack-php/slack-php-slick) - Dependency-free micro-framework for building Slack apps in PHP - -### PowerShell - -- [PSSlack](https://github.com/RamblingCookieMonster/PSSlack) - PowerShell module for simple Slack integration. - -### Python - -- [blockkit](https://github.com/imryche/blockkit) - A fast way to build Block Kit interfaces in Python -- [bolt-python](https://github.com/slackapi/bolt-python) - Slack's official Python framework for building Slack apps -- [django-slack](https://github.com/lamby/django-slack) - Slack integration for Django, using the templating engine to generate messages -- [django-slack-oauth](https://github.com/izdi/django-slack-oauth) - Slack OAuth module for Django -- [python-slack-events-api](https://github.com/slackapi/python-slack-events-api) - Slack Events API adapter for Python -- [python-slack-sdk](https://github.com/slackapi/python-slack-sdk) - Slack's official SDK for Python -- [slackblocks](https://github.com/nicklambourne/slackblocks) - Python API for building Slack Block Kit messages -- [slack-php-api](https://github.com/jolicode/slack-php-api) - PHP Slack client based on the official OpenAPI specification -- [slacker-cli](https://github.com/juanpabloaj/slacker-cli) - Messages to slack from the command line -- [slashbot](https://github.com/ebrassell/slashbot) - An easy way to create slash commands using AWS Lambda functions -- [boltworks](https://github.com/YSaxon/boltworks) - Extensions to Slack's bolt framework: expandable GUIs, easier callbacks, richer CLIs - -### R - -- [slackr](https://github.com/hrbrmstr/slackr) - A package to send webhook API messages to Slack channels/users from R - -### Ruby - -- [slack-notifier](https://github.com/stevenosloan/slack-notifier) - A simple wrapper for posting to Slack -- [slack-notify](https://github.com/sosedoff/slack-notify) - Send notifications to Slack -- [slack-poster](https://github.com/rikas/slack-poster) - Simple gem to post messages on Slack using webhooks -- [slack-ruby-block-kit](https://github.com/CGA1123/slack-ruby-block-kit) - A ruby wrapper for Slack's Block Kit -- [slack-ruby-bot](https://github.com/dblock/slack-ruby-bot) - The easiest way to write a Slack bot in Ruby -- [slack-ruby-bot-server](https://github.com/slack-ruby/slack-ruby-bot-server) - Ruby library for building Slack applications -- [slack-ruby-client](https://github.com/dblock/slack-ruby-client) - A Ruby client for the Slack Web and RealTime Messaging APIs - -### Rust - -- [slack-morphism-rust](https://github.com/abdolence/slack-morphism-rust) - A modern async Slack API client for Rust - -### Scala - -- [slack-scala-client](https://github.com/gilbertw1/slack-scala-client) - A Scala Slack client for the Web and RTM API - -### Swift - -- [SwiftBlocksUI](https://github.com/SwiftBlocksUI/SwiftBlocksUI/) - Interactive Slack messages and modals using a SwiftUI-like declarative style - -## :gear: Open-Source Slack Apps and Integrations - -### CoffeeScript - -- [jinora](https://github.com/sdslabs/jinora) - Slack webhook app to create anonymous public channels - -### Java - -- [simple-slack-api](https://github.com/Ullink/simple-slack-api) - A Slack client library in Java -- [tasks-app](https://github.com/slackapi/tasks-app) - Simple task management app produced by Slack - -### JavaScript/Typescript - -- [definition-app](https://github.com/slackapi/definition-app) - App for storing and accessing company-specific phrases -- [slack-github-action](https://github.com/slackapi/slack-github-action) - Send data into Slack using this GitHub Action -- [slack-reporting-tool](https://github.com/slackapi/slack-reporting-tool) - App that allows team members to report offensive messages -- [tesla-slack](https://github.com/heikkipora/tesla-slack) - Track your Tesla from Slack -- [tasks-app](https://github.com/slackapi/tasks-app) - Simple task management app produced by Slack - -### PHP - -- [MantisBT-Slack](https://github.com/infojunkie/MantisBT-Slack) - MantisBT plugin to send bug updates to Slack -- [monolog](https://github.com/Seldaek/monolog) - Sends your logs to Slack - -### Python - -- [slackbot](https://github.com/lins05/slackbot) - A chat bot for Slack -- [slacker-cli](https://github.com/juanpabloaj/slacker-cli) - Messages to slack from the command line -- [tasks-app](https://github.com/slackapi/tasks-app) - Simple task management app produced by Slack -- [wee-slack](https://github.com/rawdigits/wee-slack) - A WeeChat plugin for Slack - -### Ruby - -- [slack-gamebot](https://github.com/dblock/slack-gamebot) - A game bot for Slack -- [snarkov](https://github.com/gesteves/snarkov) - Sinatra-based Markov bot for Slack -- [tickbot](https://github.com/barryf/tickbot) - Simple team time tracking reminder -- [trebekbot](https://github.com/gesteves/trebekbot) - A Jeopardy! bot for Slack - -## :busts_in_silhouette: Contributions - -Contributions are always welcome! Please read the [contribution guidelines](https://github.com/matiassingers/awesome-slack/blob/master/contributing.md) first. - -## :classical_building: License - -[](http://creativecommons.org/publicdomain/zero/1.0/) - -To the extent possible under law, [Matias Singers](http://mts.io) has waived all copyright and related or neighboring rights to this work. + +## Awesome Slack Communities [](https://github.com/sindresorhus/awesome) +[](https://travis-ci.org/filipelinhares/awesome-slack) + +A list of communities about web development and design that are powered by **Slack**. + +## What's Slack +> Slack is a platform for team communication: everything in one place, instantly searchable, available wherever you go. *- slack.com* + + +## Development +- [Ember](https://ember-community-slackin.herokuapp.com/) +- [Laravel](https://larachat.co/) +- [Ruby](https://rubydevelopers.typeform.com/to/l7WVWl) +- [Front end](https://frontenddevelopers.org/) +- [Android](https://androidchat.co/) +- [GO](https://docs.google.com/forms/d/e/1FAIpQLScNsNXbz2SCLH5hVNoZS0C70nPAXv730SW9F3K1g6iVvlcUTg/viewform?fbzx=4754263898376949596) +- [PHP Chat](https://phpchat.co) +- [Clojure](http://clojurians.net/) +- [iOS Developers](https://ios-developers.io/) +- [Elixir](https://elixir-slackin.herokuapp.com/) +- [slashrocket](https://slashrocket.io/) +- [Cordova](http://slack.cordova.io/) +- [Python Community](https://pythoncommunity.herokuapp.com/) +- [CFML/ColdFusion](https://cfml-slack.herokuapp.com/) + + +## Regional +- [Australia & New Zealand](http://devanz.co) +- [Les Pitonneux - Montreal QC Canada](https://pitonneux.slack.com) +- [Python Brazilian Community](http://slack-pythonbrasil.herokuapp.com/) +- [Remote workers in Romania](https://github.com/filipelinhares/awesome-slack/blob/master/weworkremotely.slack.com/) +- [Russian-speaking developers community](https://rusdevs.herokuapp.com/) +- [Kazan Developers](https://devkzn.slack.com/) +- [Polish developers](http://slackin.devstyle.pl/) +- [Spanish-speaking developer communities list](https://github.com/comunidad-tecnologica/awesome-spanish-slack-dev-groups) +- [Ruby Turkey Community](https://rubytr.herokuapp.com/) +- [Rochester NY USA Developers (RocDev)](https://rocdev.org/) +- [Vancouver Developers (yvrdev)](https://yvrdev.slack.com/) + +## Design +- [Sketch](http://teamsketch.io/) +- [Design Talks](https://docs.google.com/forms/d/e/1FAIpQLSeKT_LC8kKTzJ4JjmgVQVpfl24i1qBkjJ7TYyQcNHL7fBQkYQ/viewform?c=0&w=1) +- [Designer Hangout](https://www.designerhangout.co/) + +## Misc +- [WordPress](https://make.wordpress.org/chat/) +- [Chit Chats](http://www.chitchats.co/) +- [The Evangelist Collective](https://github.com/evangelistcollective/) +- [Psychedelic Chat](http://psychedelicchat.com/) +- [LGBTQ in Technology](https://lgbtq.technology/) +- [#Startup](http://startup.chat) +- [Safelight](http://safelight.herokuapp.com/) - Photography. +- [DFIR Community](https://rishi28.typeform.com/to/sTbTI8) - Information Security. +- [First Contributors](https://firstcontributors.slack.com/join/shared_invite/enQtNjkxNzQwNzA2MTMwLTVhMWJjNjg2ODRlNWZhNjIzYjgwNDIyZWYwZjhjYTQ4OTBjMWM0MmFhZDUxNzBiYzczMGNiYzcxNjkzZDZlMDM#/) - Help / mentorship for open source contributors. +- [IT Pro Community](https://www.electric.ai/it-pro-slack) - Connect and network with IT practitioners and decision-makers +- [SaaS Community](https://join.slack.com/t/saas-hgv7803/shared_invite/zt-qwvrywyr-8DmSpEzBiSWD2WQuB9r9pw) - Community for SaaS product builders, to discuss the challenges involved. +- [Developer Marketing](https://marketingto.dev/) - Passionate marketing folks working in API Marketing, developer tooling, or actively marketing to developers. + +## DevOps +- [Google Cloud Platform](http://bit.ly/gcp-slack) +- [Kubernetes](http://slack.kubernetes.io/) +- [DevOps](https://devopschat.co/) +- [Devop Engineers](https://www.devopsengineers.com/) +- [SweetOps](https://slack.cloudposse.com/) +## Looking for more lists like that +- [Awesome Community](https://github.com/phpearth/awesome-community) + +## Contribute +Your contributions and suggestions are :heart: welcome. Ensure to read the [guidelines](https://github.com/filipelinhares/awesome-slack/blob/master/CONTRIBUTING.md) first. + +## License +[](https://creativecommons.org/publicdomain/zero/1.0/) diff --git a/docs/awesome/awesome-webaudio.md b/docs/awesome/awesome-webaudio.md index 8e18c781ae..83c79e01c4 100644 --- a/docs/awesome/awesome-webaudio.md +++ b/docs/awesome/awesome-webaudio.md @@ -40,6 +40,7 @@ Please raise a [Pull-Request](https://github.com/notthetup/awesome-webaudio/pull - [p5.sound](https://p5js.org/reference/#/libraries/p5.sound) - An extension that adds Web Audio functionality to the creative coding library [p5.js](https://p5js.org/). - [@magenta/music](https://github.com/magenta/magenta-js/tree/master/music) - A JavaScript library to use machine learning models and generate music in the browser, by having some neat abstractions over the Webaudio API. - [soundfont-player](https://www.npmjs.com/package/soundfont-player) - A soundfont loader/player to play MIDI sounds using WebAudio API. +- [html-midi-player](https://github.com/cifkao/html-midi-player) - HTML elements for easy MIDI playback and visualization, without the need to write any custom JS code, but scriptable and stylable as needed. ### Utilities diff --git a/docs/awesome/awesome-zsh-plugins.md b/docs/awesome/awesome-zsh-plugins.md index 605cd53370..2a6b90ec0e 100644 --- a/docs/awesome/awesome-zsh-plugins.md +++ b/docs/awesome/awesome-zsh-plugins.md @@ -394,7 +394,6 @@ Here are a few good sources for Nerd Fonts and Powerline-compatible fonts: - [Outrageously Useful Tips To Master Your Z Shell](http://reasoniamhere.com/2014/01/11/outrageously-useful-tips-to-master-your-z-shell/) - covers some of the features that ZSH has that Bash doesn't, and using oh-my-zsh. - [rs-example](https://github.com/al-jshen/zshplug-rs-example) - An example plugin showing how a Rust program can listen to and process commands from ZSH. - [Why ZSH is Cooler than your Shell](https://www.slideshare.net/jaguardesignstudio/why-zsh-is-cooler-than-your-shell-16194692) - slideshare presentation. -- [xVanjaZ](https://github.com/xVanjaZ/xVanjaZ-ZSH-Theme) - wrote a quick setup document for oh-my-zsh beginners showing how to use the [spaceship](https://github.com/denysdovhan/spaceship-prompt.git) prompt, syntax highlighting at the prompt, autosuggestion and a custom iTerm 2 theme. - [zephyr](https://github.com/mattmc3/zephyr) - Zephyr uses built-in Zsh features to set up better default options, completions, keybindings, history, and much more. - [ZSH for Humans](https://github.com/romkatv/zsh4humans) - A turnkey configuration for ZSH that aims to work really well out of the box. It combines a curated set of ZSH plugins into a coherent whole that feels like a finished product rather than a DIY starter kit. - [ZSH Pony](https://github.com/mika/zsh-pony) - Covers customizing ZSH without a framework. @@ -805,6 +804,7 @@ Here are a few good sources for Nerd Fonts and Powerline-compatible fonts: - [hanami](https://github.com/davydovanton/hanami-zsh) - ZSH plugin for [hanami](http://hanamirb.org) projects. - [hangul](https://github.com/gomjellie/zsh-hangul) - Auto correct hangul(한글, korean) to English when it was supposed to be typed in English. 영어를 타이핑 해야되는데 한글로 타이핑된경우 자동으로 수정합니다. - [hbt](https://github.com/lzambarda/hbt) - Heuristic ZSH suggestion system based on past command usage. +- [hebzsh](https://github.com/admons/hebzsh) - If a command is not found as typed in Hebrew, translates the command as if it was typed on a keyboard with a US English layout and tries again. - [hints](https://github.com/joepvd/zsh-hints) - Display glob and parameter flags and other non completable info right under your editing buffer. - [hipchat](https://github.com/robertzk/hipchat.zsh) - Send hipchat messages from the shell. - [hist](https://github.com/marlonrichert/zsh-hist) - Edit your history in ZSH, without ever leaving the command line. @@ -825,7 +825,7 @@ Here are a few good sources for Nerd Fonts and Powerline-compatible fonts: - [hub-ci-zsh-plugin](https://github.com/raymondjcox/hub-ci-zsh-plugin) - A simple plugin for adding `hub` ci-status to your ZSH theme. - [hub](https://github.com/soraliu/zsh-hub) - ZSH plugin for forking model. - [igit](https://github.com/ytakahashi/igit) - Interactive `git` commands using [fzf](https://github.com/junegunn/fzf). -- [incsearch](https://github.com/aoyama-val/zsh-incsearch) - Friendlier `vim` mode for ZSH. +- [incsearch](https://github.com/aoyama-val/zsh-incsearch) - Friendlier `vim` mode for ZSH. Moves cursor with incremental search within current line. - [ing](https://github.com/rummik/zsh-ing) - Streamlined `ping` output. - [instant-repl](https://github.com/jandamm/instant-repl.zsh) - Activate a REPL for any command in your current ZSH session. - [interactive-cd](https://github.com/changyuheng/zsh-interactive-cd) - Fish-like interactive tab completion for `cd`. diff --git a/docs/awesome/computer-science.md b/docs/awesome/computer-science.md index 99db4df146..900f415941 100644 --- a/docs/awesome/computer-science.md +++ b/docs/awesome/computer-science.md @@ -56,10 +56,10 @@ just remember that you can't purchase success! **Process**. Students can work through the curriculum alone or in groups, in order or out of order. - We recommend doing all courses in Core CS, only skipping a course when you are certain that you've already learned the material previously. -- For simplicity, we recommend working through courses (especially Core CS) in order from top to bottom, as they have already been [topologically sorted](https://en.wikipedia.org/wiki/Topological_sorting) by their prerequisites. -- Courses in Advanced CS are electives. Choose one subject (e.g. Advanced programming) you want to become an expert in and take all the courses under that heading. You can also create your own custom subject, but we recommend getting validation from the community on the subject you choose. +- For simplicity, we recommend working through courses (especially Core CS) in order from top to bottom. Some students choose to study multiple courses at a time in order to vary the material they are working on is a day/week. A popular option is to take the math courses in parallel with the introductory courses. Course prerequisites are listed to help you determine if you are prepared for a given course. +- Courses in Advanced CS are electives. Choose one subject (e.g. Advanced programming) you want to become an expert in and take all the courses under that heading. You can also create your own custom subject; the discord community may provide feedback on your planned subject. -*Do NOT disrespect the code of conduct* that you signed in the beginning of each course! +*Respect the code of conduct* that you signed in the beginning of each course! **[How to contribute](https://github.com/ossu/computer-science/blob/master/CONTRIBUTING.md)** @@ -270,7 +270,7 @@ Courses | Duration | Effort | Prerequisites | Discussion [Databases: Relational Databases and SQL](https://www.edx.org/course/databases-5-sql)| 2 weeks | 10 hours/week | core programming | [chat](https://discord.gg/P8SPPyF) [Databases: Semistructured Data](https://www.edx.org/course/semistructured-data)| 2 weeks | 10 hours/week | core programming | [chat](https://discord.gg/duCJ3GN) [Machine Learning](https://www.coursera.org/specializations/machine-learning-introduction)| 11 weeks | 9 hours/week | Basic coding | [chat](https://discord.gg/NcXHDjy) -[Computer Graphics](https://www.edx.org/course/computer-graphics-2)| 6 weeks | 12 hours/week | C++ or Java, linear algebra | [chat](https://discord.gg/68WqMNV) +[Computer Graphics](https://www.edx.org/course/computer-graphics-2) ([alt](https://cseweb.ucsd.edu/~viscomp/classes/cse167/wi22/schedule.html))| 6 weeks | 12 hours/week | C++ or Java, linear algebra | [chat](https://discord.gg/68WqMNV) [Software Engineering: Introduction](https://www.edx.org/course/software-engineering-introduction) | 6 weeks | 8-10 hours/week | Core Programming, and a [sizable project](https://github.com/ossu/computer-science/blob/master/FAQ.md#why-require-experience-with-a-sizable-project-before-the-Software-Engineering-courses) | [chat](https://discord.gg/5Qtcwtz) ### Core ethics diff --git a/docs/awesome/github-cheat-sheet.md b/docs/awesome/github-cheat-sheet.md index 7d4413efe5..3f8203ae68 100644 --- a/docs/awesome/github-cheat-sheet.md +++ b/docs/awesome/github-cheat-sheet.md @@ -1,36 +1,36 @@ ## GitHub Cheat Sheet [](https://github.com/sindresorhus/awesome) - Git 和 GitHub 的隐藏和不那么隐藏的很酷的功能的集合. 这个备忘单的灵感来自 [Zach Holman](https://github.com/holman)'s [Git and GitHub Secrets](http://confreaks.tv/videos/aloharuby2012-git-and-github-secrets) 在 2012 年 Aloha Ruby 大会上的演讲（[slides](https://speakerdeck.com/holman/git-and-github-secrets)） 和他 [More Git and GitHub Secrets](https://vimeo.com/72955426) 在 WDCNZ 2013 演讲 ([slides](https://speakerdeck.com/holman/more-git-and-github-secrets)). +A collection of cool hidden and not so hidden features of Git and GitHub. This cheat sheet was inspired by [Zach Holman](https://github.com/holman)'s [Git and GitHub Secrets](http://confreaks.tv/videos/aloharuby2012-git-and-github-secrets) talk at Aloha Ruby Conference 2012 ([slides](https://speakerdeck.com/holman/git-and-github-secrets)) and his [More Git and GitHub Secrets](https://vimeo.com/72955426) talk at WDCNZ 2013 ([slides](https://speakerdeck.com/holman/more-git-and-github-secrets)). *Shortlink: [`http://git.io/sheet`](http://git.io/sheet)* -*阅读其他语言版本： [English](https://github.com/tiimgreen/github-cheat-sheet/blob/master/README.md), [한국어](https://github.com/tiimgreen/github-cheat-sheet/blob/master/README.ko.md), [日本語](https://github.com/tiimgreen/github-cheat-sheet/blob/master/README.ja.md), [简体中文](https://github.com/tiimgreen/github-cheat-sheet/blob/master/README.zh-cn.md), [正體中文](https://github.com/tiimgreen/github-cheat-sheet/blob/master/README.zh-tw.md).* +*Read this in other languages: [English](https://github.com/tiimgreen/github-cheat-sheet/blob/master/README.md), [한국어](https://github.com/tiimgreen/github-cheat-sheet/blob/master/README.ko.md), [日本語](https://github.com/tiimgreen/github-cheat-sheet/blob/master/README.ja.md), [简体中文](https://github.com/tiimgreen/github-cheat-sheet/blob/master/README.zh-cn.md), [正體中文](https://github.com/tiimgreen/github-cheat-sheet/blob/master/README.zh-tw.md).* -GitHub 备忘单由 [Drawpoint: create interactive maps and images for your website with no coding](https://www.drawpoint.io) +GitHub Cheat Sheet is sponsored by [Snapshot: create interactive professional-quality product photos using AI](https://www.snapshotapp.io/) ## GitHub ### Ignore Whitespace -将 `?w=1` 添加到任何 diff URL 将仅删除空白中的任何更改，使您只能看到已更改的代码. +Adding `?w=1` to any diff URL will remove any changes only in whitespace, enabling you to see only the code that has changed.  [*Read more about GitHub secrets.*](https://github.com/blog/967-github-secrets) ### Adjust Tab Space -将 `?ts=4` 添加到 diff 或文件 URL 会将制表符显示为 4 个空格而不是默认的 8 个空格.可以根据您的喜好调整 `ts` 之后的数字. 这不适用于要点或原始文件视图，但 [Chrome extension](https://chrome.google.com/webstore/detail/tab-size-on-github/ofjbgncegkdemndciafljngjbdpfmbkn) 可以自动化这个. +Adding `?ts=4` to a diff or file URL will display tab characters as 4 spaces wide instead of the default 8. The number after `ts` can be adjusted to suit your preference. This does not work on Gists, or raw file views, but a [Chrome extension](https://chrome.google.com/webstore/detail/tab-size-on-github/ofjbgncegkdemndciafljngjbdpfmbkn) can automate this. -这是添加 `?ts=4` 之前的 Go 源文件： +Here is a Go source file before adding `?ts=4`:  -...这是在添加 `?ts=4` 之后： +...and this is after adding `?ts=4`:  ### Commit History by Author -要查看作者对 repo 的所有提交，请将 `?author={user}` 添加到 URL. +To view all commits on a repo by author add `?author={user}` to the URL. ``` https://github.com/rails/rails/commits/master?author=dhh @@ -41,7 +41,7 @@ https://github.com/rails/rails/commits/master?author=dhh [*Read more about the differences between commits views.*](https://help.github.com/articles/differences-between-commit-views/) ### Cloning a Repository -克隆存储库时，可以将 `.git` 放在末尾. +When cloning a repository the `.git` can be left off the end. ```bash $ git clone https://github.com/tiimgreen/github-cheat-sheet @@ -52,28 +52,28 @@ $ git clone https://github.com/tiimgreen/github-cheat-sheet ### Branch #### Compare all Branches to Another Branch -如果你去回购 [Branches](https://github.com/tiimgreen/github-cheat-sheet/branches) 页面，在“提交”按钮旁边： +If you go to the repo's [Branches](https://github.com/tiimgreen/github-cheat-sheet/branches) page, next to the Commits button: ``` https://github.com/{user}/{repo}/branches ``` -...您会看到未合并到主分支的所有分支的列表. +... you would see a list of all branches which are not merged into the main branch. -从这里您可以访问比较页面或单击按钮删除分支. +From here you can access the compare page or delete a branch with a click of a button.  #### Comparing Branches -要使用 GitHub 比较分支，请将 URL 更改为如下所示： +To use GitHub to compare branches, change the URL to look like this: ``` https://github.com/{user}/{repo}/compare/{range} ``` -其中`{range} = master...4-1-stable` +where `{range} = master...4-1-stable` -例如： +For example: ``` https://github.com/rails/rails/compare/master...4-1-stable @@ -81,18 +81,18 @@ https://github.com/rails/rails/compare/master...4-1-stable  -`{range}` 可以更改为： +`{range}` can be changed to things like: ``` https://github.com/rails/rails/compare/master@{1.day.ago}...master https://github.com/rails/rails/compare/master@{2014-10-04}...master ``` -*这里，日期的格式是`YYYY-MM-DD`* +*Here, dates are in the format `YYYY-MM-DD`*  -分支也可以在 `diff` 和 `patch` 视图中进行比较： +Branches can also be compared in `diff` and `patch` views: ``` https://github.com/rails/rails/compare/master...4-1-stable.diff @@ -102,13 +102,13 @@ https://github.com/rails/rails/compare/master...4-1-stable.patch [*Read more about comparing commits across time.*](https://help.github.com/articles/comparing-commits-across-time/) #### Compare Branches across Forked Repositories -要使用 GitHub 比较分支存储库中的分支，请将 URL 更改为如下所示： +To use GitHub to compare branches across forked repositories, change the URL to look like this: ``` https://github.com/{user}/{repo}/compare/{foreign-user}:{branch}...{own-branch} ``` -例如： +For example: ``` https://github.com/rails/rails/compare/byroot:master...master @@ -117,61 +117,61 @@ https://github.com/rails/rails/compare/byroot:master...master  ### Gists -[Gists](https://gist.github.com/) 是一种无需创建完全成熟的存储库即可使用少量代码的简单方法. +[Gists](https://gist.github.com/) are an easy way to work with small bits of code without creating a fully fledged repository.  -将 .pibb 添加到任何 Gist URL 的末尾（[like this](https://gist.github.com/tiimgreen/10545817.pibb)) 以获得适合嵌入任何其他站点的 *HTML-only* 版本. +Add `.pibb` to the end of any Gist URL ([like this](https://gist.github.com/tiimgreen/10545817.pibb)) in order to get the *HTML-only* version suitable for embedding in any other site. -Gists 可以被视为一个存储库，因此它们可以像其他任何东西一样被克隆： +Gists can be treated as a repository so they can be cloned like any other: ```bash -$ git 克隆 https://gist.github.com/tiimgreen/10545817 +$ git clone https://gist.github.com/tiimgreen/10545817 ```  -这意味着您还可以修改和推送更新到 Gists： +This means you also can modify and push updates to Gists: ```bash -$ git 提交 -$ git 推送 +$ git commit +$ git push Username for 'https://gist.github.com': -“https://tiimgreen@gist.github.com”的密码： +Password for 'https://tiimgreen@gist.github.com': ``` -但是，Gists 不支持目录. 所有文件都需要添加到存储库根目录. +However, Gists do not support directories. All files need to be added to the repository root. [*Read more about creating Gists.*](https://help.github.com/articles/creating-gists/) ### Git.io -[Git.io](http://git.io) 是 GitHub 的简单 URL 缩短器. +[Git.io](http://git.io) is a simple URL shortener for GitHub.  -您还可以使用 Curl 通过纯 HTTP 使用它： +You can also use it via pure HTTP using Curl: ```bash -$ curl -i http://git.io -F "url=https://github.com/..." -HTTP/1.1 201 已创建 -位置：http://git.io/abc123 +$ curl -i http://git.io -F "url=https://github.com/..." +HTTP/1.1 201 Created +Location: http://git.io/abc123 $ curl -i http://git.io/abc123 -HTTP/1.1 302 找到 -位置：https://github.com/... +HTTP/1.1 302 Found +Location: https://github.com/... ``` [*Read more about Git.io.*](https://github.com/blog/985-git-io-github-url-shortener) ### Keyboard Shortcuts -在存储库页面上时，键盘快捷键可让您轻松导航. +When on a repository page, keyboard shortcuts allow you to navigate easily. - - 按 `t` 将调出一个文件资源管理器. - - 按 `w` 将调出分支选择器. - - 按 `s` 将聚焦当前存储库的搜索字段. 按 ↓ 选择“所有 GitHub”选项更改字段以搜索所有 GitHub. - - 按 `l` 将编辑现有问题的标签. - - 在查看文件时按 `y` **（例如，`https://github.com/tiimgreen/github-cheat-sheet/blob/master/README.md`）会将您的 URL 更改为，实际上冻结了您正在查看的页面. 如果此代码发生更改，您仍然可以看到您在当前时间看到的内容. + - Pressing `t` will bring up a file explorer. + - Pressing `w` will bring up the branch selector. + - Pressing `s` will focus the search field for the current repository. Pressing ↓ to select the “All GitHub” option changes the field to search all of GitHub. + - Pressing `l` will edit labels on existing Issues. + - Pressing `y` **when looking at a file** (e.g., `https://github.com/tiimgreen/github-cheat-sheet/blob/master/README.md`) will change your URL to one which, in effect, freezes the page you are looking at. If this code changes, you will still be able to see what you saw at that current time. -要查看当前页面的所有快捷方式，请按 `?`： +To see all of the shortcuts for the current page press `?`:  @@ -189,13 +189,13 @@ https://github.com/rails/rails/blob/master/activemodel/lib/active_model.rb#L53-L  ### Closing Issues via Commit Messages -如果一个特定的提交修复了一个问题，任何关键字`fix/fixes/fixed`、`close/closes/closed` 或 `resolve/resolves/resolved`，后跟问题编号，将在提交后关闭问题到存储库的默认分支. +If a particular commit fixes an issue, any of the keywords `fix/fixes/fixed`, `close/closes/closed` or `resolve/resolves/resolved`, followed by the issue number, will close the issue once it is committed to the repository's default branch. ```bash $ git commit -m "Fix screwup, fixes #12" ``` -这将关闭问题并引用关闭提交. +This closes the issue and references the closing commit.  @@ -209,11 +209,11 @@ To link to an issue in another repository, `{user}/{repo}#ISSUE_NUMBER`, e.g., `  ### Locking Conversations -拉取请求和问题现在可以由回购的所有者或合作者锁定. +Pull Requests and Issues can now be locked by owners or collaborators of the repo.  -这意味着不是项目协作者的用户将无法再发表评论. +This means that users who are not collaborators on the project will no longer be able to comment.  @@ -221,7 +221,7 @@ To link to an issue in another repository, `{user}/{repo}#ISSUE_NUMBER`, e.g., ` ### CI Status on Pull Requests -如果设置正确，每次收到 Pull Request 时， [Travis CI](https://travis-ci.org/) 将像每次进行新提交时一样构建该 Pull Request. 阅读更多关于如何 [get started with Travis CI](http://docs.travis-ci.com/user/getting-started/). +If set up correctly, every time you receive a Pull Request, [Travis CI](https://travis-ci.org/) will build that Pull Request just like it would every time you make a new commit. Read more about how to [get started with Travis CI](http://docs.travis-ci.com/user/getting-started/). [](https://github.com/octokit/octokit.rb/pull/452) @@ -229,80 +229,80 @@ To link to an issue in another repository, `{user}/{repo}#ISSUE_NUMBER`, e.g., ` ### Filters -问题和拉取请求都允许在用户界面中进行过滤. +Both issues and pull requests allow filtering in the user interface. -对于 Rails 存储库：https://github.com/rails/rails/issues，通过选择标签“activerecord”构建以下过滤器： +For the Rails repo: https://github.com/rails/rails/issues, the following filter is built by selecting the label "activerecord": `is:issue label:activerecord` -但是，您还可以找到所有未标记为 activerecord 的问题： +But, you can also find all issues that are NOT labeled activerecord: -`is:issue-label:activerecord` +`is:issue -label:activerecord` -此外，这也适用于拉取请求： +Additionally, this also works for pull requests: -`is:pr-label:activerecord` +`is:pr -label:activerecord` -Github 有用于显示打开或关闭的问题和拉取请求的选项卡，但你 -还可以看到合并的拉取请求. 只需将以下内容放入过滤器中： +Github has tabs for displaying open or closed issues and pull requests but you +can also see merged pull requests. Just put the following in the filter: `is:merged` [*Read more about searching issues.*](https://help.github.com/articles/searching-issues/) -最后，github 现在允许您按 Status API 的状态进行过滤. +Finally, github now allows you to filter by the Status API's status. -只有成功状态的拉取请求： +Pull requests with only successful statuses: `status:success` [*Read more about searching on the Status API.*](https://github.com/blog/2014-filter-pull-requests-by-status) ### Syntax Highlighting in Markdown Files -例如，要在 Markdown 文件中语法高亮显示 Ruby 代码，请编写： +For example, to syntax highlight Ruby code in your Markdown files write: - ```红宝石 - 需要'tabbit' - table = Tabbit.new('姓名', '邮箱') - table.add_row('蒂姆格林', 'tiimgreen@gmail.com') - 将 table.to_s + ```ruby + require 'tabbit' + table = Tabbit.new('Name', 'Email') + table.add_row('Tim Green', 'tiimgreen@gmail.com') + puts table.to_s ``` -这将产生： +This will produce: ```ruby -需要'tabbit' -table = Tabbit.new('姓名', '邮箱') -table.add_row('蒂姆格林', 'tiimgreen@gmail.com') -将 table.to_s +require 'tabbit' +table = Tabbit.new('Name', 'Email') +table.add_row('Tim Green', 'tiimgreen@gmail.com') +puts table.to_s ``` -GitHub 使用 [Linguist](https://github.com/github/linguist) 执行语言检测和语法突出显示. 您可以通过仔细阅读 [languages YAML file](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). +GitHub uses [Linguist](https://github.com/github/linguist) to perform language detection and syntax highlighting. You can find out which keywords are valid by perusing the [languages YAML file](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). [*Read more about GitHub Flavored Markdown.*](https://help.github.com/articles/github-flavored-markdown/) ### Emojis -可以使用 `:name_of_emoji:` 将表情符号添加到拉取请求、问题、提交消息、存储库描述等. +Emojis can be added to Pull Requests, Issues, commit messages, repository descriptions, etc. using `:name_of_emoji:`. -GitHub 上支持的表情符号的完整列表可以在以下位置找到 [emoji-cheat-sheet.com](http://www.emoji-cheat-sheet.com/) 或者 [scotch-io/All-Github-Emoji-Icons](https://github.com/scotch-io/All-Github-Emoji-Icons). -一个方便的表情符号搜索引擎可以在 [emoji.muan.co](http://emoji.muan.co/). +The full list of supported Emojis on GitHub can be found at [emoji-cheat-sheet.com](http://www.emoji-cheat-sheet.com/) or [scotch-io/All-Github-Emoji-Icons](https://github.com/scotch-io/All-Github-Emoji-Icons). +A handy emoji search engine can be found at [emoji.muan.co](http://emoji.muan.co/). -GitHub 上使用最多的 5 个表情符号是： +The top 5 used Emojis on GitHub are: -1.`：船：` -2.`：火花：` +1. `:shipit:` +2. `:sparkles:` 3. `:-1:` 4. `:+1:` -5.`：拍手：` +5. `:clap:` ### Images/GIFs -图片和 GIF 可以添加到评论、README 等： +Images and GIFs can be added to comments, READMEs etc.: ```  ``` -来自 repo 的原始图像可以通过直接调用它们来使用： +Raw images from the repo can be used by calling them directly.: ```  @@ -310,21 +310,21 @@ GitHub 上使用最多的 5 个表情符号是：  -所有图像都缓存在 GitHub 上，因此如果您的主机出现故障，图像将仍然可用. +All images are cached on GitHub, so if your host goes down, the image will remain available. #### Embedding Images in GitHub Wiki -有多种方法可以在 Wiki 页面中嵌入图像. 有标准的 Markdown 语法（如上所示）. 但是还有一种语法允许指定图像的高度或宽度： +There are multiple ways of embedding images in Wiki pages. There's the standard Markdown syntax (shown above). But there's also a syntax that allows things like specifying the height or width of the image: ```markdown - [[ http://www.sheawong.com/wp-content/uploads/2013/08/keephatin.gif | 高度 = 100px ]] +[[ http://www.sheawong.com/wp-content/uploads/2013/08/keephatin.gif | height = 100px ]] ``` -哪个产生： +Which produces:  ### Quick Quoting -当在评论线程中并且您想引用某人之前说过的话时，突出显示文本并按 `r`，这将以块引用格式将其复制到您的文本框中. +When on a comment thread and you want to quote something someone previously said, highlight the text and press `r`, this will copy it into your text box in the block-quote format.  @@ -332,20 +332,20 @@ GitHub 上使用最多的 5 个表情符号是： ### Pasting Clipboard Image to Comments -_（仅适用于 Chrome 浏览器）_ +_(Works on Chrome browsers only)_ -截图并添加到剪贴板后（mac：`cmd-ctrl-shift-4`），您只需将图像粘贴（`cmd-v / ctrl-v`）到评论部分，它就会自动-上传到github. +After taking a screenshot and adding it to the clipboard (mac: `cmd-ctrl-shift-4`), you can simply paste (`cmd-v / ctrl-v`) the image into the comment section and it will be auto-uploaded to github.  [*Read more about issue attachments.*](https://help.github.com/articles/issue-attachments/) ### Quick Licensing -创建存储库时，GitHub 为您提供了添加预制许可证的选项： +When creating a repository, GitHub gives you the option of adding in a pre-made license:  -您还可以通过 Web 界面创建新文件，将它们添加到现有存储库中. 当输入名称 `LICENSE` 时，您将获得使用模板的选项： +You can also add them to existing repositories by creating a new file through the web interface. When the name `LICENSE` is typed in you will get an option to use a template:  @@ -354,52 +354,52 @@ Also works for `.gitignore`. [*Read more about open source licensing.*](https://help.github.com/articles/open-source-licensing/) ### Task Lists -在 Issues 和 Pull requests 中，可以使用以下语法添加复选框（注意空格）： +In Issues and Pull requests check boxes can be added with the following syntax (notice the space): ``` -- []很棒 -- [ ] 准备晚餐 - - [ ] 研究配方 - - [ ] 购买原料 - - [] 烹饪食谱 -- [ ] 睡觉 +- [ ] Be awesome +- [ ] Prepare dinner + - [ ] Research recipe + - [ ] Buy ingredients + - [ ] Cook recipe +- [ ] Sleep ```  -单击它们时，它们将在纯 Markdown 中更新： +When they are clicked, they will be updated in the pure Markdown: ``` -- [x] 很棒 -- [ ] 准备晚餐 - - [x] 研究配方 - - [x] 购买原料 - - [] 烹饪食谱 -- [ ] 睡觉 +- [x] Be awesome +- [ ] Prepare dinner + - [x] Research recipe + - [x] Buy ingredients + - [ ] Cook recipe +- [ ] Sleep ``` [*Read more about task lists.*](https://help.github.com/articles/writing-on-github/#task-lists) #### Task Lists in Markdown Documents -在完整的 Markdown 文档中，**只读**清单现在可以使用以下语法添加： +In full Markdown documents **read-only** checklists can now be added using the following syntax: ``` -- [ ] 汞 -- [x] 金星 -- [x] 地球 - - [x] 月亮 -- [x] 火星 - - [ ] 火卫二 - - [ ] 火卫一 +- [ ] Mercury +- [x] Venus +- [x] Earth + - [x] Moon +- [x] Mars + - [ ] Deimos + - [ ] Phobos ``` -- [ ] 汞 -- [x] 金星 -- [x] 地球 - - [x] 月亮 -- [x] 火星 - - [ ] 火卫二 - - [ ] 火卫一 +- [ ] Mercury +- [x] Venus +- [x] Earth + - [x] Moon +- [x] Mars + - [ ] Deimos + - [ ] Phobos [*Read more about task lists in markdown documents.*](https://github.com/blog/1825-task-lists-in-all-markdown-documents) @@ -410,26 +410,26 @@ Relative links are recommended in your Markdown files when linking to internal c [Link to a file](https://github.com/tiimgreen/github-cheat-sheet/blob/master/docs/readme) ``` -绝对链接必须在 URL 更改时更新（例如，存储库重命名、用户名更改、项目分叉）. 使用相关链接可以使您的文档轻松独立. +Absolute links have to be updated whenever the URL changes (e.g., repository renamed, username changed, project forked). Using relative links makes your documentation easily stand on its own. [*Read more about relative links.*](https://help.github.com/articles/relative-links-in-readmes/) ### Metadata and Plugin Support for GitHub Pages -在 Jekyll 页面和帖子中，存储库信息在 `site.github` 命名空间内可用，并且可以显示，例如，使用 `{{ site.github.project_title }}`. +Within Jekyll pages and posts, repository information is available within the `site.github` namespace, and can be displayed, for example, using `{{ site.github.project_title }}`. -Jemoji 和 jekyll-mentions 插件启用 [emoji](#emojis) 和 [@mentions](https://github.com/blog/821) in your Jekyll posts 和 pages to work just like you'd expect when interacting with a repository on GitHub.com. +The Jemoji and jekyll-mentions plugins enable [emoji](#emojis) and [@mentions](https://github.com/blog/821) in your Jekyll posts and pages to work just like you'd expect when interacting with a repository on GitHub.com. [*Read more about repository metadata and plugin support for GitHub Pages.*](https://github.com/blog/1797-repository-metadata-and-plugin-support-for-github-pages) ### Viewing YAML Metadata in your Documents -许多博客网站，例如 [Jekyll](http://jekyllrb.com/) 和 [GitHub Pages](https://pages.github.com) ，取决于帖子开头的一些 YAML 格式的元数据. GitHub 会将此元数据呈现为水平表格，以便于阅读 +Many blogging websites, like [Jekyll](http://jekyllrb.com/) with [GitHub Pages](https://pages.github.com), depend on some YAML-formatted metadata at the beginning of your post. GitHub will render this metadata as a horizontal table, for easier reading  [*Read more about viewing YAML metadata in your documents.*](https://github.com/blog/1647-viewing-yaml-metadata-in-your-documents) ### Rendering Tabular Data -GitHub 支持以“.csv”（逗号分隔）和“.tsv”（制表符分隔）文件的形式呈现表格数据. +GitHub supports rendering tabular data in the form of `.csv` (comma-separated) and `.tsv` (tab-separated) files.  @@ -437,16 +437,16 @@ GitHub 支持以“.csv”（逗号分隔）和“.tsv”（制表符分隔） ### Rendering PDF -GitHub 支持渲染 PDF： +GitHub supports rendering PDF:  [*Read more about rendering PDF.*](https://github.com/blog/1974-pdf-viewing) ### Revert a Pull Request -合并拉取请求后，您可能会发现它没有任何帮助，或者合并拉取请求是一个错误的决定. +After a pull request is merged, you may find it does not help anything or it was a bad decision to merge the pull request. -您可以通过单击拉取请求页面中提交右侧的 **Revert** 按钮来还原它，以创建一个拉取请求，其中包含对此特定拉取请求的还原更改. +You can revert it by clicking the **Revert** button on the right side of a commit in the pull request page to create a pull request with reverted changes to this specific pull request.  @@ -454,33 +454,33 @@ GitHub 支持渲染 PDF： ### Diffs #### Rendered Prose Diffs -提交和拉取请求，包括 GitHub 支持的渲染文档（例如 Markdown）、特性 *source* 和 *rendered* 视图. +Commits and pull requests, including rendered documents supported by GitHub (e.g., Markdown), feature *source* and *rendered* views.  -单击“呈现”按钮以查看更改将出现在呈现的文档中. 当您添加、删除和编辑文本时，呈现的散文视图很方便： +Click the "rendered" button to see the changes as they'll appear in the rendered document. Rendered prose view is handy when you're adding, removing, and editing text:  [*Read more about rendered prose diffs.*](https://github.com/blog/1784-rendered-prose-diffs) #### Diffable Maps -每当您在 GitHub 上查看包含地理数据的提交或拉取请求时，GitHub 都会呈现更改内容的可视化表示. +Any time you view a commit or pull request on GitHub that includes geodata, GitHub will render a visual representation of what was changed. [](https://github.com/benbalter/congressional-districts/commit/2233c76ca5bb059582d796f053775d8859198ec5) [*Read more about diffable maps.*](https://github.com/blog/1772-diffable-more-customizable-maps) #### Expanding Context in Diffs -使用 diff 栏中的 *unfold* 按钮，您可以通过单击显示额外的上下文行. 您可以一直单击 *unfold* 直到显示整个文件，并且该功能在 GitHub 呈现差异的任何地方都可用. +Using the *unfold* button in the gutter of a diff, you can reveal additional lines of context with a click. You can keep clicking *unfold* until you've revealed the whole file, and the feature is available anywhere GitHub renders diffs.  [*Read more about expanding context in diffs.*](https://github.com/blog/1705-expanding-context-in-diffs) #### Diff or Patch of Pull Request -您可以通过添加 .diff 或 .patch 来获取 Pull Request 的差异 -扩展到 URL 的末尾. 例如： +You can get the diff of a Pull Request by adding a `.diff` or `.patch` +extension to the end of the URL. For example: ``` https://github.com/tiimgreen/github-cheat-sheet/pull/15 @@ -488,51 +488,51 @@ https://github.com/tiimgreen/github-cheat-sheet/pull/15.diff https://github.com/tiimgreen/github-cheat-sheet/pull/15.patch ``` -`.diff` 扩展名将以纯文本形式为您提供： +The `.diff` extension would give you this in plain text: ``` diff --git a/README.md b/README.md -指数 88fcf69..8614873 100644 ---- 一个/README.md -+++ b/自述文件.md - @@ -28,6 +28,7 @@ Git 和 GitHub 的所有隐藏和非隐藏功能. 这个备忘单是我 -@@ -381,6 +382,19 @@ 当它们被点击时，它们将在纯 Markdown 中更新： - - [ ] 睡觉 +index 88fcf69..8614873 100644 +--- a/README.md ++++ b/README.md +@@ -28,6 +28,7 @@ All the hidden and not hidden features of Git and GitHub. This cheat sheet was i +@@ -381,6 +382,19 @@ When they are clicked, they will be updated in the pure Markdown: + - [ ] Sleep (...) ``` #### Rendering and diffing images - GitHub 可以显示几种常见的图像格式，包括 PNG、JPG、GIF 和 PSD. 此外，还有几种方法可以比较这些图像格式版本之间的差异. +GitHub can display several common image formats, including PNG, JPG, GIF, and PSD. In addition, there are several ways to compare differences between versions of those image formats. [](https://github.com/blog/1845-psd-viewing-diffing) [*Read more about rendering and diffing images.*](https://help.github.com/articles/rendering-and-diffing-images/) ### Hub -[Hub](https://github.com/github/hub) 是一个命令行 Git 包装器，它为您提供额外的功能和命令，使您可以更轻松地使用 GitHub. +[Hub](https://github.com/github/hub) is a command line Git wrapper that gives you extra features and commands that make working with GitHub easier. -这使您可以执行以下操作： +This allows you to do things like: ```bash -$ hub 克隆 tiimgreen/toc +$ hub clone tiimgreen/toc ``` [*Check out some more cool commands Hub has to offer.*](https://github.com/github/hub#commands) ### Contribution Guidelines -GitHub 支持添加 3 个不同的文件，以帮助用户为您的项目做出贡献. -这些文件可以放在存储库的根目录中，也可以放在根目录下的 .github 目录中. +GitHub supports adding 3 different files which help users contribute to your project. +These files can either be placed in the root of your repository or a `.github` directory under the root. #### CONTRIBUTING File -将 `CONTRIBUTING` 或 `CONTRIBUTING.md` 文件添加到您的存储库的根目录或 `.github` 目录将在贡献者创建问题或打开合并请求时添加指向您的文件的链接. +Adding a `CONTRIBUTING` or `CONTRIBUTING.md` file to either the root of your repository or a `.github` directory will add a link to your file when a contributor creates an Issue or opens a Pull Request.  [*Read more about contributing guidelines.*](https://github.com/blog/1184-contributing-guidelines) #### ISSUE_TEMPLATE file -您可以为项目中打开的所有新问题定义一个模板. 当用户创建新问题时，此文件的内容将预填充新问题框. 将 `ISSUE_TEMPLATE` 或 `ISSUE_TEMPLATE.md` 文件添加到存储库的根目录或 `.github` 目录. +You can define a template for all new issues opened in your project. The content of this file will pre-populate the new issue box when users create new issues. Add an `ISSUE_TEMPLATE` or `ISSUE_TEMPLATE.md` file to either the root of your repository or a `.github` directory. [*Read more about issue templates.*](https://github.com/blog/2111-issue-and-pull-request-templates) @@ -541,14 +541,14 @@ GitHub 支持添加 3 个不同的文件，以帮助用户为您的项目做出  #### PULL_REQUEST_TEMPLATE file -您可以为项目中打开的所有新拉取请求定义一个模板. 当用户创建拉取请求时，此文件的内容将预填充文本区域. 将 `PULL_REQUEST_TEMPLATE` 或 `PULL_REQUEST_TEMPLATE.md` 文件添加到存储库的根目录或 `.github` 目录. +You can define a template for all new pull requests opened in your project. The content of this file will pre-populate the text area when users create pull requests. Add a `PULL_REQUEST_TEMPLATE` or `PULL_REQUEST_TEMPLATE.md` file to either the root of your repository or a `.github` directory. [*Read more about pull request templates.*](https://github.com/blog/2111-issue-and-pull-request-templates) [Pull request template file generator](https://www.talater.com/open-source-templates/) ### Octicons -GitHubs 图标 (Octicons) 现已开源. +GitHubs icons (Octicons) have now been open sourced.  @@ -556,35 +556,35 @@ GitHubs 图标 (Octicons) 现已开源. ### GitHub Student Developer Pack -如果您是学生，您将有资格获得 GitHub 学生开发包. 这为您提供免费信用、免费试用和早期访问软件，这些软件将在您进行开发时提供帮助. +If you are a student you will be eligible for the GitHub Student Developer Pack. This gives you free credit, free trials and early access to software that will help you when developing.  [*Read more about GitHub's Student Developer Pack*](https://education.github.com/pack) ### GitHub Resources - | 标题 | 链接 | +| Title | Link | | ----- | ---- | - | GitHub 探索 | https://github.com/explore | - | GitHub 博客 | https://github.com/博客 | - | GitHub 帮助 | https://help.github.com/ | - | GitHub 培训 | https://training.github.com/ | - | GitHub 开发者 | https://developer.github.com/ | - | Github Education（免费微型账户和其他面向学生的东西）| https://education.github.com/ | - | GitHub 最佳实践 | [Best Practices List](https://www.datree.io/resources/github-best-practices) | +| GitHub Explore | https://github.com/explore | +| GitHub Blog | https://github.com/blog | +| GitHub Help | https://help.github.com/ | +| GitHub Training | https://training.github.com/ | +| GitHub Developer | https://developer.github.com/ | +| Github Education (Free Micro Account and other stuff for students) | https://education.github.com/ | +| GitHub Best Practices | [Best Practices List](https://www.datree.io/resources/github-best-practices) | #### GitHub Talks - | 标题 | 链接 | +| Title | Link | | ----- | ---- | - | GitHub 如何使用 GitHub 构建 GitHub | https://www.youtube.com/watch?v=qyz3jkOBbQY | - | GitHub 的 Scott Chacon 介绍 Git | https://www.youtube.com/watch?v=ZDR433b0HJY | - | GitHub 如何不再工作 | https://www.youtube.com/watch?v=gXD1ITW7iZI | - | Git 和 GitHub 的秘密 | https://www.youtube.com/watch?v=Foz9yvMkvlA | - | 更多 Git 和 GitHub 秘密 | https://www.youtube.com/watch?v=p50xsL-iVgU | +| How GitHub Uses GitHub to Build GitHub | https://www.youtube.com/watch?v=qyz3jkOBbQY | +| Introduction to Git with Scott Chacon of GitHub | https://www.youtube.com/watch?v=ZDR433b0HJY | +| How GitHub No Longer Works | https://www.youtube.com/watch?v=gXD1ITW7iZI | +| Git and GitHub Secrets | https://www.youtube.com/watch?v=Foz9yvMkvlA | +| More Git and GitHub Secrets | https://www.youtube.com/watch?v=p50xsL-iVgU | ### SSH keys -您可以通过访问以下网址获取纯文本格式的公共 ssh 密钥列表： +You can get a list of public ssh keys in plain text format by visiting: ``` https://github.com/{user}.keys @@ -596,7 +596,7 @@ e.g. [https://github.com/tiimgreen.keys](https://github.com/tiimgreen.keys) ### Profile Image -您可以通过访问以下网址获取用户的个人资料图片： +You can get a user's profile image by visiting: ``` https://github.com/{user}.png @@ -606,11 +606,11 @@ e.g. [https://github.com/tiimgreen.png](https://github.com/tiimgreen.png) ### Repository Templates -您可以在您的存储库上启用模板，这允许任何人复制目录结构和文件，允许他们立即使用这些文件（例如，用于教程或编写样板代码）. 这可以在您的存储库的设置中启用. +You can enable templating on your repository which allows anyone to copy the directory structure and files, allowing them to instantly use the files (e.g. for a tutorial or if writing boilerplate code). This can be enabled in the settings of your repository.  -更改为模板存储库将提供一个可以共享的新 URL 端点，并立即允许用户将您的存储库用作模板. 或者，他们可以转到您的存储库并单击“用作模板”按钮. +Changing to a template repository will give a new URL endpoint which can be shared and instantly allows users to use your repository as a template. Alternatively, they can go to your repository and click the 'Use as template' button.  @@ -618,43 +618,43 @@ e.g. [https://github.com/tiimgreen.png](https://github.com/tiimgreen.png) ## Git ### Remove All Deleted Files from the Working Tree -当您使用 `/bin/rm` 删除大量文件时，您可以使用以下命令将它们从工作树和索引中删除，从而无需单独删除每个文件： +When you delete a lot of files using `/bin/rm` you can use the following command to remove them from the working tree and from the index, eliminating the need to remove each one individually: ```bash $ git rm $(git ls-files -d) ``` -例如： +For example: ```bash -$ git 状态 -在分行主 -未暂存提交的更改： - 删除：一个 - 删除：c +$ git status +On branch master +Changes not staged for commit: + deleted: a + deleted: c $ git rm $(git ls-files -d) -rm 'a' -室'c' +rm 'a' +rm 'c' -$ git 状态 -在分行主 -要提交的更改： - 删除：一个 - 删除：c +$ git status +On branch master +Changes to be committed: + deleted: a + deleted: c ``` ### Previous Branch -要移动到 Git 中的上一个分支： +To move to the previous branch in Git: ```bash -$ 结帐 - +$ git checkout - ## Switched to branch 'master' -$ 结帐 - +$ git checkout - ## Switched to branch 'next' -$ 结帐 - +$ git checkout - ## Switched to branch 'master' ``` @@ -662,66 +662,66 @@ $ 结帐 - ### Stripspace -Git 条带空间： +Git Stripspace: -- 去除尾随空格 -- 折叠换行符 -- 在文件末尾添加换行符 +- Strips trailing whitespace +- Collapses newlines +- Adds newline to end of file -调用命令时必须传递一个文件，例如： +A file must be passed when calling the command, e.g.: ```bash -$ git stripspace < README.md +$ git stripspace < README.md ``` [*Read more about the Git `stripspace` command.*](http://git-scm.com/docs/git-stripspace) ### Checking out Pull Requests -拉取请求是 GitHub 存储库上的特殊分支，可以通过多种方式在本地检索： +Pull Requests are special branches on the GitHub repository which can be retrieved locally in several ways: -检索特定的 Pull Request 并将其临时存储在 `FETCH_HEAD` 中，以便快速进行 `diff`-ing 或 `merge`-ing： +Retrieve a specific Pull Request and store it temporarily in `FETCH_HEAD` for quickly `diff`-ing or `merge`-ing: ```bash $ git fetch origin refs/pull/[PR-Number]/head ``` -通过 refspec 获取所有 Pull Request 分支作为本地远程分支： +Acquire all Pull Request branches as local remote branches by refspec: ```bash -$ git fetch origin '+refs/pull/*/head:refs/remotes/origin/pr/*' +$ git fetch origin '+refs/pull/*/head:refs/remotes/origin/pr/*' ``` -或者通过在存储库的 `.git/config` 中添加这些相应的行来设置远程自动获取拉取请求： +Or setup the remote to fetch Pull Requests automatically by adding these corresponding lines in your repository's `.git/config`: ``` -[远程“起源”] +[remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = git@github.com:tiimgreen/github-cheat-sheet.git ``` ``` -[远程“起源”] +[remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = git@github.com:tiimgreen/github-cheat-sheet.git fetch = +refs/pull/*/head:refs/remotes/origin/pr/* ``` -对于基于 Fork 的 Pull Request 贡献，“checkout”代表 Pull Request 的远程分支并从中创建本地分支很有用： +For Fork-based Pull Request contributions, it's useful to `checkout` a remote branch representing the Pull Request and create a local branch from it: ```bash $ git checkout pr/42 pr-42 ``` -或者你应该在更多的存储库上工作，你可以在全局 git 配置中全局配置获取拉取请求. +Or should you work on more repositories, you can globally configure fetching pull requests in the global git config instead. ```bash -git config --global --add remote.origin.fetch "+refs/pull/*/head:refs/remotes/origin/pr/*" +git config --global --add remote.origin.fetch "+refs/pull/*/head:refs/remotes/origin/pr/*" ``` -这样，您可以在所有存储库中使用以下简短命令： +This way, you can use the following short commands in all your repositories: ```bash -git 获取来源 +git fetch origin ``` ```bash @@ -731,37 +731,37 @@ git checkout pr/42 [*Read more about checking out pull requests locally.*](https://help.github.com/articles/checking-out-pull-requests-locally/) ### Empty Commits -通过添加 --allow-empty 可以在不更改代码的情况下推送提交： +Commits can be pushed with no code changes by adding `--allow-empty`: ```bash -$ git commit -m "大屁股提交" --allow-empty +$ git commit -m "Big-ass commit" --allow-empty ``` -这方面的一些用例（有意义）包括： +Some use-cases for this (that make sense), include: - - 注释大量新工作或新功能的开始. - - 当您对与代码无关的项目进行更改时进行记录. - - 与使用您的存储库的人交流. - - 存储库的第一次提交：`git commit -m "Initial commit" --allow-empty`. + - Annotating the start of a new bulk of work or a new feature. + - Documenting when you make changes to the project that aren't code related. + - Communicating with people using your repository. + - The first commit of a repository: `git commit -m "Initial commit" --allow-empty`. ### Styled Git Status Running: ```bash -$ git 状态 +$ git status ``` produces:  -通过添加“-sb”： +By adding `-sb`: ```bash -$ git 状态 -sb +$ git status -sb ``` -这是产生的： +this is produced:  @@ -771,56 +771,56 @@ $ git 状态 -sb Running: ```bash -$ git log --all --graph --pretty=format:'%Cred%h%Creset -%C(auto)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an> %Creset' --abbrev-commit --date=relative +$ git log --all --graph --pretty=format:'%Cred%h%Creset -%C(auto)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --date=relative ``` produces:  -归功于 [Palesz](http://stackoverflow.com/users/88355/palesz) +Credit to [Palesz](http://stackoverflow.com/users/88355/palesz) -*这可以使用找到的说明进行别名 [here](https://github.com/tiimgreen/github-cheat-sheet#aliases).* +*This can be aliased using the instructions found [here](https://github.com/tiimgreen/github-cheat-sheet#aliases).* [*Read more about the Git `log` command.*](http://git-scm.com/docs/git-log) ### Git Query -Git 查询允许您搜索所有以前的提交消息并找到与查询匹配的最新提交消息. +A Git query allows you to search all your previous commit messages and find the most recent one matching the query. ```bash -$ git 显示：/查询 +$ git show :/query ``` -其中“query”（区分大小写）是您要搜索的术语，然后找到最后一个并提供有关已更改行的详细信息. +where `query` (case-sensitive) is the term you want to search, this then finds the last one and gives details on the lines that were changed. ```bash -$ git 显示：/打字错误 +$ git show :/typo ```  -*按 `q` 退出.* +*Press `q` to quit.* ### Git Grep -Git Grep 将返回匹配模式的行列表. +Git Grep will return a list of lines matching a pattern. Running: ```bash -$ git grep 别名 +$ git grep aliases ``` -将显示所有包含字符串 *aliases* 的文件. +will show all the files containing the string *aliases*.  -*按 `q` 退出.* +*Press `q` to quit.* -您还可以使用多个标志进行更高级的搜索. 例如： +You can also use multiple flags for more advanced search. For example: - * `-e` 下一个参数是模式（例如，正则表达式） - * `--and`、`--or` 和 `--not` 组合多个模式. + * `-e` The next parameter is the pattern (e.g., regex) + * `--and`, `--or` and `--not` Combine multiple patterns. -像这样使用它： +Use it like this: ```bash $ git grep -e pattern --and -e anotherpattern ``` @@ -831,23 +831,23 @@ $ git grep 别名 Running: ```bash -$ git 分支 --merged +$ git branch --merged ``` -将为您提供已合并到当前分支的所有分支的列表. +will give you a list of all branches that have been merged into your current branch. Conversely: ```bash -$ git 分支 --no-merged +$ git branch --no-merged ``` -将为您提供尚未合并到当前分支的分支列表. +will give you a list of branches that have not been merged into your current branch. [*Read more about the Git `branch` command.*](http://git-scm.com/docs/git-branch) ### Fixup and Autosquash -如果之前的提交有问题（可以是 HEAD 中的一个或多个），例如 `abcde`，请在修改问题后运行以下命令： +If there is something wrong with a previous commit (can be one or more from HEAD), for example `abcde`, run the following command after you've amended the problem: ```bash $ git commit --fixup=abcde $ git rebase abcde^ --autosquash -i @@ -856,7 +856,7 @@ $ git rebase abcde^ --autosquash -i [*Read more about the Git `rebase` command.*](http://git-scm.com/docs/git-rebase) ### Web Server for Browsing Local Repositories -使用 Git `instaweb` 命令即时浏览 `gitweb` 中的工作存储库. 此命令是一个简单的脚本，用于设置 `gitweb` 和用于浏览本地存储库的 Web 服务器. +Use the Git `instaweb` command to instantly browse your working repository in `gitweb`. This command is a simple script to set up `gitweb` and a web server for browsing the local repository. ```bash $ git instaweb @@ -869,90 +869,90 @@ opens: [*Read more about the Git `instaweb` command.*](http://git-scm.com/docs/git-instaweb) ### Git Configurations -你的 .gitconfig 文件包含你所有的 Git 配置. +Your `.gitconfig` file contains all your Git configurations. #### Aliases -别名是帮助您定义自己的 git 调用的助手. 例如，您可以设置 `git a` 来运行 `git add --all`. +Aliases are helpers that let you define your own git calls. For example you could set `git a` to run `git add --all`. -要添加别名，请导航至“~/.gitconfig”并按以下格式填写： +To add an alias, either navigate to `~/.gitconfig` and fill it out in the following format: ``` [alias] - co =结帐 - 厘米 = 提交 - p = 推 - #显示有关标签、分支或远程的详细输出 - 标签=标签-l - 分支=分支-a - 遥控器=远程-v + co = checkout + cm = commit + p = push + # Show verbose output about tags, branches or remotes + tags = tag -l + branches = branch -a + remotes = remote -v ``` -...或在命令行中输入： +...or type in the command-line: ```bash $ git config --global alias.new_alias git_function ``` -例如： +For example: ```bash $ git config --global alias.cm commit ``` -对于具有多个功能的别名，请使用引号： +For an alias with multiple functions use quotes: ```bash - $ git config --global alias.ac '添加 -A . ＆＆ 犯罪' +$ git config --global alias.ac 'add -A . && commit' ``` -一些有用的别名包括： +Some useful aliases include: - | 别名 | 命令 | 键入什么 | +| Alias | Command | What to Type | | --- | --- | --- | - | `混帐厘米` | `git 提交` | `git config --global alias.cm commit` | - | `git co` | `git checkout` | `git config --global alias.co checkout` | - | `git ac` | `混帐添加. -A` `git commit` | `git config --global alias.ac '!git add -A && git commit'` | - | `git st` | `git status -sb` | `git config --global alias.st 'status -sb'` | - | `git 标签` | `git 标签-l` | `git config --global alias.tags 'tag -l'` | - | `git 分支` | `git 分支-a` | `git config --global alias.branches 'branch -a'` | - | `git 清理` | `git branch --merged \| grep -v '*' \| xargs git 分支-d` | `git config --global alias.cleanup "!git branch --merged \| grep -v '*' \| xargs git branch -d"` | - | `git 遥控器` | `git remote -v` | `git config --global alias.remotes 'remote -v'` | - | `git lg` | `git log --color --graph --pretty=format:'%Cred%h%Creset -%C(黄色)%d%Creset %s %Cgreen(%cr) %C(粗蓝色)<%an> %Creset' --abbrev-commit --` | `git config --global alias.lg "log --color --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C （粗体蓝色）<%an>%Creset' --abbrev-commit --"` | - -*一些别名取自 [@mathiasbynens](https://github.com/mathiasbynens) 点文件：https://github.com/mathiasbynens/dotfiles/blob/master/.gitconfig* +| `git cm` | `git commit` | `git config --global alias.cm commit` | +| `git co` | `git checkout` | `git config --global alias.co checkout` | +| `git ac` | `git add . -A` `git commit` | `git config --global alias.ac '!git add -A && git commit'` | +| `git st` | `git status -sb` | `git config --global alias.st 'status -sb'` | +| `git tags` | `git tag -l` | `git config --global alias.tags 'tag -l'` | +| `git branches` | `git branch -a` | `git config --global alias.branches 'branch -a'` | +| `git cleanup` | `git branch --merged \| grep -v '*' \| xargs git branch -d` | `git config --global alias.cleanup "!git branch --merged \| grep -v '*' \| xargs git branch -d"` | +| `git remotes` | `git remote -v` | `git config --global alias.remotes 'remote -v'` | +| `git lg` | `git log --color --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --` | `git config --global alias.lg "log --color --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --"` | + +*Some Aliases are taken from [@mathiasbynens](https://github.com/mathiasbynens) dotfiles: https://github.com/mathiasbynens/dotfiles/blob/master/.gitconfig* #### Auto-Correct - Git 为拼写错误的命令提供建议，如果启用了自动更正，则可以自动修复和执行命令. 通过指定一个整数来启用自动更正，该整数是 git 运行更正命令之前的十分之一秒的延迟. 零是不进行更正的默认值，负值将立即运行更正的命令. +Git gives suggestions for misspelled commands and if auto-correct is enabled the command can be fixed and executed automatically. Auto-correct is enabled by specifying an integer which is the delay in tenths of a second before git will run the corrected command. Zero is the default value where no correcting will take place, and a negative value will run the corrected command with no delay. -例如，如果你输入 `git comit` 你会得到这个： +For example, if you type `git comit` you will get this: ```bash -$ git comit -m “消息” +$ git comit -m "Message" ## git: 'comit' is not a git command. See 'git --help'. ## Did you mean this? ## commit ``` -可以像这样启用自动更正（延迟 1.5 秒）： +Auto-correct can be enabled like this (with a 1.5 second delay): ```bash $ git config --global help.autocorrect 15 ``` -所以现在命令 `git comit` 将自动更正为 `git commit`，如下所示： +So now the command `git comit` will be auto-corrected to `git commit` like this: ```bash -$ git comit -m “消息” +$ git comit -m "Message" ## WARNING: You called a Git command named 'comit', which does not exist. ## Continuing under the assumption that you meant 'commit' ## in 1.5 seconds automatically... ``` -git 重新运行命令之前的延迟是为了让用户有时间中止. +The delay before git will rerun the command is so the user has time to abort. #### Color -要为 Git 输出添加更多颜色： +To add more color to your Git output: ```bash $ git config --global color.ui 1 @@ -961,45 +961,45 @@ $ git config --global color.ui 1 [*Read more about the Git `config` command.*](http://git-scm.com/docs/git-config) ### Git Resources - | 标题 | 链接 | +| Title | Link | | ----- | ---- | - | Git 官方网站 | http://git-scm.com/ | - | 官方 Git 视频教程 | http://git-scm.com/videos | - | 代码学校尝试 Git | http://try.github.com/ | - | Git 入门参考和教程 | http://gitref.org/ | - | Git 官方教程 | http://git-scm.com/docs/gittutorial | - | 日常 Git | http://git-scm.com/docs/everyday | - | Git 沉浸 | http://gitimmersion.com/ | - | Git 神 | https://github.com/gorosgobe/git-god | +| Official Git Site | http://git-scm.com/ | +| Official Git Video Tutorials | http://git-scm.com/videos | +| Code School Try Git | http://try.github.com/ | +| Introductory Reference & Tutorial for Git | http://gitref.org/ | +| Official Git Tutorial | http://git-scm.com/docs/gittutorial | +| Everyday Git | http://git-scm.com/docs/everyday | +| Git Immersion | http://gitimmersion.com/ | +| Git God | https://github.com/gorosgobe/git-god | | Git for Computer Scientists | http://eagain.net/articles/git-for-computer-scientists/ | - | Git 魔法 | http://www-cs-students.stanford.edu/~blynn/gitmagic/ | +| Git Magic | http://www-cs-students.stanford.edu/~blynn/gitmagic/ | | Git Visualization Playground | http://onlywei.github.io/explain-git-with-d3/#freeplay | - | 学习 Git 分支 | http://pcottle.github.io/learnGitBranching/ | - | 一组有用的 .gitignore 模板 | https://github.com/github/gitignore | - | Unixorn 的 git 脚本的 git-extra-commands 集合 | https://github.com/unixorn/git-extra-commands | +| Learn Git Branching | http://pcottle.github.io/learnGitBranching/ | +| A collection of useful .gitignore templates | https://github.com/github/gitignore | +| Unixorn's git-extra-commands collection of git scripts | https://github.com/unixorn/git-extra-commands | #### Git Books - | 标题 | 链接 | +| Title | Link | | ----- | ---- | - | 使用 Git 的实用版本控制 | https://pragprog.com/titles/tsgit/pragmatic-version-control-using-git | - | 对于 Git | http://git-scm.com/book | - | Git 内幕 https://github.com/pluralsight/git-internals-pdf | - | 战壕中的 Git | http://cbx33.github.io/gitt/ | - | 使用 Git 进行版本控制 | http://www.amazon.com/Version-Control-Git-collaborative-development/dp/1449316387 | - | Git 实用指南 | https://pragprog.com/titles/pg_git/pragmatic-guide-to-git | - | Git：每个人的版本控制 | https://www.packtpub.com/application-development/git-version-control-everyone | +| Pragmatic Version Control Using Git | https://pragprog.com/titles/tsgit/pragmatic-version-control-using-git | +| Pro Git | http://git-scm.com/book | +| Git Internals PluralSight | https://github.com/pluralsight/git-internals-pdf | +| Git in the Trenches | http://cbx33.github.io/gitt/ | +| Version Control with Git | http://www.amazon.com/Version-Control-Git-collaborative-development/dp/1449316387 | +| Pragmatic Guide to Git | https://pragprog.com/titles/pg_git/pragmatic-guide-to-git | +| Git: Version Control for Everyone | https://www.packtpub.com/application-development/git-version-control-everyone | #### Git Videos - | 标题 | 链接 | +| Title | Link | | ----- | ---- | - | Git 上的 Linus Torvalds | https://www.youtube.com/watch?v=4XpnKHJAok8 | - | 与 Scott Chacon 一起介绍 Git | https://www.youtube.com/watch?v=ZDR433b0HJY | - | Git 从零开始 | https://www.youtube.com/watch?v=MYP56QJpDr4 | - | 图、散列和压缩，天哪！ | https://www.youtube.com/watch?v=ig5E8CcdM9g | - | GitHub 培训和指南 | https://www.youtube.com/watch?list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&v=FyfwLX4HAxM | +| Linus Torvalds on Git | https://www.youtube.com/watch?v=4XpnKHJAok8 | +| Introduction to Git with Scott Chacon | https://www.youtube.com/watch?v=ZDR433b0HJY | +| Git From the Bits Up | https://www.youtube.com/watch?v=MYP56QJpDr4 | +| Graphs, Hashes, and Compression, Oh My! | https://www.youtube.com/watch?v=ig5E8CcdM9g | +| GitHub Training & Guides | https://www.youtube.com/watch?list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&v=FyfwLX4HAxM | #### Git Articles - | 标题 | 链接 | +| Title | Link | | ----- | ---- | - | GitHub 流程 | http://scottchacon.com/2011/08/31/github-flow.html | - | 迁移到 Git 大文件存储 (Git LFS) | http://vooban.com/en/tips-articles-geek-stuff/migrating-to-git-lfs-for-developing-deep-learning-applications-with-large-files/ | +| GitHub Flow | http://scottchacon.com/2011/08/31/github-flow.html | +| Migrating to Git Large File Storate (Git LFS) | http://vooban.com/en/tips-articles-geek-stuff/migrating-to-git-lfs-for-developing-deep-learning-applications-with-large-files/ |