ianwremmel/boilerize

boilerize applies common config to an existing JavaScript repo

boilerize's Issues

github password not saved?

I think I've been prompted for it more often than I should be.

An in-range update of @ianwremmel/eslint-config is breaking the build 🚨

Version 1.2.0 of @ianwremmel/eslint-config just got published.

Branch	Build failing 🚨
Dependency	@ianwremmel/eslint-config
Current Version	1.1.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @ianwremmel/eslint-config is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

• ❌ ci/circleci Your tests failed on CircleCI Details

Release Notes

v1.2.0

1.2.0 (2017-02-05)

Features

• config: remove "raw" folder in favor of @ciscospark/eslint-config; use "all" configs for (65354551)

Commits

The new version differs by 8 commits .

• 7d2d19a Merge pull request #6 from ianwremmel/no-raw
• 6535455 feat(config): remove "raw" folder in favor of @ciscospark/eslint-config;
• 9a02f77 Merge pull request #5 from ianwremmel/greenkeeper/initial
• 3db5006 chore(package): update dependencies
• 6d72737 Merge pull request #4 from ianwremmel/greenkeeper/eslint-plugin-jsx-a11y-4.0.0
• 40d04cf chore(package): update eslint-plugin-jsx-a11y to version 4.0.0
• b38e68c Merge pull request #3 from ianwremmel/greenkeeper/initial
• f45095e docs(readme): add Greenkeeper badge

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

format-readme should take README.md as its input

The unfortunate JSON->Markdown flow that currently exists is because there so far doesn't appear to be a compatible set of markdown parser, transformer, and renderer for javascript. This kinda sucks for end-users. Hopefully commonmark will finish their markdown outputter soon.

command: config

get/list/set config

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

On deployment, update github description with package.json description

change deployment name to production

command: automate

• create circle.yml
• configure circle to update the github.com description according to package description
• ensure package.json has a github url (does this go in format-package?)
• set node version in circle.yml according to package.json engines
• install semantic release
• add semantic release to circle.yml
• release 1.0.0
• tell circle to follow the project
• set the NPM_AUTH and GITHUB_TOKEN circle env vars
• disable push-to-master

If possible with circle API:

• build forks
• autocancel redundant builds

command: secrets

get/list/set secrets

Implement heroku deployment

Use inquirer to determine project defaults

https://www.npmjs.com/package/inquirer

Do you have a common config?
What is the module containing your common config?

Is this a node module?
Is this a browser project?
Is this a react project?
Will this project use es6 imports?
Does this project include CSS?
What license will you use?

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

keychain keys should include project name

toc includes sections that don't exist

replace nconf with rc

Detect github org, project name from .git folder, not .boilerizerc

toc includes pre-toc sections

add junit support for eslint

"lint:eslint": "eslint $([ -n \"$CI\" ] && echo '--format=junit --output-file=${CIRCLE_TEST_REPORTS}/eslint.xml' || echo '') --ignore-path .gitignore",

Add npm test command, add lint as posttest command

command: init

• add tooling inspired by react boilerplate
• lint staged before commit
• ensure github project exists
• setup eslint
• editor config

init and automate should just be the default action

maybe with a set of prompts

need to install peer dependencies for eslint config

command: format-package

Sort package.json according to predefined rules. Apply default values from boilerizerc

Allow for common config

Publish your config to npm and have boilerize try to require it?

command: init

• do everying npm init does
• move default actions into init
  • github setup
  • circle setup
• create initial readme
• accept a license string and fetch the specified license from github's license site

Clean up prompts

• add @prompt decorator
• ensure passwords never go into the config object
• automate storing passwords as secrets
• add an @cache decorator (which stores the result of a function in secrets)?

npm install -g doesn't work

Looks like some combination of global installation and babel-register don't cooperate. need to fix with a build step.

command: export-config

Spits out a new project to use as common config
new project should:

• include circle ci/semantic-release
• have a github url

If the current project reference a common config, then this should check it out, copy the local config, and open a PR with the diff.

Publish 1.0.0 once semrel is setup