Dealing with a large pull request
I’m currently working on a project with a team that’s using a git workflow. It’s fairly simple: master should be in a deployable state and branches are used to create features and hotfixes. Whenever we have a feature or bugfix completed and tested then we move that over to master as soon as we can. The idea is that branches should be as small as possible to make it easier to merge them back into master. We have a policy that any code pushed to master branch should be in a deployable state and pass the tests.
Dealing with a large pull request
I’m currently working on a project with a team that’s using a git workflow. It’s fairly simple: master should be in a deployable state and branches are used to create features and hotfixes. Whenever we have a feature or bugfix completed and tested then we move that over to master as soon as we can. The idea is that branches should be as small as possible to make it easier to merge them back into master. We have a policy that any code pushed to master branch should be in a deployable state and pass the tests.
Dealing with a large pull request
I’m currently working on a project with a team that’s using a git workflow. It’s fairly simple: master should be in a deployable state and branches are used to create features and hotfixes. Whenever we have a feature or bugfix completed and tested then we move that over to master as soon as we can. The idea is that branches should be as small as possible to make it easier to merge them back into master. We have a policy that any code pushed to master branch should be in a deployable state and pass the tests.
Git work-flow for uncertain premise (pending decision)
I am not quite sure, how to name my problem. But I will start with how I usually used git.
Git work-flow for uncertain premise (pending decision)
I am not quite sure, how to name my problem. But I will start with how I usually used git.
Git work-flow for uncertain premise (pending decision)
I am not quite sure, how to name my problem. But I will start with how I usually used git.
Git work-flow for uncertain premise (pending decision)
I am not quite sure, how to name my problem. But I will start with how I usually used git.
Tomcat + Spring + CI workflow [closed]
Closed 9 years ago.
Best Git workflow suitable for our needs
I need help with the workflow that is best suitable for our needs. We are a 3-4 person team and are working on 4 different projects.
Best Git workflow suitable for our needs
I need help with the workflow that is best suitable for our needs. We are a 3-4 person team and are working on 4 different projects.