0.4.0

⚠️ Breaking Changes
This release includes a database schema change. Action is required if you are updating an existing installation.

Database Schema Update: The primary key for the slack_messages table has been changed from a single column (pr_number) to a composite primary key of pr_number and gh_repository. This change is critical for correctly handling identical PR numbers across different repositories.

Action Required: You must run the latest database migration to update your schema. Please consult the Upgrade Documentation for a detailed upgrade path.

✨ Features and Enhancements
Production-Ready Docker Environment: We've introduced full Docker support for production usage, which will significantly simplify the deployment, installation, and scaling of the PR bot.

See the Production Docker Documentation for setup instructions.

Data Integrity Refactoring: The core SlackMessage entity and related code have been refactored to enforce data integrity using the new composite primary key, guaranteeing that unique messages are tracked per repository.

🐛 Fixes
Multi-Repository Update Fix: Resolved an issue where message updates were incorrect or failed when multiple registered repositories had pull requests with the same number. (Fixes #15: Message is not updated when multiple repositories with the same RP number)

Ignored Draft PR Creation: The bot now correctly ignores events for newly created Draft PRs, preventing the bot from attempting to process a pull request before it's been marked as ready for review.

Full Changelog: 0.3.3...0.4.0

v0.3.3

Full Changelog: 0.3.2...0.3.3

Bugfix

• Fixed open pr use case so when new draft pr is created application ignores it.

v0.3.2

Full Changelog: 0.3.1...0.3.2

Bugfix

• Fixed open pr use case so when new draft pr is created application ignores it.

v0.3.1

What's Changed

• PR comments and request change event handling by @pavelmaksimov25 in #14

Full Changelog: 0.3.0...0.3.1

After update

If the Slack messages feature is used, update the env variables. Two new reactions were introduced

1. SLACK_REACTION_PR_COMMENTED is used in case PR has any comments.
2. SLACK_REACTION_PR_REQUEST_CHANGE is used in case PR has any comments.

Caution

Run composer dump-env prod for the production environment or composer dump-env dev for the development environment to populate new env variables.

v0.3.0

What's Changed

• Add slack reaction on PR approved event by @pavelmaksimov25 in #13

BC Break

This release can cause a BC Break only if the reactions feature is enabled.
Default values for the emojis were changed. Please check the configuration inside the .env* files.

Full Changelog: 0.2.1...0.2.2

v0.2.1

What's Changed

• Bugfix: differentiation between repositories in slack messages by @pavelmaksimov25 in #12

Full Changelog: 0.2.0...0.2.1

v0.2.0

Release [v0.2.0]

What's New

• Feature: Multi-repository setup by @pavelmaksimov25 . #5
• Feature: PR title in the slack message by @Chemaclass. #7
• Improvement: Better documentation by @pavelmaksimov25 #9

Changes

0.1.0...0.2.0

v0.1.0

Initial Release

Out-of-the-box features:

• Listen to GitHub webhooks.
• Posts message to slack channel when PR is created.
• Updates the previous message when PR is closed or merged and adds a reaction to increasing visibility.
• Removes Slack message if PR becomes draft.
• Customizable Slack mentions and emojis.