| 07:02 | <rkirsling> | this is interesting because I actually have colleagues that are interested in attending, for the first time ever |
| 07:02 | <rkirsling> | so let me finally confirm about how that works :D |
| 07:03 | <rkirsling> | specifically, is there any expedited flow for somebody who's like "oh, I'd like to observe for a day"? |
| 07:04 | <rkirsling> | should they still do the same delegate registration as anybody else? |
| 07:51 | <Rob Palmer> | If the person is part of a member company, onboarding them as a delegate is already expedited. TTJ (time to Jordan adding them to your GitHub team) is <24 hours. |
| 07:53 | <Rob Palmer> | If you do not wish to make them a delegate, and it is accepted they will not speak in the meeting, then you can announce them as an observer on the Reflector post for the meeting, so that the chairs know they are meant to be there. You will be responsible for relaying entry details to them. |
| 07:53 | <Rob Palmer> | Overall it is simplest to make them a delegate, if you are on the fence. |
| 08:29 | <rkirsling> | cool, thanks |
| 16:13 | <Michael Ficarra> | oops, I just realised this isn't the editors channel 😳 |
| 18:16 | <shu> | github question: is it possible to give someone access to a single branch in a repo? |
| 18:40 | <Chris de Almeida> | github question: is it possible to give someone access to a single branch in a repo? |
| 18:41 | <Chris de Almeida> | you may be able to get close to that by using branch protection patterns, but that's not quite the same |
| 18:42 | <shu> | very well, they get to access everything then |