Skip to content

Instantly share code, notes, and snippets.

View gaiguodonfbu's full-sized avatar
💭
I may be slow to respond.

Alex gaiguodonfbu

💭
I may be slow to respond.
  • bbd Group
  • 0588 ,Emelia Rest .Marcelene port ,Idaho
View GitHub Profile
@ninehills
ninehills / chatpdf-zh.ipynb
Last active April 23, 2025 10:17
ChatPDF-zh.ipynb
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
# install docker
curl -fsSL get.docker.com -o get-docker.sh
sh get-docker.sh
if [ ! $(getent group docker) ];
then
sudo groupadd docker;
else
echo "docker user group already exists"
fi
@robertpainsi
robertpainsi / commit-message-guidelines.md
Last active April 22, 2025 14:24
Commit message guidelines

Commit Message Guidelines

Short (72 chars or less) summary

More detailed explanatory text. Wrap it to 72 characters. The blank
line separating the summary from the body is critical (unless you omit
the body entirely).

Write your commit message in the imperative: "Fix bug" and not "Fixed
bug" or "Fixes bug." This convention matches up with commit messages
@ericavonb
ericavonb / git-commit-style-guide.md
Last active April 5, 2025 19:10
Git Commit Style Guide

Git Commit Style Guide

Inspiration: Deis Commit Style Guide

I often quote Deis in sections below.

Motivation

It makes going back and reading commits easier. It also allows you to spend less time thinking about what your commit message should be.