Github: Difference between revisions
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
*A repo looks like this - it has a Clone or Download button | *A repo looks like this - it has a Clone or Download button | ||
[[File:repo.jpg|800px]] | [[File:repo.jpg|800px]] | ||
*Therefore, the current '''OSE Repo Structure is OpenSourceEcology/ProjectName | |||
:*The difficult part is that eventually there will be 50-200 projects like this, but that is ok | |||
=Links= | =Links= | ||
Revision as of 20:59, 25 May 2018
Notes on OSE Directory Structure
- In order to allow Git Clone of an entire directory, the directory must be right below the main directory like this - OpenSourceEcology/3D-Printer-OSE-Marlin
- It would be nice to do OpenSourceEcology/3D-Printer/OSE-Marlin - but then OSE-Marlin is not a repository in itself - it's a part of a repository, and therefore can't take advantage of Githubs collaboration workflow (fork/merge/pull request, etc).
- It is possible to set up a repo within a repo, but it is a pain to set up.
- A repo looks like this - it has a Clone or Download button
- Therefore, the current OSE Repo Structure is OpenSourceEcology/ProjectName
- The difficult part is that eventually there will be 50-200 projects like this, but that is ok
Links
- Discussion with Daniel - http://www.youtube.com/watch?v=N9gpPZ1yevU&feature=share
OSE Usage
- Branch management, forks, pull requests, and merges can be done automatically with Github. OSE should use this capacity to manage hardware development projects with high complexity and many iterations.
- STL viewing is available in GitHub since 2013 - [1]