test/tools at 1858eba4731934bbc29267b3f3ee60a52c24aeea - test

Files

Julian Eisel 5a5e1b7d14 Tools: Group commits in weekly report scripts

Since ec141ba3ff, commits from all branches are listed. Issue is that
commits from different repositories and branches will be mixed.
Personally I prefer grouping commits better, so I always edit the output
manually.

With this, commits will be grouped by branch, or PR if one can be found.
The branches and commits will then be printed under their target
repository. This isn't the owning repository of the branch or PR (often
people's personal fork), but the one it targets. This worked much better
in own tests.

Further:
- For some common repositories more readable names are used, e.g.
  "Blender Manual" instead of "blender/blender-manual".
- Commits of the Blender repository are listed first, without grouping
  under a `blender/blender`.
- Commits to each repository's main branch are listed first, directly
  under the repository grouping.
- See PR for a textual mockup of the output format.

Pull Request: https://projects.blender.org/blender/blender/pulls/138615

2025-05-20 19:13:43 +02:00

check_blender_release

Tests: Add 'with ASAN' knowledge to Linux release checks.

2025-01-21 09:40:50 +01:00

check_docs

Cleanup: declare __all__ for many scripts in tools/

2025-01-04 20:27:58 +11:00

check_source

Cleanup: spelling in comments (make check_spelling_*)

2025-05-15 10:13:23 +10:00

config

LSAN suppression rules: add exception for ffmpeg x265 malloc.

2024-11-13 13:26:56 +01:00

debug/gdb

Fix: missing import in gdb pretty printers

2025-02-25 22:56:12 +01:00

git

Cleanup: declare __all__ for Python scripts

2025-01-06 16:45:36 +11:00

modules

Cleanup: wrap Python lines exceeding 120

2025-02-13 10:01:03 +11:00

svn_rev_map

Cleanup: declare __all__ for Python scripts

2025-01-06 16:45:36 +11:00

triage

Tools: Group commits in weekly report scripts

2025-05-20 19:13:43 +02:00

utils

Docs: note what git_data_canonical_authors.py is used for.

2025-04-24 01:30:11 +00:00

utils_api

VSE: Python API: Deprecate sequence properties and replace with new ones

2025-01-21 11:30:20 +01:00

utils_build

Cleanup: declare __all__ for many scripts in tools/

2025-01-04 20:27:58 +11:00

utils_doc

Cleanup: spelling in comments

2025-04-01 12:37:36 +11:00

utils_ide

Build: expand Visual Studio natvis file

2025-05-14 14:45:40 +02:00

utils_maintenance

UI: include rip in the UV menu

2025-05-07 15:49:21 +10:00

readme.rst

…

readme.rst

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).