I am developing a pretty large JavaScript library (Formula.js) of functions (450+). Most of them are pretty independent from each other and totally self-contained, or make use of well-known third-party libraries (Moment.js for example). In order to support discussions and manage contributions at the function level rather than at the library level, I created one Gist per function (Cf. CONVERT Gist), and one repository for the entire library. This makes it easy to include the code of a function in the function's documentation (Cf. CONVERT documentation).

My question is: how do I keep the master repository synchronized with the Gists?

The solution should:

• allow changes to be made from the master repository and from the individual Gists
• automate the inclusion of copyright headers on the individual Gists
• automate the inclusion of ments related to third-party libraries on the individual Gists

Additional thoughts:

I could not find many examples of projects being managed that way. I'm also rather unexperienced with Git. Therefore, the workflow I'm suggesting might be totally flawed, or introduce unwanted plexity. Any thoughts on possible best practices for keeping things under control are much wele.

I am developing a pretty large JavaScript library (Formula.js) of functions (450+). Most of them are pretty independent from each other and totally self-contained, or make use of well-known third-party libraries (Moment.js for example). In order to support discussions and manage contributions at the function level rather than at the library level, I created one Gist per function (Cf. CONVERT Gist), and one repository for the entire library. This makes it easy to include the code of a function in the function's documentation (Cf. CONVERT documentation).

My question is: how do I keep the master repository synchronized with the Gists?

The solution should:

• allow changes to be made from the master repository and from the individual Gists
• automate the inclusion of copyright headers on the individual Gists
• automate the inclusion of ments related to third-party libraries on the individual Gists

Additional thoughts:

I could not find many examples of projects being managed that way. I'm also rather unexperienced with Git. Therefore, the workflow I'm suggesting might be totally flawed, or introduce unwanted plexity. Any thoughts on possible best practices for keeping things under control are much wele.

• javascript
• git
• version-control
• github
• gist

Share Improve this question Follow asked Jan 26, 2013 at 15:10 Ismael GhalimiIsmael Ghalimi 3,56533 gold badges2424 silver badges2626 bronze badges

Add a ment  | 

2 Answers 2

Sorted by: Reset to default 7

Seeing as each gist is in fact a git repository, you could use the git submodule feature to include them all in your primary GitHub repository.

Have a look at this page from the book, http://git-scm./book/en/Git-Tools-Submodules , it even has a section on so-called Superprojects.

And you could use Github.js to add copyright headers and library-related ments.