Traduzir "branch you created" para polonês

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 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 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 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 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 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 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 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 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 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 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 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 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 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 Go back to your local terminal window and send your committed changes to Bitbucket using git push origin main. This command specifies that you are pushing to the main branch (the branch on Bitbucket) on origin (the Bitbucket server).

• local terminal window
• send your committed
• Bitbucket using git
• origin main
• branch
• branch on Bitbucket
• origin
• Bitbucket server

EN Branch selection: Pick the branch you want to view

• Branch selection
• Pick the branch
• want to view

EN A. Branch with new file: Change if you want to add file to a different branch. B. New file area: Add content for your new file here. 

• different branch
• file area

EN This command creates a branch but does not switch you to that branch, so your repository looks something like this:

• does not switch
• branch
• repository looks something

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 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 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 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 Under this model, developers create a feature branch and delay merging it to the main trunk branch until the feature is complete

• Under this model
• branch
• main trunk branch
• feature is complete

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 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 A complete example demonstrating a Feature Branch Flow is as follows. Assuming we have a repo setup with a main branch.

• complete example demonstrating
• Feature Branch Flow
• follows
• main

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 For a visual example, this diagram shows the main branch and the other branch with a bug fix update.

• visual example
• branch
• fix

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 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 For privacy information, go to: https://branch.io/policies/#privacy To opt-out, visit: https://branch.app.link/optout

• policies
• opt-out
• visit
• optout

EN Once created, fetch and checkout the branch from your local system. Bitbucket will automatically show you the command needed, and it will look something like this: git fetch && git checkout

• Once created
• fetch
• checkout the branch
• local system
• Bitbucket will automatically
• command needed
• git fetch
• git checkout

EN Once created, fetch and checkout the branch from your local system. Bitbucket will automatically show you the command needed, and it will look something like this: git fetch && git checkout

• Once created
• fetch
• checkout the branch
• local system
• Bitbucket will automatically
• command needed
• git fetch
• git checkout

EN Once created, fetch and checkout the branch from your local system. Bitbucket will automatically show you the command needed, and it will look something like this: git fetch && git checkout

• Once created
• fetch
• checkout the branch
• local system
• Bitbucket will automatically
• command needed
• git fetch
• git checkout

EN Once created, fetch and checkout the branch from your local system. Bitbucket will automatically show you the command needed, and it will look something like this: git fetch && git checkout

• Once created
• fetch
• checkout the branch
• local system
• Bitbucket will automatically
• command needed
• git fetch
• git checkout

EN Checkout the new branch you just created to start using it.

EN Feature branches are generally created off to the latest develop branch.

• latest develop

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

EN A develop branch is created from main

• main

EN A release branch is created from develop

• develop

EN If an issue in main is detected a hotfix branch is created from main

• issue in main
• detected a hotfix
• created from main

EN That’s because the future-plans branch never interacted with the remote repository, only the change we created and committed.

• because the future-plans
• remote repository
• change we created

EN Clones the repo at ＜repo location＞ and applies the template from ＜template directory＞ to the newly created local branch. A thorough refrence on Git templates can be found on our git init page.  

• Clones the repo
• applies the template
• newly created local
• git init page