With Azure Pipelines integrated to GitHub and continuous integration enabled, which setting ensures the system waits for a running build to complete before queuing another build for the same branch?

The "batch changes" setting in Azure Pipelines prevents multiple concurrent builds for the same branch. When enabled, if a build is already running for a specific branch, subsequent commits to that branch will not trigger new builds immediately. Instead, these changes are batched, and a single new build is queued only after the current build completes, incorporating all changes made during the previous build's execution. This optimizes resource usage and prevents redundant builds. "Path filters" define which file changes trigger a build, not how builds are queued. "Scheduled builds" trigger builds at specific times, independent of code changes. "Branch filters" specify which branches trigger a build, but don't manage concurrent builds on the same branch.