文件列表:

LICENSE (11357, 2019-02-15)
arctic_training.Rproj (205, 2019-02-15)
data_reformat.Rmd (4549, 2019-02-15)
data_reformat.html (747156, 2019-02-15)
function_tutorial.Rmd (1954, 2019-02-15)
index.Rmd (4125, 2019-02-15)
index.html (923652, 2019-02-15)
sf_tutorial.Rmd (3784, 2019-02-15)
sf_tutorial.html (2711130, 2019-02-15)
test_py-rmark.Rmd (607, 2019-02-15)
test_py-rmark.html (783480, 2019-02-15)

# Arctic Training Hands on Materials Arctic Data Science Center Training Tutorial February 2019: Hands on materials for the Arctic training workshop. - Data - Lessons - Notes Made some changes from RStudio. - changes show up in Staging after I hit save. - but this doesn't save changes to the repository until I check Staged & Commit. You can explicitly choose what goes into the commit. - Unless it is a binary file, then it changes the whole thing. Format of commit descriptions: - What? (Concise) - Why? (Descriptive) Using the command line - git status - git add - git commit Great job! Thanks! Pushing at the same time. - the second person to push will get an error message - it will then tell you to pull first - then it will auto-merge and commit (you'll see a branch in the git window) - then the second person will push the most recent version - everyone should pull before they start to edit and not edit same place at same time - when a conflict arises someone (the owner?) should resolve the merge Pull -> Edit -> Add -> Pull -> Commit -> Push Branching - git branch [branch_name] **to create branch - git checkout [branch_name] **to switch - git merge **to merge the branch Adding fork_in_road branch for testing - Gave a conflict to resolve - You're merges if they are on the same place will be like the conflict w/ a collaborator

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：