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.

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

Pcc57 #411

Merged
merged 2 commits into from Nov 9, 2018

Conversation

Projects
None yet
3 participants
@candacehv

candacehv commented Oct 31, 2018

ATTENTION: before clicking "Create Pull Request" please submit some meta data, thanks!

Difficulty level (1-10): [3]
Estimated time spent (hours): [2]
Completed (yes/no): [Yes]
I stretched my coding skills (if yes what did you learn?): [The Git was the most challenging part - but good practice! I got a little distracted trying to solve new problems. ]
Other feedback (what can we improve?): [Awesome! Thanks for the video tutorial and steps. ]

@pybites

This comment has been minimized.

Owner

pybites commented Nov 9, 2018

I hope the git part gets easier upon subsequent challenges. What was the challenging part here for you?

Are you on Windows/Unix? Sometimes the former makes this a bit more challenging for people because they need a tool like git bash, cygwin or cmder.

Anyways, once you get it working it's a nice way to submit code without asking you for write access to your Github account. Hope to see you on more challenges.

Cheers,
Bob

@pybites

This comment has been minimized.

Owner

pybites commented Nov 9, 2018

Thanks for the Pandas insights too, this is more concise than my solution (just starting out)

@pybites pybites merged commit 9557d43 into pybites:community Nov 9, 2018

@bbelderbos

This comment has been minimized.

Collaborator

bbelderbos commented Nov 9, 2018

Once you have your fork cloned to your machine subsequent challenges should be easier. I just did this for our new NLP challenge #58:

In my cloned fork directory:

  1. get changes:
$ git checkout community
$ git pull upstream community
  1. Make my new branch and inside the "58" challenge directory a new "username" directory:
$ git checkout -b PCC58
Switched to a new branch 'PCC58'
$ mkdir 58/bbelderbos && cd $_

TODO ... do challenge work ...

When I am done coding I would send the changes to my fork:

$ git add . && git commit -m 'PCC58 bbelderbos'
$ git push origin PCC58

HTH
Bob

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment