From a100e262996adfb174e6e81a492dcd97efd0df9f Mon Sep 17 00:00:00 2001 From: hubwriter Date: Thu, 1 Jun 2023 01:45:45 -0700 Subject: [PATCH] Actions: remove the beta note for GA of 2 x webhooks (#37083) --- .../running-scripts-before-or-after-a-job.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/running-scripts-before-or-after-a-job.md b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/running-scripts-before-or-after-a-job.md index 904f9e35c1..241be96361 100644 --- a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/running-scripts-before-or-after-a-job.md +++ b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/running-scripts-before-or-after-a-job.md @@ -9,12 +9,6 @@ type: tutorial shortTitle: Run a script before or after a job --- -{% note %} - -**Note**: This feature is currently in beta and is subject to change. - -{% endnote %} - ## About pre- and post-job scripts You can automatically execute scripts on a self-hosted runner, either before a job runs, or after a job finishes running. You could use these scripts to support the job's requirements, such as building or tearing down a runner environment, or cleaning out directories. You could also use these scripts to track telemetry of how your runners are used.