I think perhaps you meant “commit” comment below? Its the commit comment that needs to be tweaked, in theory, by the TH1…not the ticket itself. So are you saying that modifying a commit comment requires that an artifact be created with TH1 somehow, if even possible?
For the ticket table, I noticed in the admin page that there is a SQL insert statement with comments that say we can add our own columns to it for whatever purpose we want. It already has a status column which could be used to store “working” status, but what I was thinking is I could stash something in a different column that basically indicates its actually THE ONE that is being worked on right now… I don’t think (?) any artifacts are needed for putting info like that into the ticket table and using TH1 to check out that data from the ticket table…it would not be any new records, but rather an additional column to an existing row in ticket table. However, it makes sense that actually updating the commit comment would be more involved, and plenty of opportunities to get it wrong if there is no API for such a thing in TH1…sounds like I would need have TH1 issue some SQL that does it…and make sure the SQL is doing things right internally to create this artifact you mentioned holding the updated commit comment. Yes? probabably easier and safer to just put this in the wrapper script I guess. On May 20, 2016, at 8:14 AM, Ron W <ronw.m...@gmail.com> wrote: > On Fri, May 20, 2016 at 2:21 AM, Steve Schow <st...@bstage.com> wrote: > Hmm, very interesting idea about using the EDITOR feature to run a > pre-script…i will have to ponder that…possibly an alternative to using an > actual wrapper script…. > > Sounds like server side TH1 probably won’t do it. > > throwing a table into the checkout DB would be easy enough to do…can use > sqlite directly for that. Its just a convenient place to put it. I’d also > interact with the repo’s ticket table to look for tickets that are “working” > status, etc. I was also thinking of adding a column to the ticket table in > the repo and then putting something there to indicate its the one I’m working > on…in which case I was thinking maybe TH1 could somehow pick it up…but it > sounds like the commit operation doesn’t get to the TH1 to do some action for > adding the ticket uid to its comment? > > Fossil has "post commit" hooks for file commits and ticket updates that run > TH1 scripts configured by the Admin/Transfers page in the Fossil web UI. > > While you might be able to change the various tables in the SQL database, > creating a "control artifact" to insert in the artifact table will also be > required. Other than the artifact table, the DB tables are caches of meta > data from the artifacts. > > In theory, a field like "working on" could live only in the ticket table, but > could be cleared by other updates to the same ticket. > > However, to insert the ticket ID into a ticket comment will require creating > a "control artifact" to contain the modified comment (see > http://fossil-scm.org/index.html/doc/trunk/www/fileformat.wiki) > > Alternately, you can edit the TH1 in the Edit Ticket UI page to support your > "working on this ticket right now" field. Then create a Ticket Report that > reports the currently "working on" tickets (if more than one ticket is > reported, you forgot to make the ticket as not "working on"). Then your > wrapper could use "fossil ticket show workReport" to get ID of "working on" > ticket and insert that ID in the commit comment. > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
