Re: Help with autopkgtest for Seqsero and python-loompy
Hi,
On Tue, Feb 23, 2021 at 11:09:39PM +0530, Nilesh Patra wrote:
> ...
Thanks Nilesh for helping out. No comment so far.
> In any case, you can enable salsa CI on your personal fork to track this.
Hmmm, I think we should not propagate personal forks. I'm afraid that
some fork might feature interesting commits but will be lost somewhere.
So I'd prefer to have salsa CI activated on the main med-team
repository.
> I'm not sure what "couldn't push my changes because it is on a protected
> branch" means here. You should be able to push unless you aren't trying to
> force-push.
I observed from time to time that master branch is marked "protected"
and I have no explanation at all and this is extremely annoying since it
might scare away newcomers. My "cure" is to simply set those people who
are affected to "Maintainer" status (which seems to enable also pushing
to protected branches). May be we should simply run a script to unprotect
all master branches ... and find out why this might happen at all.
> If you aren't force-pushing, then you need better access than developer
> probably for this one. I just granted you maintainer access for this repo,
> try pushing once.
I've set general maintainer access. I think if we want to enable people
to create new repositories all should get this status. I fail to see any
sense in different levels of membership.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: