Skip to content

Conversation

@giorgionaps
Copy link
Contributor

@giorgionaps giorgionaps commented Nov 27, 2025

Description

Retro review of RPA docs.
Closes #7356

When should this change go live?

  • This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
  • This is already available but undocumented and should be released within a week. (add available & undocumented label)
  • This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
  • This is part of a scheduled alpha or minor. (add alpha or minor label)
  • There is no urgency with this change (add low prio label)

PR Checklist

  • My changes are for an upcoming minor release and are in the /docs directory (version 8.9).
  • My changes are for an already released minor and are in a /versioned_docs directory.

@CLAassistant
Copy link

CLAassistant commented Nov 27, 2025

CLA assistant check
All committers have signed the CLA.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 27, 2025

👋 🤖 🤔 Hello, @mesellings! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.8/.

  • docs/components/rpa/getting-started.md
  • docs/components/rpa/overview.md
  • docs/components/rpa/production.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

@giorgionaps giorgionaps added the low prio There is no urgency with this change. label Nov 27, 2025
Copy link
Collaborator

@mesellings mesellings left a comment

Choose a reason for hiding this comment

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

Thanks @giorgionaps - I made a few other edits, but think this is good to get some approval from the RPA team now before we backport any changes 🚀

@mesellings mesellings added hold This issue is parked, do not merge. Retro review required This PR was merged without a TW review; retro review required. labels Dec 5, 2025
@mesellings mesellings requested a review from marstamm December 5, 2025 11:37
@mesellings
Copy link
Collaborator

@marstamm we are just doing a retro review on the RPA docs to standardise them with our other docs a bit more - requested your review if you wanted to check you are happy with the changes first? 🙏

@mesellings mesellings added component:rpa Issues related with robotic Process Automation (RPA) and removed Retro review required This PR was merged without a TW review; retro review required. labels Dec 5, 2025
@marstamm
Copy link
Member

marstamm commented Dec 5, 2025

Thank you @giorgionaps and @mesellings ! I will have a look into this on Monday 👀

Copy link
Member

@marstamm marstamm 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 for the rework, this looks all good from the technical side and reads much nicer 🥇

@mesellings mesellings removed the hold This issue is parked, do not merge. label Dec 8, 2025
@mesellings
Copy link
Collaborator

Thanks @giorgionaps please backport the changes as required, you can do that in this PR or a separate one if you want? Nice work! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component:rpa Issues related with robotic Process Automation (RPA) low prio There is no urgency with this change.

Projects

Status: 👀 In Review

Development

Successfully merging this pull request may close these issues.

Retro review of RPA documentation

5 participants