Skip to content

Conversation

@martinjagodic
Copy link
Member

Explain changes from decaporg/decap-cms#7579

@netlify
Copy link

netlify bot commented Oct 16, 2025

Deploy Preview for decap-www ready!

Name Link
🔨 Latest commit b138527
🔍 Latest deploy log https://app.netlify.com/projects/decap-www/deploys/690096240e06760008dcd0b5
😎 Deploy Preview https://deploy-preview-140--decap-www.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link

@palant palant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good apart from the one minor issue.

There is a more fundamental issue here but it isn’t a new one: this piece of documentation assumes that the repository isn’t a local checkout that needs to be synced up with a remote server. Arguably, modifying the primary repository directly should be an uncommon setup.

It is possible to add a post-commit hook that will automatically push the changes committed by Decap Proxy, yet pulling prior to commit doesn’t seem to be doable with hooks. I had to solve this by modifying my version of Decap Proxy but I’m not sure what a good general solution would look like.

@martinjagodic
Copy link
Member Author

Thanks for your review.

Updating the local folder is the intended behavior. I also changed the wording because of this. Before, docs said local repository, now it's local folder.

However, we could have a flag that would update the remote repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants