-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
render after resolving merge conflicts
- Loading branch information
1 parent
44ac063
commit e3f670a
Showing
3 changed files
with
6 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -158,21 +158,21 @@ | |
| "href": "git-faqs.html", | ||
| "title": "Git and Github FAQs", | ||
| "section": "", | ||
| "text": "Git and GitHub seem a little scary. How do I get started?\nStart by using these tools for solo work. It is the lowest stakes way to develop skills that will be valuable for collaboration.\nWhere can I go for help if I get stuck?\nRunning into errors is an inevitable part of working with Git and GitHub, but we’re here to help! Drop a message in the #github Slack channel when you have issues, or email Aaron Williams ([email protected]) or Erika Tyagi ([email protected]).\nCan I use Git and GitHub with projects that have confidential data stored on the Y Drive?\nYes! Read this guide for tips on how to do so.\nShould I use Git inside of Box? (i.e. turn a Box folder into a Git repository)\nNo – we strongly recommend keeping Box folders and GitHub repositories separate.\nWhat kinds of files should I track with Git?\nGenerally, you should only track code (i.e., scripts written in R, Stata, SAS, Python, etc.) with Git. You should not track large data files or binary files (i.e., Word, Excel files). There are occasions when tracking small data files with Git might make sense, but you should never store confidential data on GitHub (even in a private repository). We recommend getting familiar with .gitignore files, which can prevent you and your collaborators from accidentally pushing files to GitHub. GitHub provides hundreds of template .gitignore files for specific programming languages (e.g. R, Stata, or Python) or operating systems (e.g. Windows or MacOS) that can be useful as a starting point.\nHow do I add documentation to my repositories?\nUse README files to add context and documentation to your repos. These are Markdown files in the root of your directory named README.md that can help folks understand the structure and contents of your repo. Markdown Live Preview can be a useful tool to help with formatting.\nWhat permissions should I give my collaborators?\nIn general, you should follow the principle of least privilege, which means that you should give folks the minimum level of access they need, but no more than that. In most cases, this will be the Write role, but you should refer to GitHub’s guide describing the different roles and what they allow. If you need elevated permissions for a repository, post a message in the #github Slack channel.\nAre there other commands that can be helpful when using Git from the command line?\nDefinitely! Learning a few simple Bash commands can be helpful for navigating the command line. A few common commands include pwd (to print your current directory), cd (to change directories), and ls (to list the files in a directory). For an introduction to these, and other, commands, we recommend this guide from Friendly Django or this guide from Happy Git with R." | ||
| "text": "Git and GitHub seem a little scary. How do I get started?\nStart by using these tools for solo work. It is the lowest stakes way to develop skills that will be valuable for collaboration.\nWhere can I go for help if I get stuck?\nRunning into errors is an inevitable part of working with Git and GitHub, but we’re here to help! Drop a message in the #github Slack channel when you have issues, or email Aaron Williams ([email protected]) or Erika Tyagi ([email protected]).\nCan I use Git and GitHub with projects that have confidential data stored on the Y Drive?\nYes! Read this guide for tips on how to do so.\nShould I use Git inside of Box? (i.e. turn a Box folder into a Git repository)\nNo – we strongly recommend keeping Box folders and GitHub repositories separate.\nWhat kinds of files should I track with Git?\nGenerally, you should only track code (i.e., scripts written in R, Stata, SAS, Python, etc.) with Git. You should not track large data files or binary files (i.e., Word, Excel files). There are occasions when tracking small data files with Git might make sense, but you should never store confidential data on GitHub (even in a private repository). We recommend getting familiar with .gitignore files, which can prevent you and your collaborators from accidentally pushing files to GitHub. GitHub provides hundreds of template .gitignore files for specific programming languages (e.g. R, Stata, or Python) or operating systems (e.g. Windows or MacOS) that can be useful as a starting point.\nHow do I add documentation to my repositories?\nUse README files to add context and documentation to your repos. These are Markdown files in the root of your directory named README.md that can help folks understand the structure and contents of your repo. Markdown Live Preview can be a useful tool to help with formatting.\nWhat permissions should I give my collaborators?\nIn general, you should follow the principle of least privilege, which means that you should give folks the minimum level of access they need, but no more than that. In most cases, this will be the Write role, but you should refer to GitHub’s guide describing the different roles and what they allow. If you need elevated permissions for a repository, post a message in the #github Slack channel.\nAre there other commands that can be helpful when using Git from the command line?\nDefinitely! Learning a few simple Bash commands can be helpful for navigating the command line. A few common commands include pwd (to print your current directory), cd (to change directories), and ls (to list the files in a directory). For an introduction to these commands and others, we recommend this guide from Friendly Django or this guide from Happy Git with R." | ||
| }, | ||
| { | ||
| "objectID": "git-faqs.html#faqs", | ||
| "href": "git-faqs.html#faqs", | ||
| "title": "Git and Github FAQs", | ||
| "section": "", | ||
| "text": "Git and GitHub seem a little scary. How do I get started?\nStart by using these tools for solo work. It is the lowest stakes way to develop skills that will be valuable for collaboration.\nWhere can I go for help if I get stuck?\nRunning into errors is an inevitable part of working with Git and GitHub, but we’re here to help! Drop a message in the #github Slack channel when you have issues, or email Aaron Williams ([email protected]) or Erika Tyagi ([email protected]).\nCan I use Git and GitHub with projects that have confidential data stored on the Y Drive?\nYes! Read this guide for tips on how to do so.\nShould I use Git inside of Box? (i.e. turn a Box folder into a Git repository)\nNo – we strongly recommend keeping Box folders and GitHub repositories separate.\nWhat kinds of files should I track with Git?\nGenerally, you should only track code (i.e., scripts written in R, Stata, SAS, Python, etc.) with Git. You should not track large data files or binary files (i.e., Word, Excel files). There are occasions when tracking small data files with Git might make sense, but you should never store confidential data on GitHub (even in a private repository). We recommend getting familiar with .gitignore files, which can prevent you and your collaborators from accidentally pushing files to GitHub. GitHub provides hundreds of template .gitignore files for specific programming languages (e.g. R, Stata, or Python) or operating systems (e.g. Windows or MacOS) that can be useful as a starting point.\nHow do I add documentation to my repositories?\nUse README files to add context and documentation to your repos. These are Markdown files in the root of your directory named README.md that can help folks understand the structure and contents of your repo. Markdown Live Preview can be a useful tool to help with formatting.\nWhat permissions should I give my collaborators?\nIn general, you should follow the principle of least privilege, which means that you should give folks the minimum level of access they need, but no more than that. In most cases, this will be the Write role, but you should refer to GitHub’s guide describing the different roles and what they allow. If you need elevated permissions for a repository, post a message in the #github Slack channel.\nAre there other commands that can be helpful when using Git from the command line?\nDefinitely! Learning a few simple Bash commands can be helpful for navigating the command line. A few common commands include pwd (to print your current directory), cd (to change directories), and ls (to list the files in a directory). For an introduction to these, and other, commands, we recommend this guide from Friendly Django or this guide from Happy Git with R." | ||
| "text": "Git and GitHub seem a little scary. How do I get started?\nStart by using these tools for solo work. It is the lowest stakes way to develop skills that will be valuable for collaboration.\nWhere can I go for help if I get stuck?\nRunning into errors is an inevitable part of working with Git and GitHub, but we’re here to help! Drop a message in the #github Slack channel when you have issues, or email Aaron Williams ([email protected]) or Erika Tyagi ([email protected]).\nCan I use Git and GitHub with projects that have confidential data stored on the Y Drive?\nYes! Read this guide for tips on how to do so.\nShould I use Git inside of Box? (i.e. turn a Box folder into a Git repository)\nNo – we strongly recommend keeping Box folders and GitHub repositories separate.\nWhat kinds of files should I track with Git?\nGenerally, you should only track code (i.e., scripts written in R, Stata, SAS, Python, etc.) with Git. You should not track large data files or binary files (i.e., Word, Excel files). There are occasions when tracking small data files with Git might make sense, but you should never store confidential data on GitHub (even in a private repository). We recommend getting familiar with .gitignore files, which can prevent you and your collaborators from accidentally pushing files to GitHub. GitHub provides hundreds of template .gitignore files for specific programming languages (e.g. R, Stata, or Python) or operating systems (e.g. Windows or MacOS) that can be useful as a starting point.\nHow do I add documentation to my repositories?\nUse README files to add context and documentation to your repos. These are Markdown files in the root of your directory named README.md that can help folks understand the structure and contents of your repo. Markdown Live Preview can be a useful tool to help with formatting.\nWhat permissions should I give my collaborators?\nIn general, you should follow the principle of least privilege, which means that you should give folks the minimum level of access they need, but no more than that. In most cases, this will be the Write role, but you should refer to GitHub’s guide describing the different roles and what they allow. If you need elevated permissions for a repository, post a message in the #github Slack channel.\nAre there other commands that can be helpful when using Git from the command line?\nDefinitely! Learning a few simple Bash commands can be helpful for navigating the command line. A few common commands include pwd (to print your current directory), cd (to change directories), and ls (to list the files in a directory). For an introduction to these commands and others, we recommend this guide from Friendly Django or this guide from Happy Git with R." | ||
| }, | ||
| { | ||
| "objectID": "git-faqs.html#additional-resources", | ||
| "href": "git-faqs.html#additional-resources", | ||
| "title": "Git and Github FAQs", | ||
| "section": "2 Additional Resources", | ||
| "text": "2 Additional Resources\n\nGit Cheat Sheet\nHappy Git and GitHub for the UserR\nGit Pocket Guide\nGetting Git Right\nGitHub Skills\nGit for Humans" | ||
| "text": "2 Additional Resources\n\nGit Cheat Sheet\nHappy Git and GitHub for the UserR\nGit Pocket Guide\nGetting Git Right\nGit for Humans" | ||
| }, | ||
| { | ||
| "objectID": "git-y-drive.html", | ||
|
|
||