diff --git a/public/partials/faq.htm b/public/partials/faq.htm index 2ca8975..8bc2f0d 100644 --- a/public/partials/faq.htm +++ b/public/partials/faq.htm @@ -351,6 +351,57 @@ +
+ +
+
+

+ Yes. The anonymized repository tracks the source on GitHub: when you push new commits to the + original repository, the anonymized view picks up those changes (cached files are refreshed + against GitHub). This means you can keep iterating on the code while reviewers have the link, + and you do not need to recreate the anonymized repository every time you update the source. +

+

+ A few practical implications worth keeping in mind: +

+
    +
  • + You can safely create the anonymized repository early in the writing process — later + commits will be visible to reviewers without any additional action. +
  • +
  • + If you rename files, add new identifiers, or introduce new contributor names after creation, + revisit the anonymization options (custom terms, file filters) to make sure the new content + is still properly anonymized. +
  • +
  • + If the original repository is made private or deleted, the anonymized repository will no + longer be able to fetch updated content. +
  • +
+
+
+
+