search

CollectionBuilder / collectionbuilder-gh

A framework for creating digital exhibits from a folder of files and a spreadsheet. See Readme below for instructions to get started!
https://collectionbuilder.github.io/collectionbuilder-gh/
MIT License
93 stars 76 forks source link

template repo #15

Closed evanwill closed 4 years ago

evanwill commented 4 years ago

new github feature, https://help.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-template-repository

@dcnb @owikle might be the best way for folks to start their own CB-gh?

It is just like import, except it throws out all the commit history, so you have a new repository with just one initial commit. pluses:

example, https://github.com/evanwill/test-template

dcnb commented 4 years ago

That is a great feature. We should definitely use that.

Any reason why not to use it for both the skin and gh versions?

On Sun, Jan 5, 2020 at 9:58 PM EvanWill notifications@github.com wrote:

new github feature,

https://help.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-template-repository

@dcnb https://github.com/dcnb @owikle https://github.com/owikle might be the best way for folks to start their own CB-gh?

It is just like import, except it throws out all the commit history, so you have a new repository with just one initial commit. pluses:

  • one button click (once enabled, it adds a green button)
  • smaller repository since dev history isn't there
  • adds "generated from " below repo title (like "forked from ").

example, https://github.com/evanwill/test-template

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/CollectionBuilder/collectionbuilder-gh/issues/15?email_source=notifications&email_token=ACTM4GICEXBV4XGEP6QOZHDQ4LCB5A5CNFSM4KC72VF2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IEEQPMQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACTM4GPDB72W6MM26JFJTA3Q4LCB5ANCNFSM4KC72VFQ .

evanwill commented 4 years ago

Not sure, the current skin method (create repo, download release) ensures they use a release (that matches current documentation) and seems sort of clean. Using CB-skin as a template saves some clicks, seems intuitive, but we need to make sure the master is the "release" version at all times (do dev from a different branch and merge back only when releasing).