fix(ci): restrict deploy workflow to push on default branch to avoid issues#1169
fix(ci): restrict deploy workflow to push on default branch to avoid issues#1169rbadillap wants to merge 1 commit intoprimer:mainfrom
Conversation
…fork permission issues
|
There was a problem hiding this comment.
Pull Request Overview
This PR fixes a CI/CD workflow issue by restricting the deploy workflow to only run on pushes to the default branch, preventing OIDC token and permission errors that occur when the workflow runs from forked repositories during pull requests.
- Changed workflow trigger from
pull_requesttopushevents on the default branch - Added explanatory comment about the trigger change
- Addresses permission issues identified in a previous PR review
Summary
Updated the deploy workflow trigger to run only on
pushevents to the default branch instead ofpull_request.This prevents OIDC token and permission errors that occur when the workflow executes from forked repositories.
List of notable changes:
Steps to test:
Reviewer checklist:
Screenshots:
Now the Deploy workflow is executed only when a push is done on the
default-branch. Means, the workflow is not getting triggered on PRs.Additional Note