Why would an administrator create rulesets that apply to tags?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Release tags are production pins — v1.2.3 getting force-moved or deleted is a supply-chain and ops nightmare. Tag rulesets lock down who can create or modify those refs. Not emoji policy, not LFS global kill switches.
Full explanation below image
Full Explanation
The correct answer is controlling tag mutations that commonly identify releases. Tag rulesets help ensure only trusted actors create release tags and prevent disruptive rewrites or deletions that break release pipelines and supply-chain trust. Option B is frivolous and incorrect. Option C is unrelated to tag policy. Option D is incorrect. Pair tag rules with signed releases, immutable release assets practices, and Actions that publish only from protected workflows so version pins remain trustworthy for production deploys.