<feed xmlns='http://www.w3.org/2005/Atom'>
<title>cgitext.git/cgitrc.5.txt, branch master</title>
<subtitle>cgitext – CGI for Git extension</subtitle>
<id>https://sayag.it/cgitext.git/atom/cgitrc.5.txt?h=master</id>
<link rel='self' href='https://sayag.it/cgitext.git/atom/cgitrc.5.txt?h=master'/>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/'/>
<updated>2026-08-01T10:50:26Z</updated>
<entry>
<title>theming: include solarized.css theme addon</title>
<updated>2026-08-01T10:50:26Z</updated>
<author>
<name>Saya Andy</name>
<email>saya.andy@posteo.com</email>
</author>
<published>2026-08-01T10:33:19Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=3beb4785562b158fc4c4e67185ac488d5bfa5c60'/>
<id>urn:sha1:3beb4785562b158fc4c4e67185ac488d5bfa5c60</id>
<content type='text'>
The solarized.css includes adoption of Solarized Light/Dark themes for
cgit, switching between light and dark variant depending on preferred
color scheme.

It is not used by default, but can be easily switched on with css
directive.
</content>
</entry>
<entry>
<title>logo: include svg variant for both favicon and logo</title>
<updated>2026-08-01T06:15:38Z</updated>
<author>
<name>Saya Andy</name>
<email>saya.andy@posteo.com</email>
</author>
<published>2026-08-01T06:15:38Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=8a90bca75c8d8755016b46747ca943bb7b37140c'/>
<id>urn:sha1:8a90bca75c8d8755016b46747ca943bb7b37140c</id>
<content type='text'>
The reasoning behind using svg as primary defaults is simple – at
close-up it is much neater, plus svg favicon is supported since 2015 in
Firefox, 2020 in Chromium, 2025 in Safari. For old browsers ico is still
kept as a fallback.

The svg was auto-generated using a Python script and then simplified to
a path, but kept close to an original.
</content>
</entry>
<entry>
<title>licensing: add author preambles where changes were done</title>
<updated>2026-07-31T04:38:28Z</updated>
<author>
<name>Saya Andy</name>
<email>saya.andy@posteo.com</email>
</author>
<published>2026-07-30T05:49:23Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=306fafc1d1d19c51d7ac24479f49c76272934ce5'/>
<id>urn:sha1:306fafc1d1d19c51d7ac24479f49c76272934ce5</id>
<content type='text'>
Add a copyright for changes done by me, also note in README the nature
of this repo
</content>
</entry>
<entry>
<title>ui-ci: let a ci-filter decide whether the tab is shown</title>
<updated>2026-07-30T05:27:31Z</updated>
<author>
<name>Saya Andy</name>
<email>saya.andy@posteo.com</email>
</author>
<published>2026-07-30T05:27:31Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=7162aef3344a4f4f2d7edd2f214d805bd744c20c'/>
<id>urn:sha1:7162aef3344a4f4f2d7edd2f214d805bd744c20c</id>
<content type='text'>
cgit cannot know whether the ref being viewed actually has a pipeline, so
the "ci" tab is offered for every ref and only reveals a missing one once
followed. Probing the ci system from cgit is not an option: the tab is
part of the page header, so it would mean a blocking request for every
page of every repository, cgit links no http client, and job pages are
usually not readable anonymously.

Add a ci filter instead, which receives the ref, whether it is a branch or
a tag, and the expanded url, and answers with its exit status. This keeps
credentials, timeouts and caching in a script, where they belong;
filters/ci-jenkins.sh demonstrates all three against Jenkins' REST API.

The verdict is memoized, so the filter runs once per request rather than
once for the tab and again for the redirect, and it governs the page as
well as the tab, so a hidden tab cannot be reached by typing the url.

Signed-off-by: Saya Andy &lt;saya.andy@posteo.com&gt;
</content>
</entry>
<entry>
<title>ui-ci: add a "ci" tab which redirects to an external ci system</title>
<updated>2026-07-30T05:26:52Z</updated>
<author>
<name>Saya Andy</name>
<email>saya.andy@posteo.com</email>
</author>
<published>2026-07-30T05:26:52Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=b4b4f2325db71041f38902143b28bae94762b111'/>
<id>urn:sha1:b4b4f2325db71041f38902143b28bae94762b111</id>
<content type='text'>
Add a "ci" page which redirects to an external ci system for the ref
being viewed, along with a tab for it in the repository header.

The target is a url template, configurable globally or per repository,
with separate settings for branches and tags because pipelines for the
two commonly live at different locations: on a Jenkins multibranch
pipeline a branch is at job/&lt;name&gt;/job/&lt;ref&gt; while a tag is at
job/&lt;name&gt;/view/tags/job/&lt;ref&gt;. $ref, $repo and $slug are substituted,
$slug being the repository url with any ".git" suffix removed and slashes
replaced by dashes, which is the shape job names usually take.

An explicit repo.ci-url drops the branch and tag urls the repository
would otherwise inherit from the global settings, as it could never take
effect otherwise.

The expansion is written to the Location header verbatim rather than
through cgit_redirect(), which percent-encodes '?', '=' and '%' and would
corrupt any url carrying a query string. An expansion containing CR or LF
is refused so that it cannot smuggle in further headers.

Signed-off-by: Saya Andy &lt;saya.andy@posteo.com&gt;
</content>
</entry>
<entry>
<title>ui-log: allow link following to be disabled per-repo</title>
<updated>2026-02-24T10:49:35Z</updated>
<author>
<name>Jason A. Donenfeld</name>
<email>Jason@zx2c4.com</email>
</author>
<published>2026-02-24T10:48:54Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=0d28d54f0a287ee3e5a12d14ffd2ee23b5e22d76'/>
<id>urn:sha1:0d28d54f0a287ee3e5a12d14ffd2ee23b5e22d76</id>
<content type='text'>
This exists for other CPU heavy operations like blame, but doesn't for
the follow functionality. Add it for that.

Signed-off-by: Jason A. Donenfeld &lt;Jason@zx2c4.com&gt;
</content>
</entry>
<entry>
<title>config: add js</title>
<updated>2022-12-19T15:50:21Z</updated>
<author>
<name>Andy Green</name>
<email>andy@warmcat.com</email>
</author>
<published>2018-06-23T10:25:53Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=aee39b4e9a45e1ba507c0017de50bb9dbbae7af8'/>
<id>urn:sha1:aee39b4e9a45e1ba507c0017de50bb9dbbae7af8</id>
<content type='text'>
Just like the config allows setting css URL path, add a config for
setting the js URL path

Signed-off-by: Andy Green &lt;andy@warmcat.com&gt;
Reviewed-by: John Keeping &lt;john@keeping.me.uk&gt;
Signed-off-by: Christian Hesse &lt;mail@eworm.de&gt;
</content>
</entry>
<entry>
<title>css: change to be a list</title>
<updated>2022-12-19T15:49:09Z</updated>
<author>
<name>Andy Green</name>
<email>andy@warmcat.com</email>
</author>
<published>2018-07-03T03:33:59Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=093ac9697068833a15cae2dbbd5ffbc0203741c0'/>
<id>urn:sha1:093ac9697068833a15cae2dbbd5ffbc0203741c0</id>
<content type='text'>
Without changing the default behaviour of including
/cgit.css if nothing declared, allow the "css" config
to be given multiple times listing one or more
alternative URL paths to be included in the document
head area.

Signed-off-by: Andy Green &lt;andy@warmcat.com&gt;
Signed-off-by: Christian Hesse &lt;mail@eworm.de&gt;
</content>
</entry>
<entry>
<title>cgitrc: handle value "0" for max-repo-count</title>
<updated>2022-12-19T15:22:26Z</updated>
<author>
<name>Christian Hesse</name>
<email>mail@eworm.de</email>
</author>
<published>2018-07-16T14:27:39Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=91f25909b9572ebdf3a0fed8224bf03d0d9bf3db'/>
<id>urn:sha1:91f25909b9572ebdf3a0fed8224bf03d0d9bf3db</id>
<content type='text'>
Setting max-repo-count to "0" makes cgit loop forever generating page
links. Make this a special value to show all repositories.

Signed-off-by: Christian Hesse &lt;mail@eworm.de&gt;
</content>
</entry>
<entry>
<title>about: allow to give head from query</title>
<updated>2022-12-19T15:13:58Z</updated>
<author>
<name>Christian Hesse</name>
<email>mail@eworm.de</email>
</author>
<published>2022-01-10T09:15:33Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=a0f6669bdb74e58b0ddb3f4283209cd5e58c0eb9'/>
<id>urn:sha1:a0f6669bdb74e58b0ddb3f4283209cd5e58c0eb9</id>
<content type='text'>
Reading the README from repository used to be limited to default
branch or a branch given in configuration. Let's allow a branch
from query if not specified explicitly.

Signed-off-by: Christian Hesse &lt;mail@eworm.de&gt;
</content>
</entry>
</feed>
