Changes to pull request do trigger the webhook but not triggering the workflow. #1542
Replies: 2 comments 1 reply
-
Hi @BryanLeong99, can you share a build id or team id, so i can look into this? |
Beta Was this translation helpful? Give feedback.
1 reply
-
This discussion is being closed due to no activity in the last 14 days. You can reopen the discussion at any time if needed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
UPDATED: I have a project hosted on AWS CodeCommit. When I am trying to trigger the build automatically using a pull request, the build did not run as expected although the webhook successfully received the deliveries upon some changes to the pull request.
I tried the following, which I expect to run perfectly, but it does not trigger, no matter what. I wish someone who is much more experienced could help me in getting through this.
Webhook log:
Update: After some checking, it happens only when there is a slash '/' in my source branch. I tried to create a branch without the slash, and it worked.
Then, I assumed that adding that pattern, "/" will work, but unfortunately, it did not work as expected. The webhook log somehow showed me an incomplete branch name in its message. For example, if the branch is named 'feature/my_feature', the log only shows 'my_feature', which is the part after the slash.
Does anyone have any solution to this?
Beta Was this translation helpful? Give feedback.
All reactions