1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
|
-
+
-
+
+
-
-
-
-
-
+
+
+
+
+
-
-
+
+
+
+
|
<h1>Fossil Cookbook</h1>
The <cite>Fossil</cite> Cookbook is a collection of task-oriented instructions for intermediate users who wish to do more than basic operations with their <cite>Fossil</cite> repositories. The [Tutorial|tutorial] is a more suitable place for newcomers trying to learn the basic concepts to go first before tackling these recipes.
<h2>Index</h2>
<ul>
<li> Server recipes:
<li>Server recipes:
<ul>
<li> <a href="#CGI">Using <cite>Fossil</cite>'s Built-In CGI</a>
<li><a href="#CGI">Using <cite>Fossil</cite>'s Built-In CGI</a>
</ul>
</li>
<li> <a href="#env">Using Environment variables</a>
<li> <a href="#css">Example CSS</a>
<li> <a href="#source-hilight">Source highlighting</a>
<li> <a href="#win32dev">Fossil Win32 Development Machine setup</a>
<li> <a href="#wysiwig">Javascript HTML WYSIWYG editor control</a>
<li><a href="#env">Using Environment variables</a></li>
<li><a href="#css">Example CSS</a></li>
<li><a href="#source-hilight">Source highlighting</a></li>
<li><a href="#win32dev">Fossil Win32 Development Machine setup</a></li>
<li><a href="#wysiwig">Javascript HTML WYSIWYG editor control</a>
<ul>
<li> <a href="#tinymce">TinyMCE</a>
<li> <a href="#markitup">markitup!</a>
<li><a href="#tinymce">TinyMCE</a></li>
<li><a href="#markitup">markitup!</a></li>
</ul>
</li>
<li><a href="#ticket-checkin-links">Link tickets to checkins</a></li>
</ul>
<h2><a name="CGI">Using <cite>Fossil</cite>'s Built-In CGI</a></h2>
<h3>Motivation</h3>
* You want to share a repository through your existing web infrastructure.
* You want to share more than one repository at the same time.
|
659
660
661
662
663
664
665
|
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
|
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
|
$(document).ready(function() {
$("#" + n).markItUp(mySettings);
});
}
}
</script>
</pre>
<h2><a name="ticket-checkin-links">Linking Tickets to Checkin's</a></h2>
It's easy to link a checkin to a ticket... simply include <nowiki>[ticket-uuid]</nowiki> in your commit comment. Now, when you do that, you also have the ability to link a ticket to the associated checkin(s).
This is just one way of doing this, and what I decided to do. You can of course alter it for your own style/layout.
First: Add a "Short UUID" to your View Ticket page. You can do this by:
<verbatim>
<th1>
set shortUuid [string range $tkt_uuid 0 9]
</th1>
</verbatim>
Then, display that to the user somewhere:
<verbatim>
Uuid: $<shortUuid>
</verbatim>
All that does is make it easy for the developer to copy/paste a sensible UUID into their commit log.
Now, continuing, on the same View Page add a link to view associated tickets:
<verbatim>
<a href="/timeline?y=ci&s=$<shortUuid>">associated tickets</a>
</verbatim>
What this does is searches all checkin's for the tickets uuid, thus, you can now see all checkin's that are linked with the given ticket.
|