The issue tracker is only for technical support, bug reports and enhancement suggestions. If you have a question (or any concern related to the public hosting of the bot), please ask it in the Discord server instead of opening an issue.
If you wish to contribute to the MonitoRSS, feel free to fork the repository and submit a pull request. ESLint and StandardJS are used to enforce a consistent coding style, so having that set up in your editor of choice is a great boon to your development process.
All development happens on dev branches.
- Fork & clone this core repo
- Create a new branch from the dev branch
- Code!
- Run
npm run eslint
to run ESLint and automatically fix problems in coding style - Push your work to your fork and submit a pull request (before that you may need to merge the latest from upstream)
This will allow you to make changes and immediately testing the changes with the clone repo.
- Fork & clone this core repo
- In the core repo, create a new branch from the dev branch
- In the core repo, run
npm link
to set up the core dev environment in the global node modules for reference by the clone repo - Fork & clone the clone repository, and make sure you're on the dev branch
- In the clone repo, set it up by following the setup in documentation
- In the clone repo, run
npm link monitorss
to create a symlink to the core repo in the global node modules - Code in the core repo!
- In the core repo, run
npm run eslint
to run ESLint and automatically fix problems in coding style - In the clone repo, run the bot to test it
- Push your work to your fork and submit a pull request (before that you may need to merge the latest from upstream)
If you use an outdated version of npm, then you may run into a lock file conflict. More info here and here.
How do I know which version of npm comes with which version of Node.js ?