How to make changes that only i can see?

For example Id like to modify the login page, so it auto-logs me.

I want those changes to ONLY work on my development station and dont be visible in push. if I make it on a branch than i would have to somehow un-merge that change before every push.

  • If you write a file to the index in a merge that was conflicted, how do you go back to the conflicted state?
  • Shortcut for git add --ignore-removal?
  • Git: what exactly causes remote branches to update?
  • How to unsquash a commit?
  • Git command to checkout any branch and overwrite local changes
  • What is a blob under the hood?
  • is that supported by git?

  • installing gitorious in windows xp
  • What ReSharper files should I keep and what files should I ignore in Source Control?
  • How can I find which commit introduced a specific line in git? Or is there a better alternative?
  • Android Studio .iml git issue
  • When do I need to run “git pull --all”?
  • How do I selectively merge files from branch into master in git?
  • 3 Solutions collect form web for “How to make changes that only i can see?”

    Why don’t use setup a gitattributes filter driver?

    smudge

    Every time to checkout your directory, it will check through a script in the smudge step) for that file (and that file only) if certain condition are met (as in “this is or is not your development station”) and will modify the content accordingly.
    The clean step would restore its content or at least ignore that particular modification.

    If you have at least Git 1.7.0, you might like this bit of ‘plumbing’:

    git update-index --skip-worktree -- path
    

    From the git update-index manpage under “Skip-worktree bit”:

    Skip-worktree bit can be defined in one (long) sentence: When reading
    an entry, if it is marked as skip-worktree, then Git pretends its
    working directory version is up to date and read the index version
    instead.

    To elaborate, “reading” means checking for file existence, reading file
    attributes or file content. The working directory version may be
    present or absent.

    The “skip-worktree bit” is the basis for the sparse checkout mechanism documented in the git read-tree manpage`.


    There is a related ‘bit’ in older versions of Git (git update-index --assume-unchanged), but it should not be used for the OP’s purpose. It seems like it might be useful for the OP’s situation, but Git’s maintainer has said that its contract (the “promise”) makes it unsuitable for such purposes.

    I’m not sure I understand the question: why can’t you just branch off? Have master your main, public branch and keep rebasing your private branch on master (or merging master with your private branch). Never bring your chances to master, only bring changes from master to your private branch.

    If you happen to make changes on your private branch that you’d like to share with master there’s no problem to cherry-pick the changes onto master.

    Git Baby is a git and github fan, let's start git clone.