git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to track history of personal changes in a repository?

From
Elijah Newren <newren@gmail.com>
Date
Aug 29, 2019, 17:04 UTC
Message-ID
<CABPp-BE0ij8zF22xbvjbcq3vG-VwWjUmjNo45Lsm0BEnH=iZ-A@mail.gmail.com>
In-Reply-To
<CAEV-cEryZZarfz5SQsRphBXeYMPJW7tdSfY8NYnzb_-ra-pGHw@mail.gmail.com>

On Thu, Aug 29, 2019 at 7:34 AM Matthew McClure <matt@continuousdelta.com> wrote:

Show 16 quoted lines
>
> Hi,
>
> I'm looking for a way to track history of personal changes in a repository. I'd
> like to protect against accidentally pushing the changes to a remote branch. I
> imagine this working a little like `git ignore`, and a little like a separate
> branch. It might be like a personal sub-branch that is ignored by `git
> push`. Or it might be like a history of the work tree that runs parallel to the
> reflog and to the history of any given branch.
>
> Does something like this exist in Git or a complementary tool?
>
> I found `git update-index --skip-worktree`. I imagine it might be relevant in
> some kind of workflow where I can maintain a personal-worktree branch.
>
> Does any of you have a personal workflow that addresses similar concerns?
Perhaps put all the changes in a specific branch and run:
  git config branch.${personalBranchName}.pushRemote
Do.Not.Push.Changes.From.This.Branch
?  (And make sure that push.default is not set to 'matching'.)
Previous: Matthew McClureNext: Matthew McClure
Message 2 of 6 in “How to track history of personal changes in a repository?”
  1. Matthew McClureAug 29, 2019
  2. Elijah NewrenAug 29, 2019
  3. Matthew McClureAug 29, 2019
  4. Elijah NewrenAug 30, 2019
  5. Philip OakleyAug 31, 2019
  6. Matthew McClureSep 3, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.