ellerbrock/conventional-changelog-angular-emoji

:thumbsup: Emoijis for the Angular Commit Guidelines with Emojis

conventional-changelog-angular-emoji

conventional-changelog angular-emoji preset

Angular Git Commit Guidelines with Emojis

This is a fork from conventional-changelog-angular.

install with npm

npm install --save-dev conventional-changelog-angular-emoji

install with yarn

yarn add --dev conventional-changelog-angular-emoji

Update Information:

Update commit convention from Angular 1x to Angular 2x.

• added: build, ci

Preview:

feat(xxx): ✨ Features your commit message

fix(xxx): 🐛 Bug Fixes

docs(xxx): 📖 Documentation

style: 💎 Styles

refactor: 📦 Code Refactoring

perf(xxx): 🚀 Performance Improvements

test(xxx): 🚨 Tests

build(xxx): 👷 Build

ci(xxx): 💻 Continuous Integration

chore(xxx): 🎫 Chores

revert(xxx): 🔙 Reverts

Video Course on egghead.io

• Writing conventional commits with commitizen
• Committing a new feature with commitizen

Contact / Social Media

Get the latest News about Web Development, Open Source, Tooling, Server & Security

License

Copyright (c) 2016 Maik Ellerbrock

conventional-changelog-angular-emoji's Issues

An in-range update of coveralls is breaking the build 🚨

The devDependency coveralls was updated from 3.0.2 to 3.0.3.

🚨 View failing branch.

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

coveralls is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for Dependency security updates

As suggested by NPM and Snyk.

Commits

The new version differs by 1 commits.

• aa2519c dependency security audit fixes from npm & snyk (#210)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of jshint is breaking the build 🚨

The devDependency jshint was updated from 2.9.6 to 2.9.7.

🚨 View failing branch.

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

jshint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 5 commits.

• 01bf8c6 v2.9.7
• 71f2f1f [[TEST]] Assert CLI behavior: stdin w/o filename
• 3a8ef8b Added Spotify to companies who use JSHint (#3333)
• 80c7fda [[CHORE]] Relocate development dependency
• f70250b [[CHORE]] Relocate development dependencies

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of through2 is breaking the build 🚨

The devDependency through2 was updated from 2.0.3 to 2.0.4.

🚨 View failing branch.

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

through2 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 4 commits.

• e839de7 2.0.4
• c778d93 added coverage
• 0293a9e replace function into arrow function in README
• 40d2668 update to latest shiny stuff

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Show all commit types in log

I've recently forked this library myself and noticed that a change you made was to not return early as the 'angular' one does so it shows all commit types in logs, any reason for that and not following the angular convention?

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

The devDependency mocha was updated from 6.0.0 to 6.0.1.

🚨 View failing branch.

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

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v6.0.1

6.0.1 / 2019-02-21

The obligatory round of post-major-release bugfixes.

🐛 Fixes

These issues were regressions.

• #3754 - Mocha again finds test.js when run without arguments (@plroebuck)
• #3756 - Mocha again supports third-party interfaces via --ui (@boneskull)
• #3755 - Fix broken --watch (@boneskull)
• #3759 - Fix unwelcome deprecation notice when Mocha run against languages (CoffeeScript) with implicit return statements; returning a non-undefined value from a describe callback is no longer considered deprecated (@boneskull)

📖 Documentation

• #3738 - Upgrade to @mocha/docdash@2 (@tendonstrength)
• #3751 - Use preferred names for example config files (@Szauka)

Commits

The new version differs by 9 commits.

• 6d3d6b4 Release v6.0.1
• 2146ece update CHANGELOG.md for v6.0.1
• 7c9221d backout deprecation of value returned from suite; closes #3744
• b7cfceb fix --watch not finding any files to execute; closes #3748
• b836d73 Upgrade docdash version - issue #3663
• 7926f47 fix --ui issues, closes #3746
• 00f2ed9 dev dep upgrades from "npm audit" and "npm upgrade"
• 34afb1a fix(cli/run.js): Revert default glob to match Mocha-5.2
• 6d5a0db Bring the example congfiguration file in line with the documentation. (#3751)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴