Fix Python Dockerfile

[GyuminJack]

dockerfile is updated 2 month ago.

there is missed change directory command. (it is originally existed)

[jameslamb]

Thanks for taking the time to contribute!

Please see one suggestion I left. In the future, we'd appreciate if you tested your changes prior to submitting them.

[jameslamb]

Suggested change

	cd LigthGBM && sh ./build-python.sh install && \
	cd ./LightGBM && \
	sh ./build-python.sh install && \

Please put this change on a separate line, for consistency with the rest of this Dockerfile (which is done to make it easier to see the sequence of commands).

And please note that it's LightGBM, not LihgtGBM.

[GyuminJack]

I misspelled it when I typed it in the source after testing it on something else.
I apologize. (i tested twice this time..😅)

Next time I contribute, I'll be sure to test or build against the changed source and open a PR.

Thanks for the thoughtful comment.

[jameslamb]

No problem, thanks for the fix!

By the way, please check you gitconfig settings. It looks like you're pushing commits here that aren't signed with an email tied to your GitHub account. That means GitHub might not include you as a "contributor" in this project's statistics, and people won't be able to click through to your account from the commit log or git blame view.

See #5532 (comment) for some details on what I mean.

[GyuminJack]

i did below code. ( ref, uptake/pkgnet#284)

git config --global user.email "my email"
git reset --soft HEAD~2
git commit -m "fix commit message"
git push origin master --force

Is this what you were expecting?

[jameslamb]

Looks like that fixed it! The commits are now tied to your GitHub.

Is this what you were expecting?

It doesn't matter to me personally, we could have merged this either way. Just want to be sure you get credit for your contribution 😊

[jameslamb]

thanks!

[github-actions]

This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this.