Moving board@ to BCC. Attempting to move discussion to builds@
I’m fine with the ASF maintaining its position on stricter provenance and
therefore disallowing third-party write-access to repos.
A suggestion was made, if I understood it correctly, to create a whole other
set of repos that could
Hi Alex,
So this was explored. It creates some problems - first double the
administration overhead - most of that is automated, but it means that
our API usage doubles, and we're already hitting limits from Github.
Second - at least one CI vendor thanked us for not doing that exactly
- because th
Hi David,
Does the idea of having a branch that does the CI like ash-site help out in
this situation.
If these workflows write into a branch that is always copied to and never is
merged back then we would be good. It seems like we can track all “3rd party”
commits in the gitbox and have a chan
Some questions inline. Apologies in advance for not really understanding this
stuff. I'm primarily a client-side developer. My projects do not have
automated PR testing at this point in time. I'm mainly exploring in case we
become popular enough some day to need it.
My line of thinking is t
So from a technical perspective - we can not limit access to specific
branches. There isn't much granularity in the ACLs for Github -
essentially we have to give away write access to the repo.
Our site building tools, which we've written only write to a specific
branch - but that's a tool that we
On Tue, Feb 4, 2020 at 3:56 AM Alex Harui wrote:
>
> Some questions inline. Apologies in advance for not really understanding
> this stuff. I'm primarily a client-side developer. My projects do not have
> automated PR testing at this point in time. I'm mainly exploring in case we
> become p
Hopefully last set of questions for now...
1) It sounds like there is a risk that as the ASF grows, GH may not be able to
grow with us. Did I understand that correctly?
2) If we have money to offer GH, why can't we offer money to the CI Vendors so
we aren't really abusing their free tiers?
3) D
On Mon, Feb 3, 2020 at 9:29 PM Alex Harui wrote:
> Hopefully last set of questions for now...
>
> 1) It sounds like there is a risk that as the ASF grows, GH may not be
> able to grow with us. Did I understand that correctly?
>
GitHub will always grow faster than us. Not a worry.
> 2) If we h
On Tue, Feb 4, 2020 at 4:29 AM Alex Harui wrote:
>
> Hopefully last set of questions for now...
Just wait, the rabbit hole gets deeper :)
>
> 1) It sounds like there is a risk that as the ASF grows, GH may not be able
> to grow with us. Did I understand that correctly?
GH CI may not be willin
(Top-posting a question that rewinds this thread a bit. Feel to continue
other discussion on the latest inline email)
Why do so many tools require write access? It seems like there's at least
*some* part of this that is a technical limitation... dare I say "error"?
My years-stale understanding (f
10 matches
Mail list logo
