Talk about new files structure for repository

[ohmydevops]

My suggestion: Each repository is a file (I hate merge conflicts) For example we have cpp directory:

/cpp/repo1
/cpp/repo2
/cpp/repo3

/cpp/repo1 contents:

amiremohamadi/DuckX

Currently, i have no idea how to naming the files.

[ohmydevops]

I think this is not work. we should make it easier. why don't we use issues?

[ohmydevops]

Yes!, issues is the key for our problem. (Fork sucks, Merge conflicts sucks, then everything sucks)

[ohmydevops]

We use issues in https://github.com/softwaretalks/newsletter and everything works great.

[ohmydevops]

Finally, our system will look like this:

1. Users create issues (based on a template) to introduce their repositories & categories.
2. If the issue is accepted, admins should close it with verified label.
3. On closing issue event, actions starting.
4. Actions should validating issue contents and if everything is fine, then contents will be added to the README.md file.

---

Sample issue template (YAML format):

## copy your repository link (example: https://github.com/softwaretalks/newsletter)
repoLink: ""

## Current categories: 
## cpp
## reactjs
## php
## other
## golang
category: ""

[ohmydevops]

I think it's time to close this issue? @mohebifar

[mohebifar]

Yup :)