With Git as a version controller, there are a number of possible workflows (Workflow), which makes us new birds unaware of what kind of workflow to choose in their actual work. Here we make a comparison of the most common git workflows, providing a reference for the corporate team.As you can imagine, the design of thes
Reprint: http://blog.jobbole.com/76847/This article by Bole Online-liding translation. without permission, no reprint!English Source: Atlassian. Welcome to join the translation team.Going to a distributed version control system looks like a daunting task, but you can also use the benefits without changing the used workflow Git . Teams can Subversion develop projects in a completely unchanging way.But using
by Dong ([email protected])
This is a translation based on the original text (by Atlassian). All content on the page is shared by the knowledge sharing-attribution (CC by 2.5 AU) Agreement unless otherwise noted.
A wide variety of workflows makes it difficult to choose when implementing Git in your project. This tutorial provides a starting point to investigate the most common git workflows for ent
One of the GIT series: Version Control Concept, distributed, git introduction and workflow
Note:
Git is powerful, flexible, and easy to use.
But it is also the flexibility of git. How to execute a unified process becomes a problem during the implementation of the compan
DefinitionGit is a software this allows you to keep track of changes made to a project over time. Git works by recording the changes do to a project, storing those changes, then allowing you to reference them as NE Eded.Git project can be thought of as has three parts:
A working Directory: where you'll be doing all the work:creating, editing, deleting and organizing files
A Stagingarea: where you ' ll list changes your make to the working
As a very popular version management tool, Git is favored by many developers. So how can git play a better role? I have summarized the following best practices for Git workflow based on my experience in actual project development. Welcome everyone to shoot bricks. Pre-conditions
I use the daily development:
Git basic commands and GitFlow Workflow
This article explains some basic team collaboration commands of Git and GitFlow workflow guide.Git team collaboration commands
1. Open BranchGit branch new branch name, for example, under the master branch, a New Development branch: git
run the clip command.
Then paste the SSH key on the GitHub website, as shown in figure
17. Run ssh-T [email protected] on the command line.
Connection successful
18. associate a remote warehouse with a local warehouse
Obtain the remote repository address.
Execute git remote add origin remote repository address
19. Pull the remote warehouse
Git pull origin master
20. Upload and associate the local rep
Cakedc Git Workflow is a workflow for project development and release, in which the development and release cycles are based on several key phases (key phases):
Development:
All active development activities are milestones driven, and outputs at this stage are very unstable code baselines
Qa:
Quality assurance testing as part of a deve
. After the project is updated, submit the local update to the server, enter the directory of the local project, and executeGit statusCheck the status to make sure that all files have been tracked and committed, and then executeGit pullUpdate the local code. Enter the server password prompt, enter it, and then executeGit pushPrompt to enter the server password. After that, the local project will be submitted to the remote server.At this point, the remote access to this project found that the pro
style revision work was delayed.
This is hard to do, and all the changes have been mixed in the same branch.
The final solution is to use
Git log
I found out all the changes. Because the comparison was too troublesome, I wrote some code to do this.
Def List_commits (Branch ):Commits = Local ( ' Git log ' + Branch + ' ^ Master -- no-merges -- format = format: % s, % H ' , Capture = true)Commits
again and again.
How to avoid the wrong operation caused by the product is not complete.
These two problems are also the purpose of our workflow.I'll take a look at some of the concepts and lifecycles of git that apply to my job responsibilities.After describing the responsibilities clearly, the workflow is as follows:Finally, it is hoped that a unified git
pipeline, and the changes in each branch are related to its target characteristics, and things like browsing the code become easier. You can keep the changes you make in the feature branch for a few minutes, a few days or even months, and then merge them when they mature, without caring about the order or the progress they set up.Now let's look at a practical example. Take a look at Figure 3-20, from bottom to top, at first wemasterWork to C1, then start a new branchiss91Try to fix bug number 9
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.