actions-marketplace-validations/tags-sync

Sync another repository new tags as branches. (upstream -> fork)

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stalelast commit Sep 23, 2022
License: None

Pinned Snippet

workflow.ymlSHA-pinned

uses: actions-marketplace-validations/chachako_tags-sync@c82db2f78e9f713cc18727cdcc8864c9de8fbaa9 # no releases — HEAD as of 2026-07-10

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
github-token	Personal access token (PAT) used to fetch and push the "head-repository". We recommend using a service account with the least permissions necessary. Also when generating a new PAT, select the least scopes necessary. [Learn more about creating and using encrypted secrets](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)	yes	—
base-repository	Base (upstream) repository name with owner. For example, torvalds/linux	yes	—
head-repository	Head (fork) repository name with owner. For example, Rust-for-Linux/linux	—	${{ github.repository }}
cloned-path	Relative path under $GITHUB_WORKSPACE to clone the head repository	—	head-repo
filter-tags	Filter tags by regular expression. For example, the regex "^v[2-9]\..*" controls tags that only sync versions larger than `v2`.	—	.*
apply-patch	URL of patch file to be applied after each tag is synced as a branch. Patch url can usually be obtained by comparing two branches or commits. The process of applying patch occurs before the "git push", so if the value is empty, it means that all new branches will be pushed directly to the "head-repository" after the tags are synced. The value based on the [URL Standard](https://url.spec.whatwg.org/). For example, apply all commits that the "head-repository" master branch is ahead of the "base-repository" master branch to each new tag: https://github.com/base-owner/base-repository/compare/master...head-owner:head-repository:master.patch	—	—
patch-message	Commit message for "git commit" when applying patch	—	""
patch-author	Author for "git commit" when applying patch	—	github-actions[bot]
patch-author-email	Author email for "git commit" when applying patch	—	github-actions[bot]@users.noreply.github.com
patch-committer	Committer for "git commit" when applying patch	—	github-actions[bot]
patch-committer-email	Committer email for "git commit" when applying patch	—	github-actions[bot]@users.noreply.github.com

Outputs

name	description
new-tags-file	A file stores the name of each new tag of the "base-repository" by line.
synced-branches-file	A file stores the name of each new branch of the "head-repository" by line, and all new branches are synchronized from new tags of the "base-repository".