We have seen issues in the past where the casing of the repository as configured in CodePipeline does not match the casing of the repository in GitHub or Bitbucket, and as a result, pipelines were not being properly triggered - even though using "Release Changes" would work.
One suggestion would be to edit the Source action in the AWS Console and use the name of the repository as it appears in the dropdown that appears when configuring the source action - for other customers this has resolved the issue.
CodeGuru not loading the list of private GitHub repositoriesAccepted Answerasked 9 months ago
How to trigger CodePipeline from GitHubasked 8 months ago
trigger CodePipeline on scheduleAccepted Answerasked 6 years ago
Can I extract the code from the aws to save it in Githubasked 3 months ago
CodePipeline Source Action Fails with "[GitHub] InternalError"asked 3 months ago
how to trigger sagemaker pipeline via code change in github?asked 11 days ago
Stop CodePipeline from triggering on every GitHub commit/pushAccepted Answerasked 2 years ago
CDK Codepipeline with github : insufficient permissionsasked 9 days ago
Use CodePipeline to deploy package stored from CodeArtifactasked 25 days ago
[CodePipeline / CodeStar] GitHub returned an Internal Error exceptionAccepted Answerasked 8 months ago