-
Introduction
- Understanding Matomo
-
Matomo Core development
- Contributing to Matomo Core
- Contributing to Matomo Plugins
- Coding Standards
- Using GitHub Issues
- Pull Requests and Reviews
- The Core Team Workflow
- Maintaining Plugins
- Maintaining Translations
- Matomo APIs
- Debugging Core
- Profiling Code
- Reproducing Issues
- FAQs
- Core Components
- Composer dependencies
- Release Management
- Using GitHub Actions
- Matomo's Roadmap
- Matomo Plugin development
- Web Interface
- Utils
- Reporting API
- Data Model
- Tests
- Tools
-
Plugin Development
This documentation is for an outdated Matomo version.
Click here if you want to read this article for the latest version.
Click here if you want to read this article for the latest version.
Contributing to Matomo Plugins
Commit message keyword to not track changes.
After your pull request is accepted and merged, Matomo uses webhooks to keep track of commits in the main branch.
All commit messages for a plugin are sent to the team on a regular interval. This way the team knows a new version of a plugin needs to be released. However, if a merged commit should not result in a new release (for example because it only fixes tests), then you need to include [ignore_release] keyword in your commit message. This way the plugins team won't be notified about this commit.
Example commit message: {YOUR_COMMIT_MESSAGE} [ignore_release]