Files
test2/tools
Julian Eisel ec141ba3ff Tools: Include commits to all branches in weekly report script
Currently the script only includes commits to "main" branches. Much of
people's work is done in branches however, so developers either
customized the script, or they would manually go through own history to
find remaining commits (I asked some).

Even if some people prefer to only list main branch commits, it's much
easier to simply remove some commits than to add missing ones.

To be able to tell which branch a commit was on, this adds a " on
`branch-name`" after the commit hash. Personally I don't find this
optimal, I'd rather group commits under their repository/branch,
proposed separately in #138615.

Pull Request: https://projects.blender.org/blender/blender/pulls/138612
2025-05-20 19:07:18 +02:00
..
2025-04-01 12:37:36 +11:00

Blender Dev Tools
#################

This repository is intended for miscellaneous tools, utilities, configurations and
anything that helps with Blender development, but aren't directly related to building Blender.

Some of the tools included may be used stand-alone, others expect Blenders source code to be available.


Usage
=====

While this is a stand-alone repository,
some of the scripts which access Blenders source code assume this repository will be located at
``tools`` within Blenders source code repository. At some point this may be included as a submodule.

Some tools also rely on the ``blender`` binary, this is assumed to be located at: ``../../blender.bin``.
*The root directory of Blender's git repository*


Categories
==========

Check Source
------------

Any tools for scanning source files to report issues with code, style, conventions, deprecated features etc.


Config
------

Configuration for 3rd party applications (IDE's, code-analysis, debugging tools... etc).


Git
---

Scripts and utilities for working with git.


Utils
-----

Programs (scripts) to help with development
(currently for converting formats, creating mouse cursor, updating themes).