Project

General

Profile

Actions

action #106607

closed

GitHub review notifications are sent to osd-admins+os-autoinst-obs@suse.de

Added by livdywan about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
-
Target version:
Start date:
2022-01-17
Due date:
2022-03-09
% Done:

0%

Estimated time:

Description

Motivation

The mailing list osd-admins@suse.de is generally used for alert emails. GitHub emails seem misplaced here.

Acceptance criteria

Suggestions

  • Configure notification settings for insert-name-here account
  • Use a different email address that's not the ml
  • Filter emails somehow
Actions #1

Updated by okurz about 2 years ago

Well, likely what you consider problematic is that emails are received due to the user "os-autoinst-obs" being part of the "tools team". IMHO the account shouldn't be part of that team but be separate. So I agree with the AC but not with the motivation "GitHub emails seem misplaced here." nor the suggestions. The bot user simply shouldn't be asked for review.

Actions #2

Updated by livdywan about 2 years ago

okurz wrote:

Well, likely what you consider problematic is that emails are received due to the user "os-autoinst-obs" being part of the "tools team". IMHO the account shouldn't be part of that team but be separate. So I agree with the AC but not with the motivation "GitHub emails seem misplaced here." nor the suggestions. The bot user simply shouldn't be asked for review.

I don't know anything about that. If this stems from some other undesired behavior and solves both issues, fine by me.

Actions #3

Updated by livdywan about 2 years ago

In Slack it was suggested that @okurz would have to remove os-autoinst-obs-workflow from the team, on account of being the owner.

I checked the list of members on the tools-team. I can't change a member's status.

Actions #4

Updated by okurz about 2 years ago

  • Priority changed from Normal to Low
Actions #5

Updated by okurz about 2 years ago

  • Due date set to 2022-03-09
  • Status changed from New to Feedback
  • Assignee set to okurz

I removed "os-autoinst-obs-workflow" from the github tools team as nobody seems to remember why we would need it on the team. Let's see what this breaks.

Actions #6

Updated by tinita about 2 years ago

We don't need it on the team, but the user has to be able to create github webhooks for the projects.
So please give it the permission to do so.

Actions #7

Updated by okurz about 2 years ago

I created a new team "obs-integration-bot" in https://github.com/orgs/os-autoinst/teams/obs-integration-bot/members and added that team on https://github.com/os-autoinst/os-autoinst/settings/access and https://github.com/os-autoinst/openQA/settings/access with role "Write". If I understand correctly custom roles to fine-tune would only be possible in github enterprise according to https://docs.github.com/en/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization . I don't know, how can we check if that works?

Actions #8

Updated by tinita about 2 years ago

I get a 404 for https://github.com/os-autoinst/os-autoinst/settings/access and https://github.com/os-autoinst/openQA/settings/access

I set it to "Admin" instead of "Write" and now it works.

Actions #9

Updated by tinita about 2 years ago

I think this is resolved.

Actions #10

Updated by tinita about 2 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF