docs: mention changeset in contributing docs

[JoshuaKGoldberg]

PR Checklist

• Addresses an existing open issue: fixes 📝 Documentation: Mention Changesets entries in contributing documentation #1012
• That issue was marked as status: accepting prs
• Steps in CONTRIBUTING.md were taken

Overview

❤️‍🔥

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8d46369

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
flint	Ready	Preview	Comment	Nov 28, 2025 5:14pm

[JoshuaKGoldberg]

For future reference, the following issue and PR are now a fairly canonical flow for this repo:

• 🐛 Bug: [ts.chainedAssignments] Shouldn't report string += ... + concatenation #1024
• fix(ts): [chainedAssignments] allow non-assignment right-side operators #1025