See how a minor change to your branch name style can make you a better programmer.
Format: <type>/#<issueNumber>-<alias>
| { | |
| "vim.showMarksInGutter": false, | |
| "vim.foldfix": true, | |
| "vim.surround": true, | |
| "vim.easymotion": true, | |
| "vim.easymotionKeys": "asdghklqwertyuiopzxcvbnmfj", | |
| "vim.leader": "<space>", | |
| "vim.normalModeKeyBindingsNonRecursive": [ | |
| { | |
| "before": [":", "w", "<CR>"], |
| local M = {} | |
| -- Cache for module state | |
| local state = { | |
| buf = nil, | |
| win = nil, | |
| ns = nil, | |
| width = 34, | |
| uses_mousemoveevent = vim.o.mousemoveevent, | |
| } |
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
| #!/usr/bin/env bash | |
| set -e | |
| declare -i last_called=0 | |
| declare -i throttle_by=4 | |
| @throttle() { | |
| local -i now=$(date +%s) | |
| if (($now - $last_called > $throttle_by)); then | |
| # delay execution |
This document contains universal development principles and practices for AI assistants working on any project. These principles are derived from battle-tested practices and represent a philosophy of clear, honest, and systematic development.
BEFORE ANY ACTION, you MUST use these tools. Tool names use double underscores between segments.
| -- ============================================================================= | |
| -- lightline to lualine theme converter | |
| -- Author: shadman | |
| -- License: MIT License | |
| -- ============================================================================= | |
| -- Instructions | |
| -- 1. Source this file in neovim with lightline installed | |
| -- 2. execute :lua light2lualine_theme_converter('theme_name') |
If you encounter a problem where you cannot commit changes in Git – neither through the terminal nor via the GitHub Desktop application – the issue might be a freeze during the Git commit process. This is often caused by GPG lock issues. Below is a concise and step-by-step guide to resolve this problem.
Open your terminal and try to perform a GPG operation (like signing a test message). If you see repeated messages like gpg: waiting for lock (held by [process_id]) ..., it indicates a lock issue.