From: Elijah Newren <newren@gmail.com>
To: Matthew McClure <matt@continuousdelta.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: How to track history of personal changes in a repository?
Date: Thu, 29 Aug 2019 10:04:29 -0700 [thread overview]
Message-ID: <CABPp-BE0ij8zF22xbvjbcq3vG-VwWjUmjNo45Lsm0BEnH=iZ-A@mail.gmail.com> (raw)
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:
>
> 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'.)
next prev parent reply other threads:[~2019-08-29 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 14:32 How to track history of personal changes in a repository? Matthew McClure
2019-08-29 17:04 ` Elijah Newren [this message]
2019-08-29 17:55 ` Matthew McClure
2019-08-30 15:21 ` Elijah Newren
2019-08-31 13:32 ` Philip Oakley
2019-09-03 12:57 ` Matthew McClure
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABPp-BE0ij8zF22xbvjbcq3vG-VwWjUmjNo45Lsm0BEnH=iZ-A@mail.gmail.com' \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=matt@continuousdelta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).