Closed
Description
The rate of issues that I faced with pdd/0pdd is too high. Time to time, it tries to create a duplicate issues or close issues while the comments are still in place. Also the issues that have been reported don't have reaction from the maintainers for a long time.
Examples:
- https://github.com/yegor256/0pdd/issues/created_by/php-coder
- https://github.com/cqfn/pdd/issues/created_by/php-coder
Checklist:
- remove 0pdd bot from collaboratorsremove a webhook
README.md
: remove a badgeremove.pdd
and.0pdd.yml
filesadd a record to decision logupdate changelog
Metadata
Metadata
Assignees
Labels
Projects
Relationships
Development
No branches or pull requests
Activity
php-coder commentedon Nov 15, 2022
Idea: a simple shell script build around
git show | grep @todo
and github cli tool can be used instead.Here is how issues can be created/closed:
php-coder commentedon May 19, 2023
It seems 0pdd doesn't work anymore: it didn't create an issue for the commit bcb9402#diff-bc5be0d131b2f5510d9173cc14505d648eb85ce582a9dd78b6d460f4dc345d4cR2
php-coder commentedon May 23, 2023
GitHub Actions that can be helpfull:
php-coder commentedon May 30, 2023
0pdd bot was removed from a list of collaborators. Also a webhook was removed as well.
[-]Stop using pdd and 0pdd[/-][+]Stop using 0pdd[/+]chore: remove 0pdd/pdd remnants
chore: mark as outdated workarounds for pdd/0pdd
docs: update NEWS.txt to mention discontinue usage of 0pdd
docs: add a decision regarding usage of 0pdd
php-coder commentedon Jun 12, 2023
Done.