Hi Jesse, Thanks for the help.
I have merged latest change from jenkinsci/jenkins to my fork and pushed it up to my fork. Is the build going to be triggered automatically now or do I have to do something? On Thursday, 9 January 2014 18:54:33 UTC, Jesse Glick wrote: > > On Thu, Jan 9, 2014 at 1:39 PM, Hangsu Ma <[email protected] <javascript:>> > wrote: > > Do you have a document for the steps? i am not familiar with Jenkins > build process. > > This is more about using GitHub generally. > > > I tried to push the change into a new remote branch on > jenkinsci/jenkins, > > that gives me 403 > > Of course, you can only push into your own fork. > > > What do you mean by feature branch? > > Normally to file a pull request you would use a different branch, not > master: > > git checkout master > git pull > git checkout -b my-change-JENKINS-12345 > # edit… > git commit -a -m '[FIXED JENKINS-12345] …' > git push --set-upstream myfork my-change-JENKINS-12345 > > which ensures that your changes are clearly differentiated from > changes in the master branch, and also that you can file multiple PRs > out of the same fork. > > Since you seem to have filed your PR directly from the master branch, > if you want to merge with the upstream master you can use > > git pull > git push myfork > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
