Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 519497

Summary:	Why are micorprofile repositories not getting proper permissions?
Product:	Community	Reporter:	John Ament <john.d.ament>
Component:	GitHub	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X
Whiteboard:	stalebug

Description John Ament

2017-07-11 07:50:45 EDT

I'd like to keep this open as a tracking ticket for our permission problems.  We're planning to create many small repositories, all of which should be writable by all members of Microprofile.  However, it seems that each time we create a new repository the wrong permission schemes are getting set.  Why is that?  What can we do to help get this setup correctly?

Comment 1 Eclipse Webmaster

2017-07-13 16:18:22 EDT

I think the main issue was that I mistakenly presumed the tool responsible for installing the webhooks and groups for GitHub repos understood wildcards. Clearly that is not the case.

If you do need a bunch of little repos perhaps we could batch them rather than filing a bug for each one?

-M.

Comment 2 Eclipse Genie

2019-07-04 07:35:27 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 3 Eclipse Webmaster

2019-07-04 09:44:57 EDT

Closing as 'worksforme' after I changed my assumptions.

-M.