qte77/Cross-Repo Issue Sync

Bidirectional GitHub issue sync across repos with mirror issues, markdown generation, and Projects board aggregation.

Trust Signals

workflow.ymlSHA-pinned

uses: qte77/gha-cross-repo-issue-sync@ddcb3f057e20eeac7d08df1f28b8a181ee034daa # v0.4.4

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

name	description	required	default
direction	Sync direction: pull (repos→tracker), push (tracker→repos), or both	yes	—
tracker_repo	Tracker repo (e.g. owner/.github-private-project-tracker)	yes	—
repos_file	Path to repos.txt (one repo name per line). Used for pull sync.	no	repos.txt
repos	Comma-separated repo list (alternative to repos_file). Used for pull sync.	no	—
repo_source	Source for repo list: file (from repos_file/repos) or account (auto-discover all repos for owner)	no	file
include_forks	Include forked repos in account mode	no	false
include_archived	Include archived repos in account mode	no	false
owner	GitHub owner/org for tracked repos	no	${{ github.repository_owner }}
token	GitHub token with Issues read+write on all repos	yes	${{ github.token }}
project_id	GitHub Projects board ID. If set, adds issues to the board.	no	—
generate_markdown	Generate TODO.md and DONE.md in the working directory	no	true
dry_run	Preview without making changes	no	false
event_action	Issue event action (for push sync). Auto-set from github.event.action.	no	${{ github.event.action }}
event_issue_number	Issue number that triggered the event (for push sync).	no	""
event_label	Label name from the event (for labeled/unlabeled).	no	""
event_assignee	Assignee login from the event (for assigned/unassigned).	no	""

no outputs