A
A
Artur Karapetyan2020-12-22 13:11:08
git
Artur Karapetyan, 2020-12-22 13:11:08

Correct permission of conficts during PR merge?

Hello, I just can't figure out what seems to be a simple thing.

I have a branch develop, it contains some feature that I want to merge into the branch master. These 2 branches differ from each other by 1 commit (in the develop branch of the path for the test environment, in master for the sale).
I create a PR and follow the instructions . After I fix the conflicts, the paths in the develop branch change from test to production, those commits from master "leak" into develop.

How can I fix PR conflicts so that unnecessary commits do not get into develop?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
V
Vitsliputsli, 2020-12-22
@Vitsliputsli

How can I fix PR conflicts so that unnecessary commits do not get into develop?

Don't commit too much in develop. Delete the extra commit.
Prod and test should not differ in code. If you still really want to put something like this under version control, then keep both configs there, and switch between them on a specific server.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question