The front end needs to package the released code. What is the order of commit,pull,push and npm run build?

problem description

the front end needs to package the released code. What is the order of commit,pull,push and npm run build?

the environmental background of the problems and what methods you have tried

the front-end code needs to be packaged and released to the test machine. Before, it has always been commit, then pull, then run build, and finally push

. < H2 > add < / H2 >

current conditions do not allow me to do operations such as automatically packaging on the test machine or starting an automatic build (I do not have this permission)


the difference between the two:
1 if the local run build is not the first direct push, you need to test the machine pull to the code, and then you need to build it.
if there is a specially packaged machine in the middle, the build process is on the intermediate machine and then pushed to the test machine, which can generally be implemented automatically.
2 run build first and then push locally, which means that the test machine can pull to build good resources for publishing.


feels that there is nothing wrong with this process, and so do I. but when I pull , I add -- rebase to keep my newly submitted code first in the commit record. In order to package and not miss other people's updated code, you must pull the build first, and then submit it to your own warehouse to merge the PR to the main branch of the project, and finally release it with the code on the main branch of the project. The specific process depends on how the project members cooperate.


the packaged content should be in .gitihnore . Push the packaged content to the tester in another way, either package it on the tester, or write a build flow (package-> released script) and pack it on the baler (any machine).

Menu