Only run the pipeline for main branches and pr to dev branch only

[KennyDizi]

type:

enhancement

---

description:

This PR modifies the GitHub Actions workflow configuration to restrict the pipeline triggers and deployment conditions. The changes include:

• The pipeline will now only be triggered for 'push' events on 'main', 'stg', and 'dev' branches, and 'pull_request' events on the 'dev' branch. Previously, it was also triggered for 'pull_request' events on 'stg' and 'main' branches.
• The condition for deploying to AWS using CDK has been simplified. Previously, it was executed if the event was a 'push' or if the branch was not 'dev', 'stg', or 'main'. Now, this condition has been removed, meaning the deployment will run unconditionally within the workflow.

---

main_files_walkthrough:

files:

- `.github/workflows/release.yml`: The changes in the 'release.yml' file include the removal of 'stg' and 'main' from the 'pull_request' trigger branches, and the removal of the condition for the 'Deploy to AWS using CDK' job.

[codiumai-pr-agent-free[bot]]

PR Description updated to latest commit (https://github.com/AI4Organization/qdrant-docker-image-ecr-deployment-cdk/commit/4dcf7c29745a1479bbfed27ce40d00a5c8bce64c)

[codiumai-pr-agent-free[bot]]

PR Analysis

• 🎯 Main theme: Restricting pipeline triggers and deployment conditions in GitHub Actions workflow

• 📝 PR summary: This PR modifies the GitHub Actions workflow configuration to limit the pipeline triggers to 'push' events on 'main', 'stg', and 'dev' branches, and 'pull_request' events on the 'dev' branch only. It also removes the condition for deploying to AWS using CDK, meaning the deployment will run unconditionally within the workflow.

• 📌 Type of PR: Enhancement

• 🧪 Relevant tests added: No

• ⏱️ Estimated effort to review [1-5]: 1, because the changes are straightforward and limited to the GitHub Actions workflow configuration.

• 🔒 Security concerns: No security concerns found

  PR Feedback

• 💡 General suggestions: The changes made in this PR are clear and straightforward. However, it would be beneficial to include a rationale for these changes in the PR description. This would help reviewers understand the context and the need for these changes.

• 🤖 Code feedback:

  - **relevant file:** ``.github/workflows/release.yml`` **suggestion:** Consider adding a comment in the code explaining why the deployment to AWS using CDK is now running unconditionally. This can help future developers understand the reasoning behind this decision. [medium] **relevant line:** [run: npx cdk deploy --require-approval never --all](https://github.com/AI4Organization/qdrant-docker-image-ecr-deployment-cdk/pull/11/files#diff-87db21a973eed4fef5f32b267aa60fcee5cbdf03c67fafdc2a9b553bb0b15f34R109)

How to use

Instructions

> To invoke the PR-Agent, add a comment using one of the following commands: > **/review**: Request a review of your Pull Request. > **/describe**: Update the PR title and description based on the contents of the PR. > **/improve [--extended]**: Suggest code improvements. Extended mode provides a higher quality feedback. > **/ask \**: Ask a question about the PR. > **/update_changelog**: Update the changelog based on the PR's contents. > **/add_docs**: Generate docstring for new components introduced in the PR. > **/generate_labels**: Generate labels for the PR based on the PR's contents. > see the [tools guide](https://github.com/Codium-ai/pr-agent/blob/main/docs/TOOLS_GUIDE.md) for more details. >To edit any configuration parameter from the [configuration.toml](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml), add --config_path=new_value. >For example: /review --pr_reviewer.extra_instructions="focus on the file: ..." >To list the possible configuration parameters, add a **/config** comment.