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
I realized we might actually run into big problems with code and output all over the repository if we all just push directly on master. I currently locked the master branch so no changes can be made to it directly.
This also means I get to look through your code as we work on things and we won't affect anyone else in this repository.
Here were the instructions @datajonbrig sent out initially:
Complete the following guide through chapter 4 (i.e. complete chapters 1-4)
The main research topic that I'm interested in as of now is doing something that analyzes how the environment has rebounded due to human inactivity. I was thinking I could maybe do something related to emissions and focus on a heavily polluted area(s).
I realized we might actually run into big problems with code and output all over the repository if we all just
push
directly onmaster
. I currently locked the master branch so no changes can be made to it directly.This also means I get to look through your code as we work on things and we won't affect anyone else in this repository.
Here were the instructions @datajonbrig sent out initially:
Creating a PR with your question/plan
I'm assuming all the commands are being run in your terminal in this projects root folder
git checkout -b branch_name
you can name it something likedan_ques
analysis/db
folder, e.g.,dan
README.md
and put down some questions you want to ask from the dataset you downloaded in Download the kaggle dataset #3add
andcommit
your changes (theREADME.md
file you just edited)git push origin branch_name
, note you need to use the same branch name from earlierREADME.md
file until we all settle on a feasible questionThe text was updated successfully, but these errors were encountered: