Anonymization tips for double-blind submission

A last-minute help list
Academic
Author

Zeel B Patel

Published

October 26, 2021

  1. Use following command locally to search for author names, institute name and other terms you think may violate double-blind
git grep <query>

Above command matches the query everywhere and thus a safe way. Avoid GitHub search for this purpose, it fails to identify some terms many times and there is no regex there (yet)!

  1. Do not use full paths inside README file. If you move content in other repo, the links will either become unusable or may violate double-blind. So follow the example below.

    • Bad practice: [link](https://github.com/patel-zeel/reponame/blob/master/dataset)

    • Good practice: [link](dataset)

  2. Point no. 2 does not work for GitHub pages links (username.github.io/stuff). Thus, keep in mind to manually update those (if you have a better idea, let everyone know in comments below)

  3. Download the repo zip locally and create an anonymized repository in your anonymized GitHub account. Open the GitHub web editor by pressing “.” (dot) at repo homepage.

  4. Now, you can select and drag all folders to the left pan of the web editor to upload them at once. Finally, commit with a meaningfull message and the changes will automatically be uploaded to the mail branch of your anonymized repo.

  5. Update the link in your manuscipt and submit !!

Edit:

After acceptance, transfer the ownership to personal account and delete the ownership of anonymized account from the personal account. This will remove all the traces of repository from the anonymized account. However, repository will still show that the commits were made by anonymized account which is anyway not violation of the doule-blind explicitely.