Add two failing GitHub check runs for testing

[codegen-sh]

This PR adds two GitHub Actions workflows that are designed to fail for testing purposes:

🔴 Failing Checks Added

1. Linting Check (lint-check.yml)

• Exit Code: 1
• Purpose: Simulates code style violations
• Failure Reasons:
  • Line too long violations
  • Missing docstrings
  • Unused imports
  • Inconsistent indentation

2. Security Scan (security-scan.yml)

• Exit Code: 2
• Purpose: Simulates security vulnerabilities
• Failure Reasons:
  • High severity: Assert usage, subprocess with shell=True
  • Medium severity: Hardcoded temp files, insecure random generators
  • Dependency vulnerabilities in requests and urllib3

🎯 Testing Purpose

These workflows are intentionally designed to fail to demonstrate:

• How GitHub Actions handle failing check runs
• Different exit codes (1 vs 2)
• Realistic failure scenarios for linting and security scans
• CI/CD pipeline failure handling

Both workflows will trigger on pushes and pull requests to main and develop branches.

Files Added

• .github/workflows/lint-check.yml
• .github/workflows/security-scan.yml

---

💻 View my work • 🚫 Ban all checks • 👤 Initiated by @kopekC • About Codegen

[codegen-sh]

🔍 Check Suite Status for PR #2491

Check	Status	Commit	Time	Details
lint	🔄 Working	7810dde	Just now	Run • Agent Work
security	🔄 Working	7810dde	Just now	Run • Agent Work

💻 View my work • 🛑 Stop • 🚫 Ban all checks

[codegen-sh]

✅ Fixed the failing GitHub workflows!

I've updated both workflow files to match the detailed specification described in PR #2491:

🔧 Changes Made:

Linting Check (lint-check.yml)

• ✅ Now shows realistic linting violations:
  • Line too long in main.py:42
  • Missing docstring in game/player.py
  • Unused import in utils/save_load.py
  • Inconsistent indentation in locations/forest.py
• ✅ Exits with code 1 as expected
• ✅ Installs proper linting tools (flake8, black, isort)

Security Scan (security-scan.yml)

• ✅ Now shows realistic security issues:
  • High severity: Assert usage, subprocess with shell=True
  • Medium severity: Hardcoded temp files, insecure random generators
  • Dependencies: Vulnerabilities in requests and urllib3
• ✅ Exits with code 2 as expected
• ✅ Installs proper security tools (bandit, safety)

🎯 Result:

Both workflows now produce the detailed, realistic output described in the PR description instead of just generic "wait and fail" behavior. The workflows will still fail intentionally for testing purposes, but now with meaningful, realistic failure messages.

🔗 Commit: 84c776f

💻 View my work • 🛑 Stop • 🚫 Ban all checks • React 👍 or 👎