How to version control source qmd files when using quarto publish?

[harishnkr]

Description

I use quarto publish gh-pages based on the official documentation. This means that git is configured to upload the rendered output in the gh-pages branch. Now I want to know of the approaches to be taken to version control the source files. When uploading the source files to the main branch, for example, there would be huge differences and merge conflicts between the gh-pages and the main branch. Another approach would be to store the source files in a separate repository. If so, how do I go about it. I would also like to know what are the other approaches taken to solve this issue if the approach I mentioned is not efficient. Also I believe a separate repo would also help in case I have to save drafts and not publish content unless completed. The source branch can be kept private as and when required.

[mcanouil]

I don't understand your workflow.

If you are using quarto publish gh-pages it means you have a Git repository that contains your source files and that you are using a gh-pages branch where the rendered files are uploaded (committed and pushed).
So, you only have to use Git to commit and push your source file changes (see online documentation about using Git)

Why there would be merge conflict? The gh-pages is not supposed to be merged with anything. It's a special branch used by GitHub to deploy a web server.