@logdna/tail-file - npm Package Compare versions

Comparing version 2.0.5 to 2.0.6

CODE_OF_CONDUCT.md

CHANGELOG.md

		@@ -0,1 +1,5 @@
		# 2021-02-09, Version 2.0.6 (Stable)

		* [[b4934ce398](https://github.com/logdna/tail-file-node/commit/b4934ce398)] - fix: Move default branch to `main` and add contributors (Darin Spivey)

		# 2021-02-05, Version 2.0.5 (Stable)
		@@ -2,0 +6,0 @@

CONTRIBUTING.md

		@@ -8,12 +8,13 @@ # Contributing

		1. Fork the repo to create your own. This repo is called the origin repo.
		2. Work your changes on a branch in your repo.
		3. Submit your changes as a PR against the upstream repo.
		4. Maintainers review your changes. If they ask for changes, you work on your
		origin repo's branch. Otherwise, the branch is merged to upstream's main
		trunk.
		1. Fork the upstream repo to create your own repo. This repo is called the origin repo.
		2. Clone the origin repo to create a working directory on your local machine.
		3. Work your changes on a branch in your working directory, then add, commit, and push your work to your origin repo.
		4. Submit your changes as a PR against the upstream repo. You can use the upstream repo UI to do this.
		5. Maintainers review your changes. If they ask for changes, you work on your
		origin repo's branch and then submit another PR. Otherwise, if no changes are made,
		then the branch with your PR is merged to upstream's main trunk, the main branch.

		When you work in a triangular workflow, you have the upstream repo, the origin
		repo, and then your local clone of the origin repo. You fetch from upstream to
		local, push from local to origin, and then do a PR from origin to
		repo, and then your working directory (the clone of the origin repo). You do
		a `git fetch` from upstream to local, push from local to origin, and then do a PR from origin to
		upstream—a triangle.
		@@ -26,13 +27,20 @@

		Thank you for your contributions; we appreciate you!

		## License

		Note that we use a standard MIT license on this repo.
		Note that we use a standard [MIT](./LICENSE) license on this repo.

		## Issues and Bugs
		## Coding style

		Please use GitHub Issues to submit issues and bugs. Also, please open an issue
		before opening a PR to discuss any changes you think need to be made.
		Code style is enforced by [eslint][]. Linting is applied CI builds when a pull request
		is made. The rule set being enforced is provided by [eslint-config-logdna][]

		## Questions?

		Reach out in the GitHub Issues, or email us at `opensource at logdna.com`.
		The easiest way to get our attention is to comment on an existing, or open a new
		[issue][].

		[eslint]: https://eslint.org
		[eslint-config-logdna]: https://github.com/logdna/eslint-config-logdna
		[issue]: https://github.com/logdna/eslint-config-logdna/issues

package.json

		{
		"name": "@logdna/tail-file",
		"version": "2.0.5",
		"version": "2.0.6",
		"description": "A node.js version of unix's `tail -f` command",
		@@ -35,3 +35,24 @@ "main": "index.js",
		"homepage": "https://github.com/logdna/tail-file-node",
		"author": "LogDNA, Inc.",
		"author": {
		"name": "LogDNA, Inc.",
		"email": "help@logdna.com"
		},
		"contributors": [
		{
		"name": "Darin Spivey",
		"email": "darin.spivey@logdna.com"
		},
		{
		"name": "Jakub Jirutka",
		"email": "jakub@jirutka.cz"
		},
		{
		"name": "Ryan Mottley",
		"email": "ryan.mottley@logdna.com"
		},
		{
		"name": "Laura Santamaria",
		"email": "dev@nimbinatus.com"
		}
		],
		"license": "SEE LICENSE IN LICENSE",
		@@ -38,0 +59,0 @@ "eslintConfig": {

README.md

		@@ -1,2 +0,2 @@
		[![Coverage Status](https://coveralls.io/repos/github/logdna/tail-file-node/badge.svg?branch=master)](https://coveralls.io/github/logdna/tail-file-node?branch=master)
		[![Coverage Status](https://coveralls.io/repos/github/logdna/tail-file-node/badge.svg?branch=main)](https://coveralls.io/github/logdna/tail-file-node?branch=main)

		@@ -3,0 +3,0 @@ # TailFile

@logdna/tail-file - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics