Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Split out practical tips into a separate tips section(s) #76

Closed
rkdarst opened this issue May 29, 2018 · 3 comments
Closed

Split out practical tips into a separate tips section(s) #76

rkdarst opened this issue May 29, 2018 · 3 comments

Comments

@rkdarst
Copy link
Member

rkdarst commented May 29, 2018

Create a separate tips section, maybe several to go in phases. These will be useful for presenting what to do with git without going into details about how. Useful for certain forms of presentation. This should especially connect with scientific stories.

Maybe this would make too many sections... but that's probably not bad.
@bast
Copy link
Member

bast commented Jun 6, 2018

Merging with points from #87:

  • how to best use git for research, if you already know some version control and don't want to go into the technical stuff
  • Leading question: "how does one apply this my work?"

@bast bast mentioned this issue Jun 6, 2018
Closed
rkdarst added a commit to rkdarst/git-intro that referenced this issue May 26, 2019
@rkdarst
Rename section on complexity and what to do
fd67e05 
- The section was called "Start simple, later increase the level of
  complexity" but the name could be a bit better.
- This is not exactly coderefinery#76 (add a practical tips section) but related.
- I propose that this section be used for practical tips in the future
@rkdarst rkdarst mentioned this issue May 26, 2019
Merged
@rkdarst
Copy link
Member Author

rkdarst commented Jun 1, 2019

#164 should be re-done, after figuring out why the title didn't work.

@rkdarst rkdarst mentioned this issue Jun 1, 2019
Closed
@rkdarst
Copy link
Member Author

rkdarst commented Jun 1, 2019

  • Once you commit, it is very, very hard to really lose your code
  • Commit early and often
  • Always fully commit (or stash) before you do dangerous things, so that you know you are safe. Otherwise it can be hard to recover.

@wikfeldt wikfeldt mentioned this issue Oct 17, 2019
Merged
@bast bast closed this as completed in 666721a Oct 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bast @rkdarst