/explore
|
You are here 
|
www.wyeworks.com | ||
| | | | |
www.brandonpugh.com
|
|
| | | | | TLDR: Git hooks are an awesome way to automatically verify your code as you commit your changes I'm sure we've all been there where we accidentally committed a change that we were supposed to undo or wasn't ready to be pushed and don't realize it until the build breaks or QA finds a bug. The first step I take to avoid committing anything unintentionally is instead of just running git add -A I make sure to review all the changes in the files I'm potentially committing. This is where a graphical tool like Gitk or SmartGit comes in handy as they allow you to click on your modified files and easily view a diff and then select which changes to stage. Unfortunately changes still slip through as happened to me yesterday when a change of mine got pushed all the way ... | |
| | | | |
sam.hooke.me
|
|
| | | | | [AI summary] A technical guide demonstrates how to configure the pre-commit tool with Poetry to automatically enforce code formatting rules using Black and isort during Git commits. | |
| | | | |
blogops.mixinet.net
|
|
| | | | | Since a long time ago I've been a gitlab-ce user, in fact I've set it up on three of the last four companies I've worked for (initially I installed it using the omnibus packages on a debian server but on the last two places I moved to the docker based installation, as it is easy to maintain and we don't need a big installation as the teams using it are small). On the company I work for now (kyso) we are using it to host all our internal repositories and to do all the CI/CD work (the automatic deployments... | |
| | | | |
arslan.io
|
|
| | | Using a single init.lua or vimrc configuration file for (Neo)Vim file is better than a multi folder/file layout approach. Let me tell why that is the case. | ||
