I find myself using GitHub for much more than source code. Lately, when I start a new project - any project, I create a new GitHub Repo.
Now I am thinking ways to combat my new problem: Repo sprawl.
1) Implement repo naming conventions
2) Include repo metadata - description, URL, taggs
3) Build for repo indexing - use common folder structure/names
4) Use rich README.md files at multiple levels in each Repo
What about you? Do you face this issue? What do you do to address it?
For further actions, you may consider blocking this person and/or reporting abuse
BekahHW -
Mitchell Mutandah -
Anton Yakutovich -
Sarah Lean 🏴 -
Once suspended, lynnlangit will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, lynnlangit will be able to comment and publish posts again.
Once unpublished, all posts by lynnlangit will become hidden and only accessible to themselves.
If lynnlangit is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Lynn Langit.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag lynnlangit:
Unflagging lynnlangit will restore default visibility to their posts.
Top comments (0)