Skip to content

Maintenance: retire Boring Cyborg greetings in favour of oss-automation #5533

Description

@dreamorosi

Summary

The organization's oss-automation now posts the first-issue welcome and first-merged-PR congratulation and is live in production. Boring Cyborg's configuration in this repository must stop posting the same greetings to avoid duplicate comments, and the app will subsequently be retired from this repository entirely through configuration file deletion and uninstall.

Tracked in detail in aws-powertools/powertools-lambda-oss-automation#203.

Why is this needed?

Both automations posting the same greetings causes duplicate comments. Removing the overlapping Boring Cyborg configuration now, then retiring the app after observing live traffic, gives contributors a single greeting from the organization's maintained automation.

Which area does this relate to?

Automation

Solution

  1. Remove firstPRMergeComment and firstIssueWelcomeComment from .github/boring-cyborg.yml (PR chore(ci): remove greetings now handled by oss-automation #5532).
  2. After observing live traffic, delete .github/boring-cyborg.yml and .github/semantic.yml, remove the PR template's deep-link to semantic.yml, and uninstall the Boring Cyborg app.

Acknowledgment

Future readers

Please react with 👍 and your use case to help us understand customer demand.

Activity

  1. added
    triageThis item has not been triaged by a maintainer, please wait
    internalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
    and removed
    triageThis item has not been triaged by a maintainer, please wait
    on Aug 4, 2026
  2. self-assigned this
    on Aug 5, 2026
  3. dreamorosi commented on Aug 5, 2026

    @dreamorosi
    ContributorAuthor

    Reopening: config-file deletion (#5535) and the app uninstall are still pending.

  4. powertools-for-aws-oss-automation commented on Aug 5, 2026

    @powertools-for-aws-oss-automation

    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 reopen the issue, or open a new issue referencing this one.
    If you wish to keep having a conversation with other community members under this issue feel free to do so.

  5. added
    completedThis item is complete and has been merged/shipped
    and removed
    pending-releaseThis item has been merged and will be released soon
    on Aug 18, 2026
  6. removed
    internalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
    completedThis item is complete and has been merged/shipped
    on Sep 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions