feat: add IssueBadge app (link-as-an-app, Automation)

[issuebadge2026]

What does this PR do?

Adds IssueBadge to the App Store as a link-as-an-app entry in the Automation category. IssueBadge issues verifiable digital certificates; with Cal.com it lets hosts send every attendee a certificate of attendance/completion automatically when a meeting, class or workshop ends (via a Cal.com webhook → IssueBadge endpoint).

Same structure as #29819 (Clara) and #27840 (Caretta): no runtime code, listing links out to the setup guide.

Files:

• packages/app-store/issuebadge/config.json — slug issuebadge, variant: automation, externalLink → https://issuebadge.com/h/integration/cal-com
• packages/app-store/issuebadge/DESCRIPTION.md + static/ (icon.svg, 3 screenshots 1200×900)
• apps.metadata.generated.ts / redirect-apps.generated.ts — registered alphabetically (same result as yarn app-store:build)

Fixes #30036

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox. — N/A (app listing only)
• I confirm automated tests are in place that prove my fix is effective or that my feature works. — N/A, no runtime code (link-as-an-app)

How should this be tested?

1. Run the app store locally (yarn dev), open /apps/issuebadge → the listing renders with icon, description and screenshots.
2. Click Install → opens the external guide in a new tab (externalLink.newTab: true).
3. yarn app-store:build produces no further changes to the generated files.

Checklist

• My code follows the style guidelines of this project
• I haven't checked if my changes generate no new warnings
• I haven't checked if new and existing unit tests pass locally with my changes

[github-actions]

Welcome to Cal.diy, @issuebadge2026! Thanks for opening this pull request.

A few things to keep in mind:

• This is Cal.diy, not Cal.com. Cal.diy is a community-driven, fully open-source fork of Cal.com licensed under MIT. Your changes here will be part of Cal.diy — they will not be deployed to the Cal.com production app.
• Please review our Contributing Guidelines if you haven't already.
• Make sure your PR title follows the Conventional Commits format.

A maintainer will review your PR soon. Thanks for contributing!

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c0b78c30-65c1-4caf-9378-262466370eee

📥 Commits

Reviewing files that changed from the base of the PR and between 176037d and 87cc0be.

⛔ Files ignored due to path filters (6)

• packages/app-store/apps.metadata.generated.ts is excluded by !**/*.generated.*
• packages/app-store/issuebadge/static/1.png is excluded by !**/*.png
• packages/app-store/issuebadge/static/2.png is excluded by !**/*.png
• packages/app-store/issuebadge/static/3.png is excluded by !**/*.png
• packages/app-store/issuebadge/static/icon.svg is excluded by !**/*.svg
• packages/app-store/redirect-apps.generated.ts is excluded by !**/*.generated.*

📒 Files selected for processing (2)

• packages/app-store/issuebadge/DESCRIPTION.md
• packages/app-store/issuebadge/config.json

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

Adds the IssueBadge app-store configuration with integration metadata and an external setup link. Adds documentation for certificate generation, verification, sharing, duplicate prevention, branding, webhook configuration, supported triggers, and integration setup.

Merge Risk: ⚪ Minimal · up to f88cb

This change adds a localized IssueBadge app listing and external setup link without runtime behavior changes; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Linked Issues check	❓ Inconclusive	The reviewable configuration and documentation satisfy the core IssueBadge App Store objectives. Verification is incomplete for the generated registrations and static assets because the relevant files…	Review the excluded generated files and static assets to confirm the alphabetical metadata and redirect registrations, icon, and screenshots required by issue #30036. The excluded files are packages/app-store/apps.metadata.generated.ts, `…

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the primary change: adding IssueBadge as a link-as-an-app in the Automation category.
Description check	✅ Passed	The description accurately describes the IssueBadge App Store listing, external setup guide, files, testing steps, and lack of runtime code.
Out of Scope Changes check	✅ Passed	The reviewable changes are limited to the IssueBadge App Store configuration and documentation, which directly support the linked issue. No unrelated code changes are shown.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…

Full details: Linked Issues check

Explanation

The reviewable configuration and documentation satisfy the core IssueBadge App Store objectives. Verification is incomplete for the generated registrations and static assets because the relevant files were excluded by path filters: apps.metadata.generated.ts and redirect-apps.generated.ts by !**/*.generated.*, plus icon.svg and the three PNG screenshots by their respective extension filters.

Resolution

Review the excluded generated files and static assets to confirm the alphabetical metadata and redirect registrations, icon, and screenshots required by issue #30036. The excluded files are packages/app-store/apps.metadata.generated.ts, packages/app-store/redirect-apps.generated.ts, packages/app-store/issuebadge/static/icon.svg, packages/app-store/issuebadge/static/1.png, packages/app-store/issuebadge/static/2.png, and packages/app-store/issuebadge/static/3.png. Ensure yarn app-store:build produces no additional changes.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[CLAassistant]

All committers have signed the CLA.

[github-actions]

This PR has been marked as stale due to inactivity. If you're still working on it or need any help, please let us know or update the PR to keep it active.

[issuebadge2026]

CLA is now signed and the branch is updated against main. Still active and ready for review whenever a maintainer has a moment — no runtime code, just the link-as-an-app listing (same structure as Clara / Caretta). Thanks!