foobar_templates 2.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 8ce07f040ecc4ee93a6ee5b6d091af7fdecda0d95f36d17404f900cb48086fa9
+  data.tar.gz: dd0c320b9a1176f5873889fc18b9304923a2771383f426bc053a9158ed98e76a
+SHA512:
+  metadata.gz: 9ed9a0c22a22e58eb73124062cd444bc547e1ce0d5ad48bf10942d68c571b3c3d15395aaeef732406ca77fe6e56ce561aa94ccefce39837ac170ebe513eb54eb
+  data.tar.gz: 1c09a14c319a55532052e0ece16582b7876a34f73377de7821c4ed0a40927483ffa675f56f843422cf8a31670d9cf3c26a4e97b29a0d99e54cc034e8dac7912b

data/.beader/.gitignore

@@ -0,0 +1,6 @@
+*.lock
+*.log
+identities.yaml
+integrations
+hooks
+issues

data/.beader/issues/1-support-flexible-template-topologies.yaml

@@ -0,0 +1,21 @@
+---
+id: 1
+title: Support Flexible Template Topologies
+type: epic
+status: closed
+priority: 1
+assignees:
+- kind-prism
+created_at: 2026-04-01T03:29:28.803231289Z
+updated_at: 2026-04-01T03:35:47.235779844Z
+closed_at: 2026-04-01T03:35:47.235778978Z
+---
+
+Broader effort to support evolving template repository structures (single-template repos and monorepo-style template collections) while preserving backward compatibility.
+
+---
+COMMENT
+2026-04-01T03:35:47.232496261Z
+author: kind-prism
+
+Epic objective delivered for this cycle through root feature #2 and child issues #3-#7. Monorepo template discovery, selection, generation integration, tests, and documentation are complete.

data/.beader/issues/2-add-monorepo-support-for-template-discovery-and-generation.yaml

@@ -0,0 +1,33 @@
+---
+id: 2
+title: Add monorepo support for template discovery and generation
+type: feature
+status: closed
+priority: 1
+parent: 1
+assignees:
+- kind-prism
+created_at: 2026-04-01T03:29:28.848153656Z
+updated_at: 2026-04-01T03:35:18.475324707Z
+closed_at: 2026-04-01T03:35:18.475323732Z
+---
+
+## User Message
+We need a syntax for bundlegem.yml file that allows us to specify that this is a monorepo with multiple templates within it. Maybe something like this...
+
+monorepo: true
+
+If that file is set, then we look for subdirectories that have their own bundlegem.yml file following the usual configurations.
+
+## Context
+Implementation plan source: /memories/session/plan.md
+
+## Goal
+Add opt-in monorepo support to template discovery and generation while preserving existing single-template behavior.
+
+---
+COMMENT
+2026-04-01T03:35:18.472408807Z
+author: kind-prism
+
+Completed monorepo support for template discovery and generation. Implemented recursive monorepo-aware inventory from monorepo: true containers, leaf-template selection by subtemplate name, actionable ambiguity and not-found errors, and generation behavior validated to use leaf template config. Added unit/integration coverage and README documentation updates. Validation: bundle exec rspec passed (29 examples, 0 failures).

data/.beader/issues/3-implement-monorepo-aware-recursive-template-inventory.yaml

@@ -0,0 +1,29 @@
+---
+id: 3
+title: Implement monorepo-aware recursive template inventory
+type: feature
+status: closed
+priority: 1
+parent: 2
+assignees:
+- kind-prism
+created_at: 2026-04-01T03:29:28.883340322Z
+updated_at: 2026-04-01T03:32:36.142758994Z
+closed_at: 2026-04-01T03:32:36.142758236Z
+---
+
+Discovered from #2.
+
+Implement recursive template inventory in configurator:
+- Add safe bundlegem.yml config loading helper
+- Classify directories as monorepo containers (monorepo: true) vs leaf templates
+- Recurse only through monorepo-marked directories
+- Emit only leaf templates for listing, preserving category behavior
+- Ensure monorepo container root files are not treated as template sources
+
+---
+COMMENT
+2026-04-01T03:32:36.139335553Z
+author: kind-prism
+
+Implemented recursive monorepo-aware template inventory in Configurator. Added safe bundlegem.yml loading, monorepo container detection via monorepo: true, recursive traversal only through monorepo containers, and leaf-only template emission for list output. Added specs for direct and nested monorepo listing behavior and helper fixture creation. Validation: bundle exec rspec passed (25 examples, 0 failures).

data/.beader/issues/4-add-leaf-template-selection-with-ambiguity-and-not-found-handling.yaml

@@ -0,0 +1,30 @@
+---
+id: 4
+title: Add leaf-template selection with ambiguity and not-found handling
+type: feature
+status: closed
+priority: 1
+parent: 2
+blocked_by:
+- 3
+assignees:
+- kind-prism
+created_at: 2026-04-01T03:29:28.915988414Z
+updated_at: 2026-04-01T03:33:38.342992036Z
+closed_at: 2026-04-01T03:33:38.342991170Z
+---
+
+Discovered from #2.
+
+Update template selection logic:
+- Resolve template by subtemplate-only leaf name
+- Fail with actionable not-found error when no match exists
+- Fail with actionable ambiguity error when multiple leaf templates share a name
+- Keep existing non-monorepo template selection behavior unchanged
+
+---
+COMMENT
+2026-04-01T03:33:38.339552995Z
+author: kind-prism
+
+Implemented monorepo leaf-template selection in TemplateManager. Added recursive leaf discovery rooted at monorepo: true containers, unique subtemplate-only name matching, actionable not-found errors listing available leaves, and actionable ambiguity errors listing conflicting paths. Added focused unit tests covering unique match, duplicate-name ambiguity, and monorepo not-found behavior. Validation: bundle exec rspec passed (28 examples, 0 failures).

data/.beader/issues/5-integrate-leaf-template-resolution-into-generation-flow.yaml

@@ -0,0 +1,30 @@
+---
+id: 5
+title: Integrate leaf template resolution into generation flow
+type: task
+status: closed
+priority: 1
+parent: 2
+blocked_by:
+- 4
+assignees:
+- kind-prism
+created_at: 2026-04-01T03:29:28.945867072Z
+updated_at: 2026-04-01T03:34:24.818985978Z
+closed_at: 2026-04-01T03:34:24.818985111Z
+---
+
+Discovered from #2.
+
+Integrate generation with leaf template paths:
+- Ensure resolved template source is a leaf template directory
+- Keep CLI::Gem config loading based on the leaf bundlegem.yml
+- Ensure bootstrap and prefix behavior come from leaf config only
+- Preserve existing single-template generation flow
+
+---
+COMMENT
+2026-04-01T03:34:24.815837053Z
+author: kind-prism
+
+Integrated monorepo leaf-template resolution into generation flow by relying on leaf path selection in TemplateManager and validating behavior end-to-end. Added integration coverage proving generation runs from a selected leaf template and uses leaf bootstrap configuration while ignoring container-level monorepo config. Validation: bundle exec rspec passed (29 examples, 0 failures).

data/.beader/issues/6-add-monorepo-discovery-and-generation-test-coverage.yaml

@@ -0,0 +1,31 @@
+---
+id: 6
+title: Add monorepo discovery and generation test coverage
+type: task
+status: closed
+priority: 1
+parent: 2
+blocked_by:
+- 5
+assignees:
+- kind-prism
+created_at: 2026-04-01T03:29:28.976366156Z
+updated_at: 2026-04-01T03:34:38.442683072Z
+closed_at: 2026-04-01T03:34:38.442681989Z
+---
+
+Discovered from #2.
+
+Add and update tests:
+- Unit tests for recursive discovery and recursion boundaries
+- Unit tests for ambiguous leaf-name selection failures
+- Integration tests for list output with monorepo leaf templates
+- Integration tests for end-to-end generation from discovered leaf templates
+- Add helper fixtures/utilities for nested monorepo test trees
+
+---
+COMMENT
+2026-04-01T03:34:38.439580189Z
+author: kind-prism
+
+Completed test coverage for monorepo behavior: added list integration tests for leaf-template discovery and nested recursion boundaries, added template-manager unit tests for ambiguous leaf-name failures and monorepo not-found behavior, added end-to-end generation integration test from discovered monorepo leaf templates, and added helper fixture utility create_monorepo_template for nested monorepo trees. Validation: bundle exec rspec passed (29 examples, 0 failures).

data/.beader/issues/7-document-monorepo-template-configuration-and-selection.yaml

@@ -0,0 +1,30 @@
+---
+id: 7
+title: Document monorepo template configuration and selection
+type: task
+status: closed
+priority: 2
+parent: 2
+blocked_by:
+- 5
+assignees:
+- kind-prism
+created_at: 2026-04-01T03:29:29.005536422Z
+updated_at: 2026-04-01T03:35:05.533255090Z
+closed_at: 2026-04-01T03:35:05.533254332Z
+---
+
+Discovered from #2.
+
+Document monorepo usage in README:
+- Describe monorepo: true semantics
+- Describe recursive traversal behavior through monorepo containers
+- Describe subtemplate-only selection behavior
+- Document ambiguity error behavior and expected resolution
+
+---
+COMMENT
+2026-04-01T03:35:05.529805865Z
+author: kind-prism
+
+Updated README with a new monorepo template section documenting monorepo: true semantics, recursive traversal through monorepo containers, leaf-only template selection using subtemplate names, and ambiguity error behavior when duplicate leaf names exist. Validation: bundle exec rspec passed (29 examples, 0 failures).

data/.beader/meta.yaml

@@ -0,0 +1 @@
+next_id: 8

data/.gitignore

@@ -0,0 +1,16 @@
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+*.bundle
+*.so
+*.o
+*.a
+*.swp
+mkmf.log
+*.gem

data/.rspec

@@ -0,0 +1,2 @@
+--format documentation
+--color

data/Gemfile

@@ -0,0 +1,3 @@
+source 'https://rubygems.org'
+
+gemspec

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2015 TheNotary
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,154 @@
+# Foobar Templates: A Pain-Free Project Templator
+[![Gem Version](https://badge.fury.io/rb/foobar_templates.svg)](https://badge.fury.io/rb/foobar_templates)
+
+Foobar Templates allow users to define project templates in the most native form to all technologist: Directory Structures, short commands, and helpful commands that make the tool's usage completely visible!
+
+Programming often involves a lot of boilerplate and configuration "boot strapping" before you can get going actually writing any code.  To automate this aspect of creating new projects and microservices, foobar_templates allows you to run a simple command `foobar_templates -t my-c-embedded-template project-name` and it will clone a template you've made with exact specifications, update the names of files and references within the files to match your project name, run any commands specified in your template.  What once would have been a 5-10 minute distraction of remembering and implementing all those little patterns, testing dependencies, and pipeline definitions now happens immediately with a single command.
+
+The most beneficial aspect of Foobar Templates is that it allows you to specify exactly how you want your 'default starting project' to look, rather than rely on what someone else thought would be generally helpful.
+
+### Installation
+
+I highly recommend the `foobar` alias!
+
+```bash
+gem install foobar_templates
+foobar_templates --install-public-templates
+
+echo "alias foobar='foobar_templates'" >> ~/.bashrc
+source ~/.bashrc
+```
+
+#### List Available Templates
+
+```bash
+$  foobar_templates -l
+PREDEFINED:
+  default - A basic ruby gem
+  service - A gem that allows installation as a service to run as a daemon
+
+MISC:
+  my_service -
+
+EMBEDDED:
+  arduino
+```
+
+### Usage
+
+These commands will create a new gem named `project_name` in `/tmp/project_name`:
+
+```bash
+$  cd /tmp
+$  foobar_templates -t arduino project_name
+```
+
+You'll find a project skeleton in ~/.foobar/templates/my_service that you can customize to your liking.
+
+### Configuration
+
+Configuration is stored in `~/.foobar/config` (created automatically on first run). At minimum, you need your git user name and email configured:
+
+```bash
+git config --global user.email your-public-gh@email.com
+git config --global user.name YOUR_GH_NAME
+```
+
+## Create Your Own Template
+
+> **WIP:** We're actively refactoring the template system. `constant_array` has been dropped and this may cause the ruby template to break. `unprefixed_name` and `unprefixed_pascal` have also been removed.
+
+###### Overview
+- Define the project as a working codebase using `foo-bar` as the project name
+- All name variants (`foo_bar`, `FooBar`, `FOO_BAR`, etc.) will be auto-replaced when generating a new project
+- Use `FOO_` prefixed placeholders for non-name variables (e.g., `FOO_AUTHOR`, `FOO_EMAIL`)
+- Add a `foobar.yml` file to the template to make it available for use
+- Run `foobar_templates --copy-to-templates` to convert an existing project's name variants into foo-bar placeholders
+- Use the template to kick off a new project, `foobar_templates -t my-template first-test`
+
+To create your own template, just create a new project using the technologies you'd like.  Place this project in `~/.foobar/templates/my-template`.  Once it's done, it's a good idea to create a git commit.  Then run something to the effect...
+
+```bash
+$  echo "category: frontend"    > foobar.yml
+$  echo "purpose: frontend"    >> foobar.yml
+$  echo "language: javascript" >> foobar.yml
+
+$  foobar_templates --copy-to-templates
+```
+
+Change the foobar.yml contents to what makes sense for your template.  The `--copy-to-templates` command will prompt you for the template's folder name (defaults to the current project's basename) and the `category` to record in `foobar.yml` (defaults to the existing value, or `misc`), then replace all occurrences of your project's name variants with `foo-bar` template placeholders.
+
+#### Categorizing Your Template
+
+You can specify the `category` of the gem by editing the `foobar.yml` file in each template's root.  Categories are just used for organizing the output when you run `foobar_templates --list`.  Here's an [example](https://github.com/TheNotary/template-html-css-js/blob/main/foobar.yml).
+
+#### Monorepo Template Collections
+
+You can organize templates in nested directories by marking a directory as a monorepo container:
+
+```yaml
+monorepo: true
+```
+
+When a directory is marked with `monorepo: true`, Foobar Templates treats it as a container and recursively scans child directories for templates. A child is treated as a template when it has its own `foobar.yml` and is not marked `monorepo: true`.
+
+Container-level files are ignored for generation. Only discovered leaf templates are selectable and usable with `foobar_templates`.
+
+Example layout:
+
+```text
+~/.foobar/templates/template-platform/
+  foobar.yml              # monorepo: true
+  template-api/
+    foobar.yml            # normal template config
+    foo-bar.rb
+  template-ui/
+    foobar.yml            # normal template config
+    foo-bar.rb
+```
+
+In this example, select templates by leaf name:
+
+```bash
+foobar_templates -t api my-service
+foobar_templates -t ui my-frontend
+```
+
+If multiple monorepo leaves share the same name, Foobar Templates fails with an ambiguity error and shows the conflicting paths so one can be renamed.
+
+#### Template Prefix Stripping
+
+Some people sort their repos with prefixes...  For instance, you might want to create a repo named `tool-go-my-tool` but have the project file take on the name `my-tool` and ignore those descriptive prefixes?
+
+You can do that!  Just setup your `foobar.yml` as below:
+```yaml
+purpose: tool
+language: go
+```
+
+You can also set the prefix explicitly in `foobar.yml`:
+```yaml
+prefix: "my-custom-prefix-"
+```
+
+#### Customizing Your Own Templates
+
+Place your own templates in `~/.foobar/templates`.  You can populate it with examples by running `foobar_templates --install-public-templates` which will effectively clone down a few sample git repos into the templates folder for you such as [Go-cli](https://github.com/TheNotary/template-go-cli) for instance.
+
+You'll get a good idea as to the possibilities by inspecting the various templates I've opensourced under my github org, e.g. [template-ruby-cli-gem](https://github.com/TheNotary/template-ruby-cli-gem).
+
+To pull up a list of available variables, run this command
+
+```
+$  foobar_templates --cheat-sheet
+```
+
+If you would find additional variables handy, set me up with a PR and assuming it seems widely helpful, I'll merge it right as soon as I can.   The implementation for the variables is largely found in [gem.rb](https://github.com/TheNotary/foobar_templates/blob/main/lib/foobar_templates/cli/template_generator.rb#L59).
+
+#### Quick Tips Regarding Project Templates
+
+- Templates are working code using `foo-bar` as the canonical project name
+- Name variants (`foo_bar`, `FooBar`, `fooBar`, `FOO_BAR`, `Foo::Bar`, `Foo Bar`, `foo/bar`) are all auto-replaced
+- Use `FOO_` prefixed placeholders for non-name variables: `FOO_AUTHOR`, `FOO_EMAIL`, `FOO_GIT_REPO_URL`, etc.
+- Running `foobar_templates --cheat-sheet` will list off available template variables
+- File **names** containing `foo-bar` or `foo_bar` will have those replaced by the project name

data/Rakefile

@@ -0,0 +1,55 @@
+require 'rake'
+require 'rspec/core/rake_task'
+
+GEM_NAME = "foobar_templates"
+GEM_SPEC = "#{GEM_NAME}.gemspec"
+
+desc "Build #{GEM_NAME} gem"
+task :build do
+  system "gem build #{GEM_SPEC}"
+  FileUtils.mkdir_p "pkg"
+  FileUtils.mv Dir.glob("#{GEM_NAME}-*.gem"), "pkg/"
+end
+
+desc "Install #{GEM_NAME} gem locally"
+task install: :build do
+  system "gem install pkg/#{Dir.children('pkg').sort.last}"
+end
+
+desc "Build and push #{GEM_NAME} gem to RubyGems"
+task release: :build do
+  gem_file = Dir.glob("pkg/#{GEM_NAME}-*.gem").sort.last
+  system "gem push #{gem_file}"
+end
+
+desc "Run unit specs"
+RSpec::Core::RakeTask.new(:unit) do |t|
+  t.rspec_opts = %w(-fd -c)
+  t.pattern = "./spec/unit/**/*_spec.rb"
+end
+
+desc "Run integration specs that are very high level"
+RSpec::Core::RakeTask.new(:integration) do |t|
+  t.rspec_opts = %w(-fd -c)
+  t.pattern = "./spec/integration/**/*_spec.rb"
+end
+
+desc "Run all specs"
+RSpec::Core::RakeTask.new(:spec) do |t|
+  t.rspec_opts = %w(-fd -c)
+end
+
+# this is for running tests that you've marked current... eg: it 'should work', current:  true do
+RSpec::Core::RakeTask.new(:current) do |spec|
+  spec.pattern = 'spec/**/*_spec.rb'
+  spec.rspec_opts = ['--tag current']
+end
+
+# alias for current
+RSpec::Core::RakeTask.new(:c) do |spec|
+  spec.pattern = 'spec/**/*_spec.rb'
+  spec.rspec_opts = ['--tag current']
+end
+
+task default:  :spec
+task test:  :spec

data/bin/foobar_templates

@@ -0,0 +1,72 @@
+#!/usr/bin/env ruby
+
+require 'optparse'
+require 'foobar_templates'
+
+
+Signal.trap("INT") { exit 1 }
+options = {}
+
+parser = OptionParser.new do |opts|
+  opts.banner = "Usage: #{File.basename($0)} [options] GEM_NAME"
+
+  opts.on("-t", "--template TEMPLATE", "Specify a template") do |template|
+    options[:template] = template
+  end
+
+  opts.on("-l", "--list", "List available templates") do
+    puts FoobarTemplates.list
+    exit
+  end
+
+  opts.on("-c", "--cheat-sheet", "Show list of variables available in templates") do
+    puts FoobarTemplates.cheat_sheet
+    exit
+  end
+
+  opts.on("-v", "--version", "Show version") do
+    puts FoobarTemplates.version
+    exit
+  end
+
+  opts.on("--install-public-templates", "Install public templates") do
+    FoobarTemplates.install_public_templates
+    exit
+  end
+
+  opts.on("--setup-personal-templates", "Create a personal mono-repo template collection") do
+    FoobarTemplates.setup_personal_templates
+    exit
+  end
+
+  opts.on("--copy-to-templates", "Exports the current project into your personal templates repo, converting it to a template") do
+    FoobarTemplates.dir_to_template
+    exit
+  end
+
+  opts.on(nil, "--help", "Show help") do
+    puts opts
+    puts FoobarTemplates::HELP_MSG
+    exit
+  end
+end
+
+# fyi parser.parse! splices options out of ARGV, so gem_name doesn't need to be specified first
+parser.parse!
+
+if ARGV.empty?
+  puts parser
+  puts FoobarTemplates::HELP_MSG
+  exit 1
+end
+
+if ARGV.length > 1
+  puts "Error: there were unrecognized parameters specified in command"
+  puts FoobarTemplates::HELP_MSG
+  exit 1
+end
+
+
+gem_name = ARGV.first
+FoobarTemplates.generate_template(options, gem_name)
+

data/changelog

@@ -0,0 +1,107 @@
+** Unreleased **
+  - Rename: project renamed from `bundlegem` to `foobar_templates`. Module is now `FoobarTemplates`, executable is `foobar_templates`, per-template config file is `foobar.yml`, and user config/templates live under `~/.foobar/`. No backward-compatibility shims.
+
+** Planned 0.2.x **
+  - Feature: templates can declare a `name_validation:` block in bundlegem.yml with two optional keys: `reserved_names` (exact-match denylist) and `regex_validator` (a Ruby regex the project name must match). Validation runs after the built-in regex check and before any files are written. All checks happen in pure Ruby — no shell, no cross-platform concerns.
+  - Removed the hardcoded ruby-cli-gem constant-collision check from core; templates now declare their own naming rules via name_validation.
+
+** 0.2.0 **
+  - Feature: improves stdout feedback to enhance UX
+  - Feature: hides stack trace when user is simply missing a bundlegem.yml file
+  - Feature: allows interpolation of template variables within bootstrap_command
+  - Feature: adds a 'config[:title]' variable
+  - Bugfix: fixes issue where .git and it's subfolders were being created from the source template repo which wasted time
+  - Bugfix: fixes a performance issue where shelling out to git check-ignored was being performed many times within high frequency loops
+  - Bugfix: fixes bug where not specifying the category of a template apparently causes the list function to crash
+  - Bugfix: Cleans out dependencies that are no longer used
+  - Bugfix: Cleaned out tons of dead code and addressed tech debt I've been putting off since 1.8.5
+  - Bugfix: Changes working directory before running bootstrap_commands
+
+** 0.1.0 **
+  - Feature: Drops .bundlegem file in favor of bundlegem.yml in templates
+  - Feature: Introduces `--to-template` switch to add a `.tt` extension to all files in the current directory
+  - Feature: Enables execution of bootstrap_commands listing in bundlegem.yml
+  - Feature: Cleans out built-in templates in favor of externally managed templates
+  - Bugfix:  Prevents creation of template files that are gitignored
+
+** 1.0.0 **
+  - Feature: Greatly expands the template interpolation values
+  - Bugfix: misc cleanup
+
+** 0.0.14 **
+  - Bugfix:  The project didn't work with ruby 3 due to use of the method `exists?`???
+
+** 0.0.13 **
+  - Adds new built-in java template
+
+** 0.0.12 **
+  - Feature:  File mode (permissions) is now cloned from source template file's permissions to dest
+  - Bugfix: project names may now contain hyphens
+  - Feature:  java project template added to best templates
+  - Feature:  python project template added to best templates
+
+** 0.0.11 **
+  - Bugfix: config[:bundler_version] was listing the version of bundlegem not bundler
+
+** 0.0.10 **
+  - Feature: tweaks built-in templates
+
+** 0.0.9 **
+  - Bugfix:  there were misconfigurations with the Rakefiles for cli_gems and c_ect gems that were corrected
+  - Feature: `--version` option added
+
+** 0.0.8 **
+
+  - Bugfix: fixes bug where git clone was attempted even when the a clone
+    already took place in a prior run
+  - Bugfix: fixes bug where I thought I was using something cool like figaro
+    but was not
+  - Bugfix: fixes bug where configuration wasn't loaded before running
+    --install-public-templates
+  - Bugfix:  fixes bug where require pry was left in
+
+** 0.0.7 **
+
+  - Feature:  Ability to load templates from github via --install-public-templates
+  - Feature:  Make each user defined gem have a subfolder that is the exact
+    project structure, so the readme for the gem can exist without fear of it
+    being copied into new projects
+  - Feature:  Gem's display names are based on what's specified in their
+    respective root .bundlegem
+  - Feature:  Allow better CLI parsing so -t t_name can be the first couple
+    arguments or at the end
+  - Bugfix: cli_gem and c_ext_gem now show up in the list
+  - Bugfix: cli_gem and c_ext_gem had typos fixed
+
+** 0.0.6 **
+    - Feature:  List now indicates default template
+    - CORE:  Created TemplateManager for working with templates
+    - BUG:  Accidentally tracked in a test gem project and fixed tests to not
+      change directory into a test area for creating new gems.
+    - BUG:  newgem template didn't have a dot in .gitignore.tt
+
+** 0.0.5 **
+  - Bug in 0.0.3 that broke building template gems fixed
+    * Template Directories part of code was being skipped for built in templates, but not all of it
+  - Bug where sub directories were not being explicitly created
+  - Added integration test just to make sure the built-in templates can be generated without problems
+  - Cleaned up internal API and how the binary works
+
+** 0.0.4 **
+  - Tell the user what files are being created
+  - Created config['git_repo_url'] variable to be used in templates
+
+** 0.0.3 **
+    - CMD:  --list to list templates (with descriptions)
+    - Raise error when project name already exists, do not overwrite!
+    - Raises error if none of the files in the template directory end in .tt
+    - Create even empty folders
+
+** 0.0.2 **
+    - Added default gem template 'service'
+    - Better syntax of bundlegem gem_name -t template_name
+    - CMD:  --help to display a help message
+
+** 0.0.1 **
+  - Very basic prototype that allows you to specify templates in
+    ~/.bundlegem/templates