• Can I opensource it in a way where changes is not open to the public?
  • I have google verification file on my git, is it ok to put it in the public?

The platform is gitlab.

  • @velox_vulnus
    link
    English
    12 months ago
    • By changes, are you talking about future commits? It depends on the license.
    • You mean API token? No. That goes in secrets or whatever they call it in GitLab. Make sure to generate a new one if you’re unable to remove it from the previous commits.
    • LemmyQuestOP
      link
      fedilink
      12 months ago
      • No I mean the old commits.

      • No, I mean when you list your website in google, they give you a code to host in your website to verify that you own the website.

      • Luke
        link
        English
        1
        edit-2
        2 months ago

        AFAIK, those codes don’t need to be kept private, but I think they only do that verification once, so you can probably just delete the file at this point. (After all, you can also use a TXT record to store the verification code for a domain with Google, and those are definitely not private; anyone can dig your domain’s TXT records.)