Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release Process #61

Open
1 task
boennemann opened this issue Jun 4, 2014 · 1 comment
Open
1 task

Release Process #61

boennemann opened this issue Jun 4, 2014 · 1 comment
Assignees
@boennemann

Comments

@boennemann
Copy link
Contributor

  • Implement the grunt/travis/npm release process
@boennemann boennemann self-assigned this Jun 4, 2014
@boennemann
Copy link
Contributor Author

Here is a Slack dump why this still isn't implemented:

My suggestion was to use the contents of a `template` subfolder if present
that way one could build way more sophisticated templates
a hoodie-template repo should contain a `template` folder, where the actual template is stored in
then one could build a build process and everything and just put the results into the template folder
hoodie-cli checks if a template subfolder is present in the given template and uses the contents of it only then
that way the change would be backwards compatible

boennemann added a commit that referenced this issue Oct 30, 2015
@boennemann
fix: remove template parts and make my-first-hoodie an app only
d19058c 
This can now also be published via semantic-release

Closes #79, Closes #78, Closes #77, Closes #61

BREAKING CHANGE: This version can no longer be used as an Hoodie template,
it's just the bare `www` folder.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@boennemann boennemann

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@boennemann