dotgit | A comprehensive solution to managing your dotfiles | Configuration Management library

by kobus-v-schoor Python Version: 2.2.9 License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | dotgit Summary

dotgit is a Python library typically used in Devops, Configuration Management applications. dotgit has no bugs, it has no vulnerabilities, it has build file available, it has a Strong Copyleft License and it has low support. You can install using 'pip install dotgit' or download it from GitHub, PyPI.

A comprehensive solution to managing your dotfiles

Support

Quality

Security

License

Reuse

Support

dotgit has a low active ecosystem.

It has 136 star(s) with 11 fork(s). There are 9 watchers for this library.

It had no major release in the last 12 months.

There are 2 open issues and 19 have been closed. On average issues are closed in 209 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of dotgit is 2.2.9

Quality

dotgit has 0 bugs and 17 code smells.

Security

dotgit has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

dotgit code analysis shows 0 unresolved vulnerabilities.

There are 3 security hotspots that need review.

License

dotgit is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

dotgit releases are available to install and integrate.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

Installation instructions are available. Examples and code snippets are not available.

dotgit saves you 950 person hours of effort in developing the same functionality from scratch.

It has 2165 lines of code, 203 functions and 29 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed dotgit and discovered the below as its top functions. This is intended to give you an instant insight into dotgit implemented functionality, and help decide if they suit your requirements.

Updates the given files
Create a copy op
Check if the destination directory exists
Create a link between source and destination
Restore files from files
Change password for repo
Run gpg command
Save a password
Create a key from a password
Perform some sanity checks on dotfiles
Removes files from the repo
Returns the diff of all of the given categories
Activate all categories in the given category list
Return a manifest manifest
Return a list of diffs that have changed
Run a git command
Return a sorted list of file states
Removes files from the repository
Generate a commit message
Commit changes

Get all kandi verified functions for this library.

dotgit Key Features

No Key Features are available at this moment for dotgit.

dotgit Examples and Code Snippets

No Code Snippets are available at this moment for dotgit.

Community Discussions

Trending Discussions on dotgit

Gitversion using date as major version in devops build

Patch version does not increase when commits are made to feature branch in MainLine mode of GitVersion

Why does GitVersion increment the major of my version number when merging a pull request to develop?

GitVersion StackOverflow on Pull Requests

QUESTION

Gitversion using date as major version in devops build

Asked 2020-Oct-23 at 17:38

I have a couple of webapps I am adding gitversion to. Main problem - GitVersion is generating a MajorMinorPatchTag where the Major is in the format yyyymmdd. Aside from this not being a valid major version, I want the usual versioning 0.1.3.alpha.1 in the example below but I am getting 20201021.1.1.

I have removed all the old build tags from the repo so it does not appear to be finding this from tags. Is there anywhere else I can force it to ignore previous build versions and use the semver starting from the gitversion.yml/next-version setting?

Detail below:

The gitversion.yml is simple:

...

ANSWER

Answered 2020-Oct-21 at 22:42

GitTools.UseGitVersion is deprected thus I recommend you switch to GitTools bundle and then you can use it like this:

Source https://stackoverflow.com/questions/64471205

QUESTION

Patch version does not increase when commits are made to feature branch in MainLine mode of GitVersion

Asked 2020-Mar-10 at 14:02

I am trying to figure out the simple Mainline developement mode.

My observation is the following.

Each direct commit on the master branch is incrementing the patch version.
When I create a feature branch, and then when I make commits on this feature branch, the patch is not increasing. I am wondering why? Only the PreReleaseTag is increasing. Example featureBranchName.1, featureBranchName.2 and so on for each commit. Patch does not change.

Why does not the patch version increase when commits are made to feature branch? Does a feature branch always imply a prerelease?

Is there a way to increase the patch on commits to feature branch?

My GitVersion.yml file is below. The -diag output follows, if that helps.

...

ANSWER

Answered 2020-Mar-10 at 14:02

You didn't set a mode for your feature branch configuration, so it is inheriting the global configuration of Mainline. In Mainline delivery mode, versioning is calculated based on merges to the branch (usually, Mainline is only used for the master branch).

Try setting mode: ContinuousDeployment to achieve the desired result.

Source https://stackoverflow.com/questions/59920495

QUESTION

Why does GitVersion increment the major of my version number when merging a pull request to develop?

Asked 2019-Sep-02 at 14:13

We have master, and develop branches. Master is currently at 1.0.0.

From develop, I have branched out a new branch, made small changes, and changed the next-version attribute to 1.0.0. When I make a pull request, I'd expect the GitVersion to calculate it to 1.0.1 or something similar, but for some reason, it always bumps it to 2.0.0.

I've tried using +semver: major while having next-version 0.0.1, but that hasn't bumped it from 0.9.0 to 1.0.0.

I've tried using next-version 0.9.9. GitVersion incremented it to 0.10.0

I've tried using next-version 1.0.0. GitVersion bumps it to 2.0.0.

My guess is, that the issue lies somewhere in my GitVersion.yml, or how I use GitVersion...

...

ANSWER

Answered 2019-Sep-02 at 14:13

My guess is, that the issue lies somewhere in my GitVersion.yml, or how I use GitVersion...

No, there's no error on your GitVersion.yml. It's all succeed and worked on my GitVersion task with your GitVersion.yml:

Noted: I just modified the value of next-version: next-version: 1.0.0.

The issue you received seemed caused by the task you are using.

According to your detailed log, I noticed that the version of GitVersion task you are using is 4.0.3. In fact, this task has fixed some bugs and be updated to 5.0.1, and also it is what I am using to test and succeed. In addition, another unusual things is you just make a pull request from some-branch-name to develop, but in your log you can see the process and loop between some-branch-name to master/original master:

To solve this issue, try using task of version 5.*.

If you could not select 5.* from the task droplist, just to uninstall this extension and re-install again to get and using the latest version of GitVersion task.

Source https://stackoverflow.com/questions/57729078

QUESTION

GitVersion StackOverflow on Pull Requests

Asked 2017-Feb-14 at 20:25

I've run across an issue with our on-prem TFS2017 builds. We have a project with a GitVersion task that will not find the version when using a pull request. I can build the branch itself without issue, but the pull request continues until GitVersion.exe exits with a stackoverflowexception.

I've tried ignoring commits using "commits-before:" and a variety of branch configuration changes for Pull Requests to no avail.

The following occurs in the log over and over until the exception...

...

ANSWER

Answered 2017-Feb-14 at 09:09

If I understand correctly, you are using GitVersion extension and enable "Automatically build pull requests" branch policy like screenshot below:

I have created a build definition with GitVersion task, when create a new pull request, the build is queued without issue. You may compare my settings with yours and try a new build.

If there is misunderstanding, please provide detailed steps to reproduce your issue.

Source https://stackoverflow.com/questions/42217553

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install dotgit

To get started with dotgit have a look at dotgit's documentation at https://dotgit.readthedocs.io/.

Support

Contributions to dotgit are welcome, just open a PR here on the repo. Please note that your contributions should be linted with Flake8 (you can check for linting errors locally by running make lint in the repo) and should also be covered using unit tests using the pytest framework.

Find more information at: