Unless you don't want to allow the repository to be publicly available, forking is all right since a public repo can be cloned anyway and re-uploaded without proper consent. At least a fork will always point back to the original source!
Haven't had an occasion where someone forked my repo without a fix in mind. Licensing the repo appropriately should also help in clearly indicating that you are the author for the content and what's okay, what's not.
If your concern is keeping certain posts private such as drafts, I think keeping the repo private is the solution.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Unless you don't want to allow the repository to be publicly available, forking is all right since a public repo can be cloned anyway and re-uploaded without proper consent. At least a fork will always point back to the original source!
Haven't had an occasion where someone forked my repo without a fix in mind. Licensing the repo appropriately should also help in clearly indicating that you are the author for the content and what's okay, what's not.
If your concern is keeping certain posts private such as drafts, I think keeping the repo private is the solution.