{"id":3046,"date":"2022-06-07T08:10:57","date_gmt":"2022-06-07T08:10:57","guid":{"rendered":"https:\/\/gitprotect.io\/blog\/?p=3046"},"modified":"2024-03-06T08:27:47","modified_gmt":"2024-03-06T08:27:47","slug":"gitprotect-v-1-2-5-is-here-update-now","status":"publish","type":"post","link":"https:\/\/gitprotect.io\/blog\/gitprotect-v-1-2-5-is-here-update-now\/","title":{"rendered":"GitProtect v.1.2.5 Is Here – Update Now"},"content":{"rendered":"\n

GitProtect.io version 1.2.5 is already available and includes a whole series of ground-breaking features and improvements. Let’s take a look at the most remarkable ones:<\/p>\n\n\n\n\n\n\n\n

<\/div>\n\n\n
\n
\"\"<\/figure><\/div>\n\n\n

Metadata selection in the Git copy<\/h2>\n\n\n\n

When setting a backup plan<\/a> for GitHub, GitLab, and Bitbucket, now you have the option to select only specific metadata to be included in a copy – and the list is gradually expanding! Thus, you can select exactly the repositories and metadata you want to protect without having to backup all, even unused metadata.<\/p>\n\n\n\n

<\/div>\n\n\n
\n
\"\"<\/figure><\/div>\n\n\n

Type of copy selection during a manual process <\/h2>\n\n\n\n

Now you can decide for yourself whether the copy you are running with the Basic scheme should be full, incremental, or made according to the scheduler settings. Thus, we give users control over the type of manually triggered copy. <\/p>\n\n\n\n

What\u2019s more? <\/h2>\n\n\n\n

Let’s see what Grzegorz B\u0105k our Product Development Manager has to say about the newest release: <\/p>\n\n\n\n