Skip to content

Conversation

@jbampton
Copy link
Contributor

Manual hook added which runs a shell script.

Can be run locally manually by Linux or Mac users and we have this also running on the GitHub Actions CI.

Will fail if Makefiles uses spaces for indentation.

Can run the manual hooks with:

pre-commit run check-makefile-indentation --all-files --hook-stage manual

Manual hook added which runs a shell script.

Can be run locally manually by Linux or Mac users and we have this also running on the GitHub Actions CI.

Will fail if Makefiles uses spaces for indentation.

Can run the manual hooks with:

`pre-commit run check-makefile-indentation --all-files --hook-stage manual`
@jbampton jbampton requested a review from matz as a code owner December 29, 2025 17:35
@github-actions github-actions bot added the build label Dec 29, 2025
@gemini-code-assist
Copy link

Summary of Changes

Hello @jbampton, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a new pre-commit hook to standardize Makefile formatting across the repository. By ensuring that all Makefiles use tabs for indentation, it aims to prevent common build issues related to whitespace and improve code consistency and readability for these critical build files.

Highlights

  • New Pre-Commit Hook: A new pre-commit hook named check-makefile-indentation has been added to enforce consistent tab-based indentation for Makefiles.
  • Indentation Enforcement Script: A new shell script, scripts/check_makefiles_for_tabs.sh, was introduced to specifically check for and disallow leading spaces in Makefile lines, ensuring they are indented with tabs.
  • Hook Configuration: The hook is configured to run manually, targets files named 'makefile' (case-insensitive), and passes the filenames to the checking script.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a new pre-commit hook to ensure Makefiles use tabs for indentation. The implementation is generally correct, but there are a couple of areas for improvement.

In scripts/check_makefiles_for_tabs.sh, the script uses grep -P, which is a GNU extension and will not work on standard macOS systems. I've suggested a more portable and efficient alternative.

In .pre-commit-config.yaml, the file matching pattern is quite restrictive and will only check a Makefile in the root directory. I've left a comment to consider making this more flexible to accommodate future Makefiles in other directories.

Comment on lines +6 to +11
if [[ -f "$makefile" ]]; then
if grep -P '^\s' "$makefile" | grep -vP '^\t' > /dev/null; then
echo "Error: File '$makefile' contains spaces at the beginning of lines instead of tabs."
exit 1
fi
fi

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

This script has a couple of issues:

  1. Portability: The use of grep -P for Perl-compatible regular expressions is a GNU extension and is not available on all systems, notably default macOS installations. This will cause the hook to fail for Mac users.
  2. Redundancy & Efficiency: The if [[ -f "$makefile" ]] check is redundant because pre-commit is configured with types: [file], which ensures only existing files are passed. Additionally, using a pipe with two grep processes is less efficient than a single grep.

You can address these points by using a single, more portable grep command to check for lines starting with a space. The [ ] syntax for a space is used for clarity and portability.

Suggested change
if [[ -f "$makefile" ]]; then
if grep -P '^\s' "$makefile" | grep -vP '^\t' > /dev/null; then
echo "Error: File '$makefile' contains spaces at the beginning of lines instead of tabs."
exit 1
fi
fi
if grep -q '^[ ]' "$makefile"; then
echo "Error: File '$makefile' contains spaces at the beginning of lines instead of tabs."
exit 1
fi

description: ensures that Makefiles are indented with tabs
entry: ./scripts/check_makefiles_for_tabs.sh
language: system
files: "(?i)^makefile$"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The regex (?i)^makefile$ will only match a file named Makefile or makefile in the root of the repository. If you ever add Makefiles in subdirectories, they will not be checked. A more flexible pattern would be something like (?i)makefile$, which would match any file ending in makefile (e.g., src/Makefile). Consider if you want to support this for future-proofing.

@jbampton jbampton marked this pull request as draft December 29, 2025 17:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant