diff options
| author | Ivan Kohler <ivan@freeside.biz> | 2017-08-06 10:11:28 -0700 |
|---|---|---|
| committer | Ivan Kohler <ivan@freeside.biz> | 2017-08-06 10:11:28 -0700 |
| commit | de9d037528895f7151a9aead6724ce2df95f9586 (patch) | |
| tree | 3ba47a923a1d6033605ffc5586ed1af439d8c141 /rt/docs/hacking.pod | |
| parent | b226bc6bd81f999176cdbfa53a799033ff0a0307 (diff) | |
rt 4.2.14 (#13852)
Diffstat (limited to 'rt/docs/hacking.pod')
| -rw-r--r-- | rt/docs/hacking.pod | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/rt/docs/hacking.pod b/rt/docs/hacking.pod index 23ce51e3a..e254665e2 100644 --- a/rt/docs/hacking.pod +++ b/rt/docs/hacking.pod @@ -204,6 +204,11 @@ before the fix and succeeds after. =head1 git quickstart +The process below describes how to get a copy of an RT repo, +modify it, and submit your changes as a patch. You can also create +an account on GitHub, fork RT, and submit a PR. GitHub has documentation +on this process: L<https://help.github.com/articles/fork-a-repo/>. + =over =item 1. @@ -299,7 +304,8 @@ This will print out the names of the files as it creates them. =item 9. Attach these files to an email using your standard email client, and -send it to C<rt-devel@bestpractical.com>. +send it to C<rt-bugs@bestpractical.com>. This will create a ticket in +our public RT instance at L<https://issues.bestpractical.com>. =back |