From 3b27aa5c3b611bfefa64a997972440b11bdd54f7 Mon Sep 17 00:00:00 2001
From: Nick Philbrook <42616679+nphilbrook@users.noreply.github.com>
Date: Wed, 9 Apr 2025 09:14:43 -0400
Subject: [PATCH 1/2] Created branch nphilbrook_vcs_events from main


From c50a0a342f0f8e8b58bba3ee7aa1952973f708a4 Mon Sep 17 00:00:00 2001
From: Nick Philbrook <42616679+nphilbrook@users.noreply.github.com>
Date: Wed, 9 Apr 2025 09:15:49 -0400
Subject: [PATCH 2/2] Add note about VCS events only being supported for GitLab

---
 website/docs/cloud-docs/vcs/index.mdx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/docs/cloud-docs/vcs/index.mdx b/website/docs/cloud-docs/vcs/index.mdx
index b75925fa6..dd318cdf7 100644
--- a/website/docs/cloud-docs/vcs/index.mdx
+++ b/website/docs/cloud-docs/vcs/index.mdx
@@ -119,6 +119,8 @@ You can use self-hosted HCP Terraform Agents to connect HCP Terraform to your pr
 
 ## Viewing events
 
+-> **Note**: The VCS Events page is still in beta as support is being added for additional VCS providers. Currently only GitLab.com connections established after December 2020 are supported.
+
 VCS events describe changes within your organization for VCS-related actions. The VCS events page only displays events from previously processed commits in the past 30 days. The VCS page indicates previously processed commits with the message, `"Processing skipped for duplicate commit SHA"`.
 
 Viewing VCS events requires permission to manage VCS settings for the organization. ([More about permissions.](/terraform/cloud-docs/users-teams-organizations/permissions))