Thanks for commit access and the information.
Nothing opposed to a fork so lets go with that route to simplify things. The
people whom I will be sharing work with are colleagues so we can share a fork
and keep things separate.
Really appreciate all the help.
> On 1 Dec 2016, at 13.19, Daniel Beck <m...@beckweb.net> wrote:
>> On 01.12.2016, at 12:13, Jacob Larfors <ja...@larfors.com> wrote:
>> Awesome - looks good. Can I also have commit access to this one, or how do
>> we plan to do this?
>> My plan was to create an update branch on this repo and then file a pull
>> request to get this into master and include the Jenkins reviewers as Oleg
>> GitHub user: jlarfors
> Granted you commit access.
> Plan sounds reasonable if it's supposed to be a branch that multiple people
> would work on (or if you're opposed to maintaining your own fork), but most
> probably develop in their own fork first and base PRs on that. It also won't
> confuse the JIRA bot as it thinks everything in the jenkinsci repos is on
> master, and even resolves issues based on that :-)
> You received this message because you are subscribed to a topic in the Google
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> To unsubscribe from this group and all its topics, send an email to
> To view this discussion on the web visit
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.