Options: 1. Add such files to .gitignore 2. git checkout ... 3. git merge --strategy=ours ...
Regards On Wed, Aug 19, 2020 at 10:00 PM Leam Hall <leamh...@gmail.com> wrote: > Hopefully I can explain this well... > > We have some files that are generated as a part of the build process. So > they can get updated frequently during some coding events. They must be in > the repo since other tools use these specific files, but do not run the > build process. However, if there is a push to the master repo, a merge > conflict isn't really an issue, since the files will get regenerated during > build. > > Is there a way to mark files as "Keep in the repo, use the current copy, > and don't worry about merge-conflicts"? > > Thanks! > > Leam > > -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to git-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/git-users/a117a00c-824b-4b1b-b617-84d995d69254o%40googlegroups.com > <https://groups.google.com/d/msgid/git-users/a117a00c-824b-4b1b-b617-84d995d69254o%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Constantine Shulyupin -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/CAE7jHC_S3tvRYshw%3DvhRF0L8s2m-qNjhZkB7J3Xy_9qZAV7ofw%40mail.gmail.com.
