#github-actions - September 2022

GitHub Actions Larger runners – Are now in public beta
GitHub Actions Larger runners - Are now in public beta

Hi folks,

not sure if this is the right place to ask, if not pls suggest where to move the conv

Cloud Posse team - have been looking a bit at various repos and have few questions:

• i see there are various GHA workflows in .github repo which i believe is treated as source of truth. What i haven't seen is what sort of method you adopted to keep / update various workflows used in different downstream repos? Is this a push from "central" or a "pull from upstream" or is just a manual process as of today?
• when you need a new git repo, is it fair to say that terraform-example-module is your boilerplate repo and you don't have any "sync" process to pull the latest version of various files/ workflows from "the source" ?

GitHub Actions: Use INLINECODE_0 with workflow_dispatch and repository_dispatch
GitHub Actions: Use GITHUB_TOKEN with workflow_dispatch and repository_dispatch

HI guys. So i dont if anyone still experiences a failure when cloning a repo in docker container even after using this.

- uses: actions/checkout@v3
      - uses: webfactory/ssh-agent@v0.5.4
        with:
          ssh-private-key: ${{ secrets.GLOBAL_GH_SSH_KEY }}
- name: Build and push
        id: docker_build
        uses: docker/build-push-action@v2
        with:
          ssh: |
            default=${{ env.SSH_AUTH_SOCK }}

I can't believe the GitHub Actions roadmap doesn't even mention a dashboard. https://github.com/orgs/github/projects/4247/views/2?filterQuery=label%3Aactions

This message was deleted.

GitHub Actions: All Actions will begin running on Node16 instead of Node12
GitHub Actions: All Actions will begin running on Node16 instead of Node12

GitHub Actions: Dynamic names for workflow runs
GitHub Actions: Dynamic names for workflow runs

GitHub Actions: Additional information available in github.event payload for scheduled workflow runs
Additional information has been added to the payload of github.event for scheduled runs. Before this change, github.event for scheduled runs would only include the cron schedule. This change adds information about the repository, organization, and enterprise (when available). For questions, visit the GitHub Actions community. To see what’s next for Actions, visit our public roadmap.

anyone know if :
can you run a github action before a webhook? or force the webhook to run after an action is completed? 🧵

does anyone know if its possible to kick off a workflow from repo X when we merge to main on repo Y ?

GitHub Actions: Self-hosted runners now support Windows ARM hardware
GitHub Actions: Self-hosted runners now support Windows ARM hardware

is it possible to get the full json payload of a pull request within an action?