title: AWS CodeCommit: Repository Notifications vs Repository Triggers
body: <p>Notifications: <a href="https://docs.aws.amazon.com/codecommit/latest/userguide/how-to-repository-email.html" rel="noreferrer">https://docs.aws.amazon.com/codecommit/latest/userguide/how-to-repository-email.html</a></p>
  
  <p>Triggers: <a href="https://docs.aws.amazon.com/codecommit/latest/userguide/how-to-notify.html" rel="noreferrer">https://docs.aws.amazon.com/codecommit/latest/userguide/how-to-notify.html</a></p>
  
  <p>The official document states that for CodeCommit repository 'events which follow CloudWatch Event Rules' (like pull requests), we use Repository Notifications.</p>
  
  <p>Whereas for CodeCommit repository events which are just 'operational events' (like creating branches, pushing code to a branch), we use Repository Triggers.</p>
  
  <p>I don't understand the difference between 'events which follow CloudWatch Event Rules' and 'operational events'. For me, both pull requests and pushing code to branch seem similar events. </p>
  
  <p>Thus, confused between why we need both Repository Notifications and Repository Triggers.</p>