Ticking a new signing algorithm (e.g. DKIM2 next to DKIM1) on an automatic domain queued nothing, so the key only showed up at the next rotation. The save now queues the DKIM task when an algorithm is added; unticking or reordering still waits for rotation.
Reported on the forum (t/271). Tests: newly_ticked_dkim_algorithm_queues_its_key, unticked_or_reordered_dkim_algorithms_queue_nothing.
Ticking a new signing algorithm (e.g. DKIM2 next to DKIM1) on an automatic domain queued nothing, so the key only showed up at the next rotation. The save now queues the DKIM task when an algorithm is added; unticking or reordering still waits for rotation.
Reported on the forum (t/271). Tests: newly_ticked_dkim_algorithm_queues_its_key, unticked_or_reordered_dkim_algorithms_queue_nothing.
Saving an automatic domain with a newly ticked signing algorithm (DKIM2
next to DKIM1, say) queued no DKIM task, so the new key only appeared at
the next rotation. Queue the DKIM task when an algorithm is added.
Unticking or reordering still waits for rotation.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Ticking a new signing algorithm (e.g. DKIM2 next to DKIM1) on an automatic domain queued nothing, so the key only showed up at the next rotation. The save now queues the DKIM task when an algorithm is added; unticking or reordering still waits for rotation.
Reported on the forum (t/271). Tests: newly_ticked_dkim_algorithm_queues_its_key, unticked_or_reordered_dkim_algorithms_queue_nothing.