Write the heading migration guides
Congratulations! You’ve been tasked with triaging a pajamas component to ensure it has the correct migration guide(s). The goal of this effort is not simply to write the migration guides, but to look deep at each component and its rules to determine the best approach. The outcome for each rule will either be a fully migratable instance with a migration guide, or an explicitly non-miratable instance with clear reasoning on why it’s not migratable… yet.
Process
Whilst there are two possible outcomes, the path to get there will be very different. Try to get the right balance between getting the job done and being pragmatic. We don’t want to spend too much time on these as we have many guides to get through and little time to do so. Good enough is good enough, we can always iterate.
With that said, there’s a general guide to triaging these migrations in the parent epic gitlab-org&12511. Use it to your advantage if you’re unsure how to proceed. If you’re still unsure, talk to each other. You’re all working on this this milestone so you’re all in the same boat.
Links
Your component area is headings. Here are some links that will help you
Tasks
-
Write what and why guide in the epic Heading scale > Implementation (gitlab-org/gitlab-services&19) -
Suggest adoption scanner rules #123 (comment 1770791851) -
Add to adoption scanner Add adoption scanner rules for headings (#128 - closed) -
Generate issues?