Package Exports
- ismetjs
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (ismetjs) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
>_ A CLI tool to automatically generate and manage git repo issues from code comments.
Overview
// $(ismet) I'm going to become a Github issue!
console.log('Hello, World!');Ismet combines the ease of use of TODO comments with the practicality of Github issues. It manages your Github issues by parsing your project for $(ismet) comments and manages your issues accordingly. Instead of using TODO comments, use $(ismet) comments and Ismet will do the rest.
Issues managed by Ismet will have the label ismet, so your existing issues won't be edited.
It is recommended to run Ismet either in a pre-commit hook or in CI. See below for instructions on how to setup Ismet to run on CI.
Installation
npm install -g ismetjsVerify your installation:
ismet --versionUsage
To see all available commands:
ismet --helpCurrently, ismet only supports JavaScript files.
Create comments on your code using the $(ismet) directive.
// $(ismet) this is an ismet comment
/* $(ismet) so is this */
/**
* You can place the directive anywhere $(ismet)
*/Currently, ismet only supports Github remotes.
By default, node_modules and everything inside .gitignore is ignored automatically. To run ismet and create your issues. :
ismet <directory>List
If you need to find a location of a comment or you want to see issues to be created before submitting them on Github, you can list all $(ismet) comments in your project with:
ismet --list
ismet -lLogging out
If you want to log out from ismet:
ismet --logoutRunning in CI
Running ismet on CI requires a personal GITHUB_TOKEN to be set as an environment variable. Your token needs to have repo access.