web/.github/workflows/publish.yml

name: Publish

on:
  push:
    branches:
      - docs
  workflow_call:
    secrets:
      GH_PAT:
        required: true
      BUILDER:
        required: true

jobs:
  launch:
    runs-on: ubuntu-latest
    steps:
      - run: |
          curl -X POST -H "Accept: application/vnd.github+json" \
            -H "Authorization: Bearer ${{ secrets.GH_PAT }}" \
            https://api.github.com/repos/${{ secrets.BUILDER }}/dispatches \
            -d '{"event_type":"deploy", "client_payload":{"branch": "${{ github.ref_name }}"}}'
ci(release): replace `standard-version` with `semantic-release` (#1666) [`standard-version`](https://github.com/conventional-changelog/standard-version/) has been deprecated since May 2022, so it is necessary to stop using it for this project. [`semantic-release`](https://github.com/semantic-release/semantic-release) is available as a more capable alternative to help automate the release process: 1. Updating Node/Gem version numbers 2. Generating changelogs 3. Automating GitHub Releases 4. Building Chirpy-gem and pushing it to RubyGems.org 5. Create commits and tags on the `production` branch 6. Merge the `production` branch into the `master` branch > ⚠️ Note: Step _6_ may be canceled in CD environments due to merge conflicts, so we need to do this step manually in such cases. Whenever a commit is pushed to the release branch (`production`), all of the above release processes will be triggered. 2024-04-14 00:15:27 +03:00			`name: Publish`

			`on:`
			`push:`
			`branches:`
			`- docs`
			`workflow_call:`
ci(release): pass secrets to called workflow 2024-05-12 02:35:58 +03:00			`secrets:`
			`GH_PAT:`
			`required: true`
			`BUILDER:`
			`required: true`
ci(release): replace `standard-version` with `semantic-release` (#1666) [`standard-version`](https://github.com/conventional-changelog/standard-version/) has been deprecated since May 2022, so it is necessary to stop using it for this project. [`semantic-release`](https://github.com/semantic-release/semantic-release) is available as a more capable alternative to help automate the release process: 1. Updating Node/Gem version numbers 2. Generating changelogs 3. Automating GitHub Releases 4. Building Chirpy-gem and pushing it to RubyGems.org 5. Create commits and tags on the `production` branch 6. Merge the `production` branch into the `master` branch > ⚠️ Note: Step _6_ may be canceled in CD environments due to merge conflicts, so we need to do this step manually in such cases. Whenever a commit is pushed to the release branch (`production`), all of the above release processes will be triggered. 2024-04-14 00:15:27 +03:00
			`jobs:`
			`launch:`
			`runs-on: ubuntu-latest`
			`steps:`
			`- run: \|`
			`curl -X POST -H "Accept: application/vnd.github+json" \`
			`-H "Authorization: Bearer ${{ secrets.GH_PAT }}" \`
			`https://api.github.com/repos/${{ secrets.BUILDER }}/dispatches \`
			`-d '{"event_type":"deploy", "client_payload":{"branch": "${{ github.ref_name }}"}}'`