•  
     
    story #1501 Clearly document the patch submission
Summary
a Gerrit noob
Clearly document the patch submission
I can submit a patch very easily and without errors
= initial submission of patch =
Given I'm visualizing the gerrit repo "mobile" in project "Firefox"
And the gerrit host is gerrit.tuleap.net
Then a section "In order to submit a patch to the master branch: 'git push gerrit.tuleap.net:Firefox-mobile refs/for/master'"


= submit a patch Update =
Given I'm visualizing the gerrit repo "mobile" in project "Firefox"
And the gerrit host is gerrit.tuleap.net
Then a section "In order to submit an update to a patch, you have to include a changeset Id in your commit message. You can either add a commit hook <URL for further instructions>. Or look up the changeset id that can be found on every changeset in Gerrit <url to gerrit>"
Empty
Empty
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#1501
Johan Martinsson (johan)
2013-07-10 09:36
2012-09-24 18:02
744

References
Referencing story #1501

Follow-ups

User avatar
Should have been done. I close.

  • Status changed from On going to Done
  • Permissions set to all_users
  • Category set to
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Status changed from Ready (stalled) to On going
  • Checklist set to