Maintenance: Pull requests automation failing after migration

[heitorlessa]

Why is this needed?

Ensure automation and governance works as expected

Which area does this relate to?

No response

Solution

No response

Acknowledgment

• This request meets Powertools for AWS Lambda (Python) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

[heitorlessa]

Gonna investigate it today.

[heitorlessa]

All working actually (cc @leandrodamascena) except those Documentation build + Changelogs + Version bump automation that need to create a Pull Request due to protected branch.

This will be fixed once OSPO addresses a disabled setting.

---

• PR extraction from fork (works)
• On new PR
  • Check for missing issue
  • Check for acknowledgment
• On label added (works)
• Label PR based on title (works, also continue to work on editing)
• On PR merge (works)

[rubenfonseca]

@leandrodamascena do you know if we can close this one?

[rubenfonseca]

Closing as done.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.