1
0
mirror of synced 2026-01-29 12:00:58 -05:00
Files
docs/translations/ru-RU/content/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts.md
James M. Greene 885da5b3d3 Local run of Translations patching process over batch (#19360)
* New Crowdin translations by Github Action

* Reset broken translated files to English

* Ran script/i18n/homogenize-frontmatter.js

* Ran script/fix-translation-errors.js

* Reverted translated files with parsing and rendering errors

* fix malformed liquid

* add next directory to exclude list

* currentversion -> currentVersion

* fix liquid errors

* fix liquid errors

* Reset broken translated files to English

* Ran script/i18n/homogenize-frontmatter.js

* Revert /ja/github/authenticating-to-github/about-authentication-with-saml-single-sign-on

* Reset known broken translation files LAST

* Run script/i18n/homogenize-frontmatter.js

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
Co-authored-by: Rachael Sewell <rachmari@github.com>
Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
2021-05-18 15:07:05 +00:00

369 B

title, intro, mapTopic, redirect_from, versions, topics
title intro mapTopic redirect_from versions topics
Addressing merge conflicts If your changes have merge conflicts with the base branch, you must address the merge conflicts before you can merge your pull request's changes. true
/articles/addressing-merge-conflicts
free-pro-team enterprise-server github-ae
* * *
Pull requests