[Csnd-dev] master branch
Date | 2023-02-05 18:02 |
From | Victor Lazzarini |
Subject | [Csnd-dev] master branch |
Hi everyone, I just wanted to let you know that I have locked the master branch to avoid any accidental pushes there. It’s read-only. If we decide to make a release, I’ll unlock prior to updating it and then lock it back again. best ======================== Prof. Victor Lazzarini Maynooth University Ireland |
Date | 2023-02-05 19:07 |
From | Rory Walsh |
Subject | Re: [Csnd-dev] master branch |
Good call, will prevent clowns like me pushing to it 😬 On Sun 5 Feb 2023, 6:02 p.m. Victor Lazzarini, <Victor.Lazzarini@mu.ie> wrote: Hi everyone, |
Date | 2023-02-05 19:12 |
From | Victor Lazzarini |
Subject | Re: [Csnd-dev] [EXTERNAL] Re: [Csnd-dev] master branch |
To be fair we never said anything about not pushing to it. Prof. Victor Lazzarini
Maynooth University
Ireland
On 5 Feb 2023, at 19:08, Rory Walsh <rorywalsh@ear.ie> wrote:
|
Date | 2023-02-05 22:36 |
From | Steven Yi |
Subject | Re: [Csnd-dev] master branch |
We could make it such that you can only merge to it via Pull Request, and do PRs for merging from develop to master. I've found that extra step to require a review works well. On Sun, Feb 5, 2023 at 1:02 PM Victor Lazzarini |
Date | 2023-02-06 08:03 |
From | Rory Walsh |
Subject | Re: [Csnd-dev] master branch |
I typically do that, but this was a one liner change to an install script. But I will stick to PRs going forward. 👍 On Sun 5 Feb 2023, 10:37 p.m. Steven Yi, <stevenyi@gmail.com> wrote: We could make it such that you can only merge to it via Pull Request, |