aeliot / todo-registrar
Register TODOs from source code in issue tracker
Package info
github.com/Aeliot-Tm/todo-registrar
Type:application
pkg:composer/aeliot/todo-registrar
Requires
- php: ^8.2
- ext-ctype: *
- ext-mbstring: *
- ext-simplexml: *
- ext-tokenizer: *
- aeliot/env-resolver: ^1.0.2
- aeliot/todo-registrar-contracts: ^2.3.0
- bugrov/yandex-tracker: 0.1.0
- guzzlehttp/guzzle: ^7.9
- http-interop/http-factory-guzzle: ^1.2
- kbsali/redmine-api: ^2.8
- knplabs/github-api: ^3.14
- lesstif/php-jira-rest-client: ^5.8
- m4tthumphrey/php-gitlab-api: ^11.14
- nikic/php-parser: ^5.7
- psr/container: ^2.0
- psr/http-client: ^1.0
- symfony/config: ^7.4
- symfony/console: ^7.4
- symfony/dependency-injection: ^7.4
- symfony/deprecation-contracts: ^3.6
- symfony/finder: ^5.4|^6.0|^7.0
- symfony/validator: ^7.4
- symfony/yaml: ^3.4|^4.0|^5.0|^6.0|^7.0
Requires (Dev)
- dg/bypass-finals: ^1.7
- phpstan/phpstan: ^2.0
- roave/security-advisories: dev-latest
- dev-main
- 3.5.1
- 3.5.0
- 3.4.5
- 3.4.4
- 3.4.3
- 3.4.2
- 3.4.1
- 3.4.0
- 3.3.0
- 3.2.0
- v3.1.0
- v3.0.0
- v2.3.1
- 2.3.0
- v2.2.0.3
- v2.2.0.2
- v2.2.0.1
- v2.2.0
- v2.1.0
- v2.0.0
- v1.8.0
- v1.7.0
- v1.6.1
- v1.6.0
- v1.5.2
- v1.5.1
- v1.5.0
- v1.4.2
- v1.4.1
- v1.4.0
- v1.3.4
- v1.3.3
- v1.3.2
- v1.3.1
- v1.3.0
- v1.2.2
- v1.2.1
- v1.1.1
- v1.1.0
- v1.0.0
- dev-yaml-comment-cleaner
- dev-exception
- dev-yaml
- dev-rc4.0
- dev-glue-same-ticket
- dev-intermediate-interfaces
- dev-glue-sequential-comments-reserve
- dev-vscode
- dev-Case-of-config
- dev-forbid-empty-list-of-tags
- dev-inline-config-styles
- dev-processing-summary_old
- dev-dev-scripts-tests-phpstan
- dev-inline_config
This package is auto-updated.
Last update: 2026-06-02 19:52:17 UTC
README
It takes TODO/FIXME and other comments from your php-code and register them as issues in Issue Trackers like JIRA. With all necessary labels, linked issues and so on.
Motivation
Time to time developers left notes in code to not forget to do something. And they forget to do it. One of the main reason is that it is difficult to manage them.
Why do developers left comment in code instead of registering of issues? It is convenient. You don't need to deal with UI of Issue Tracker and to fill lots of field. And lots of times to register each issue. It takes time. The second reason, comment in code permit to mark exact place which have to be modified. And many other reasons. No matter why they do it. They do it and leave this comments for years.
Somebody have to manage it.
So, we need in tool which will be responsible for registering of issues and save time of developers. After that you can use all power of management to plan solving of lacks of your code.
This script do it for you. It registers issues with all necessary params. Then injects IDs/Keys of created issues into comment in code. This prevents creating of issues twice and injected marks helps to find proper places in code quickly.
How it works
- Detect TODO in comment.
- Create issue in issue tracker (list of supported).
- Inject number of ticket into TODO-comment.
See latest benchmark here.
Using
Basic using:
- Create configuration file.
- Call shell script with necessary command line options.
- Commit updated files. You can config your pipeline/job on CI which commits updates.
There are prepared several ways of using:
- Using of GitHub Action: TODO Registrar Action.
- Using of Docker Container.
- Using of PHAR file.
- Using of Composer Package.
I recommend TODO Registrar Action for repositories hosted on GitHub.
The next recommendation is using of Docker container. It provides fully isolated solution. There is no matter which version of PHP installed in yous system and which components required by Composer (no dependency hell).
The next one is using of single PHAR file. It frees you from dependency hell,
but you have to pay attention to version of PHP installed in you system and its modules.
However, this may be more familiar for you.
The last one is using of Composer package. The most common, but less flexible method.
Documentation references
- Command Line Options
- Configuration:
- General Config
- Config format:
- Inline Config
- Specific for issue trackers supported out of the box:
- General Config
- Supported formats of comments
- Integration on CI
- Customization
Supported Issue Trackers
| Issue Tracker | Description |
|---|---|
| See description of configuration. Supported via API tokens. | |
| See description of configuration. Supported via API tokens (HTTP Token or OAuth). | |
| See description of configuration. Supported via API tokens. | |
| See description of configuration. Supported via API keys or Basic Auth. | |
| See description of configuration. Supported via OAuth tokens. | |
| Any custom Issue Tracker | Read about customization |
Articles
RU: https://habr.com/ru/articles/832994/