The next thing to do is to create a pull request to the original instance of the plugin. Just go to your repo and click on the "Compare, review, create a pull request" green button. After that you will be able to select a destination and to create a pull request.
2015-08-31 8:17 GMT+03:00 Thilina Madhusanka <[email protected]>: > Hi > > im new to git hub > > i have forked zaproxy plugin and commit changes to the git repo that i > have forked [1] > > this added ajax spider > > can you please guide me through this. > > Thanks. > > > [1] - https://github.com/thilina27/zaproxy-plugin.git > > On Monday, August 31, 2015 at 8:55:58 AM UTC+5:30, Thilina Madhusanka > wrote: >> >> Hi >> >> Thanks for the info ill do them. >> >> This additional methods need to be complete and this methods are work >> properly in the newest weekly release of the zap. >> >> Some ZAP methods are also fixed in the source code after the weekly >> release so this will work best on the source build of the ZAP. >> >> Im new to these things sorry if any thing im doing not right. >> >> Thanks. >> >> On Sunday, August 30, 2015 at 3:21:44 PM UTC+5:30, Oleg Nenashev wrote: >>> >>> Yes, we cannot do anything if you don't provide links to the code to be >>> reviewed >>> >>> пятница, 28 августа 2015 г., 14:12:23 UTC+3 пользователь Richard Bywater >>> написал: >>>> >>>> Unfortunately I'm not the right person to do it but the best bet might >>>> be to raise a Work In Progress Pull Request in GitHub so people can see and >>>> comment on what you've done. >>>> >>>> Richard. >>>> >>>> On Fri, 28 Aug 2015 at 22:38 Thilina Madhusanka <[email protected]> >>>> wrote: >>>> >>>>> Hi >>>>> >>>>> I have modified the ZAProxy [1] plugin to use both authentication and >>>>> Ajaxspider . >>>>> >>>>> Need help to finalize things. >>>>> testing of usability >>>>> changing input configuration in jenkins. >>>>> >>>>> thanks. >>>>> >>>>> [1] - https://wiki.jenkins-ci.org/display/JENKINS/ZAProxy+Plugin >>>>> <https://wiki.jenkins-ci.org/display/JENKINS/ZAProxy+Plugin> >>>>> >>>>> -- >>>>> 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]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/dde8fd2f-1d9d-4868-9c0a-f045b97cfb26%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/dde8fd2f-1d9d-4868-9c0a-f045b97cfb26%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/ZBw-zrdSaCc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/86f7878d-f1b5-48dc-8645-8c66ba3f0813%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/86f7878d-f1b5-48dc-8645-8c66ba3f0813%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDF0ARqMGkaQL_G7mYfMYoN9C4LaKNZapG0-BVyHJomRg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
