docs: Fix outdated continuous integration docs

Author: patrikbraborec

sources/platform/actors/development/deployment/continuous_integration.md

@@ -1,13 +1,13 @@
 ---
 title: Continuous integration
-description: Learn how to integrate your Actors by setting up automated builds, deploys, and testing for your Actors using GitHub Actions or Bitbucket Pipelines.
+description: Learn how to integrate your Actors by setting up automated builds, deploys, and testing for your Actors.
 slug: /actors/development/deployment/continuous-integration
 sidebar_position: 2
 ---
 
 # Continuous integration for Actors
 
-**Learn how to set up automated builds, deploys, and testing for your Actors using GitHub Actions or Bitbucket Pipelines.**
+**Learn how to set up automated builds, deploys, and testing for your Actors.**
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
@@ -18,37 +18,73 @@ Automating your Actor development process can save time and reduce errors, espec
 
 You can automate Actor builds and tests using your Git repository's automated workflows like [GitHub Actions](https://github.com/features/actions) or [Bitbucket Pipelines](https://www.atlassian.com/software/bitbucket/features/pipelines).
 
-This article focuses on GitHub, but [we also have a guide for Bitbucket](https://help.apify.com/en/articles/6988586-setting-up-continuous-integration-for-apify-actors-on-bitbucket).
 
-## Set up automated builds and tests
+:::tip Using Bitbucket?
+Follow our step-by-step guide to set up continuous integration for your Actors with Bitbucket Pipelines: [Read the Bitbucket CI guide](https://help.apify.com/en/articles/6988586-setting-up-continuous-integration-for-apify-actors-on-bitbucket).
+:::
 
-To set up automated builds and tests for your Actors you need to:
+There are two main ways to set up continuous integration for your Actors: [Trigger builds with a Webhook](#option-1-trigger-builds-with-a-webhook), or [Set up automated builds and tests with GitHub Actions](#option-2-set-up-automated-builds-and-tests-with-github-actions). Choose the method that best fits your workflow.
 
-1. Create a GitHub repository for your Actor code.
+## Option 1: Trigger builds with a Webhook
+
+To set up triggered builds with a webhook:
+
+1. Go to your Actor's detail page in Apify Console, click on the API tab in the top right, then select API Endpoints. Copy the **Build Actor** API endpoint URL. The format is as follows:
+
+      ```cURL
+      https://api.apify.com/v2/acts/YOUR-ACTOR-NAME/builds?token=YOUR-TOKEN-HERE&version=0.0&tag=beta&waitForFinish=60
+      ```
+
+   :::note API token
+   Make sure you select the correct API token from the dropdown.
+   :::
+1. In your GitHub repository, go to Settings > Webhooks > Add webhook.
+1. Paste the API URL into the Payload URL field and add the webhook.
+
+![GitHub integration](./images/ci-github-integration.png)
+
+Now your Actor will automatically rebuild on every push to the GitHub repository.
+
+## Option 2: Set up automated builds and tests with GitHub Actions
+
+To set up automated builds and tests with GitHub Actions, you need to:
+
+1. You need to push your Actor to a GitHub repository.
 1. Get your Apify API token from the [Apify Console](https://console.apify.com/settings/integrations)
 
     ![Apify token in app](./images/ci-token.png)
 
 1. Add your Apify token to GitHub secrets
-   1. Go to your repository > Settings > Secrets > New repository secret
+   1. Go to your repository > Settings > Secrets and variables > Actions > New repository secret
    1. Name the secret & paste in your token
-1. Add the Builds Actor API endpoint URL to GitHub secrets
-   1. Use this format:
+
+     ![Add Apify token to secrets](./images/ci-add-token.png)
+
+1. Add the Build Actor API endpoint URL to GitHub secrets
+   1. Go to your repository > Settings > Secrets and variables > Actions > New repository secret
+   1. In Apify Console, go to your Actor's detail page, click the API tab in the top right, and then select API Endpoints. Copy the **Build Actor** API endpoint URL. The format is as follows:
+      :::note API token
+      Make sure you select the correct API token from the dropdown.
+      :::
 
       ```cURL
       https://api.apify.com/v2/acts/YOUR-ACTOR-NAME/builds?token=YOUR-TOKEN-HERE&version=0.0&tag=beta&waitForFinish=60
       ```
-
+   1. Name the secret & paste in your API endpoint
+      
       ![Add build Actor URL to secrets](./images/ci-add-build-url.png)
 
-   1. Name the secret
 1. Create GitHub Actions workflow files:
    1. In your repository, create the `.github/workflows` directory
-   2. Add `latest.yml` and `beta.yml` files with the following content
+   1. Add `latest.yml`. If you want, you can also add `beta.yml` to build actors from the develop branch (or other branches).
 
     <Tabs groupId="main">
     <TabItem value="latest.yml" label="latest.yml">
 
+    :::note Use your secret names
+    Make sure to use the exact secret names you set in the previous step.
+    :::
+
     ```yaml
     name: Test and build latest version
     on:
@@ -57,7 +93,7 @@ To set up automated builds and tests for your Actors you need to:
           - master
           - main
     jobs:
-      test:
+      test-and-build:
         runs-on: ubuntu-latest
         steps:
           # Install dependencies and run tests
@@ -66,25 +102,28 @@ To set up automated builds and tests for your Actors you need to:
           # Build latest version
           - uses: distributhor/workflow-webhook@v1
             env:
-              webhook_url: ${{ secrets.LATEST_BUILD_URL }}
+              webhook_url: ${{ secrets.BUILD_ACTOR_URL }}
               webhook_secret: ${{ secrets.APIFY_TOKEN }}
 
     ```
 
-    With this setup, pushing to the `main` or `master` branch builds a new latest version.
+    With this setup, pushing to the `main` or `master` branch tests the code and builds a new latest version.
 
     </TabItem>
-
     <TabItem value="beta.yml" label="beta.yml">
 
+    :::note Use your secret names
+    Make sure to use the exact secret names you set in the previous step.
+    :::
+
     ```yaml
     name: Test and build beta version
     on:
       push:
         branches:
           - develop
     jobs:
-      test:
+      test-and-build:
         runs-on: ubuntu-latest
         steps:
           # Install dependencies and run tests
@@ -93,24 +132,18 @@ To set up automated builds and tests for your Actors you need to:
           # Build latest version
           - uses: distributhor/workflow-webhook@v1
             env:
-              webhook_url: ${{ secrets.BETA_BUILD_URL }}
+              webhook_url: ${{ secrets.BUILD_ACTOR_URL }}
               webhook_secret: ${{ secrets.APIFY_TOKEN }}
 
     ```
 
-    With this setup, pushing to the `develop` branch builds a new beta version.
+    With this setup, pushing to the `develop` branch tests the code and builds a new beta version.
 
     </TabItem>
     </Tabs>
 
-## GitHub integration
-
-To set up automatic builds from GitHub:
-
-1. Go to your Actor's detail page and coy the Build Actor API endpoint URL from the API tab.
-1. In your GitHub repository, go to Settings > Webhooks > Add webhook.
-1. Paste the API URL into the Payload URL field.
+## Conclusion
 
-![GitHub integration](./images/ci-github-integration.png)
+Setting up continuous integration (CI) for your Apify actors ensures that your code is always tested and built automatically whenever you push changes to your repository. This helps catch issues early and streamlines your deployment process, whether you're releasing to production or maintaining a beta branch.
 
-Now your Actor will automatically rebuild on every push to the GitHub repository.
+You can also integrate directly with GitHub, check out the [official Apify GitHub integration documentation](/platform/integrations/github).