fix: use PUT for repository ruleset updates

[hugo2006alm]

Resumo

Corrige o método HTTP usado por tools/repo_security.py ao atualizar rulesets existentes.

• troca PATCH por PUT apenas no endpoint repos/{owner}/{repo}/rulesets/{ruleset_id};
• mantém PATCH no endpoint de CodeQL Default Setup, onde continua a ser o método correto;
• evita o 404 Not Found observado ao aplicar presets com --apply.

Validação: o endpoint de rulesets foi confirmado manualmente no template-sei-website, onde PUT atualizou com sucesso os rulesets main e dev.

[Copilot]

🟡 Changes recommended

The switch to PUT can unintentionally clear live-only ruleset fields (e.g., bypass_actors) that are not present in the preset payload, changing ruleset behavior during --apply.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR adjusts tools/repo_security.py to use the correct HTTP method when updating existing GitHub repository rulesets, aligning the script with the Rulesets REST API behavior and preventing the 404 Not Found seen during --apply.

Changes:

• Switches ruleset updates from PATCH to PUT on repos/{owner}/{repo}/rulesets/{ruleset_id}.
• Keeps PATCH for CodeQL Default Setup (where it remains the appropriate method).
• Clarifies the CLI help description to explicitly mention “repository rulesets”.

File summaries

File	Description
tools/repo_security.py	Uses PUT for ruleset updates and refines CLI description text.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.