-
Notifications
You must be signed in to change notification settings - Fork 249
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
Add exercises questions to merged chapters #46
Add exercises questions to merged chapters #46
Conversation
Thanks @AlexAndorra |
You're welcome 😉
Ow you mean my branch is based on an earlier version of master?
Le sam. 24 août 2019 à 18:49, Ravin Kumar <[email protected]> a
écrit :
… Thanks @AlexAndorra <https://github.com/AlexAndorra>
I'll fix Chapter 3. I think this is based off an older commit than master
though :( I merged the Chapter 3 and 4 notebooks which I believe is causing
the merge conflict.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#46?email_source=notifications&email_token=AHIJMTCPRIZR6E4R37ZOUXTQGFQ73A5CNFSM4IPGMY5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5CDUUY#issuecomment-524565075>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHIJMTGQUHY5IH42KSF4P3LQGFQ73ANCNFSM4IPGMY5A>
.
|
I think so :( Try updating your master branch and see if more commits get
pulled down
…On Sat, Aug 24, 2019 at 11:04 AM Alexandre ANDORRA ***@***.***> wrote:
You're welcome 😉
Ow you mean my branch is based on an earlier version of master?
Le sam. 24 août 2019 à 18:49, Ravin Kumar ***@***.***> a
écrit :
> Thanks @AlexAndorra <https://github.com/AlexAndorra>
> I'll fix Chapter 3. I think this is based off an older commit than master
> though :( I merged the Chapter 3 and 4 notebooks which I believe is
causing
> the merge conflict.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <
#46?email_source=notifications&email_token=AHIJMTCPRIZR6E4R37ZOUXTQGFQ73A5CNFSM4IPGMY5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5CDUUY#issuecomment-524565075
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AHIJMTGQUHY5IH42KSF4P3LQGFQ73ANCNFSM4IPGMY5A
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#46?email_source=notifications&email_token=ABXBFYK4UDPTNSYVVBL4HJTQGFZZFA5CNFSM4IPGMY5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5CE3EA#issuecomment-524570000>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABXBFYMW6MKCSVRUT4HLCSTQGFZZFANCNFSM4IPGMY5A>
.
|
Just did a |
From what you described things should be fine. I'm just not sure how a merge conflict occurred. No worries though, hopefully they aren't too bad to resolve. I'll hold off on making any changes until this branch is merged. |
Hi, sorry for being late to the party. I see there are conflicts but I am not able to solve see them or solve them using github. @AlexAndorra did you follow these recommendations? Step 1: From your project repository, check out a new branch and test the changes. git checkout -b AlexAndorra-add-questions-to-merged-nbs master Step 2: Merge the changes and update on GitHub. git checkout master |
Mmmh seems like I missed a couple steps there... When started working on this feature, I did Can I do what you recommend or do we need something else? |
Those steps should fix this (hopefully) |
Ok, so I can't do the first step (
The problem is I can't open the Chapter 3 NB in jupyter to see the conflicts and resolve them... Do you where to go from there? |
Not sure how to proceed now, @canyon289 o you have any suggestions or hint? |
There's two paths. |
Thank you Ravin! So you mean fetch the last changes from upstream/master, create a whole new branch, and re-change the notebooks on this new branch? |
That or just download Chapter 3 and 4 from master directly, through the
github webui or checking out from the latest master, then just make the
changes again. That might be the easiest
…On Thu, Aug 29, 2019 at 8:42 AM Alexandre ANDORRA ***@***.***> wrote:
Thank you Ravin! So you mean fetch the last changes from upstream/master,
create a whole new branch, and re-change the notebooks on this new branch?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#46?email_source=notifications&email_token=ABXBFYKMB4JQG7XPFIJD5GTQG7U5TA5CNFSM4IPGMY5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5O5UVI#issuecomment-526244437>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABXBFYM7HQX22RU3TBSYXW3QG7U5TANCNFSM4IPGMY5A>
.
|
I just deleted chapters 3 and 4 from this PR, which solved the conflicts. Will do a whole new PR for 3 and 4 ASAP, as per Ravin advice. BTW, thanks for your help Ravin, taught me valuable git lessons 😉 |
Great, thank you! |
@AlexAndorra No problem. I'm sorry about the merge conflicts, it's truly a pain when it comes to notebooks |
As discussed in #40 here are the already merged notebooks, where I added the questions before the answers. The notebooks should be even easier to follow for readers.
Note that I didn't re-run the notebooks - under the assumption that they run correctly because they were already merged - but can do it if needed.
Finally, in chapter 3, I noticed that :
Tell me if you need help with that @canyon289 😉
Take care and PyMCheers!