Update system test mapping to use dummy target repositories for testing

[kooomix]

PR Type

enhancement

---

Description

• Updated the system_test_mapping.json to replace real target repositories with dummy ones for testing purposes.
• This change affects the teams_alerts and slack_alerts sections, ensuring that tests do not impact real data.
• The modification is aimed at improving the reliability and safety of system tests by using non-production data.

---

Changes walkthrough 📝

	Relevant files
Enhancement	system_test_mapping.json Use dummy target repositories for alert testing                    system_test_mapping.json Updated target repositories to use dummy repositories for testing. Modified entries under teams_alerts and slack_alerts. Ensured testing environments are not affected by real repository data. +6/-6

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 Security concerns Sensitive information exposure: The PR contains an email address in plain text at line 1397 (owner: "[email protected]"). Consider removing or masking email addresses in test configuration files.

⚡ Recommended focus areas for review Naming Convention Verify that the dummy repository names follow the team's naming conventions for test resources and are properly documented somewhere

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Security	Remove hardcoded email addresses from configuration files to protect sensitive information Remove the hardcoded email address from the configuration file to prevent potential security issues and maintain privacy. system_test_mapping.json [1397] -"owner": "[email protected]" +"owner": "" Apply this suggestion Suggestion importance[1-10]: 8 Why: Removing hardcoded email addresses from configuration files is a critical security best practice to prevent potential data leaks and maintain privacy, especially in test configuration files that might be committed to version control.	8

💡 Need additional feedback ? start a PR chat

[github-actions]

Failed to generate code suggestions for PR