[PR #1589] [MERGED] Add Git Hooks #1700

New Issue

GiteaMirror · 2025-11-06T15:58:26-06:00

GiteaMirror commented

2025-11-06 15:58:26 -06:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/1589
Author: @CompSciLauren
Created: 7/27/2019
Status: ✅ Merged
Merged: 9/22/2019
Merged by: @sindresorhus

Base: master ← Head: patch-1

📝 Commits (1)

5f93882 Add Git Hooks

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 readme.md (+1 -0)

📄 Description

https://github.com/CompSciLauren/awesome-git-hooks

This list is about git hooks, scripts that can be customized to automate a wide variety of tasks during git workflows.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Yes

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Yes

Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
Understood
You have to review at least 2 other open pull requests.
PR: https://github.com/sindresorhus/awesome/pull/1582
PR: https://github.com/sindresorhus/awesome/pull/1585
You have read and understood the instructions for creating a list.
Yes
This pull request has a title in the format Add Name of List.
Yes
Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
Yes
Your entry should be added at the bottom of the appropriate category.
Exception requested - Added it to the bottom of the git/GitHub related lists under Development Environment, but that is not the very bottom of the section. The git/GitHub lists seem to be grouped together, so it makes sense to me that git hooks would be with them rather than separate at the bottom. I thought this would be okay, but if moving it to the bottom is preferred still then I will move it.
The suggested Awesome list complies with the below requirements.
Yes

Requirements for your Awesome list

Has been around for at least 30 days.
That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Yes
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Waited
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
Awesome-Lint Passing
Includes a succinct description of the project/theme at the top of the readme. (Example)
Yes
It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
Yes
The repo name of your list should be in lowercase slug format: awesome-name-of-list.
Yes
The heading title of your list should be in title case format: # Awesome Name of List.
Yes
Non-generated Markdown file in a GitHub repo.
Yes
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Yes, with added topics as well
Not a duplicate. Please search for existing submissions.
Not a duplicate, though other attempts have already been made by others but were not added. I looked through them to make sure I would not run into the same issues discussed in those ones.
Only has awesome items. Awesome lists are curations of the best, not everything.
Yes
Includes a project logo/illustration whenever possible.
- Either centered, fullwidth, or placed at the top-right of the readme. (Example)
- The image should link to the project website or any relevant website.
- The image should be high-DPI. Set it to maximum half the width of the original image.
  Yes
Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Yes
Includes the Awesome badge.
- Should be placed on the right side of the readme heading.
  - Can be placed centered if the list has a centered graphics header.
- Should link back to this list.
  Yes
Has a Table of Contents section.
- Should be named Contents, not Table of Contents.
- Should be the first section in the list.
- Should only have one level of nested lists, preferably none.
  Yes, and did not nest any lists. Under "Overview of Hooks" I have nine sub-sections based on the type of hook described. However, the Overview of Hooks section is not terribly long so I didn't think nesting each category was necessary. As more hooks are added over time it could become necessary. I chose to not include a nested list, but I'm open to feedback on this if anyone thinks it would be better to have the categories mentioned in the table of contents.
Has an appropriate license.
- That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
- WTFPL and Unlicense are not acceptable licenses.
- If you use a license badge, it should be SVG, not PNG.
  Yes. Uses CC0 license.
- To verify that you've read all the guidelines, please add comment with just the word unicorn.
  See comments section :)
Has contribution guidelines.
- The file should be named contributing.md. Casing is up to you.
  Yes
Has consistent formatting and proper spelling/grammar.
- The link and description are separated by a dash.
  Example: - [AVA](…) - JavaScript test runner.
- The description starts with an uppercase character and ends with a period.
- Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
  Yes
Doesn't include a Travis badge.
You can still use Travis for list linting, but the badge has no value in the readme.
No Travis badge
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.
Yes

Go to the top and read it again.
I went through considerable effort to make sure I did everything correctly, re-read it multiple times and compared what I have to previous PRs and other lists in the Awesome list. Optimistic that I did everything correctly but I'll be quick to fix any changes if needed! Thank you for your time!

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/1589 **Author:** [@CompSciLauren](https://github.com/CompSciLauren) **Created:** 7/27/2019 **Status:** ✅ Merged **Merged:** 9/22/2019 **Merged by:** [@sindresorhus](https://github.com/sindresorhus) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`5f93882`](https://github.com/sindresorhus/awesome/commit/5f938824dfb4604c89e8c31d78b7d8ab56f8ce07) Add Git Hooks ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description **https://github.com/CompSciLauren/awesome-git-hooks** **This list is about git hooks, scripts that can be customized to automate a wide variety of tasks during git workflows.** ### By submitting this pull request I confirm I've read and complied with the below requirements 🖖 Yes **Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.** Yes ## Requirements for your pull request - **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive. Understood - **You have to review at least 2 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** PR: https://github.com/sindresorhus/awesome/pull/1582 PR: https://github.com/sindresorhus/awesome/pull/1585 - You have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/master/create-list.md). Yes - This pull request has a title in the format `Add Name of List`. Yes - Your entry here should include a short description about the project/theme of the list. **It should not describe the list itself.** The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. Yes - Your entry should be added at the bottom of the appropriate category. Exception requested - Added it to the bottom of the git/GitHub related lists under Development Environment, but that is not the very bottom of the section. The git/GitHub lists seem to be grouped together, so it makes sense to me that git hooks would be with them rather than separate at the bottom. I thought this would be okay, but if moving it to the bottom is preferred still then I will move it. - The suggested Awesome list complies with the below requirements. Yes ## Requirements for your Awesome list - **Has been around for at least 30 days.** That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent. Yes - Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Waited - Run [`awesome-lint`](https://github.com/sindresorhus/awesome-lint) on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please [report it](https://github.com/sindresorhus/awesome-lint/issues/new). Awesome-Lint Passing - **Includes a succinct description of the project/theme at the top of the readme.** [(Example)](https://github.com/willempienaar/awesome-quantified-self) Yes - It's the result of hard work and the best I could possibly produce. **If you have not put in considerable effort into your list, your pull request will be immediately closed.** Yes - The repo name of your list should be in lowercase slug format: `awesome-name-of-list`. Yes - The heading title of your list should be in [title case](https://capitalizemytitle.com/) format: `# Awesome Name of List`. Yes - Non-generated Markdown file in a GitHub repo. Yes - The repo should have `awesome-list` & `awesome` as [GitHub topics](https://help.github.com/articles/about-topics). I encourage you to add more relevant topics. Yes, with added topics as well - Not a duplicate. Please search for existing submissions. Not a duplicate, though other attempts have already been made by others but were not added. I looked through them to make sure I would not run into the same issues discussed in those ones. - Only has awesome items. Awesome lists are curations of the best, not everything. Yes - Includes a project logo/illustration whenever possible. - Either centered, fullwidth, or placed at the top-right of the readme. [(Example)](https://github.com/sindresorhus/awesome-electron) - The image should link to the project website or any relevant website. - **The image should be high-DPI.** Set it to maximum half the width of the original image. Yes - Entries have a description, unless the title is descriptive enough by itself. It rarely is though. Yes - Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge). - Should be placed on the right side of the readme heading. - Can be placed centered if the list has a centered graphics header. - Should link back to this list. Yes - Has a Table of Contents section. - Should be named `Contents`, not `Table of Contents`. - Should be the first section in the list. - Should only have one level of [nested lists](https://commonmark.org/help/tutorial/10-nestedLists.html), preferably none. Yes, and did not nest any lists. Under "Overview of Hooks" I have nine sub-sections based on the type of hook described. However, the Overview of Hooks section is not terribly long so I didn't think nesting each category was necessary. As more hooks are added over time it could become necessary. I chose to not include a nested list, but I'm open to feedback on this if anyone thinks it would be better to have the categories mentioned in the table of contents. - Has an [appropriate license](https://github.com/sindresorhus/awesome/blob/master/awesome.md#choose-an-appropriate-license). - That means something like CC0, **not a code licence like MIT, BSD, Apache, etc.** - [WTFPL](http://www.wtfpl.net) and [Unlicense](http://unlicense.org) are not acceptable licenses. - **If you use a license badge, it should be SVG, not PNG.** Yes. Uses CC0 license. - To verify that you've read all the guidelines, please add comment with just the word `unicorn`. See comments section :) - Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-contribution-guidelines). - The file should be named `contributing.md`. Casing is up to you. Yes - Has consistent formatting and proper spelling/grammar. - The link and description are separated by a dash. Example: `- [AVA](…) - JavaScript test runner.` - The description starts with an uppercase character and ends with a period. - Consistent and correct naming. For example, `Node.js`, not `NodeJS` or `node.js`. Yes - Doesn't include a Travis badge. You can still use Travis for list linting, but the badge has no value in the readme. No Travis badge - Doesn't include an `Inspired by awesome-foo` or `Inspired by the Awesome project` kinda link at the top of the readme. The Awesome badge is enough. Yes **Go to the top and read it again.** I went through considerable effort to make sure I did everything correctly, re-read it multiple times and compared what I have to previous PRs and other lists in the Awesome list. Optimistic that I did everything correctly but I'll be quick to fix any changes if needed! Thank you for your time! --- 🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

GiteaMirror added the pull-request label 2025-11-06 15:58:26 -06:00

GiteaMirror closed this issue