Update contact email in Code of Conduct

[theresantonie]

Replaced the outdated opensource@muenchendigital.io address with the new opensource@muenchen.de.

Summary by CodeRabbit

• Chores
  • Updated the Code of Conduct with revised contact information and minor grammatical corrections.

[coderabbitai]

Walkthrough

Updated enforcement contact information in the Code of Conduct by changing the email domain from muenchendigital.io to muenchen.de in two locations and corrected a minor grammatical inconsistency.

Changes

Cohort / File(s)	Summary
Code of Conduct metadata CODE_OF_CONDUCT.md	Updated enforcement contact email address (muenchendigital.io → muenchen.de) in two locations; applied minor grammatical correction (added "the" before "reporter of any incident")

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A whisker-twitch of text so fine,
The email hops to a new line,
From digital dreams to Munich's door,
Grammar polished—now it's more! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Update contact email in Code of Conduct" directly and accurately summarizes the main change in the pull request. The changeset's primary objective is to replace the outdated email address with a new one in the CODE_OF_CONDUCT.md file, which the title captures clearly and concisely. The title is specific enough to convey the meaningful change without unnecessary noise, and a teammate scanning the project history would immediately understand the purpose of this change. The title also appropriately leaves out the minor secondary grammatical adjustment, which is expected for a succinct title.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch emailadress

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5abcede and 335d632.

📒 Files selected for processing (1)

• CODE_OF_CONDUCT.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*

⚙️ CodeRabbit configuration file

**/*: Apply the following Clean Code guidelines to all files, as summarized by wojteklu's Clean Code gist:

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

1. Keep configurable data at high levels.
2. Prefer polymorphism to if/else or switch/case.
3. Separate multi-threading code.
4. Prevent over-configurability.
5. Use dependency injection.
6. Follow Law of Demeter. A class should know only its direct dependencies.

Understandability tips

1. Be consistent. If you do something a certain way, do all similar things in the same way.
2. Use explanatory variables.
3. Encapsulate boundary conditions. Boundary conditions are hard to keep track of. Put the processing for them in one place.
4. Prefer dedicated value objects to primitive type.
5. Avoid logical dependency. Don't write methods which works correctly depending on something else in the same class.
6. Avoid negative conditionals.

Names rules

1. Choose descriptive and unambiguous names.
2. Make meaningful distinction.
3. Use pronounceable names.
4. Use searchable names.
5. Replace magic numbers with named constants.
6. Avoid encodings. Don't append prefixes or type information.

Functions rules

1. Small.
2. Do one thing.
3. Use descriptive names.
4. Prefer fewer arguments.
5. Have no side effects.
6. Don't use flag arguments. Split method into several independent methods that can b...

Files:

• CODE_OF_CONDUCT.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: call-php-build-images / build (zmsstatistic, 8.3)
• GitHub Check: call-php-build-images / build (zmsadmin, 8.3)

🔇 Additional comments (2)

CODE_OF_CONDUCT.md (2)

62-62: Verify the new enforcement contact email is active and monitored.

The email update from opensource@muenchendigital.io to opensource@muenchen.de is the intended change. Ensure the new address is properly configured, actively monitored, and can receive Code of Conduct violation reports.

---

62-66: Clarify discrepancy between AI summary and marked changes.

The AI summary mentions two email address changes and a grammatical adjustment on line 66 (changing "reporter of any incident." to "the reporter of any incident."), but only line 62 is marked with a change indicator. Line 66 currently reads "reporter of any incident." without the article "the".

Please confirm:

• Were both email addresses intended to be updated?
• Was the grammatical adjustment on line 66 intentional but omitted, or is the AI summary inaccurate?

---

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 and usage tips.}

The base branch was changed.