Add discord noticiation workflow

[JGStyle]

This PR adds the same discord notification workflow for PRs that receive the label 'schau mi o'

For this to work, we would need to copy over / config the DISCORD_WEBHOOK_ID and DISCORD_WEBHOOK_TOKEN env vars (or configure as org level secret)

Summary by CodeRabbit

• New Features
  • Added automated Discord notifications for pull requests when a specific label is applied.
  • Notification messages now include the PR title, link, and author, making updates easier to track.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new GitHub Actions workflow file is added that fires on pull_request labeled events. When the label schau mi o is applied, a single job runs on ubuntu-latest and posts a Discord webhook message containing the PR title, URL, author, and a maintainer mention.

Changes

Discord PR Notification Workflow

Layer / File(s)	Summary
Workflow trigger, permissions, job condition, and Discord notification step .github/workflows/discord-notifications.yml	New workflow triggered on pull_request labeled events, restricted to contents: read permissions, with a notify job that runs only when the label equals schau mi o and posts a formatted message to Discord via appleboy/discord-action@v1.2.0 using DISCORD_WEBHOOK_ID and DISCORD_WEBHOOK_TOKEN secrets.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A label drops, the rabbit hops,
🐇 "Schau mi o!" the workflow pops!
It pings the Discord, spreads the word,
Of every PR seen and heard.
With webhook tokens, secrets tight,
The bunny keeps the team in sight! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: adding a Discord notification workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch add-discord-notification-workflow

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/discord-notifications.yml:
- Around line 16-19: The Discord notification step is using the mutable
appleboy/discord-action@v1.2.0 tag while handling webhook secrets. Update the
uses reference in the discord-notifications workflow to the current pinned
commit SHA for that action instead of the version tag, so the workflow stays
fixed to an immutable revision.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 052342cf-43c8-4fa0-b2ac-f3acd8f7ac9e

📥 Commits

Reviewing files that changed from the base of the PR and between 1f8ae8e and 6c7a3d3.

📒 Files selected for processing (1)

• .github/workflows/discord-notifications.yml

[rappm]

@Mtze can you add the secrets here?