fix: clean_on_pr_closed workflow not getting triggered incase if the PR consists merge conflicts

[KrishnaVAMSI-2003]

Description

This PR introduces the fix for the issue #63, in which clean_on_pr_closed workflow is not getting triggered incase if the PR consists merge conflicts. Replaced pull_request event trigger with pull_request_target as a fix for this problem.

Plase note:

• The pull_request_target event will not trigger if the workflow is just placed in the .github/workflows directory of the PR's head branch, but it must exist in the base branch. We should make sure the workflow exists in the base branch at the time the PR is opened. So moving forward this will work as expected but won't work for the existing PR's until their base branch have been edited and added as main.

Database schema changes

• NA

Tests

Automated test cases added

• NA

Manual test cases run

For each manual test case, list the steps to test or reproduce the PR.

• NA (refer PR)

[jalan-technologies-sonarqube[bot]]

Analysis Details

0 Issues

• 0 Bugs
• 0 Vulnerabilities
• 0 Code Smells

Coverage and Duplications

• No coverage information (0.00% Estimated after merge)
• 0.00% Duplicated Code (0.40% Estimated after merge)

Project ID: jalantechnologies_rflask-boilerplate

View in SonarQube

[github-actions[bot]]

Deployment (frm-boilerplate) is available at - https://6905caad90e785f.preview.platform.jalantechnologies.com

[jalan-technologies-sonarqube[bot]]

Analysis Details

0 Issues

• 0 Bugs
• 0 Vulnerabilities
• 0 Code Smells

Coverage and Duplications

• No coverage information (0.00% Estimated after merge)
• No duplication information (0.40% Estimated after merge)

Project ID: jalantechnologies_rflask-boilerplate

View in SonarQube

[github-actions[bot]]

Deployment (frm-boilerplate) is available at - https://6905caad90e785f.preview.platform.jalantechnologies.com