G
G
grabbee2017-06-24 14:02:20
css
grabbee, 2017-06-24 14:02:20

How to work with building a JS project in GIT?

It turns out that there are two folders, with source codes and files ready after assembly. At the same time, ready ones always change after assembly, and when changing branches / comparing / merging, there are conflicts. But the finished built files need to be saved in GIT. And during development and merging, they interfere.
After
git update-index --skip-worktree
Can't change branch and git stash doesn't work because it doesn't see changes

Your local changes to the following files would be overwritten by checkout

How to do it right?

Answer the question

In order to leave comments, you need to log in

4 answer(s)
Z
Zbiten, 2018-11-25
@Zbiten

position: fixed

T
t00rt, 2018-11-26
@t00rt

Set the parent block to position: static;
And make sure that all parent blocks also have position: static;
If the parent block has position: relative; then absolute positioning pushes the child block away from it.

V
Vladimir Rozhkov, 2017-06-24
@r0zh0k

Why store builds in git? Post them somewhere.

V
Victor, 2017-06-24
@v_decadence

Git doesn't need to store anything that can be built from source.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question