Thank you for your interest in contributing. This document explains how to get involved, report issues, and submit changes.
Be respectful. Constructive criticism is welcome; hostility is not.
- Report bugs
- Suggest features
- Improve documentation
- Submit code via pull requests
Before opening an issue, please check that it has not already been reported.
When filing a bug report, include:
- Your backend (FreshRSS, Miniflux, etc.) and its version
- Your browser and OS
- Steps to reproduce the issue
- Expected vs. actual behavior
- Any relevant logs or screenshots
Open a feature request issue and describe:
- The problem you are trying to solve
- Your proposed solution
- Any alternatives you considered
- Node.js 20+
- npm 9+
- A running FreshRSS or Miniflux instance (or a test account)
git clone https://github.com/your-username/open-airss.git
cd open-airss
npm install
cp .env.example .env
# Fill in your backend URL in .env
npm run dev- Fork the repository
- Create a branch from
main:git checkout -b fix/your-bug-description
- Make your changes
- Run the tests:
npm run test - Run the linter:
npm run lint
- Commit with a clear message (see below)
- Push and open a pull request against
main
Follow the Conventional Commits format:
type(scope): short description
Examples:
feat(reader): add keyboard shortcut for marking all as read
fix(api): handle expired session tokens correctly
docs(readme): update Docker instructions
Types: feat, fix, docs, style, refactor, test, chore
| Type | Pattern |
|---|---|
| Feature | feat/short-description |
| Bug fix | fix/short-description |
| Docs | docs/short-description |
| Refactor | refactor/short-description |
By contributing to Open-AIRSS, you agree that your contributions will be licensed under the AGPL-3.0.