Help Center and Support
Find answers to common questions, troubleshoot issues, and get in touch with our support team. We are here to help you get the most out of Engammo's automated release note generation.
Get in Touch
Email Support
Send us an email and we usually reply within one business day.
Send Email →Chat Assistant
Use the chat widget in the bottom corner of any page to get instant answers from our AI assistant, available to everyone around the clock.
Open Dashboard →Documentation
Browse our comprehensive documentation for setup guides, integration instructions, and detailed explanations of every feature.
Browse Docs →Common Issues
Step-by-step solutions for the most frequently reported issues.
Pull Requests Not Detected
Engammo is not generating release notes when PRs are merged.
- 1Verify the Engammo GitHub App is installed on the repository. Go to your GitHub organization settings and check the installed apps.
- 2Confirm the repository is selected in the Engammo dashboard under repository settings.
- 3Check that the PR was merged (not just closed) into the repository's target branch.
- 4Review the webhook delivery log in GitHub settings to ensure events are being sent successfully.
- 5If the issue persists, uninstall and reinstall the Engammo GitHub App from your GitHub settings.
Incorrect Release Note Categorization
Release notes are being assigned the wrong category (e.g., a bug fix is labeled as a feature).
- 1Check that your PR has appropriate labels. Engammo uses labels as the primary categorization signal.
- 2Check that the PR has a label Engammo recognizes, such as bug, fix, feature, enhancement, breaking, security, docs, or refactor.
- 3If no labels are present, the AI infers the category from PR content. Add descriptive labels for more accurate categorization.
- 4You can edit a note's title, description, and list of changes in the dashboard.
Slow Release Note Generation
Release notes are taking longer than expected to appear after a PR is merged.
- 1Generation usually completes within a minute. If notes take longer, check the status page at engammo.com/status.
- 2Large PRs with extensive diffs may take slightly longer to process due to the volume of code being analyzed.
- 3Verify that GitHub webhook delivery is not delayed by checking the Recent Deliveries tab in your GitHub App settings.
- 4If delays are persistent, contact support with your repository name so we can investigate.
Permission and Access Errors
Getting permission denied errors or unable to access repositories.
- 1Verify your role in the workspace. Members can generate and edit notes; only Admins and Owners can change repository settings, and only Owners can manage billing.
- 2Check that the GitHub App has access to the specific repository. Repository access can be limited during installation.
- 3If you recently changed your GitHub permissions, you may need to re-authenticate in Engammo.
- 4Workspace admins can manage members from Settings > Team.
Troubleshooting Guides
GitHub App Reinstallation
If the GitHub integration stops working, reinstall the Engammo GitHub App from your GitHub organization's Installed GitHub Apps page. Your existing release notes are preserved.
Webhook Debugging
GitHub logs all webhook deliveries. Go to your GitHub organization settings, select "Installed GitHub Apps," find Engammo, and click "App settings." The "Recent Deliveries" tab shows the status of each webhook event. A 200 status means the event was received successfully. A non-200 status indicates a delivery failure that should be reported to Engammo support.
Regenerating Release Notes
If a release note is inaccurate or incomplete, click the "Regenerate" button on the note detail page. This re-runs the AI analysis on the original PR data and produces a new summary. Regenerating replaces the current content, so copy any manual edits you want to keep first.
Managing Organization Members
Workspace admins can invite, remove, and change the roles of team members from Settings > Team. Available roles are Owner (billing and workspace deletion), Admin (repository settings and team management), and Member (generate and edit notes). Changes take effect immediately.
More Resources
Frequently Asked Questions
What are the support hours?
Email support is available on business days (CET). The AI chat assistant is available around the clock to everyone.
How do I report a bug?
Send a detailed bug report to [email protected]. Include your repository name, a description of the expected behavior, the actual behavior, and any relevant screenshots or webhook delivery logs. This helps us diagnose and resolve the issue quickly.
Is there a status page for service health?
Yes. Visit engammo.com/status to check current service health and recent incidents.
Can I request a feature through support?
Yes. Send feature requests to [email protected]. We review every request and consider it for our roadmap. You can view current plans on our roadmap page.
What information should I include in a support request?
Include your organization name, the affected repository, a description of the issue, steps to reproduce it, and any relevant error messages or screenshots. For webhook issues, include the GitHub webhook delivery ID from the delivery log.
Do you offer onboarding assistance for enterprise customers?
Yes. Enterprise customers can request an onboarding call to help connect repositories and configure settings.
How do I cancel my subscription?
Workspace owners can go to Settings > Billing and click "Manage Billing" to cancel in the billing portal. Your plan stays active until the end of the billing period, then generating new release notes stops until you subscribe again; existing notes stay in your workspace. Your data is kept unless you delete the workspace.
Is support available in languages other than English?
Currently, support is available in English only. Our documentation is also available in English, with localized versions planned for the future.
Need help getting started?
We can help you set up automated release notes for your GitHub repositories. Start a 14-day free trial, or email us about enterprise plans.