Handbook: Add ritual and handbook section about responding to website code scanning alerts

[eashaw]

Changes:

• Added a new section to the website handbook page about responding to website code scanning alerts.
• Added a "Respond to website code scanning alerts" ritual to the engineering rituals

Summary by CodeRabbit

• Chores
  • Established a weekly process for responding to website code scanning alerts to enhance code quality and security.

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

_{Tip: disable this comment in your organization's Code Review settings.}

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 6e2caee4-f99d-4cf7-9c9c-fdd4e53b77b1

📥 Commits

Reviewing files that changed from the base of the PR and between c55cae6 and f95d72b.

⛔ Files ignored due to path filters (1)

• handbook/engineering/website.md is excluded by !**/*.md

📒 Files selected for processing (1)

• handbook/engineering/engineering.rituals.yml

---

Walkthrough

A new weekly engineering ritual task titled "Respond to website code scanning alerts" was added to the engineering rituals configuration file. The task is scheduled to start on 2024-05-04, includes a reference link to the handbook, designates eashaw as the directly responsible individual, and is configured with an automated issue creation block that targets the Fleet repository with a #g-website label.

Possibly related PRs

• fleetdm/fleet#44443: Also modifies the engineering rituals configuration file with website-related ritual entries

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is minimal but covers the key changes. However, it does not follow the required template structure with sections like 'Related issue', 'Checklist for submitter', 'Testing', etc.	Consider using the repository's PR description template to provide more context, such as related issues, testing approach, and relevant checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main changes: adding a ritual and handbook section about website code scanning alerts.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch handbook-update-website-page

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}