Skip to content
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.

Sign up for GitHub

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

Jump to bottom

If you forked or cloned the repos before Dec 21, 2017, please do re-fork or re-clone it again due to git history change. #10

Closed
linmajia opened this issue Dec 21, 2017 · 1 comment
Closed

If you forked or cloned the repos before Dec 21, 2017, please do re-fork or re-clone it again due to git history change. #10

linmajia opened this issue Dec 21, 2017 · 1 comment
Labels
bug

Comments

@linmajia
Copy link
Contributor

No description provided.

@linmajia linmajia changed the title There is a problem with git history, please fork or clone the repos again. Please fork or clone the repos again due to git history change. Dec 21, 2017
@TobeyQin TobeyQin mentioned this issue Feb 27, 2018
Closed
@linmajia linmajia changed the title Please fork or clone the repos again due to git history change. If you forked or cloned the repos before Dec 21, 2017, please do re-fork or re-clone it again due to git history change. Jun 10, 2018
@linmajia
Copy link
Contributor Author

If you forked or cloned the repos after Dec 21, 2017, you won't be affected.

@linmajia linmajia added the bug label Jun 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@linmajia