Closed MichaelClifford closed 2 years ago
/assign committee/steering
/assign @durandom @goern
/test all
could you please add sig/sig-data-science/OWNERS, example at https://github.com/open-services-group/community/blob/main/wg-byon-build-pipelines/OWNERS the wg-<wg_name>-leads
OWNERS ALIAS is created automatically in https://github.com/open-services-group/community/blob/main/OWNERS_ALIASES
/test all
the failed unit test is rooted in the fact, that https://github.com/open-services-group/community/pull/7/files#diff-e530f01fe535a415df76b0ee18da2f51049031bfb3b5328d9033dcfbf96d9d7dR17 is not a parable date.
could you please add sig/sig-data-science/OWNERS, example at https://github.com/open-services-group/community/blob/main/wg-byon-build-pipelines/OWNERS the wg-
-leads OWNERS ALIAS is created automatically in https://github.com/open-services-group/community/blob/main/OWNERS_ALIASES
@goern how does it automatically know who the members of the group defined in OWNERS is?
@goern how does it automatically know who the members of the group defined in OWNERS is?
It's derived from the chair specification in sigs.yaml, as it is not an alias for 'the members' but for 'the leads' (chairs) of the WG
The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as [members]() of the open-services-group org. You can then trigger verification by writing /verify-owners
in a comment.
:heart: it! and merge it manually! thanks for putting the work in to make it nice and clean! /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: goern
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Signed-off-by: MichaelClifford mcliffor@redhat.com
This PR includes a first draft of the Data Science SIG charter for review by the team and steering committee as well as an update to the the
sigs.yaml
corresponding to the potential creation of the new SIG.committee/steering