pre-commit / pre-commit/identify

Feature request: classify whatever.BUILD files as bazel files

Open
#103 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
297
Forks
179
PR merge metrics
No merged PRs in 30d

Description

Currently identify has support for BUILD and BUILD.bazel files. it would be good to add support for *.BUILD files as well.

In case its helpful, here is the relevant regex that should describe a bazel file, when matching against a filepath:

^(.*/)?(BUILD\.bazel|BUILD)$|\.BUILD$

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing filename classification rule for BUILD and BUILD.bazel files in identify, then compare it with the proposed regex. Done means paths ending in .BUILD are classified as bazel files while BUILD and BUILD.bazel continue to work; verify the matching behavior with the project's relevant checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.