/scalate-website/src/_creating_patches.ssp.md

http://github.com/scalate/scalate · Markdown · 22 lines · 14 code · 8 blank · 0 comment · 0 complexity · 26750c0d10fdad86090752225772fe4f MD5 · raw file 

    

  1. ### New to GitHub?
    2. 

  2. 

  3. We track patches by using GitHub.  GitHub makes it easy to fork the project, and for the project team to monitor the progress of those forks and easily merge those forks back into the mainline.  To get started with GitHub:
    4. 

  4.  
    5. 

  5. * You will need a [SSH key](http://help.github.com/key-setup-redirect) to push you changes to GitHub
    6. 

  6. * Then [create a GitHub account](https://github.com/signup/free)
    7. 

  7. * Then [configure git so that commits are linked to your GitHub account](http://help.github.com/git-email-settings)
    8. 

  8. 

  9. ### Already a GitHub User?
    10. 

  10. 

  11. * go to the [${project_name} github page](${github_page}) and follow the [Forking Guide](http://help.github.com/forking/) to
    12. 

  12.   get your own copy of the project.
    13. 

  13. * hack your copy as much as you like, pushing your local changes back to your git repo on github.
    14. 

  14. 

  15. Once your happy with your changes, notify us that that your want your changes merged back:
    16. 

  16. 

  17. * click on the pull request button the [${project_name} github page](${github_page}) to let us know you've a patch you'd like to contribute.
    18. 

  18. * you may want to [create a new Issue in the Issue Tracker](${project_issue_url})
    19. 

  19. * fire off an email to the [Community](community.html) linking to the issue
    20. 

  20. 

  21. When a ticket is created in JIRA it automatically sends an email to the [commit mailing list](community.html) but an email always helps alert folks (as lots of emails are generated from every change to every JIRA).
    22.