Skip to content

Conversation

mariekirsch
Copy link
Contributor

What does it do?

Adds the mention of the new project metadata section and the subscription ID

Why is it needed?

New feature

@mariekirsch mariekirsch self-assigned this Oct 10, 2025
@mariekirsch mariekirsch added pr: new content PRs for new product features or new documentation sections source: Strapi Cloud PRs/issues targeting the Strapi Cloud documentation labels Oct 10, 2025
Copy link

vercel bot commented Oct 10, 2025

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

Project Deployment Preview Comments Updated (UTC)
documentation Ready Ready Preview Comment Oct 10, 2025 2:33pm

@github-actions github-actions bot added the internal PRs created by the Strapi core team label Oct 10, 2025
@pwizla pwizla added pr: chore and removed pr: new content PRs for new product features or new documentation sections labels Oct 10, 2025
Copy link
Collaborator

@pwizla pwizla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @mariekirsch!

A quick note on the GitHub labels. I always forget to tell you about it 😅 And this should be handled by our bot; not sure why it didn’t run:

The distinction between "new", "updated", and "chore" should be made from the docs point of view, not the product point of view. A new feature for Cloud might actually have a tiny impact on docs. The logic is already encoded in our bot, so once I fix the automation you won’t need to think about it.

Screenshot 2025-10-10 at 16 53 52

Here's how to use them:

  • Adds a new text file → pr: new content
  • Updates an existing file:
    • 10 changed lines or more → pr: updated content
    • fewer changed lines, or just some screenshot updates → pr: chore (not semantically perfect, but we use this label to group very small updates)

It's important to us because the automated release notes generation depends on proper label usage ⚙️
Thank you! 🤓

@mariekirsch
Copy link
Contributor Author

Thank you @mariekirsch!

A quick note on the GitHub labels. I always forget to tell you about it 😅 And this should be handled by our bot; not sure why it didn’t run:

The distinction between "new", "updated", and "chore" should be made from the docs point of view, not the product point of view. A new feature for Cloud might actually have a tiny impact on docs. The logic is already encoded in our bot, so once I fix the automation you won’t need to think about it.

Screenshot 2025-10-10 at 16 53 52 Here's how to use them:
  • Adds a new text file → new content

  • Updates an existing file:

    • 10 changed lines or more → updated content
    • fewer changed lines → chore (not semantically perfect, but we use this label to group very small updates)

Thank you! 🤓

Thanks Pierre, makes sense!! Will make sure to assign the correct label. Thank you 😃

@pwizla pwizla added this to the 6.9.4 milestone Oct 10, 2025
@pwizla pwizla added the flag: merge pending release Pending Strapi Release label Oct 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

flag: merge pending release Pending Strapi Release internal PRs created by the Strapi core team pr: chore source: Strapi Cloud PRs/issues targeting the Strapi Cloud documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants