Best practices in Application’s flow diagram [closed]
Closed 10 years ago.
Best practices in Application’s flow diagram [closed]
Closed 10 years ago.
Should we be using git branches or separate repositories?
So I have talked my employer into finally jumping on version control…up until now my experience with git has been for personal projects and freelance work where everything is on one server, or small scripts…so, this is a bit above my knowledge.
Should we be using git branches or separate repositories?
So I have talked my employer into finally jumping on version control…up until now my experience with git has been for personal projects and freelance work where everything is on one server, or small scripts…so, this is a bit above my knowledge.
Should we be using git branches or separate repositories?
So I have talked my employer into finally jumping on version control…up until now my experience with git has been for personal projects and freelance work where everything is on one server, or small scripts…so, this is a bit above my knowledge.
Should we be using git branches or separate repositories?
So I have talked my employer into finally jumping on version control…up until now my experience with git has been for personal projects and freelance work where everything is on one server, or small scripts…so, this is a bit above my knowledge.
Should we be using git branches or separate repositories?
So I have talked my employer into finally jumping on version control…up until now my experience with git has been for personal projects and freelance work where everything is on one server, or small scripts…so, this is a bit above my knowledge.
Should we be using git branches or separate repositories?
So I have talked my employer into finally jumping on version control…up until now my experience with git has been for personal projects and freelance work where everything is on one server, or small scripts…so, this is a bit above my knowledge.
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.