diff --git a/src/docs/tutorials/deploy-an-otel-collector-stack.md b/src/docs/tutorials/deploy-an-otel-collector-stack.md index 6316301a3..96968c227 100644 --- a/src/docs/tutorials/deploy-an-otel-collector-stack.md +++ b/src/docs/tutorials/deploy-an-otel-collector-stack.md @@ -33,7 +33,7 @@ To be successful using this tutorial, you should already have - If you are looking for a quicker way to get started, you can deploy the collector and backend stack from a template by clicking the button below. Deploy on Railway -We also have a live demo of the project you will build in this tutorial here, and you can access the code repository here in Github. You can find some example apps, including the one we will build in this tutorial, in the exampleApps folder. +We also have a live demo of the project you will build in this tutorial here, and you can access the code repository here in GitHub. You can find some example apps, including the one we will build in this tutorial, in the exampleApps folder. **Let's get started!** diff --git a/src/docs/tutorials/github-actions-post-deploy.md b/src/docs/tutorials/github-actions-post-deploy.md index ac2ac3108..4c8228b1f 100644 --- a/src/docs/tutorials/github-actions-post-deploy.md +++ b/src/docs/tutorials/github-actions-post-deploy.md @@ -3,13 +3,13 @@ title: GitHub Actions Post-Deploy description: Learn how to use GitHub Actions to run post-deployment commands. --- -[Github Actions](https://github.com/features/actions) come with a pretty neat set of features to automate your workflows. In this post, we talk about using Github Actions to run post-deploy actions. +[GitHub Actions](https://github.com/features/actions) come with a pretty neat set of features to automate your workflows. In this post, we talk about using GitHub Actions to run post-deploy actions. -At Railway, we've set up Github triggers for automatic deployments when you push to a selected branch, and with Github Actions, you can automate several parts of your development workflow. Recently, within our [Discord](https://discord.gg/railway) and [Slack](/reference/support#slack), we've had a couple of users ask us how they'd go about running commands or webhooks after their app is deployed so we thought it'd be a good idea to publish a short tutorial doing just that, with Github Actions. +At Railway, we've set up GitHub triggers for automatic deployments when you push to a selected branch, and with GitHub Actions, you can automate several parts of your development workflow. Recently, within our [Discord](https://discord.gg/railway) and [Slack](/reference/support#slack), we've had a couple of users ask us how they'd go about running commands or webhooks after their app is deployed so we thought it'd be a good idea to publish a short tutorial doing just that, with GitHub Actions. ## The Action -Since Railway makes the deployment status available to Github, we'll be using the `deployment_status` event to trigger our action. This event is triggered when a deployment status changes, and we'll be using the `success` state to trigger our action. +Since Railway makes the deployment status available to GitHub, we'll be using the `deployment_status` event to trigger our action. This event is triggered when a deployment status changes, and we'll be using the `success` state to trigger our action. Make a new file in your repository called `.github/workflows/post-deploy.yml` and add the following - diff --git a/src/docs/tutorials/github-actions-pr-environment.md b/src/docs/tutorials/github-actions-pr-environment.md index addf44d7f..ae9a002cd 100644 --- a/src/docs/tutorials/github-actions-pr-environment.md +++ b/src/docs/tutorials/github-actions-pr-environment.md @@ -3,7 +3,7 @@ title: GitHub Actions PR Environment description: Learn how to use the CLI in a GitHub Action to create environments for PRs --- -[Github Actions](https://github.com/features/actions) come with a pretty neat set of features to automate your workflows. In this post, we talk about using Github Actions alongside the [Railway CLI](https://github.com/railwayapp/cli) to create specific environments for any PR that is created, alongside closing it whenever it is closed/merged. +[GitHub Actions](https://github.com/features/actions) come with a pretty neat set of features to automate your workflows. In this post, we talk about using GitHub Actions alongside the [Railway CLI](https://github.com/railwayapp/cli) to create specific environments for any PR that is created, alongside closing it whenever it is closed/merged. This can be useful if you need to create a branch on a [Neon](https://neon.tech) database, allowing you to automatically inject the correct database url.