make-anonymous-branch

You prepare a research repository for double-blind submission by creating an anonymous branch and stripping personal identifiers from code, data, and paper files. This ensures the main branch remains untouched while meeting review requirements.

When anonymizing a git branch, you should audit common leak sources like author names, email addresses, home directories, wandb metadata, PDFs, and LaTeX output. Checking these areas prevents accidental exposure of your identity during review.

Yes, the anonymization workflow supports cleaning PDF metadata and fixing LaTeX rendering for anonymous mirrors. It handles review-readiness tasks like scrubbing metadata from generated PDFs to ensure no author information is embedded in the output files.

Yes, you can use this process to bundle code, data, and paper materials for an anonymous.4open.science submission or any double-blind publication workflow. It creates a safe anonymous submission branch that mirrors all required review materials.

To verify no personal identifiers remain after scrubbing a research repo, you perform final validation checks on the anonymous branch. This verification step ensures all identity leaks in code, metadata, and LaTeX outputs are fully resolved before submission.