https://bugs.kde.org/show_bug.cgi?id=500476
Luke Horwell <c...@horwell.me> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOT A BUG
Status|REPORTED |RESOLVED
--- Comment #4 from Luke Horwell <c...@horwell.me> ---
Thank you for the feedback and information. On reflection, it seems like it's
not worth it.
The current "static" approach (once, on open, on close) will be more reliable
then risking a "dynamic" aspect. I was thinking it would enumerate the Bugzilla
comments (authored by bot) before commenting, but I hadn't dug deeper into
these APIs. There's always the risk of breakage if the string changed in
future, as well as increased maintenance if/when an API or library changes.
Completely missed that area of the wiki, my bad. My searches and entry points
yesterday kept me within the "Get Involved" areas. Didn't spot any links
towards the "Policies" area. The previews when searching the wiki wasn't as
obvious:
-
https://community.kde.org/index.php?search=%22BUG%3A%22&title=Special%3ASearch&profile=default&fulltext=1
[Yesterday]
-
https://community.kde.org/index.php?search=%22BUG%3A%22+keywords&title=Special%3ASearch&profile=default&fulltext=1
[Today]
I see now it is also mentioned in:
https://community.kde.org/Infrastructure/GitLab#Write_a_good_commit_message and
https://community.kde.org/Infrastructure/Git/Hooks#Keywords too.
Thanks again for considering the suggestion!
--
You are receiving this mail because:
You are watching all bug changes.
