GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption, please take a look at our documentation.
@@ -31,3 +31,6 @@ Doc also refers to local.css which is only comments on branchable.com anyway.
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Been trying shortly git-annex a few times. Considering to put some important stuff inside now (1Tb photos/videos). I love git-annex concept and believes that you Joey have the eye for details that make rock-solid software possible (I do that for a living). I've been using Unison for about 15 years. Unison is nice enough for *sync* if storage devices are mounted always on same machine in same directory. For source code *history*, I've been relying on git with great satisfaction (and seen quite a few git repos wrecked by a missing or corrupted file in .git, good job remote repos come to the rescue). Since git allows to change remote URLs at any time and just work, I believe git-annex will bring the best of both worlds. Also I love your style: everything not essential is just not added, preserving efficiency. Best way for a solid system is adding only what's necessary.
> Ok, I've added the ikiwiki underlay to get the style sheets.