Hasty Briefsbeta

All tags

#git

147 stories total

Bilingual

Using Git-upload-pack for a simpler CI integration
a year ago
- Screenshotbot does not require read-access to GitHub repositories, enhancing security and ease of integration with various Git providers.
- The platform uses a 'commit-graph' to track commit SHAs and their parents, without storing additional repository data.
- Challenges include difficulty supporting shallow clones and inefficiency with large monorepos.
- A new feature utilizes the git-upload-pack protocol to efficiently fetch commit information via SSH, bypassing the need for GitHub-specific APIs.
- The git-upload-pack protocol involves server-client negotiation for refs and commits, using packfiles for data transfer.
- Implementation of git-upload-pack in Screenshotbot allows for shallow clones and reduces network traffic by avoiding unnecessary blob transfers.
- Caveats include the protocol's complexity, variations in Git server behaviors, and specific requirements like multi_ack mode for Azure DevOps.
- The update enables Screenshotbot users to utilize shallow clones, improving build times.
Show HN: acmsg (automated commit message generator)
a year ago
- A CLI tool in Python for generating git commit messages using AI models via OpenRouter API.
- Analyzes staged changes in git repositories to generate contextual commit messages.
- Supports multiple AI models through OpenRouter and allows editing of generated messages.
- Automatically commits changes with the AI-generated message upon confirmation.
- Requires an OpenRouter API key for operation.
- Installable via pipx, NixOS flakes, or standalone Nix profiles.
- Configuration file located at ~/.config/acmsg/config.yaml.
- First run prompts for OpenRouter API token configuration.
- Licensed under the MIT License.
Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges
a year ago
- git-bug is a distributed, offline-first issue management tool that integrates with Git repositories.
- Features include native Git storage for issues, distributed and versioned architecture, and lightning-fast search.
- Supports third-party bridges for platforms like GitHub and GitLab, with flexible CLI, TUI, and web interfaces.
- Easy to integrate with minimal setup required.
- Installation and documentation are available for quick start.
- Community contributions are welcomed, with channels for discussion and live chat on Matrix.
- Project is supported by contributors, backers, and sponsors, with appreciation for all contributions.
- Licensed under GPLv3 or later, with the logo under CC BY 4.0.
- Originally created by Michael Muré, with ongoing community support.
Show HN: Doxxer – CLI tool for dynamic SemVer versioning using tags
a year ago
- doxxer is a CLI tool written in Rust for dynamic SemVer version generation based on Git tags and commits.
- Inspired by `git describe --tags`, it complies with SemVer specifications.
- Install via Cargo: `cargo install doxxer`.
- Commands include `current` (returns current version), `next` (returns next version), and `help`.
- Options allow specifying Git directory, tag prefix, and output formatting.
- `next` command supports strategies like major, minor, patch, pre-release, and build metadata.
- Templates for pre-release and build metadata can be customized with variables like `{pre}`, `{hash}`, and `{distance}`.
- Default strategy is `pre-build` to reflect development iteration goals.
- Project name 'doxxer' humorously refers to exposing Git repo version information.
- Future enhancements include adding a shell script for prebuilt binary installation and `{timestamp}` variable support.
Git: Move files from one repo to another with history (2021)
a year ago
- Exporting files with history between Git repos can be complex, but using `git filter-repo` simplifies the process.
- `git filter-branch` is no longer recommended due to history rewriting issues and warnings from Git CLI.
- Patching is an alternative but can be complex and less seamless compared to `filter-repo`.
- Install `git filter-repo` separately, as it's not included with Git CLI by default.
- Key `filter-repo` options: `--path` to include files/folders, `--invert-paths` to exclude them.
- Steps to move files with history: clean source repo, add source as remote in target repo, fetch and merge changes, then cleanup.
- Perform cleanup in a local branch first to avoid impacting the original repo.
- Use `git remote add`, `git fetch`, and `git merge --allow-unrelated-histories` to integrate changes.
- Cleanup involves removing the remote source and branch after merging.
Working with Git Patches in Apple Mail (2023)
a year ago
- Create a 'Patches' mailbox folder in Apple Mail for organizing git email patches.
- Move the email containing the git patch to the 'Patches' folder.
- Export the 'Patches' mailbox folder to a local directory, preferably named 'Patches'.
- Navigate to the project directory in the terminal where the patch should be applied.
- Use the command 'git apply' with the path to the saved patches mailbox folder to apply the patch.
- Regularly clean up the local 'Patches' folder to maintain organization.
Show HN: Lnk – Git-native dotfiles manager
a year ago
- Git-native dotfiles management tool called 'lnk'.
- Moves dotfiles to ~/.config/lnk and creates symlinks back to original locations.
- Supports commands like init, add, push, pull, status for managing dotfiles.
- Multiple installation methods: quick install, Homebrew, manual download, and from source.
- Features include atomic operations, relative symlinks, and XDG compliance.
- Comparison with other tools like chezmoi, yadm, dotbot, and stow.
- Handles existing Git repos and machine-specific configs via Git branches.
- Windows support is possible but untested.
- Pre-1.0 status with potential API changes.
- Development involves standard Makefile with quality checks and integration tests.
Creating Debian packages from upstream Git
a year ago
- Optimal workflow for creating new Debian packages in 2025, preserving upstream git history.
- Key elements include using Git fork/clone of upstream repository, consistent git-buildpackage commands, DEP-14 tag and branch names, pristine-tar and upstream signatures, and efficient use of Salsa.
- Demonstration using the command-line tool Entr, covering steps from creating a packaging repository to posting a Merge Request on Salsa.
- Detailed instructions on setting up the repository structure, using dh_make for initial packaging, and identifying build dependencies.
- Building Debian sources with dpkg-buildpackage and git-buildpackage, including handling upstream releases and patches.
- Guidance on opening Merge Requests for review, submitting fixes upstream, and using language-specific dh-make alternatives.
- Explanation of the difference between source git repositories, source packages, and binary packages.
- Options for repackaging source packages with Files-Excluded lists and handling multiple upstream source packages.
- When not to start the Debian packaging repository as a fork of the upstream one.
- Conclusion highlighting the evolution of Debian packaging and the importance of standardized workflows.
Edamagit: Magit for VSCode
a year ago
- Magit for VSCode is inspired by the original Magit and provides Git functionality within VSCode.
- Keybindings include shortcuts for common Git actions like status, commit, fetch, pull, push, rebase, and more.
- Essential commands include refreshing the buffer, toggling sections, visiting entities, and navigating with cursor movements.
- Forge functionality can be enabled to show pull requests and issues from platforms like GitHub.
- Customizable keybindings can be set in VSCode's keybindings.json, including Vim-like bindings.
- Monorepo support requires configuration to detect parent .git directories.
- Feature requests and issues are welcome, with a roadmap including more interactivity, config menus, and additional Git features.
Show HN: Git-Add–Interactive with Enhancements
a year ago
- Go port of Git's interactive add functionality with enhancements.
- Interactive staging and patch mode with commands like y/n/s/e/q/a/d.
- Hunk operations: split, edit, navigate between hunks.
- Multiple patch modes: stage, reset, checkout, stash, worktree operations.
- Git integration with full color configuration and repository support.
- Terminal UI with color-coded interface and keyboard shortcuts.
- Filter hunks across files using regex patterns.
- Automatically split hunks to maximum granularity.
- Accept all hunks across files after filtering and splitting.
- Local search within current file without affecting global filter.
- Status display shows filter and auto-split indicators.
- Cross-file filtering persists across all files in the session.
- Build and install instructions to replace Perl script with Go implementation.
- Commands to revert back to the original Perl implementation.
- Direct usage and patch mode commands explained.
- Codebase organization and main packages overview.
- Test suite and conventions followed.
- Comprehensive unit tests, Git integration, error handling.
The Perfect Commit (2022)
a year ago
- The Perfect Commit includes implementation, tests, documentation, and a link to an issue.
- Each commit should be a single, focused change for easier review and future understanding.
- Tests increase productivity by ensuring changes don't break existing features.
- Documentation should live in the same repository as the code for trust and versioning.
- Issue threads provide unlimited space for background, decisions, and links related to the change.
- Not every commit needs to be perfect; exceptions include typo fixes and minor bug fixes.
- Exploratory or experimental code can be written in branches and later squashed into a perfect commit.
Hardening fixes lead to hard questions
a year ago
- Kees Cook's 'hardening fixes' pull request for the 6.16 merge window led to unexpected issues, including temporary blocking of his kernel.org account.
- Linus Torvalds reacted strongly to the pull request, suspecting malicious activity due to modified commits with altered metadata.
- The issue stemmed from the use of the b4 tool's trailers subcommand, which rewrote commit history unintentionally.
- Cook demonstrated the issue was accidental, and his account was reactivated after review.
- Changes to b4 are planned to prevent similar mistakes, including refusing to rewrite commits not made by the user running the command.
- The incident highlights the risks of powerful tools like Git and the importance of caution and guardrails in their use.
The X.Org Server just got forked (announcing XLibre)
a year ago
- The text appears to be a list of commit descriptions from a version control system.
- The commits are dated June 5, 2025.
- There are multiple commit IDs listed, each with a 'Show description' option.
- The interface includes a branch selector, user selector, and datepicker.
- The commits are paginated, indicating there are more commits than displayed.
Decreasing Gitlab repo backup times from 48 hours to 41 minutes
a year ago
- Repository backups are critical for disaster recovery but become challenging as repositories grow.
- GitLab's Rails repository took 48 hours to back up due to a 15-year-old Git function with O(N²) complexity.
- The issue was fixed with an algorithmic change, reducing backup times exponentially.
- Challenges with large repository backups include time-prohibitive processes, resource intensity, and increased failure risk.
- The root cause was identified as the `object_array_remove_duplicates()` function in Git, which had poor scalability.
- The fix replaced nested loops with a map data structure, improving performance by 6x in benchmarks.
- Backup times for GitLab's largest repository dropped from 48 hours to 41 minutes.
- Benefits include transformed backup strategies, enhanced business continuity, and reduced operational overhead.
- The fix was contributed upstream to Git, benefiting the broader Git community.
- GitLab 18.0 includes these improvements, requiring no further configuration.
Remove Bug Bounty Program
a year ago
- 3 files were changed with 0 additions and 12 deletions.
- Each file had 4 lines deleted, totaling 12 deletions across all files.
- No commit comments were provided.
Miru (anime player) is no longer open source
a year ago
- Instructions for comparing changes between two branches.
- Option to open a new pull request by comparing changes.
- Note about potential issues with rendering large comparisons.
- Suggestion to run the git diff command locally for large comparisons.
Git 2.50
a year ago
- Git 2.50 released with contributions from 98 contributors, including 35 new ones.
- Improvements for multiple cruft packs with new option `--combine-cruft-below-size`.
- Support for incremental multi-pack reachability bitmaps in Git 2.50.
- ORT merge engine replaces recursive, offering better performance and features.
- New features in `git cat-file` for object filtering and removal of `--allow-unknown-type`.
- Enhancements to `git maintenance` with new tasks like `worktree-prune` and `reflog-expire`.
- Performance improvements in reference processing and updates to `git update-ref`.
- New HTTP configuration options for TCP Keepalive behavior.
- Reduction in Perl dependencies in Git's test suite and documentation.
- Cosmetic updates to `git rebase -i` for better clarity in commit messages.
- Improvements to `bundle-uri` feature for faster clones.
- Better support for sparse checkouts in `git add -p` and `git add -i`.
Show HN: Tool to Automatically Create Organized Commits for PRs
10 months ago
- Git Smart Squash uses AI to automatically organize messy commit histories into clean, logical commits.
- Before and after examples show AI transforming disorganized commits into well-structured ones with conventional commit messages.
- Install via pip and choose between local AI (Ollama) for privacy or cloud AI (OpenAI, Anthropic, Gemini) with API keys.
- Commands include `git-smart-squash` for a dry run and `--auto-apply` to skip confirmation.
- Safety features include dry runs, backup branches, and no automatic pushing.
- Config files allow customization of AI providers per project or globally.
- Local AI has a token limit; large diffs may require chunking or switching to cloud providers.
- Documentation and issue tracking are available for further assistance.
- Open-source under MIT License, designed for developers seeking cleaner git history.
Git Notes: Git's coolest, most unloved feature (2022)
10 months ago
- Git notes are a powerful but underutilized feature for appending metadata to git objects like commits, blobs, and trees without altering the objects themselves.
- They are commonly used for adding information such as acknowledgments, mailing list discussions, and review/test results to commits.
- Git notes can be used for distributed code review systems, enabling offline access to review metadata and facilitating forge-independent workflows.
- Despite their potential, git notes suffer from poor usability and limited adoption, with platforms like GitHub no longer displaying them by default.
- Examples of git notes usage include tracking time per commit, adding review/testing info to git log, and implementing distributed code review systems like git-appraise.
- Git notes offer a path toward forge independence by distributing project history and metadata alongside the code itself.
`Git stage` over `Git add`
10 months ago
- The author prefers using 'git stage' over 'git add'.
- Both commands are synonyms, but 'git stage' makes the intent clearer.
- The manual for 'git add' describes it as adding file contents to the index.
- The manual for 'git stage' describes it as adding file contents to the staging area.
- The author feels 'git stage' aligns better with Git's staging/unstaging terminology in 'git status'.
- The preference might be influenced by the author's familiarity with staging terminology.

first prev1next

About|Login

#git

Using Git-upload-pack for a simpler CI integration

Show HN: acmsg (automated commit message generator)

Git Bug: Distributed, Offline-First Bug Tracker Embedded in Git, with Bridges

Show HN: Doxxer – CLI tool for dynamic SemVer versioning using tags

Git: Move files from one repo to another with history (2021)

Working with Git Patches in Apple Mail (2023)

Show HN: Lnk – Git-native dotfiles manager

Creating Debian packages from upstream Git

Edamagit: Magit for VSCode

Show HN: Git-Add–Interactive with Enhancements

The Perfect Commit (2022)

Hardening fixes lead to hard questions

The X.Org Server just got forked (announcing XLibre)

Decreasing Gitlab repo backup times from 48 hours to 41 minutes

Remove Bug Bounty Program

Miru (anime player) is no longer open source

Git 2.50

Show HN: Tool to Automatically Create Organized Commits for PRs

Git Notes: Git's coolest, most unloved­ feature (2022)

`Git stage` over `Git add`

Git Notes: Git's coolest, most unloved feature (2022)