Перекладіть "i branch hotfix" на Англійська

EN Hotfix branches are a lot like release branches and feature branches except they're based on main instead of develop

• lot like release
• feature branches except
• based on main
• develop

EN Similar to finishing a release branch, a hotfix branch gets merged into both main and develop.

• Similar to finishing
• release branch
• hotfix branch gets
• both main

EN Making release branches is another straightforward branching operation. Like feature branches, release branches are based on the develop branch. A new release branch can be created using the following methods.

• Making release branches
• another straightforward branching
• feature branches
• develop branch

EN Once the hotfix is complete it is merged to both develop and main

• Once the hotfix
• both develop
• main

EN List the branches for this repository. You’ll see the default branch master, and the new branch you created. git branch

• List the branches
• repository
• default branch master
• branch you created
• git branch

EN List the branches for this repository. You’ll see the default branch master, and the new branch you created. git branch

• List the branches
• repository
• default branch master
• branch you created
• git branch

EN This branch will contain the complete history of the project, whereas main will contain an abridged version. Other developers should now clone the central repository and create a tracking branch for develop.

• branch will contain
• project
• abridged version
• central repository
• create a tracking

EN List the branches for this repository. You’ll see the default branch main, and the new branch you created. git branch

• List the branches
• repository
• default branch main
• branch you created
• git branch

EN Typically, the developer will specify their feature branch as the source branch and the main branch as the destination branch.

• Typically
• developer will specify
• source branch
• destination

EN In addition to the feature and release flow, a hotfix example is as follows:

• release flow

EN Features are generally merged into the develop branch, while release and hotfix branches are merged into both develop and main. Pull requests can be used to formally manage all of these merges.

• Features are generally
• develop branch
• while release
• both develop
• main
• used to formally

EN Pipelines can be aligned with the branch structure, making it easier to work with branching workflows like feature branching or git-flow. 

• branch structure
• making it easier
• branching
• git-flow

EN The default development branch. Whenever you create a git repository, a branch named "main" is created, and becomes the active branch.

• default development branch
• Whenever you create
• git repository
• branch named
• created
• becomes the active

EN From the popup that appears, select a Type (if using the Branching model), enter a Branch name and click Create.

• popup that appears
• select a Type
• Branching model
• enter a Branch
• click

EN Create a branch using the Git branch command. git branch

• Create a branch
• Git branch command
• git branch

EN Close branch: Select if you want to automatically close the branch when the pull request is merged.

• Close branch

EN Pipelines can be aligned with the branch structure, making it easier to work with branching workflows like feature branching or git-flow. 

• branch structure
• making it easier
• branching
• git-flow

EN The default development branch. Whenever you create a git repository, a branch named "main" is created, and becomes the active branch.

• default development branch
• Whenever you create
• git repository
• branch named
• created
• becomes the active

EN From the popup that appears, select a Type (if using the Branching model), enter a Branch name and click Create.

• popup that appears
• select a Type
• Branching model
• enter a Branch
• click

EN Create a branch using the Git branch command. git branch

• Create a branch
• Git branch command
• git branch

EN Close branch: Select if you want to automatically close the branch when the pull request is merged.

• Close branch

EN Giflow is an alternative Git branching model that involves the use of feature branches and multiple primary branches

• Git branching model
• feature branches
• multiple primary branches

EN The main branch stores the official release history, and the develop branch serves as an integration branch for features

• main branch stores
• official release history
• develop branch serves

EN The first step is to complement the default main with a develop branch. A simple way to do this is for one developer to create an empty develop branch locally and push it to the server:

• develop branch
• developer to create
• empty develop branch

EN Note that feature branches combined with the develop branch is, for all intents and purposes, the Feature Branch Workflow. But, the Gitflow workflow doesn’t stop there.

• Note that feature
• intents
• purposes
• Feature Branch Workflow
• Gitflow workflow
• stop

EN You can think of maintenance branches as ad hoc release branches that work directly with main

• think of maintenance
• ad hoc release
• directly with main

EN The default development branch. Whenever you create a git repository, a branch named "main" is created, and becomes the active branch.

• default development branch
• Whenever you create
• git repository
• branch named
• created
• becomes the active

EN From the popup that appears, select a Type (if using the Branching model), enter a Branch name and click Create.

• popup that appears
• select a Type
• Branching model
• enter a Branch
• click

EN Create a branch using the Git branch command. git branch

• Create a branch
• Git branch command
• git branch

EN Close branch: Select if you want to automatically close the branch when the pull request is merged.

• Close branch

EN For example, a plan with two jobs that are building against three branches (the plan's original branch, plus two extra branches) will contribute two jobs toward the limit.

• example
• plan with two
• building against three
• plan's original branch
• plus two extra
• contribute two jobs

EN The default development branch. Whenever you create a git repository, a branch named "main" is created, and becomes the active branch.

• default development branch
• Whenever you create
• git repository
• branch named
• created
• becomes the active

EN Pipelines can be aligned with the branch structure, making it easier to work with branching workflows like feature branching or git-flow. 

• branch structure
• making it easier
• branching
• git-flow

EN The repository history remains unchanged. All you get is a new pointer to the current branch. To begin working on the new branch, you have to check out the branch you want to use.

• repository history remains
• branch

EN Because you are creating a branch to work on something new, every time you create a new branch (with git branch), you want to make sure to check it out (with git checkout) if you're going to use it

• branch
• git branch
• git checkout

EN Notice the On branch future-plans line? If you entered git status previously, the line was on branch main because you only had the one main branch

• Notice the On
• future-plans line
• entered git status
• branch

EN Instead of “actually” merging the branches, all Git has to do to integrate the histories is move (i.e., “fast-forward”) the current branch tip up to the target branch tip

• merging the branches
• integrate the histories
• move
• current branch tip
• target branch tip

EN Before she starts writing any code, Mary needs to create a new branch for the feature. This branch is what she will use as the source branch of the pull request.

• Before she starts
• code
• pull

EN Mary wants to merge her feature into the main codebase, so the source branch is her feature branch, the destination repository is John’s public repository, and the destination branch is main

• main codebase
• feature branch
• public repository

EN Maintenance or “hotfix” branches are used to quickly patch production releases

• Maintenance
• branches are used
• quickly patch production

EN A hotfix branch can be created using the following methods:

EN Recommend specific conditions on merges for individual branches or branch patterns. Or enforce merge checks through Bitbucket Premium.

• Recommend specific conditions
• merges for individual
• branch patterns
• enforce merge checks
• Bitbucket

EN Release 14% more often with Jira Software and Bitbucket, which are seamlessly integrated from branch to deployment. Create Bitbucket branches from within Jira Software or transition issues without ever leaving Bitbucket.

• Release more often
• Jira Software
• Bitbucket
• deployment
• Create Bitbucket branches
• within Jira Software
• transition issues without
• leaving

EN Release 14% more often with Jira Software and Bitbucket, which are seamlessly integrated from branch to deployment. Create Bitbucket branches from within Jira Software or transition issues without ever leaving Bitbucket.

• Release more often
• Jira Software
• Bitbucket
• deployment
• Create Bitbucket branches
• within Jira Software
• transition issues without
• leaving

EN From the repository, click + in the global sidebar and under Get to work, select Create a branch.

• repository
• click
• global sidebar

EN Make your changes locally and then add, commit, and push your changes to the  branch:git add . git commit -m "adding a change from the feature branch" git push origin

• changes locally
• then add
• commit
• push your changes
• add
• git commit
• git push origin

EN Merge a pull requestAfter your code has been reviewed and approved in a pull request, click the Merge button to merge your branch into the main branch

• Merge a pull
• request
• click the Merge
• merge your branch
• main branch

EN The code changes from the source branch are now fully incorporated into the target branch.

• target

EN Recommend specific conditions on merges for individual branches or branch patterns. Or enforce merge checks through Bitbucket Premium.

• Recommend specific conditions
• merges for individual
• branch patterns
• enforce merge checks
• Bitbucket

EN From the repository, click + in the global sidebar and under Get to work, select Create a branch.

• repository
• click
• global sidebar