Scott,
Thanks for researching this and send it out.
Yes, I think all MR on DMPLEX should use a label DMPLEX; I don't think
having an additional DM label is worth the effort since all the meat at the
moment is DMPLEX.
We should probably also have a TS label. Maybe others
In a conversation with Barry, he mentioned that we hadn't
really discussed label subscription on this mailing list,
despite the fact that this is perhaps the more useful control
of notifications than what is in given in Settings.
Following up on this discussion, if folks go here:
"Mills, Richard Tran via petsc-dev" writes:
> On 9/12/19 6:33 AM, Jed Brown via petsc-dev wrote:
> [...]
>> https://docs.gitlab.com/ee/user/project/code_owners.html
>>
>> We currently require approval from Integration (of which you are a
>> member) and a code owner (as specified in the file).
>>
On 9/12/19 6:33 AM, Jed Brown via petsc-dev wrote:
[...]
Can you explain CODEOWNERS to me? I cannot find it on the GItlab site. I
want to see every MR.
https://docs.gitlab.com/ee/user/project/code_owners.html
We currently require approval from Integration (of which you are a
member) and a
I added it.
"Balay, Satish" writes:
> Ah good to know.
>
> I've tried adding back 'Team' with 'petsc/developers' listed - but
> 'petsc/developers' keeps disappearing from it. Not sure whats
> happening..
>
>
> thanks,
> Satish
>
> On Thu, 12 Sep 2019, Scott Kruger wrote:
>
>>
>>
>> Here's
Ah good to know.
I've tried adding back 'Team' with 'petsc/developers' listed - but
'petsc/developers' keeps disappearing from it. Not sure whats
happening..
thanks,
Satish
On Thu, 12 Sep 2019, Scott Kruger wrote:
>
>
> Here's what I did:
>
> Settings -> Notifications -> developers +
Here's what I did:
Settings -> Notifications -> developers + Participate
The default is "Global". "Participate" is what I'm using now.
There is a "Custom", but it confuses me since it says you can
use it to match "Participate", but you can't do something like:
Email all new issues, but
On Thu, 12 Sep 2019, Jed Brown via petsc-dev wrote:
> Matthew Knepley via petsc-dev writes:
>
> > On Thu, Sep 12, 2019 at 9:05 AM Balay, Satish via petsc-dev <
> > petsc-dev@mcs.anl.gov> wrote:
> >
> >> When a new MR is created, approval rules default to 'Integration' and
> >> 'Team'
> >>
> >>
Matthew Knepley via petsc-dev writes:
> On Thu, Sep 12, 2019 at 9:05 AM Balay, Satish via petsc-dev <
> petsc-dev@mcs.anl.gov> wrote:
>
>> When a new MR is created, approval rules default to 'Integration' and
>> 'Team'
>>
>> So everyone in the team probably receives emails on all MRs. Now that
When a new MR is created, approval rules default to 'Integration' and 'Team'
So everyone in the team probably receives emails on all MRs. Now that
we have CODEOWNERS setup - perhaps the Team should be removed?
Ok removed for now - I think this will apply only to new MRs.
[I don't know enough
I'm receiving notifications for all activities originating from Merge
Requests since I'm listed as developer of PETSc.
The level of notification set in my GITLAB profile is "participate". Should
I push this down to "mentions"? Are "developers" always participating in
Merge Request discussions?
11 matches
Mail list logo
