FAQ callout for using runners with Sourcegraph (#1045)

This PR introduces a section that could potentially be asked by
customers in the future about automating batch changes with code host
runners. This section offers general guidance on how to approach it.

<!-- Explain the changes introduced in your PR -->

## Pull Request approval

You will need to get your PR approved by at least one member of the
Sourcegraph team. For reviews of docs formatting, styles, and component
usage, please tag the docs team via the #docs Slack channel.

Author: airamare01

docs/batch-changes/faq.mdx

@@ -65,6 +65,17 @@ However, [steps](/batch-changes/batch-spec-yaml-reference#steps-run) can run any
 - [Jira tickets](https://github.com/sourcegraph/batch-change-examples/blob/main/ticketing-systems/jira-tickets/README)
 - [GitHub issues](https://github.com/sourcegraph/batch-change-examples/blob/main/ticketing-systems/github-issues/README)
 
+## Can I use GitHub/GitLab runners to automate my batch changes?
+To an extent, yes, you can use GitHub Actions or GitLab CI/CD runners to automate Sourcegraph batch changes to allow you to trigger batch changes automatically after events like library updates or on a schedule. 
+The implementation requirements are network access where your CI/CD runners must be able to reach your Sourcegraph instance and have authentication through a Sourcegraph access token for API access along with appropriate permissions to create batch changes.
+
+If you'd want to implement this automation:
+
+The best way would be to contact your SRE/Infrastructure team to verify if your CI/CD runners can access your Sourcegraph instance and if access is not available, work with your SRE team to request this capability.
+Once access is confirmed, you can proceed with implementing the automation
+
+However, this requires your CI/CD runners to have network access to your Sourcegraph instance. In many enterprise environments, this access may be restricted by default.
+
 ## What happens to the preview page if the batch spec is not applied?
 
 Unapplied batch specs are removed from the database after **seven days**.