How to contribute? (pull requests or non-publishing repo)
Pierre-Yves David
pyd at fb.com
Fri Apr 25 05:31:46 UTC 2014
On 04/24/2014 07:08 PM, Greg Ward wrote:
> Pierre-Yves --
>
> during the PyCon sprints last week, you said the best way to
> contribute is via pull requests. To me, "pull request" pretty much
> implies "immutable published history", at least with the current state
> of bitbucket (and github for that matter). (That's the main reason I
> don't like pull-request workflow, but never mind.)
> But then you rebased the changesets in my pull request and attached
> a funny picture to one of them:
>
> https://urldefense.proofpoint.com/v1/url?u=https://bitbucket.org/gward/mutable-history/commits/52f009c0b806edeae0d50ed9ea9e98f5%23comment-899202&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=%2FK4Ejhuv7bDwZug4J4h9cg%3D%3D%0A&m=8lZUUQGMZYGw0yQamBLXw30Pf2RGofWFBQl18NeM9lg%3D%0A&s=aa9b9f0546d372ab4a3da3f4d1f29c81441ff863abf797406b6023dbd9d65d68
>
> which means I'm going to have to strip those changesets from my
> bitbucket repo. Argh. Annoying.
>
> So which is it? Do you want pull requests *OR* do you want me to
> maintain a public non-publishing repo? Either one is fine by me. But
> taking pull requests and then rebasing the changesets in them is
> annoying.
bitbucket can have non-publishing repo. But you still have to strip
thing. Best is to setup a non-publishing + obsmarker enabled repo
somewhere. Then:
- Patch bomb on mercurial-devel with an evolve-ext flags
- adds a comment explaing where to pull your changes from.
--
Pierre-Yves David
More information about the Evolve-testers
mailing list