Skip to content

[chore][ping-codeowners-on-new-issue] Process issue even if code owner filed #38841

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 20, 2025

Conversation

crobert-1
Copy link
Member

@crobert-1 crobert-1 commented Mar 20, 2025

Description

Currently when a code owner files an issue the component's label is not added and the code owners are not pinged. This changes functionality so that even if a code owner files an issue, the component label is added and the code owners are pinged. I investigated this as a result of confusion because of the existing behavior.

Note: If the component is included in the title the label will be properly added to the component even before this change.

Pros for this change:

  • Labels are added automatically
  • Other code owners (for the case of >1 code owner for a component) are notified of a new issue against their component.

Cons for this change:

  • It might result in noise for the code owner who is filing issues, especially if they're filing in bulk.

Alternatives:

  • We could at least add the label even if a code owner filed the issue.
  • We could try to remove the filing code owner's handle from the ping message so they don't get pinged, and add a case for not pinging code owners if the user filing is the only code owner.

Related:
#33437
#30136

@crobert-1 crobert-1 requested a review from a team as a code owner March 20, 2025 22:26
@crobert-1 crobert-1 requested a review from evan-bradley March 20, 2025 22:26
Copy link
Member

@songy23 songy23 left a comment

Choose a reason for hiding this comment

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

Other code owners (for the case of >1 code owner for a component) are notified of a new issue against their component.

+1 I think this is the main benefit

@songy23 songy23 added the ci-cd CI, CD, testing, build issues label Mar 20, 2025
@atoulme atoulme merged commit f3288ea into open-telemetry:main Mar 20, 2025
183 checks passed
@github-actions github-actions bot added this to the next release milestone Mar 20, 2025
@mowies
Copy link
Member

mowies commented Mar 24, 2025

this change could also be ported to the scripts in the collector core repo so that they are consistent

github-merge-queue bot pushed a commit to open-telemetry/opentelemetry-collector that referenced this pull request Mar 25, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
Code owners should be pinged even if a code owner filed an issue. This
helps other code owners, in the case of more than one for a single
component, be notified of relevant issues being filed.

This is the same change as
open-telemetry/opentelemetry-collector-contrib#38841,
as
[requested](open-telemetry/opentelemetry-collector-contrib#38841 (comment)).
github-merge-queue bot pushed a commit to open-telemetry/opentelemetry-collector that referenced this pull request Mar 27, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
Code owners should be pinged even if a code owner filed an issue. This
helps other code owners, in the case of more than one for a single
component, be notified of relevant issues being filed.

This is the same change as
open-telemetry/opentelemetry-collector-contrib#38841,
as
[requested](open-telemetry/opentelemetry-collector-contrib#38841 (comment)).
Fiery-Fenix pushed a commit to Fiery-Fenix/opentelemetry-collector-contrib that referenced this pull request Apr 24, 2025
…r filed (open-telemetry#38841)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
Currently when a code owner files an issue the component's label is not
added and the code owners are not pinged. This changes functionality so
that even if a code owner files an issue, the component label is added
and the code owners are pinged. I investigated this as a result of
[confusion because of the existing
behavior](open-telemetry#38672 (comment)).

Note: If the component is included in the title the label will be
properly added to the component even before this change.

Pros for this change:
- Labels are added automatically
- Other code owners (for the case of >1 code owner for a component) are
notified of a new issue against their component.

Cons for this change:
- It might result in noise for the code owner who is filing issues,
especially if they're filing in bulk.

Alternatives:
- We could at least add the label even if a code owner filed the issue.
- We could try to remove the filing code owner's handle from the ping
message so they don't get pinged, and add a case for not pinging code
owners if the user filing is the only code owner.

Related:

open-telemetry#33437

open-telemetry#30136
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-cd CI, CD, testing, build issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants