I'm looking at scratch and it's branches off projects, and I'm thinking “Wouldn't it be great if Scratch had pull requests?” It would be that when you have an addition added to your branch, you can start a pull request. Would this be possible/hard to implement?

Maybe you should explain what a pull request is to others, some people may not know ^^

Neutral support.

I think this an interesting idea, it could be an alternative of remixes. However, could you elaborate your suggestion a little bit more? I'm thinking of a dropdown with two buttons: one saying “remix” and another one saying “pull request”. Would the owner of the original project have the option to merge the pull request?
I also think that the majority of scratchers probably wouldn't tell the difference between a remix and a pull request, or wouldn't even understand what a pull request means and what “merge” would do. So I'd rather stick to the current remixing system.
It's not that hard to simulate a pull request anyways. Person A makes a remix, person B approves, person B downloads person A's remix, then uploads it to the original project.
I do like the idea of pull requests on Scratch, though.

I know that this is sort of a necropost, but I was going to make this and I found this as a duplicate. I think that this sounds like a great idea, maybe some sort of better naming system though as not everyone would know what a ‘Pull request’ is. I think that this should work through remixing. Maybe a button for you on a remix? Either way, total support!

bump

(thiz izn't git)

Semi-support. This could potentially introduce kids to Git but it seems a little bit too heavy to understand.

edit: omg I hate bmp

I believe it'd be too much of a stretch to go and do a Github.
I doubt a PR would be understandable to an 8 year old - How about titling it “Mix”, “fuse”, or something a lot simpler?

Bump.

how beneficial is this?
the idea of scratch is mainly to encourage remixing, although i guess this kind of concept would kill the need for collaboration accounts
but then this would involve a concept similar to git, which causes the project to spiral out of control (referring to spiral development)
i think we need to manage scope here but you're suggesting a pretty complex feature

Banana

It looks like this is a duplicate topic of this one over here so I'll close it to keep the conversation all in one place.

Please use the existing topic in the link above.