Shared tslint config for DCOS projects using typescript


010.1.13 years ago4 years agoMinified + gzip package size for @dcos/tslint-config in KB



Shared tslint config for DCOS projects using typescript


You should follow conventional commit formatting rules, as they provide a framework to write explicit messages that are easy to comprehend when looking through the project history and enable automatic change log generation.

These Guidelines were written based on AngularJS Git Commit Message Conventions.

<type>[optional scope]: <description>

[optional body]

[optional footer]

Release / Publishing

After your PR is merged to master to cut a release is very simple, assuming you are on master branch follow the steps below.

Fetch all git tags

git fetch origin --tags

Then run the command to automatically update the package.json, changelog.md and create a new release commit.

npm run release

Now push the latest commit and the tag created (run git tag to see all tags).

git push origin master && git push origin TAG_VERSION

And finally publish to npm.

npm publish

If you find any bugs or have a feature request, please open an issue on github!

The npm package download data comes from npm's download counts api and package details come from npms.io.