On Sat, Dec 10, 2016 at 9:59 AM, Marek Marczykowski-Górecki <[email protected]> wrote: > A `git diff` could be used to avoid this, but still it makes much sense > to have it always fast-forward.
This does not catch someone rewriting old commit messages to hide things. AFAIK there is no better way than manually checking each commit since the common ancestor. > Being member of the organization does not imply write access to the > repository. I agree this somehow makes the separate organization > a bit weird, but those two points above still holds. Ah, I did not understand that. In that case all seems good :) > You know, you can push a branch, wait for Travis and only then open PR > ;) > This require just signing up to Travis yourself (and enabling it for > particular repository). I tried to do that, but (at least at the time) the authorization scheme used gave them a token enabling write access to the contents of (all!) your repositories, and I did not want to allow that. Perhaps this has changed since, idk. -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/CABQWM_CD0RpC1LTdYOSSM%2BUOnObrSF7Bu7B9T_vtG7jw5qMRNQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
