Polling a Git repository for new commits is considered a Jenkins anti-pattern. What is a sound alternative to SVN polling?

Polling a Git repository for new commits is considered a Jenkins anti-

1.	Polling a Git repository for new commits is considered a Jenkins anti-pattern. What is a sound alternative to SVN polling?
Answer» A continuously checking /monitoring SCM tools like GIT or subversion for identifying any new commits are CONSIDERED a waste of clock cycles and not considered best practices. We should avoid this process. There is a better approach available to us which is a reversal of the above approach. The other approach is industry STANDARD one and more POPULAR. The other approach encourages build getting triggered from SOURCE code tool whenever new code is COMMITTED or existing code undergoes some change. This is very easy to configure with GitHub or GItLab using a post-commit hook that runs every time code commit is successful. This setup eliminates the need for constantly monitoring source code as a post-commit hook will trigger the build whenever any code gets committed in the source code.