Examples of using Code changes in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
The code changes every two minutes.
Partial redisign because of structural code changes.
Multiple code changes and improvements.
First, you create a branch for your code changes.
The code changes automatically at midnight.
Investing in CI results in fast feedback on code changes.
Smaller code changes, conflicts are simpler.
We can, because apparently, the code changes during your life.
This code changes with each created widget.
RNA is equally important andis in fact the messenger that relays code changes to DNA.
Version control Enables developers to manage code changes conveniently, including reverting and"change porting.
Realize the benefits of using containers for applications-with little or no code changes.
Close the loop for traceability between code changes and issues when you connect Fisheye to Jira Software.
CloudWatch Logs uses your log data for monitoring; so, no code changes are required.
Successful CI means new code changes to an app are regularly built, tested, and merged to a shared repository.
She might update her working branch multiple times with code changes in response to comments.
This made merging code changes difficult and time-consuming, and also resulted in bugs accumulating for a long time without correction.
The Obnam user interface is not currently translatable,and making it so will require code changes.
Continuously integrate your code with Bamboo and see which code changes triggered your builds in FishEye.
The current production database could be detached,and the new database attached- all without any code changes.
Maintenance of the Apache HTTP server and related packages in Debian: code changes, reproducing bugs, talking to upstream etc.
This parameter mainly serves to achieve a switch between the two modes with minimal code changes.
Creating pull requests helps other users see and review your code changes before you merge them into another branch.
You can use your local Git client to push commits to the source branch,which updates the pull request with code changes.
Comes with a child theme so if you ever want to make any code changes they will not be overwritten when you update the theme.
When applied to IT development, the revolving door represents the environment in which code changes pass through.
Piwigo 2.3 in numbers: 50 new features, 600 code changes on Subversion, 6 new languages and a much shorter release cycle of 6 months.
A pull request is the primary way you and other repository users can review, comment on, and merge code changes from one branch to another.
This means that no new, big, upstream code changes will be accepted in Mageia until our final release in June; then we will re-open the doors.
All code changes are done in the main application which is then rolled out to the translated shadow applications with the"seed" and"publish" operations.