By policy, most repositories are set up
so it takes special action or web master assistance to create a new "permeant"
branch ... BUT, any committer can create a new "topic branch"
... the format of the name just needs to be committerId/topic ... so, perhaps
"nick/develop" will work for you? (The reason for this is that
"permeant branches" should never be deleted, hence it is made
"harder" to create them ... whereas if you create a topic branch
with your committer ID as part of the name, then the system will not only
allow you to create it, but you can delete it later).
discussions for paho project <paho-dev@xxxxxxxxxxx>,
02/01/2014 09:05 AM
a new branch in git
project to get back to the point where the .js file in git can actually
be used without running it through a maven build. This involved adding
a very small wrapper for the node-based tests to use so the client can
still use the browser-specific apis.
so we have a -min.js version (30Kb) as well as the original one (76kb).
I wanted to push this to a new branch (nick-develop) so
that anyone with an interest could have a look to make sure we're happy
for it to go into the main develop branch. However, when I try to push
the new branch, I'm told I don't have the right permissions:
error: insufficient permission for adding
an object to repository database ./objects
Does creating a new branch really need more permissions
than I have as a committer? If so, what is the expected work flow
for this sort of thing? (I suspect I'm too used to the github work flow
where this is second nature...)