@simulacrum What would think about moving/copying the documentation for triagebot from the wiki to forge? Obviously it loses the tight coupling and could take a bit longer to be up to date, but I think it would make the documentation easier to find for users.
seems fine to me, though we'll probably want to leave a link to forge
I mostly didn't really want to spend the time getting forge working and such when I started the wiki
I was about to draft some documentation about the triagebot, but luckily I was pointed to this stream.
Where can I find the Triagebot documentation ? thx
mentions (just in case) @XAMPPRocky @simulacrum
You'll find it in the Wiki of the triagebot repo
ah right the main repo! I was on a fork and there was no wiki :upside_down:
You're welcome :slight_smile:
What are you searching for btw? The documentation about "requesting prioritization" is probably outdated
the "backstory" for my question was that in this todo list for the wg-prio
there are some tasks about offloading some tasks to the triagebot instead of (this was my understanding) generating some markdown "by hand", (example " Implement @triagebot commands for each step of our procedure" and following).
So I thought about first starting to gather a bit of docs to 1) understand how that work and 2) if there's something I can help with
I'm catching up with all the past discussions, so I'm rebuilding the history little by little :)
I've implemented a few things in Triagebot for the WG, so feel free to ping me if you think I might be able to answer it, otherwise forward it to simulacrum
@apiraino I've been meaning to move all the triagebot documentation from forge if you'd like I'd accept a PR that moves everything to forge. I think the most appropriate place would be under "chat platforms".
I've also been meaning to rename that to platforms to have single category that encapsulates all the different platforms we use.
ah that would be a "good first issue" :-) I'll have a look at that!
@XAMPPRocky sorry for this basic question, I don't understand what this comment requires to do, it has to do with me not being familiar with mdbook:
All the subchapters under "Chat platforms" point to the directory
/chat/. Renaming the chapter to "Platforms" should not change this fact, If am I correct.
I could not find out elsewhere in
./booklinks that seems to need a redirect, so Im wondering which links should I map :thinking:
@apiraino Well I feel that we should also move the source files to match the layout so that the structure in the repo matches the website.
E.g. I think it shouldn't be
oh right, now I understand (and of course it makes sense). Renaming the whole subdir to
./platforms and then maps the redirects
ok now I get it, otherwise we all the people visiting old "chat/*" links would get a 404
@apiraino If it isn’t too much hassle once you’re done with the feedback would you be able to squash the changes into a smaller set of commits? Should hopefully make it easier to review. I was thinking one for the move to platforms and then one for adding the bot docs but feel free to choose what you think is best.
squash the changes into a smaller set of commits
absolutely, that was already in my plans for that PR (I usually rebase messy PRs into a new PR). There are a couple more things I want to check before raising the hand and ask for more feedback. When the content will be finalized, I'd rebase into a new PR with clean commits