|
Documentation Channel for #raku | This channel is logged | Roadmap: github.com/raku/doc/wiki Set by [Coke] on 23 May 2022. |
|||
| [Coke] | did buildkite.com/raku/doc-website/builds/5810 kick off a build? doesn't look like error-report was updated. | 00:39 | |
| er, a deploy? | |||
|
05:19
ab5tract left,
ab5tract joined
08:29
sena_kun joined
11:02
sena_kun left,
Altai-man joined
15:02
Altai-man left
15:06
sena_kun joined
|
|||
| coleman | The buildkite-agent is running but it is having trouble connecting to the server | 16:04 | |
| restarting | |||
| seems good now | 16:07 | ||
| [Coke] | ok - error-report was not regen'd by that, will try another docs-dev commit to poke it | 17:42 | |
| Geth | doc-website/docs-dev: df2c554c89 | (Will Coleda)++ | README.md whitespace |
||
| [Coke] | TIL about git -C | 17:56 | |
| ... Wow, that would have saved me some effort in a raku script I wrote to checkout all the git repos in an azdo project. | |||
| ok. buildkite.com/raku/doc-website/builds/5820 completed... does this result in a deploy? | 17:57 | ||
| lizmat | heh... will need to remember that for App::Rak --show-blame option :-) | ||
| [Coke] | ok, it hasn't updated the website by now either. Coleman, how do I get an update to date build of the site (not just the latest docs) to deploy to docs-dev? I've been pushing changes to raku/doc:main, then doing a whitespace change on raku/doc-website:docs-dev | 18:09 | |
| Is there a buildkite pipeline i need to trigger? something else? | |||
| [Coke] will try to do a local build, I guess. | 18:10 | ||
| oh, I think I missed the "then every 30m a deploy is done", and that's not tracked on buildkite. | 18:11 | ||
| would really like a way to monitor that "every 30m" bit. | 18:48 | ||
| I'm not seeing my expected changes yet. | |||
| So I am sure I'm missing some step here. | |||
| coleman | the tag was updated quay.io/repository/colemanx/raku-d...e?tab=tags | 18:52 | |
| checking the site | 18:53 | ||
| [Coke] | The shas at docs-dev.raku.org/about seem to be correct. | 18:57 | |
|
18:58
finanalyst joined
|
|||
| [Coke] | so I was expecting error-report to be much shorter. I'll try to find an explicit one that doesn't seem right, maybe I didn't fix what I thought. | 18:59 | |
| ARGH. So the first of the bad links I checked, it was still really a bad link I hadn't fixed. Figures! | 21:00 | ||
| Geth | doc/main: a89742bdfe | (Will Coleda)++ | 11 files fix more links Part of #4476 |
21:13 | |
| doc-website/fix_issue_403: ecc441d4d5 | finanalyst++ | Website/plugins/link-error-test/let-templates.raku addresses issue in #403 adds time/date in glitches section |
22:13 | ||
| doc-website: finanalyst++ created pull request #404: addresses issue in #403 adds time/date in glitches section |
22:14 | ||
| doc-website/main: a754afa082 | (Richard Hainsworth)++ (committed using GitHub Web editor) | Website/plugins/link-error-test/let-templates.raku addresses issue in #403 adds time/date in glitches section (#404) |
22:33 | ||
|
22:33
sena_kun left
|
|||
| Geth | doc-website/fix_issue_401: e563ff9d07 | finanalyst++ | Website/plugins/link-error-test/let-callable.raku addresses issue in #401 whitelists all links with typegraphs - all typegraph headings have an id of typegraphrelations - if a target contains this, the target is passed - it will not work if the target is in an external file, so this test is too broad, but given the rarity of such a link, I think this fix is the best use of time |
22:40 | |
| doc-website: finanalyst++ created pull request #405: addresses issue in #401 whitelists all links with typegraphs |
|||
|
23:36
finanalyst left
|
|||