Traduzir "merge your branch" para polonês

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 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 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 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 -branch argument lets you specify a specific branch to clone instead of the branch the remote HEAD is pointing to, usually the main branch. In addition you can pass a tag instead of branch for the same effect.

• branch argument lets
• specify a specific
• branch the remote
• usually the main
• same

EN Your space station is growing, and it's time for the opening ceremony of your Mars location. Now that your future plans are becoming a reality, you can merge your future-plans branch into the main branch on your local system.

• Mars location
• reality
• merge your future-plans
• local

EN Because you created only one branch and made one change, use the fast-forward branch method to merge

• Because you created
• branch
• made one change
• fast-forward branch method
• merge

EN You can do a fast-forward merge because you have a linear path from the current branch tip to the target branch

• fast-forward merge because
• current branch tip
• target branch

EN Merge changes from the future-plans branch into the main branch. It will look something like this:

• main branch

EN Creating a "branch" in VCS tools keeps multiple streams of work independent from each other while also providing the facility to merge that work back together, enabling developers to verify that the changes on each branch do not conflict

• VCS tools keeps
• each other while
• providing the facility
• together
• changes on each
• conflict

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 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 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 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 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 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 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 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 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 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 Our premium plan lets you enforce merge checks i.e., until the merge conditions are met, the PR will not be merged. 

• premium plan lets
• enforce merge checks
• until the merge
• met
• merged

EN Our premium plan lets you enforce merge checks i.e., until the merge conditions are met, the PR will not be merged. 

• premium plan lets
• enforce merge checks
• until the merge
• met
• merged

EN What is the difference between a merge check and an enforced merge check?

• check
• enforced merge check

EN Create a Git repository Copy your Git repository and add files Pull changes from your Git repository on Bitbucket Cloud Use a Git branch to merge a file

• Create a Git
• Copy your Git
• add files Pull
• branch to merge
• file

EN When you’re ready to merge the changes, you’ll push your branch to Bitbucket so that it can be reviewed in a pull request.

• ready to merge
• changes
• push your branch

EN Ensure that your team is shipping secure software with Bitbucket’s branch permissions and enforced merge checks

• shipping secure software
• branch permissions
• enforced merge checks

EN Destination: The repository and branch where you want to merge your changes into.

• Destination
• repository
• merge your changes

EN When you’re ready to merge the changes, you’ll push your branch to Bitbucket so that it can be reviewed in a pull request.

• ready to merge
• changes
• push your branch

EN Destination: The repository and branch where you want to merge your changes into.

• Destination
• repository
• merge your changes

EN When you’re ready to merge the changes, you’ll push your branch to Bitbucket so that it can be reviewed in a pull request.

• ready to merge
• changes
• push your branch

EN Destination: The repository and branch where you want to merge your changes into.

• Destination
• repository
• merge your changes

EN When you’re ready to merge the changes, you’ll push your branch to Bitbucket so that it can be reviewed in a pull request.

• ready to merge
• changes
• push your branch

EN Destination: The repository and branch where you want to merge your changes into.

• Destination
• repository
• merge your changes

EN Ensure that your team is shipping secure software with Bitbucket’s branch permissions and enforced merge checks

• shipping secure software
• branch permissions
• enforced merge checks

EN You've essentially moved the pointer for the main branch forward to the current head and your repository looks something like the fast forward merge above.

• You've essentially moved
• current head
• repository looks something
• fast forward merge

EN Restrict access to certain users, and control their actions with branch permissions and merge checks for quality code.

• users
• control their actions
• branch permissions

EN Restrict access to certain users, and control their actions with branch permissions and merge checks for quality code.

• users
• control their actions
• branch permissions

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 Source: The repository and branch where you made the code changes that you want to merge.

• Source
• repository

EN To merge the branch you will have to open a new pull request.

• merge the branch

EN Enforced merge checks allow you to require that certain conditions are met on pull request merges for individual branches or branch patterns

• Enforced merge checks
• require that certain
• met on pull
• merges for individual
• branch patterns

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 Give developers the right access, to the right code, at the right time. Manage and override existing access for specific users and enable merge restrictions at the branch level.

• access
• right code
• Manage
• override existing access
• specific users
• enable merge restrictions
• branch

EN Source: The repository and branch where you made the code changes that you want to merge.

• Source
• repository

EN To merge the branch you will have to open a new pull request.

• merge the branch

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 Restrict access to certain users, and control their actions with branch permissions and merge checks for quality code.

• users
• control their actions
• branch permissions

EN Source: The repository and branch where you made the code changes that you want to merge.

• Source
• repository