2

Let's assume that I want to comment out the login verification or hardcode a password in an application, just for the personal convenience of logging in immediately while developing.

I don't want to ever commit this change and I am 100% sure that I am not going to modify the source file for other reasons. In git I would use skip-worktree. I've seen that in Mercurial offers a "secret" phase, but that is a completely new concept for me. Can I make this a "secret" commit and be sure it will never pop-up in the official repo?

lib
  • 2,918
  • 3
  • 27
  • 53

1 Answers1

1

"Secret" phase treat whole changeset as secret (all commits from your confidential to tip and all next made). So you will not be able to push them to public server. You'll have to rebase them to "non-secret" branch before push, but it is annoying and vulnerable to a fateful mistake.

Jacek Szumigaj
  • 113
  • 2
  • 8
  • Thanks for the answer.. With further thinking, probably this is not good to my use case, since I will want to commit the children – lib Feb 06 '17 at 21:37