You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm little bit confused how things are organized at GitHub. We as organization have '/sculptor' and one repository 'base.git'. However we can't have Wiki or Issues at organization level only inside repository. Can I create new repository, e.g. 'sculptor' for issues and wiki for org level, or we will keep 'base' and do wiki and issues here, and maybe another one 'documentation' for web site?
The text was updated successfully, but these errors were encountered:
You're right, the organization level is just a container of repositories and nothing special. Some groups just create a "docs" folder right inside of the repository. That would be ok, but has the downside of getting pulled in when you just want to work on code. As long as all documentation organized into that directory only, that'd be fine. One of the issues with the prior project was there were docs fragmented here and there, which tend to get forgotten.
Or a "site" or "website" or "documentation" repository would work ... I don't really have a preference one way or the other -- others, any thoughts?
I'm little bit confused how things are organized at GitHub. We as organization have '/sculptor' and one repository 'base.git'. However we can't have Wiki or Issues at organization level only inside repository. Can I create new repository, e.g. 'sculptor' for issues and wiki for org level, or we will keep 'base' and do wiki and issues here, and maybe another one 'documentation' for web site?
The text was updated successfully, but these errors were encountered: