Add support for readme autogeneration for content package

[ishleenk17]

Issue: #1052

Related Issue: https://github.com/elastic/obs-integration-team/issues/1004

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e82b0c1c-a469-4014-9ad2-0cbaa393471c

📥 Commits

Reviewing files that changed from the base of the PR and between 5237d2c and a7e0033.

📒 Files selected for processing (2)

• spec/changelog.yml
• test/packages/good_content_with_dev/_dev/build/docs/README.md

✅ Files skipped from review due to trivial changes (2)

• test/packages/good_content_with_dev/_dev/build/docs/README.md
• spec/changelog.yml

---

📝 Walkthrough

Walkthrough

Added a new optional build folder entry to spec/content/_dev/spec.yml (type: folder, required: false, $ref: "../../integration/_dev/build/spec.yml"). Appended a changelog entry in spec/changelog.yml under 3.6.1-next noting that _dev/build/docs is permitted for README auto-generation. Added a test README at test/packages/good_content_with_dev/_dev/build/docs/README.md.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

• 🛠️ Update Documentation: Commit on current branch
• 🛠️ Update Documentation: Create PR

---

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.}

[teresaromero]

could we add this to the good_content fixture? thanks

EDIT: also, could you add a changelog entry?

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: a7e0033

History

• 💚 Build #2093 succeeded 5237d2c