Re: Github commit messages to pgsql-www
От | Alvaro Herrera |
---|---|
Тема | Re: Github commit messages to pgsql-www |
Дата | |
Msg-id | 1296051075-sup-2946@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Github commit messages to pgsql-www (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: Github commit messages to pgsql-www
|
Список | pgsql-www |
Excerpts from Magnus Hagander's message of mar ene 25 16:55:20 -0300 2011: > What do we want to do with them... > > Andrew has set it up for the bulidfarm client code, and it does work, > except they get caught in the moderator queue - becuase they are sent > from noreply@github.com. The way I see it we have a couple of options > for making this work: > > 1) Whiltelist noreply@github.com. We have no way of controlling this > though, so *anybody* with a github repo can have it sent there, and > they all come from the same address. I don't think we can whitelist on > the combination of email and some part of the email,thus filtering > based on repo. > > 2) Just moderate the commit messages as they show up. As a pgsql-committers moderator I am not happy with #2. It would be a lot better if we could somehow do #1 coupled with some filtering that only allows selected projects to go through unmoderated. However, I spent some time looking at Mj2 settings yesterday without success. Could we do #3 but instead of moving the primary to git.pg.org just have a hook or cron'ed task that pushes from github (or pulls from it)? -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-www по дате отправления: