Traduzir "изменений сделаны коммиты" para inglês

EN Enter the git status command to be sure you have all your changes committed and find out what branch you have checked out.

• Enter the git
• changes committed

EN This lets you create highly focused commits, even if you’ve made a lot of local changes.

• lets you create
• focused commits
• made a lot
• local

EN Open the sheet and click Highlight Changes  on  the toolbar. The Highlight Changes window appears.

• Open the sheet
• click Highlight Changes
• toolbar
• Highlight Changes window

EN Track changes tracks all changes made to documents and enables you to accept/reject them later.

• Track changes tracks

EN Check out the release video and the OpenMW-CS release video by the prodigious Atahualpa, and see below for the full list of changes.

• video
• OpenMW-CS release video
• prodigious Atahualpa

EN Check out the release video and the OpenMW-CS release video by the prodigious Atahualpa, and see below for the full list of changes.

• video
• OpenMW-CS release video
• prodigious Atahualpa

EN Undoing Changes: git reset Reset, Checkout, and Revert: Commit-level Operation Reset, Checkout, and Revert: File-level Operations Undoing Changes: git clean

• Undoing Changes
• git reset Reset
• Checkout
• Revert
• Commit-level Operation Reset
• File-level Operations Undoing
• git clean

EN Open the sheet and click Highlight Changes  on  the toolbar. The Highlight Changes window appears.

• Open the sheet
• click Highlight Changes
• toolbar
• Highlight Changes window

EN Improve efficiency by connecting branches, commits, and pull requests to Jira Software issues.

• branches
• commits
• Software

EN Get clean and clear commits with Sourcetree's interactive rebase tool.

• clean
• interactive rebase

EN Correlate deployments and commits to incidents directly from Opsgenie.

• Correlate deployments
• commits to incidents

EN Improve efficiency by connecting branches, commits, and pull requests to Jira Software issues.

• branches
• commits
• Software

EN Keep projects organized by attaching Bitbucket branches, commits, and pull requests to Trello cards

• Keep projects organized
• attaching Bitbucket branches
• commits
• cards

EN New commits are recorded in the history for the current branch, which results in a fork in the history of the project.

• commits are recorded
• branch

EN Follow-up commits will show up right next to the relevant comments.

• relevant

EN Other developers can then provide suggestions inside of the pull request, or even fix the problem themselves with additional commits.

• developers can then
• pull request
• themselves with additional

EN Access branches, build status, commits, and status on Jira issues or Trello cards

• Access branches
• build status
• commits
• status on Jira
• Trello cards

EN New commits are recorded in the history for the current branch, which results in a fork in the history of the project.

• commits are recorded
• branch

EN Improve efficiency by connecting branches, commits, and pull requests to Jira Software issues.

• branches
• commits
• Software

EN View and create branches and pull requests and view commits right inside the Jira issue development panel.

• View
• create branches
• pull requests
• view commits right
• Jira issue development

EN Access branches, build status, commits, and status on Jira issues or Trello cards

• Access branches
• build status
• commits
• status on Jira
• Trello cards

EN New commits are recorded in the history for the current branch, which results in a fork in the history of the project.

• commits are recorded
• branch

EN And when you include your issue key in commits, your Jira issue statuses update automatically.

• include your issue
• commits
• Jira issue statuses

EN Correlate deployments and commits to incidents directly from Opsgenie.

• Correlate deployments
• commits to incidents

EN And when you include your issue key in commits, your Jira issue statuses update automatically.

• include your issue
• commits
• Jira issue statuses

EN Get clean and clear commits with Sourcetree's interactive rebase tool.

• clean
• interactive rebase

EN Access branches, build status, commits, and status on Jira issues or Trello cards

• Access branches
• build status
• commits
• status on Jira
• Trello cards

EN New commits are recorded in the history for the current branch, which results in a fork in the history of the project.

• commits are recorded
• branch

EN This prevents Mary from overwriting official commits

• official commits

EN This keeps your commits as focused as possible and makes for a clean project history

• keeps your commits
• focused as possible
• project history

EN View and create branches and pull requests and view commits right inside the Jira issue development panel.

• View
• create branches
• pull requests
• view commits right
• Jira issue development

EN Keep projects organized by attaching Bitbucket branches, commits, and pull requests to Trello cards

• Keep projects organized
• attaching Bitbucket branches
• commits
• cards

EN See all deployments and commits leading up to an incident, gain insights into code changes.

• deployments
• incident

EN Follow-up commits will show up right next to the relevant comments.

• relevant

EN Other developers can then provide suggestions inside of the pull request, or even fix the problem themselves with additional commits.

• developers can then
• pull request
• themselves with additional

EN Work on the feature and make commits like you would any time you use Git

• feature
• Git

EN When ready, push your commits, updating the feature branch on Bitbucket.

• ready
• push your commits
• updating the feature

EN Now teammates comment and approve the pushed commits

• teammates comment
• approve the pushed

EN Mary adds a few commits to her feature over the course of the morning

• commits to her

EN But first, she should make sure the central repository has her most recent commits:

• recent

EN Any commits he added would also show up in the pull request.

• commits he added
• pull

EN This is the command to use if you want to permanently throw away all of the commits associated with a particular line of development.

• want to permanently

EN To start adding commits to it, you need to select it with git checkout, and then use the standard git add and git commit commands. 

• start adding commits
• checkout
• git add
• git commit commands

EN When you click the Commits option in the sidebar, you find that you have no commits because you have not created any content for your repository

• click the Commits
• sidebar
• created any content
• repository

EN Your commits are now on the remote repository (origin).

• remote repository
• origin

EN If you want to see a list of the commits you've made so far, click Commits in the sidebar.

EN It's important to understand that branches are just pointers to commits

• branches are just
• commits

EN This effectively combines the histories, since all of the commits reachable from the target branch are now available through the current one.

EN Click Commits and you can see the commit you made on your local system

• Click Commits
• commit you made
• local system

EN In addition to checking out old commits and old file revisions, git checkout is also the means to navigate existing branches

• addition to checking
• old commits
• old file revisions
• means to navigate
• branches