is it safe to add a directory *inside* of the .git/ folder
I am making a git hook that needs to store some metadata about the repo between runs. (more precisely a hook that pre-writes commit messages using an llm, and I need to keep a vector database indexing the code of the repo for RAG).
is it safe to add a directory *inside* of the .git/ folder
I am making a git hook that needs to store some metadata about the repo between runs. (more precisely a hook that pre-writes commit messages using an llm, and I need to keep a vector database indexing the code of the repo for RAG).
is it safe to add a directory *inside* of the .git/ folder
I am making a git hook that needs to store some metadata about the repo between runs. (more precisely a hook that pre-writes commit messages using an llm, and I need to keep a vector database indexing the code of the repo for RAG).
is it safe to add a directory *inside* of the .git/ folder
I am making a git hook that needs to store some metadata about the repo between runs. (more precisely a hook that pre-writes commit messages using an llm, and I need to keep a vector database indexing the code of the repo for RAG).
The `pre-commit` hook can stage new changes during its execution, but `pre-merge-commit` cannot. Why is that?
I have a repository with a version (semantic versioning) hardcoded in one of its files. Each time a developer adds a change (let’s call it a type 1 change), I need to review those changes and increment the minor version component. If a developer adds a type 2 change, I increment the patch version component.
The `pre-commit` hook can stage new changes during its execution, but `pre-merge-commit` cannot. Why is that?
I have a repository with a version (semantic versioning) hardcoded in one of its files. Each time a developer adds a change (let’s call it a type 1 change), I need to review those changes and increment the minor version component. If a developer adds a type 2 change, I increment the patch version component.
The `pre-commit` hook can stage new changes during its execution, but `pre-merge-commit` cannot. Why is that?
I have a repository with a version (semantic versioning) hardcoded in one of its files. Each time a developer adds a change (let’s call it a type 1 change), I need to review those changes and increment the minor version component. If a developer adds a type 2 change, I increment the patch version component.
Where does git get the author information from
====== STR Start ======
Add an action to commit, to be executed post-pull – something like a one-time only git post-merge hook?
Is it possible to furnish a single commit with something akin to a pull-completion-handler?
Why isn’t there a git `post-push` hook?
I’m curious why Git doesn’t have a post-push hook. Is it due to technical reasons, or has it just not been implemented yet, or are there other considerations?