fem-on-colab/Is synced with upstream?
Determine if a ref in a repository is synced with another ref of an upstream repository
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jun 23, 2026
- License
- MIT
Pinned Snippet
uses: fem-on-colab/is-synced-with-upstream-action@f4d4a7988a560ea8c951d6779274cd230d13879b # v1.0.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| upstream-repository | Name of the upstream repository. | yes | — |
| upstream-ref | Source ref name in the upstream repository. | yes | — |
| target-ref | Traget ref name in the current repository. | yes | — |
| file-patterns | Patterns that limit which files should be compared and synced. | yes | — |
| commit-message-prefix | Prefix for automatic commit message. | yes | — |
| push-changes | Push any detected changes to a new branch, and return a failure. A non-default value should only be used while testing the action itself. | no | true |
| expect-out-of-sync | Expect upstream and target refs to be out of sync, and do not return a failure in such case. A non-default value should only be used while testing the action itself. | no | false |
| expected-target-range | If upstream and target refs are expect to be out of sync, compare the obtained difference with the one in this range. A non-default value should only be used while testing the action itself. | no | "" |
| token | Token that enables reading the upstream repository and/or writing to the target repository. | no | "" |
Outputs
no outputs