| 1 |
On 15 September 2014 02:40, Michał Górny <mgorny@g.o> wrote: |
| 2 |
|
| 3 |
> However, I'm wondering if it would be possible to restrict people from |
| 4 |
> accidentally committing straight into github (e.g. merging pull |
| 5 |
> requests there instead of to our main server). |
| 6 |
> |
| 7 |
|
| 8 |
|
| 9 |
Easy. |
| 10 |
|
| 11 |
Put the Gentoo repo in its own group. |
| 12 |
Don't give anyone any kinds of permissions on it. |
| 13 |
Have only one approved account for the purpose of pushing commits. |
| 14 |
Have a post-push hook that replicates to github as that approved account |
| 15 |
|
| 16 |
=> Github is just a read only mirror, any pull reqs submitted there will be |
| 17 |
fielded and pushed to gentoo directly. |
| 18 |
|
| 19 |
Only downside there is the way github pull reqs work is if the final SHA1's |
| 20 |
that hit tree don't match, the pull req doesn't close. |
| 21 |
|
| 22 |
Solutions: |
| 23 |
|
| 24 |
- A) Have somebody tasked with reaping old pull reqs with permissions |
| 25 |
granted. ( Uck ) |
| 26 |
- B) Always use a merge of some kind to mark the pull req as dead ( for |
| 27 |
instance, an "ours" merge to mark the branch as deprecated ) |
| 28 |
|
| 29 |
Both of those options are kinda ugly. |
| 30 |
|
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Kent |
| 35 |
|
| 36 |
*KENTNL* - https://metacpan.org/author/KENTNL |
Archives