• Understand the issue: Add working-directory input to support monorepo architecture
• Analyze the current prepare-release.yml workflow structure
• Run linter to ensure current state is working
• Add working-directory input to the workflow
• Update pull-request-labeler job to use working-directory with config-name
• Update release-configuration job to use working-directory for CONFIG_PATH
• Update the documentation (prepare-release.md)
• Run linter to validate changes
• Fix code review feedback: correct config-name path to be relative to .github directory
• Add comments explaining path construction logic
• Run security scan (no alerts found)
• Address reviewer feedback (round 1):
  • Store config files in .github/release-configs/{slug}.yml instead of {working-directory}/.github/release-drafter.yml
  • Add include-paths to filter PRs to files in the specified working directory
  • Add support for feat! and type(scope)!: patterns (conventional commit breaking change)
• Address reviewer feedback (round 2):
  • Add prepare job for config name computation to avoid duplication
  • Improve slugify method to handle spaces and special characters
  • Add include-paths input for custom additional paths
  • Include current workflow file in include-paths for monorepo context
• Address code review suggestions:
  • Add error details to warning message for JSON parse failures
  • Add fallback handling for GITHUB_WORKFLOW_REF environment variable
• Address reviewer feedback (round 3):
  • Add condition to prepare job to only run for pull_request or push to default branch
  • Simplify pull-request-labeler condition syntax
  • Use core.setFailed() instead of warning for JSON parse errors
  • Add include-paths section when additionalPaths is not empty even without working-directory

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.