Until now, Subtree Split service was used to split the main repository to smaller repositories for each component (Common, Http, Plugin) and provider.
There is currently an issue with that service since mid-2022 but I just discovered it now (ping @Nyholm) and I can't seem to figure out what's going on.
Since all of our CI/CD tasks have been migrated to GitHub Actions, I thought about migrating that "Subtree split" to GitHub Actions as well and that's what this PR is about.
Detect if there are changes if component/provider directory
If there are changes, extract Git history and directory using git-filter-repo
Push "new" Git history and files to component/provider repository
This workflow requires a GitHub Personal Access Token (PAT). I've configured a personal token and have stored as SUBTREE_GITHUB_TOKEN organization secret.
Until now, Subtree Split service was used to split the main repository to smaller repositories for each component (Common, Http, Plugin) and provider.
There is currently an issue with that service since mid-2022 but I just discovered it now (ping @Nyholm) and I can't seem to figure out what's going on.
Since all of our CI/CD tasks have been migrated to GitHub Actions, I thought about migrating that "Subtree split" to GitHub Actions as well and that's what this PR is about.
This workflow is based on GitHub documentation and works like this:
git-filter-repo
This workflow requires a GitHub Personal Access Token (PAT). I've configured a personal token and have stored as
SUBTREE_GITHUB_TOKEN
organization secret.