In the last entry I've shown how to create a PowerShell based git hook, passing following parameters to the hook for sake of validating it. The parameters were: $local_sha - the signature of the local commit $remote_ref - the remote branch name $remote_sha - the signature of the remote commit This is more than enough … Continue reading TeamCity queries with powershell (for sake of healthy develop)
Git
Git hooks with PowerShell
It's time to provide some client-side hooks for our Git repository! Git hooks are stored in the .git directory under following path: .git/hooks As you can see there's plenty of them, ending with .sample. When we remove this extension, the hook will kick in, handling events according to its name. There's an issue with Git hooks. … Continue reading Git hooks with PowerShell
Git plumbing with PowerShell
In the recent post I've shown the need of securing the development branch in GitFlow. The same should be applied to all release branches and hotfixes as well. To provide a proper protection we need tooling and ability to gather some information from the git repository. Fortunately, Git structure is extremely easy and as shown … Continue reading Git plumbing with PowerShell
GitFlow and Continuous Build
In the recent post I've described the idea how to ensure, that your feature-to-develop GitFlow merge commits are reviewed before being introduced to the develop branch. This preserves the quality of the develop branch, ensuring that it's truly possibly deployable. How one would like to build his/her repository and provide artifacts? Which commits and which … Continue reading GitFlow and Continuous Build
GitFlow and code reviews
Many companies that uses GIT as its code repository use git-flow as the branching model for its projects. The question, that one can come up with is where and when the code review should be taken? Should it be before: git flow feature finish MYFEATURE If yes, then the reviewer looks through some version of … Continue reading GitFlow and code reviews
Embracing domain leads solution towards event oriented design
One of the most powerful aspects of git is it's simplicity. One can easily read the object chapter of the Git book during one afternoon and learn, that git stores nothing more than snapshots of the current state of the items added to the repository. If an item is repeated in multiple commits with no … Continue reading Embracing domain leads solution towards event oriented design
Git repository as a graph
One of the greatest misunderstanding of git is trying to map it 1-1 to SVN. It's easy to follow this fallacy when one starts migrating from SVN and all he/she fears the most is loosing the precious branches and all the rituals connected with them. Let's state from the beginning: Don't be stupid. Learn Git. … Continue reading Git repository as a graph
