-
-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
coretasks, docs: fix auto-saving .blocks add host
; improve "Ignoring Users" docs & x-refs
#2550
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I especially like the definition of extlinks
! Leaving myself a note here that once this PR is merged, it would make sense to sweep up the other references in Sphinx's view to issues/PRs to use that feature.
FWIW, when adding the |
I did the same check and thought I saw a few, but upon review, I see that the ones that aren't part of your changeset are comments outside of Sphinx's domain anyway. Oops! |
unblockable
/*_blocks
.blocks add host
; improve "Ignoring Users" docs & x-refs
Maybe still not perfect, but there's at least a way to find out what might make a callable "blockable" (and necessitate using `unblockable` to change that), and how to bypass something that you don't want to be blocked getting blocked. We do still need proper documentation on how to use built-in commands from `coretasks`, but I don't particularly want to link the migrated wiki page at https://sopel.chat/usage/ignoring-people/ here. That old stuff will continue getting folded into the Sphinx docs over time. Arguably, describing the `.blocks` command in `configuration.rst` is already enough to mark the old website page for deletion.
f4ab768
to
1d7122d
Compare
Eliminated the link (to a webpage we're probably going to delete) in favor of directly specifying the available arguments, and added an example of how to `del` a block. (The only examples before were `add`.)
1d7122d
to
a30aad5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, @SnoopJ already did a review of this, and I've nothing to add. Ship it!
Maybe still not perfect, but there's at least a way to find out what might make a callable "blockable" (and necessitate using
unblockable
to change that), and how to bypass something that you don't want to be blocked getting blocked.We do still need proper documentation on how to use built-in commands from
coretasks
, but I don't particularly want to link the migrated wiki page at https://sopel.chat/usage/ignoring-people/ here.That old stuff will continue getting folded into the Sphinx docs over time. Arguably, describing the
.blocks
command inconfiguration.rst
is already enough to mark the old website page for removal as part of sopel-irc/sopel.chat#45.Checklist
make qa
(runsmake lint
andmake test
)