{"version":"2.1.281","anchor":"credential-file-sync-block-new-wording-and-a-push-option","canonical_anchor":"credential-file-sync-block-new-wording-and-a-push-option","heading":"Credential-file sync block: new wording and a push option","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/credential-file-sync-block-new-wording-and-a-push-option","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Credential-file sync block: new wording and a push option\n\nThe warning about credential-like files blocking sync now suggests amending or rebasing, or pushing the branch first\n\n**Unclear.** The finding does not say which sync feature shows this message.\n\n**What**\n\nThe message shown when commits contain files that look like credentials (passwords, keys and similar), which sync will not carry, has new wording. It now suggests removing those files from the commits by amending them (editing the latest commit) or rebasing (rewriting earlier commits).\n\nWhen the branch can be pushed, it adds \"or push this branch first if the commits belong on origin\".\n\n**Why**\n\nThe message now tells you how to get past the block, including the option of pushing to your own remote repository when the commits are meant to be there."}