_   _           _                _
  /_\ | | ___ _ __| |_  /\  /\_   _| |__
 //_\\| |/ _ \ '__| __|/ /_/ / | | | '_ \
/  _  \ |  __/ |  | |_/ __  /| |_| | |_) |
\_/ \_/_|\___|_|   \__\/ /_/  \__,_|_.__/

AlertHub is a simple tool written with NodeJS to get alerted from GitHub and GitLab releases, tags and commits.

When you watch a release over GitHub, you also auto watch the issues and comments etc., however if you want to only follow new releases, or only commits or tags, there isn't a way to achieve this from GitHub directly.

There's been a service called sibbell.com, but they shut down on 15th May, 2018. That's why, I decided to make one for myself.

This simple cli tool watches the releases set in config, and notifies you with E-mail or PushBullet, and provides you an aggregated RSS feed which you can use in IFTTT or your personal feed reader.

Update 2018.11.28: GitHub now supports following the repositories' releases, however, it's still buggy for me, and they still don't cover the push notification feature which this tool offers.

Some people still wonder why this tool, which was released before GitHub release feature announced, yet exists, so I wanted to list the features as a bullet list:

• You can watch GitHub releases, tags, commits and issues
• You can also watch private GitHub repositories by providing an access token
• You can watch GitLab tags and commits
• You can watch 3rd party releases which are neither from GitHub nor GitLab
• You can get notified with e-mail when a new update to your watch list is published
• You can also get notified with push notification, using services PushBullet and / or PushOver
• You can also get notified using Telegram bots. Just put your bot to the channels, or get your chat id, provide the bot token and your updates will be carried through the Telegram bot.
• You can generate an aggreagated RSS feed with this tool for all your watches, which is sorted by date, and use this aggregated feed to source to your favorite news reader application, or to pipe to services such as IFTTT etc.
• Self-hosted. Also, no GUI. You can simply set it and forget it

• NodeJS 20.x or newer
• (Optional) PushBullet Api Key
• (Optional) PushOver Api Key
• (Optional) SMTP credentials to dispatch e-mail
• (Optional) Telegram API key and Chat ID for the messages to be dispatched.

You can install and run AlertHub with some simple steps:

1. Clone this repository or get the latest release version.
2. Navigate to the repository's folder, and run npm install to install dependencies.
3. Copy .env.example to .env and fill in your configuration values.

AlertHub includes a comprehensive Makefile that runs all commands through Docker, ensuring a consistent development environment across different systems.

• Docker installed on your system
• No need for Node.js locally - everything runs in containers

# Clone the repository
git clone https://github.com/Ardakilic/alerthub.git
cd alerthub

# Install dependencies
make install

# Initialize environment file
make init

# Run tests
make test

# Run tests with coverage
make test-coverage

# Run linting
make lint

# Fix linting issues automatically
make lint-fix

# Start the application
make start

The project includes comprehensive test suites for all utilities:

# Run all tests
make test

# Run tests with detailed coverage report
make test-coverage

# Watch mode for development
make test-watch

# Run specific test files (using shell)
make shell
npm test rssGenerator.test.js
npm test rssMonitor.test.js

The project uses Biome for fast linting and formatting:

# Check code quality
make lint

# Automatically fix issues
make lint-fix

# Check everything (lint + test + coverage)
make check-all

All commands run in a Node.js 22 container with:

• Image: node:22
• Working Directory: /app (mapped to your project folder)
• Environment: NODE_OPTIONS="--experimental-vm-modules" for ES modules support
• Volume Mount: Your project directory is mounted for live development

If you prefer running Docker commands directly:

# Run tests with coverage
docker run --rm -v "$(pwd)":/app -w /app -e NODE_OPTIONS="--experimental-vm-modules" node:22 npm run test:coverage

# Run linting
docker run --rm -v "$(pwd)":/app -w /app -e NODE_OPTIONS="--experimental-vm-modules" node:22 npm run lint

# Start the application
docker run --rm -v "$(pwd)":/app -w /app -e NODE_OPTIONS="--experimental-vm-modules" node:22 npm start

# Interactive shell for debugging
docker run --rm -it -v "$(pwd)":/app -w /app -e NODE_OPTIONS="--experimental-vm-modules" node:22 /bin/bash

For continuous integration, use the CI-specific targets:

# Run complete test suite with coverage for CI
make ci-test

# Run linting for CI
make ci-lint

These generate coverage reports in the ./coverage/ directory that can be uploaded to coverage services. 4. Run npm start or something like pm2 start npm -- start and run the application.

AlertHub now uses environment variables for configuration. Copy the .env.example file to .env and modify the values according to your needs:

cp .env.example .env

The configuration supports the following environment variables:

• INTERVAL: Feed check interval in milliseconds (default: 60000)
• USER_AGENT: User agent string for HTTP requests
• GITHUB_TOKEN: GitHub token to bypass rate limits and access private repos
• LOG_LEVEL: Logging level (debug, info, warn, error) (default: info)

PushBullet:

• PUSHBULLET_ENABLED: Enable PushBullet notifications (true/false)
• PUSHBULLET_ACCESS_TOKEN: Your PushBullet access token

PushOver:

• PUSHOVER_ENABLED: Enable PushOver notifications (true/false)
• PUSHOVER_USER: PushOver user key
• PUSHOVER_TOKEN: PushOver application token

Email:

• EMAIL_ENABLED: Enable email notifications (true/false, default: true)
• EMAIL_HOST: SMTP server hostname
• EMAIL_PORT: SMTP server port (default: 465)
• EMAIL_SECURE: Use secure connection (true/false, default: true)
• EMAIL_AUTH_USER: SMTP username
• EMAIL_AUTH_PASS: SMTP password
• EMAIL_FROM: From email address
• EMAIL_TO: Recipient email address(es)
• EMAIL_SUBJECT_PREFIX: Subject line prefix

Telegram:

• TELEGRAM_ENABLED: Enable Telegram notifications (true/false)
• TELEGRAM_TOKEN: Telegram bot token
• TELEGRAM_CHAT_ID: Telegram chat ID

• RSS_ENABLED: Enable RSS feed server (true/false, default: true)
• RSS_PORT: RSS server port (default: 3444)
• RSS_TITLE: RSS feed title
• RSS_DESCRIPTION: RSS feed description
• RSS_INCLUDE_FROM_EACH_REPOSITORY: Number of releases per repository (default: 10)
• RSS_COUNT: Total number of items in feed (default: 50)
• RSS_SITE_URL: Site URL for the RSS feed
• RSS_FEED_URL: Feed URL for self-reference

For repositories, you can use JSON format in environment variables:

• GITHUB_RELEASES: JSON array of GitHub repositories for releases
• GITHUB_TAGS: JSON array of GitHub repositories for tags
• GITHUB_COMMITS: JSON object mapping repositories to branch arrays
• GITHUB_ISSUES: JSON object mapping repositories to issue filter objects
• GITLAB_TAGS: JSON array of GitLab repositories for tags
• GITLAB_COMMITS: JSON object mapping repositories to branch arrays
• EXTRAS: JSON array of direct RSS feed URLs

Example:

GITHUB_RELEASES='["Ardakilic/alerthub","expressjs/express"]'
GITHUB_COMMITS='{"laravel/laravel":["*"],"acikkaynak/acikkaynak":["master"]}'

Create a .env file with your configuration and run:

docker run --name alerthub -d --env-file .env -p 3444:3444 ghcr.io/ardakilic/alerthub:2

docker run --name alerthub -d \
  -e GITHUB_RELEASES='["Ardakilic/alerthub","expressjs/express"]' \
  -e EMAIL_ENABLED=true \
  -e EMAIL_HOST=smtp.example.com \
  -e [email protected] \
  -e EMAIL_AUTH_PASS=yourpassword \
  -e [email protected] \
  -p 3444:3444 \
  ghcr.io/ardakilic/alerthub:2

I'll keep track of each release in the CHANGELOG.md.

Please refer to UPGRADING.md.

• Telegram Notifications
• Following GitLab releases
• Following BitBucket releases
• Multi user feature
• Per-repository webhooks
• Aggregated RSS
• Following commits and tags in addition to releases
• PushOver integration
• Following commits from a specific branch (GitHub and GitLab)
• Find a way to bring back GitHub private repositories support #80
• Gitea support #88
• You say!

MIT

Donations are kindly accepted to help develop my projects further.

BTC: 1QFHeSrhWWVhmneDBkArKvpmPohRjpf7p6

ETH / ERC20 Tokens: 0x3C2b0AC49257300DaB96dF8b49d254Bb696B3458

Stellar (XLM): GBTYNE5RDGH44E7VH4DNYB4NV72GCV5VUH6PJLCJY27JZRO2K7XUML2Q