Opened 15 years ago
Last modified 9 years ago
#9216 new enhancement
changeset hook for wiki pages
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | lowest | Milestone: | next-major-releases |
Component: | wiki system | Version: | |
Severity: | normal | Keywords: | resource consider |
Cc: | leho@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I configured a changeset post-commit hook from SVN to Trac, and now every time I add a new changeset to SVN with a properly formatted comment, Trac automatically adds a message to the corresponding ticket. Would be nice to have the same functionality for wiki pages. When I make a change to some wiki page, and format comment properly, Trac ticket gets a message, automatically. Thanks.
Attachments (0)
Change History (9)
comment:1 by , 15 years ago
Component: | general → wiki system |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
comment:2 by , 15 years ago
Thanks for comment, will try to implement it with a custom plugin.
However, the question is - why SVN+Trac hook is useful (it's in core now), and Wiki+Trac is not useful? What is the key difference between them?
comment:3 by , 15 years ago
Resolution: | wontfix |
---|---|
Status: | closed → reopened |
comment:4 by , 15 years ago
Keywords: | resource consider added |
---|---|
Milestone: | → 2.0 |
The key difference is that in the past 5 years or so, I've seen a lot of people ask for the first one and be happy with the contrib/trac-post-commit-hook (and we hope to keep them happy with the newer style tracopt.ticket.commit_updater), but here it's the first time someone requests the ability to be able to do the same from a Wiki page…
Not necessarily a bad idea, but a less common requirement for sure ;-)
That being said, I wonder if we couldn't have this ticket commit updater react on the future directly to IResourceChangeListener notifications (#8834), and hence could simply be configured to react also on wiki changes.
comment:5 by , 15 years ago
I see little difference between a source code in SVN and a documentation/specification page in Wiki. They both have version control and their changes are related to Trac tickets… On the other hand, 5 years experience really proves something :)
Anyway, thanks for adding this feature to your future plans.
comment:6 by , 15 years ago
Cc: | added |
---|
comment:8 by , 14 years ago
Milestone: | triaging → next-major-0.1X |
---|---|
Priority: | normal → lowest |
comment:9 by , 9 years ago
Status: | reopened → new |
---|
That's a nice idea, and all the infrastructure is already there to make this happen in a plugin. Look for the
IWikiChangeListener
in trac/wiki/api.py.However, I don't think this functionality is useful to enough people to be included in core.