Closed SimonSimCity closed 4 years ago
Should we be building docs and storing them into some special branch? And then have GitHub pages there?
Could well do this - I just don't want to update these generated docs every time I update the code.
OK, see https://github.com/Meteor-Community-Packages/meteor-roles/issues/284 for more information.
Would you keep it in this branch? I wouldn't ... and I've also removed the generated docs from the v3 branch I have. If git has something as assets or if we could push those docs to a separate repo, I'd be on it - I just see it at the wrong place in this repo - or at least on this branch - together with the code.
Yes, generally you have a special branch for static pages, and then you git force push into it when you rebuild docs, so that they do not collect in history.
Would be nice to get this set up. Please let me know how I could do this. Until then, I'll at least keep all this documentation out of the branches where we do active development on the codebase.
Let's discuss this in #284.
Reopening https://github.com/Meteor-Community-Packages/meteor-roles/pull/272