Github Workflow Sync - Github Action

Github Action To Sync Github Action's Workflow Files Across Repositories

Use Case 🤔 ?

This Github Action can come in handy when you have lot of projects like i do. where in some case certain projects users action workflow which are common across projects. Example : Project 1 & Project 2 it can be pain to keep all the workflow updated with Github Action's Module's version.

This also isn't limited to Github Action yaml files - another use case could be keeping the .editorconfig, LICENSE, tsconfig.json, tslint.json, .gitignore, etc. in sync across all your repositories.

Here where this action comes in and reduces your stress 😉 it can update all your repository actions file based on the config provided

⚙️ Configuration

Personal Access Token Scope

Github Personal Token Is required with the below scope

ℹ️ Full Repo is only required when you need to update private repository if your are updating only public repository then just select public_repo inside repo scope

Click Here To Generate A Token

REPOSITORIES Configuration Examples

WORKFLOW_FILES Configuration Examples

1. If you use = as a file seperator file1.md=myfile.md then file1 from the current repository will be copied to remote repository with the name of myfile.md
2. If you use != as a file seperator file1.md!=myfile.md then file1 from the current repository will be copied to remote repository with the name of myfile.md only if myfile.md already not exists in the remote repository

How Files Sync Work ?

Before copying the WORKFLOW_FILES from the source to destination. this action will provide some flexibility. this searchs for a file in various locations for example lets take settings.yml as the file that you want to sync for multiple repository

Below are the locations that this action search for the file/folder

• ./{OWNER}/{REPO_NAME}/workflows/{filename}
• ./{OWNER}/workflows/{filename}
• ./{WORKFLOW_FILES_DIR}/{filename}
• ./.github/workflows/{filename}
• ./{OWNER}/{REPO_NAME}/{filename}
• ./{OWNER}/{filename}
• ./{filename}

if the settings.yml is found inside workflows folder then the destination is automaitcally forced to .github/workflows in the destination repo

if the settings.yml is outside of workflows folder then the destination then its copied to the destination

How this can be useful ?

Lets assume that you want to maintain all the common github files in a single repository and suddenly a repository needs a single file to be changed in that case instead of editing the action yml file. you can just create a folder like {REPO_OWNER}/{REPO_NAME}/{FILE} to copy the overriden file to the destination

🚀 Usage

Step 1

Create a New Repository or use our Repository Template

Step 2

if you have used our template repository then edit the file inside .github/workflows/workflow-sync.yml

OR

Create a new file in .github/workflows/ named workflow-sync.yml and copy & paste the below file content

workflow-sync.yml content

name: Workflow Sync

on:
  push:
    branches:
      - master
env:
  DRY_RUN: false
  REPOSITORIES: |

  WORKFLOW_FILES: |

jobs:
  Github_Workflow_Sync:
    runs-on: ubuntu-latest
    steps:
      - name: Fetching Local Repository
        uses: actions/checkout@master
      - name: Running Workflow Sync
        uses: varunsridharan/action-github-workflow-sync@main
        with:
          DRY_RUN: ${{ env.DRY_RUN }}
          REPOSITORIES: ${{ env.REPOSITORIES }}
          WORKFLOW_FILES: ${{ env.WORKFLOW_FILES }}
          GITHUB_TOKEN: ${{ secrets.PERSONAL_ACCESS_TOKEN }}

Troubleshooting

Spacing

Spacing around the equal sign is important. For example, this will not work:

WORKFLOW_FILES: |
  folder/file-sync.yml = folder/test.txt

It passes to the shell file 3 distinct objects

• folder/file-sync.ymll
• =
• folder/test.txt

instead of 1 object

• folder/file-sync.yml = folder/test.txt

and there is nothing I can do in code to make up for that

Slashes

You do not need (nor want) leading / for the file path on either side of the equal sign

The only time you need / trailing is for folder copies. While a file copy will technically still work with a leading /, a folder copy will not

📝 Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Checkout CHANGELOG.md

🤝 Contributing

If you would like to help, please take a look at the list of issues.

💰 Sponsor

I fell in love with open-source in 2013 and there has been no looking back since! You can read more about me here. If you, or your company, use any of my projects or like what I’m doing, kindly consider backing me. I'm in this for the long run.

• ☕ How about we get to know each other over coffee? Buy me a cup for just $9.99
• ☕️☕️ How about buying me just 2 cups of coffee each month? You can do that for as little as $9.99
• 🔰 We love bettering open-source projects. Support 1-hour of open-source maintenance for $24.99 one-time?
• 🚀 Love open-source tools? Me too! How about supporting one hour of open-source development for just $49.99 one-time ?

📝 License & Conduct

• MIT license © Varun Sridharan

📣 Feedback

• ⭐ This repository if this project helped you! :wink:
• Create An 🔧 Issue if you need help / found a bug

Connect & Say 👋

• Follow me on 👨‍💻 Github and stay updated on free and open-source software
• Follow me on 🐦 Twitter to get updates on my latest open source projects
• Message me on 📠 Telegram
• Follow my pet on Instagram for some dog-tastic updates!

Built With ♥ By Varun Sridharan 🇮🇳