You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feedback from an attendee to the Jan 29 session (with some editorializing by me):
I think it went really well! it was really helpful information and gave lots of opportunity for playing around and figure out breakages and error test in real time
some personal thoughts, would be helpful to:
have some sort of document with the common git codes we went over today for reference
warning before we start playing with new docs that anything we create in that folder would go up to our github (I may have made one that started with "whoop whoop that's the sound of the police" with the intent for it to just be on my computer )
maybe hammer home a bit more throughout the session that a key thing before people ACTUALLY start using git and github is really understanding * the gitignore function and to not do actual work in github until that's really nailed down in people's workflows
For next steps, I think:
having a training session that goes over gitignore in more detail / with much more practice opportunities in there (e.g., working on several collabs with faked data files and making sure that each one is set up correctly / correct files are being ignored / people are thinking about what needs to be ignored
also having intro to git via RStudio in that session
but it was REALLY good and helpful and it was great to be able to practice it first-hand and also have the active troubleshooting & breakout rooms as needed!!
driving home the idea that data doesn't go on github, and how we actually are set up to use github, should probably be a more highlighted piece
100% say it out loud, often, and also write it in big, bright letters
highlight in training that please don't practice with real work stuff in your personal space
The text was updated successfully, but these errors were encountered:
Feedback from an attendee to the Jan 29 session (with some editorializing by me):
I think it went really well! it was really helpful information and gave lots of opportunity for playing around and figure out breakages and error test in real time
some personal thoughts, would be helpful to:
For next steps, I think:
but it was REALLY good and helpful and it was great to be able to practice it first-hand and also have the active troubleshooting & breakout rooms as needed!!
The text was updated successfully, but these errors were encountered: