Add flag to force mut to sync redirects#78
Merged
Conversation
cbush
approved these changes
Feb 3, 2025
|
|
||
| --json print published urls as json | ||
| --dry-run do not actually do anything | ||
| --dry-run do not actually do anythinggi |
There was a problem hiding this comment.
🤌
Suggested change
| --dry-run do not actually do anythinggi | |
| --dry-run do not actually do anything |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DOP-5355
Notes and Context
Redirects have not been uploading to S3 on Netlify builds and this PR is an attempt to address this.
This PR adds a
force_sync_redirectsflag to themut-publishcommand. Passing in this flag will now ensure that redirects in the.htacessfile are synced with S3 regardless of which git branch is being built.