How do you usually manage it? Private git repo?
Also, what do you feel when people forked your GitHub Pages, for instance?
For further actions, you may consider blocking this person and/or reporting abuse
How do you usually manage it? Private git repo?
Also, what do you feel when people forked your GitHub Pages, for instance?
For further actions, you may consider blocking this person and/or reporting abuse
Scott Reno -
DevOps Descent -
Jamie -
Sukhpinder Singh -
Top comments (3)
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.
You made a point. Still, I don't want to think about being Fork'd. I don't want to make it too explicit.
I made it private. Don't have any problems with this approach. The biggest disadvantage are typos, anyone who have GitHub account can fix the. But whit private repo you need to have 3d party apps to manage this. Just create a list of pros/cons for private repo and chose the most valuable for you ;)