"commit of pull aanvraag" тілін Ағылшын тіліне аударыңыз

EN Clicking on Mary’s pull request will show him a description of the pull request, the feature’s commit history, and a diff of all the changes it contains.

• him a description
• pull request
• commit history

EN Simply set a trigger, like a commit or pull request, and customize with your rules, like updating a Jira issue, reassigning an issue for QA, and more.

• commit
• pull request
• updating a Jira
• reassigning an issue
• QA

EN Update Jira issues, send Slack/MS Teams messages and run any action you can dream of, using triggers like ‘When PR is merged’ or ‘When commit is created’.

• Update Jira issues
• send Slack
• MS Teams messages
• run any action

EN Include an issue key in a commit, branch name, or PR and it will automatically update in Jira.

• Include an issue
• commit
• branch name
• PR

EN He can either post a comment to the pull request as a whole, or he can select a specific commit in the feature’s history to comment on.

• He can either
• he can select
• history to comment

EN This commit is automatically added to the original pull request, and John can review the changes again, right next to his original comment.

• commit is automatically
• original pull request
• John can review
• changes again
• original

EN You can see this pull request from the Pull requests lists in the side navigation of your repository.

• Pull requests lists

EN You can also find open pull requests from the Pull requests tab on your Dashboard

• open pull requests
• Pull requests tab
• Dashboard

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 You can see this pull request from the Pull requests lists in the side navigation of your repository.

• Pull requests lists

EN You can also find open pull requests from the Pull requests tab on your Dashboard

• open pull requests
• Pull requests tab
• Dashboard

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 On the Your work dashboard you’ll see open pull requests that have you as a reviewer, open pull requests you’ve created, and a list of repositories you can access.

• dashboard
• open pull requests
• reviewer
• created
• list of repositories

EN Pull requests are where code review happens in Bitbucket, and the Pull requests view helps you quickly find what needs your attention. 

• code review happens
• Bitbucket
• Pull requests view
• attention

EN You can see this pull request from the Pull requests lists in the side navigation of your repository.

• Pull requests lists

EN You can also find open pull requests from the Pull requests tab on your Dashboard

• open pull requests
• Pull requests tab
• Dashboard

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 With Bitbucket, spend less time on code reviews with an experience that makes it easier to identify changes and juggle multiple pull requests. Assign tasks or create Jira issues directly from your pull request.

• Bitbucket
• experience that makes
• easier to identify
• juggle multiple pull
• Assign tasks
• create Jira issues
• pull

EN In the Data File Transfer section set the transfer type to either "Pull" (to use CDR Pull) or "Push-Daily" (to use CDR Push)

• File Transfer section
• CDR Pull
• CDR Push

EN Then click the Data File Transfer tab - on this screen you can configure the actual transfer options (choosing either "Pull" for CDR Pull or "Push - Daily" for CDR Push)

• File Transfer tab
• actual transfer options
• choosing either
• CDR Pull
• CDR Push

EN The above diagram shows a pull request that asks to merge a feature branch into the official main branch, but there are many other ways to use pull requests.

• above diagram shows
• merge a feature
• official main branch

EN After Bitbucket has her feature branch, Mary can create the pull request through her Bitbucket account by navigating to her forked repository and clicking the Pull request button in the top-right corner

• feature branch
• Mary can create
• her forked repository
• clicking the Pull
• corner

EN John can access all of the pull requests people have filed by clicking on the Pull request tab in his own Bitbucket repository

• John can access
• filed by clicking
• Pull request tab
• his own Bitbucket

EN Internally, the git checkout command simply updates the HEAD to point to either the specified branch or commit

• Internally
• git checkout command
• updates the HEAD
• point to either
• specified branch
• commit

EN When it points to a branch, Git doesn't complain, but when you check out a commit, it switches into a “detached HEAD” state.

• Git doesn't complain
• detached

EN The Other Dinner is an experimental and interactive dinner that investigates the meat culture of the past, the present and the future.

• past
• present

EN Full-colour catalog gives an overview of the Connected programme 2003-2005.

• Full-colour catalog gives
• programme

EN Waag is one of the partners within the COMMIT research programme

• research programme

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 Auto-complete tasks with commit messages, create tasks from bug reports and link to commits straight from MeisterTask.

• messages
• reports
• link to commits

EN The COMMIT program brings together leading researchers in search engines, parallel computing, databases, interaction in context, embedded systems and…

• COMMIT program brings
• engines
• parallel computing
• databases
• interaction in context
• embedded systems

EN Are you a (fashion) designer, developer, medical-expert or just interested in practical applications of smart textiles for well-being? Join us!

• fashion
• designer
• developer
• medical-expert
• applications of smart
• well-being

EN (Thanks to Joes Janmaat, intern for COMMIT /Touch at Waag)

• Thanks to Joes
• intern for COMMIT
• Touch at Waag

EN Automatically see which repositories your team works across right within the Code in Jira view. Simply include an issue key in a commit, branch name, or PR summary from Bitbucket, and it will automatically update in Jira.

• team works across
• within the Code
• Jira view
• branch name

EN Each piece of work - whether it’s an idea, a commit, or branch – is linked to a Jira ticket, which ladders up into top-level visibility and insights.

• whether
• idea
• commit
• branch
• ticket
• visibility

EN Internally, the git checkout command simply updates the HEAD to point to either the specified branch or commit

• Internally
• git checkout command
• updates the HEAD
• point to either
• specified branch
• commit

EN When it points to a branch, Git doesn't complain, but when you check out a commit, it switches into a “detached HEAD” state.

• Git doesn't complain
• detached

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 Internally, the git checkout command simply updates the HEAD to point to either the specified branch or commit

• Internally
• git checkout command
• updates the HEAD
• point to either
• specified branch
• commit

EN When it points to a branch, Git doesn't complain, but when you check out a commit, it switches into a “detached HEAD” state.

• Git doesn't complain
• detached

EN The tree of actual checked out files, normally containing the contents of the HEAD commit's tree and any local changes you've made but haven't yet committed.

• tree of actual
• files
• HEAD commit's tree
• local changes you've
• haven't yet

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 Bitbucket Pipelines is managed as code - commit a yaml file with your CLI commands and environment variables and kick builds off immediately

• code
• commit a yaml
• CLI commands
• environment variables
• kick builds off

EN Developer license* keys (lets you test the upgrades before committing!)

• Developer
• keys
• lets you test
• upgrades before committing

EN In this example a clone of ＜repo＞ is made and only the most recent commit is included in the new cloned Repo

• example a clone
• made
• cloned Repo

EN Shallow cloning is most useful when working with repos that have an extensive commit history

• useful when working
• extensive commit history

EN Bitbucket Pipelines is managed as code - commit a yaml file with your CLI commands and environment variables and kick builds off immediately

• code
• commit a yaml
• CLI commands
• environment variables
• kick builds off

EN To correct the error, Mary adds another commit to her feature branch and pushes it to her Bitbucket repository, just like she did the first time around

• correct the error
• Mary adds another
• her feature branch
• Bitbucket repository
• just like she
• around

EN GitHub has been around since 2008, when cofounder Chris Wanstrath created the first code commit for what would become the world’s leading platform for software development

• since
• cofounder Chris Wanstrath
• development

EN GitHub has been around since 2008, when cofounder Chris Wanstrath created the first code commit for what would become the world’s leading platform for software development

• since
• cofounder Chris Wanstrath
• development