In Stash, how is it possible to cherry pick a change onto a branch that the developer doesn't have direct write access to?

[Michael Hanna]

In our configuration, we have:

master ----> (read access)
    develop ----> (read access)
         support/1.0.x ----> (read, write access)

the developer creates a remote off of support/1.0.x and when they are complete does a pull request. However, the change will need to be propagated to develop, where they don't have write access. Before we adopted Stash, they would simply cherry pick onto develop. However, since they don't have write access to develop, how can they propagate the change to develop without making a new pull request?

[Balázs Szakmáry · Accepted solution]

With or without a pull request, the person who propagates the change to develop needs to have write access to that branch. There is (by design) no trick that would allow a user who does not have write access to a branch to get changes into that branch.

You can either restrict write access to a certain group of people by setting the appropiate branch permissions or you can enable write access to all the users. (Depends on how many people you have and how much you trust them.)

[Deleted user]

With or without a pull request, the person who propagates the change to develop needs to have write access to that branch. There is (by design) no trick that would allow a user who does not have write access to a branch to get changes into that branch.

You can either restrict write access to a certain group of people by setting the appropiate branch permissions or you can enable write access to all the users. (Depends on how many people you have and how much you trust them.)