We're manually importing actions into our GHES, so the first thing i did as a good CI/

An actions-sync action about actions-sync HOT 4 CLOSED

actions commented on July 19, 2024 2

An actions-sync action

from actions-sync.

Comments (4)

hutson commented on July 19, 2024 2

Here is what our team does using an Actions workflow on our GHES instance:

name: actions-sync

on:
  workflow_dispatch:
    inputs:
      token:
        description: 'Personal access token with repo permissions to GitHub.example.com'
        required: true

jobs:
  actions-org:
    runs-on: [self-hosted, ubuntu-latest]
    steps:
      - name: setup
        run: |
          wget https://github.com/actions/actions-sync/releases/download/v202009231612/gh_202009231612_linux_amd64.tar.gz
          tar -xf gh_202009231612_linux_amd64.tar.gz
      - name: sync
        run: |
          mkdir -p cache
          # can't sync actions/cache, actions/upload-release-asset as it has "been retired and cannot be reused"
          ./bin/actions-sync sync \
            --cache-dir "cache" \
            --destination-token "${{ github.event.inputs.token }}" \
            --destination-url "https://github.example.com" \
            --repo-name-list "\
                              actions/.github,\
                              actions/actions-sync,\
                              actions/add-to-project,\
                              actions/boost-versions,\
                              actions/checkout,\
                              actions/container-action,\
                              actions/container-toolkit-action,\
                              actions/create-release,\
                              actions/delete-package-versions,\
                              actions/deploy-pages,\
                              actions/download-artifact,\
                              actions/example-services,\
                              actions/first-interaction,\
                              actions/github,\
                              actions/github-script,\
                              actions/go-versions,\
                              actions/hello-world-docker-action,\
                              actions/hello-world-javascript-action,\
                              actions/heroku,\
                              actions/http-client,\
                              actions/humans.txt,\
                              actions/javascript-action,\
                              actions/jekyll-build-pages,\
                              actions/labeler,\
                              actions/node-versions,\
                              actions/publish-action,\
                              actions/python-versions,\
                              actions/runner,\
                              actions/setup-dotnet,\
                              actions/setup-elixir,\
                              actions/setup-go,\
                              actions/setup-haskell,\
                              actions/setup-java,\
                              actions/setup-node,\
                              actions/setup-python,\
                              actions/setup-ruby,\
                              actions/stale,\
                              actions/starter-workflows,\
                              actions/toolkit,\
                              actions/typescript-action,\
                              actions/upload-artifact,\
                              actions/versions-package-tools,\
                              actions/virtual-environments,\
                              actions/virtual-environments-packages"

from actions-sync.

andymckay commented on July 19, 2024 1

That sounds like a great idea. There's at least one situation where an Action wouldn't work, the case where an instance of GHES is completely air gapped from the rest of the internet. However, I think for the moment we could figure out what an Action would look like, the permissions required and at least document this well in this repo if people wanted to do that.

from actions-sync.