protobuf/.github/workflows/generate_files.yml

name: Auto-generate checked-in files

on:
  push:
    branches:
      - main
      - '[0-9]+.x'
      # The 21.x branch predates support for auto-generation, so we make sure
      # to exclude it.
      - '!21.x'

jobs:
  cmake:
    if: github.repository == 'protocolbuffers/protobuf'
    runs-on: ubuntu-latest

    strategy:
      fail-fast: false   # Don't cancel all jobs if one fails.

    steps:
      - uses: actions/checkout@v3
        with:
          # Note: this token has an expiration date, so if the workflow starts
          # failing then you may need to generate a fresh token.
          token: ${{ secrets.BOT_ACCESS_TOKEN }}
      - name: Configure name and email address in Git
        run: cd ${{ github.workspace }} && git config user.name "Protobuf Team Bot" && git config user.email "protobuf-team-bot@google.com"
      - name: Commit and push update
        run: cd ${{ github.workspace }} && ./push_auto_update.sh
Update auto-generation script to handle well-known types I went ahead and deleted the update_file_list.sh script, because (a) there was no good reason for it to be in a separate script and (b) we now need to handle the well-known types in addition to file_lists.cmake. With this change, we just invoke the staleness tests from the main script to update everything. While I was at it I made a couple small fixes: - Don't skip the update step just because the previous commit was by "Protobuf Team Bot". Copybara commits use this name and we still want to do the auto-update step after them. - Include the CL number in the description if the previous commit came from a CL. PiperOrigin-RevId: 487231324 2 years ago			`name: Auto-generate checked-in files`
Adding Github Action to keep CMake generated file lists up to date (#10243) 2 years ago
			`on:`
Auto-generate CMake file lists in GitHub action (#10592) This GitHub action will run after each pull request merge and will auto-update the file lists in in src/file_lists.cmake. The action will run as our bot account. I realized that if a bug somehow made the file generation non-idempotent, this could trigger an infinite loop of commits, so I put in an extra safeguard against that. If the previous commit was by "Protobuf Team Bot", the GitHub action will revert any local changes to ensure that no new commit will be made. 2 years ago			`push:`
			`branches:`
			`- main`
			`- '[0-9]+.x'`
Update auto-generation script to handle well-known types I went ahead and deleted the update_file_list.sh script, because (a) there was no good reason for it to be in a separate script and (b) we now need to handle the well-known types in addition to file_lists.cmake. With this change, we just invoke the staleness tests from the main script to update everything. While I was at it I made a couple small fixes: - Don't skip the update step just because the previous commit was by "Protobuf Team Bot". Copybara commits use this name and we still want to do the auto-update step after them. - Include the CL number in the description if the previous commit came from a CL. PiperOrigin-RevId: 487231324 2 years ago			`# The 21.x branch predates support for auto-generation, so we make sure`
			`# to exclude it.`
Auto-generate CMake file lists in GitHub action (#10592) This GitHub action will run after each pull request merge and will auto-update the file lists in in src/file_lists.cmake. The action will run as our bot account. I realized that if a bug somehow made the file generation non-idempotent, this could trigger an infinite loop of commits, so I put in an extra safeguard against that. If the previous commit was by "Protobuf Team Bot", the GitHub action will revert any local changes to ensure that no new commit will be made. 2 years ago			`- '!21.x'`
Adding Github Action to keep CMake generated file lists up to date (#10243) 2 years ago
			`jobs:`
			`cmake:`
Run CMake file auto-generation only on the main protobuf repo (#10611) This workflow will otherwise fail on forks, so let's make sure to do it only on the main repo where we need it. 2 years ago			`if: github.repository == 'protocolbuffers/protobuf'`
Adding Github Action to keep CMake generated file lists up to date (#10243) 2 years ago			`runs-on: ubuntu-latest`

			`strategy:`
			`fail-fast: false # Don't cancel all jobs if one fails.`

			`steps:`
Auto-generate CMake file lists in GitHub action (#10592) This GitHub action will run after each pull request merge and will auto-update the file lists in in src/file_lists.cmake. The action will run as our bot account. I realized that if a bug somehow made the file generation non-idempotent, this could trigger an infinite loop of commits, so I put in an extra safeguard against that. If the previous commit was by "Protobuf Team Bot", the GitHub action will revert any local changes to ensure that no new commit will be made. 2 years ago			`- uses: actions/checkout@v3`
			`with:`
			`# Note: this token has an expiration date, so if the workflow starts`
			`# failing then you may need to generate a fresh token.`
			`token: ${{ secrets.BOT_ACCESS_TOKEN }}`
			`- name: Configure name and email address in Git`
			`run: cd ${{ github.workspace }} && git config user.name "Protobuf Team Bot" && git config user.email "protobuf-team-bot@google.com"`
			`- name: Commit and push update`
Update auto-generation script to handle well-known types I went ahead and deleted the update_file_list.sh script, because (a) there was no good reason for it to be in a separate script and (b) we now need to handle the well-known types in addition to file_lists.cmake. With this change, we just invoke the staleness tests from the main script to update everything. While I was at it I made a couple small fixes: - Don't skip the update step just because the previous commit was by "Protobuf Team Bot". Copybara commits use this name and we still want to do the auto-update step after them. - Include the CL number in the description if the previous commit came from a CL. PiperOrigin-RevId: 487231324 2 years ago			`run: cd ${{ github.workspace }} && ./push_auto_update.sh`