diff --git a/content/en/intelligent_test_runner/troubleshooting/_index.md b/content/en/intelligent_test_runner/troubleshooting/_index.md
index e7b60535faa..3a75f636f48 100644
--- a/content/en/intelligent_test_runner/troubleshooting/_index.md
+++ b/content/en/intelligent_test_runner/troubleshooting/_index.md
@@ -28,7 +28,17 @@ Due to these restrictions, the first time you enable Intelligent Test Runner, yo
 
 Intelligent Test Runner only takes into account the commit history and test code coverage information for the past month. Additionally, it does not take into account code coverage information that is generated more than one week after a commit was made.
 
-There is a limitation when [synchronizing a fork through GitHub's UI][4] which causes all tests to be run for the generated synchronization commit.
+### Synchronizing a fork through GitHub's UI
+
+[Synchronizing a fork through GitHub's UI][4] causes all tests to be run for the generated synchronization commit.
+
+### Collecting coverages on GitHub Actions CI triggered by pull request events
+
+If you run tests on GitHub Actions CI using the [`pull_request` trigger][5] tests might not be skipped. Code coverage information collected from merge commits is not supported.
+
+### Squash and merge your commits
+
+Using [squash and merge][6] to integrate commits into the base branch causes the git history of the feature branch to be lost. As a result, Intelligent Test Runner can run tests in the base branch that should have been skipped.
 
 ## Intelligent Test Runner incorrectly skipped a test
 
@@ -49,3 +59,5 @@ If you are authoring a commit that includes any of those cases, you can force-di
 [2]: /continuous_integration/intelligent_test_runner/
 [3]: https://developer.harness.io/kb/continuous-integration/articles/using_git_credentials_from_codebase_connector_in_ci_pipelines_run_step/
 [4]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-branch-from-the-web-ui
+[5]: https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request
+[6]: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges#squash-and-merge-your-commits