summaryrefslogtreecommitdiff
path: root/rt/docs/hacking.pod
diff options
context:
space:
mode:
authorIvan Kohler <ivan@freeside.biz>2017-08-25 15:06:19 -0700
committerIvan Kohler <ivan@freeside.biz>2017-08-25 15:06:19 -0700
commitcbfeb5f6b7490f78361318ce6290bfb442dbfcbe (patch)
treee6409692bc2376649eeda94344f0a7f578a75428 /rt/docs/hacking.pod
parent8ffd7de981603a189cd0ea62ca948eaf3f66ca49 (diff)
parent5b5eb87bf66f1fac003a13dc2db48e8970c5c986 (diff)
Merge branch 'master' of git.freeside.biz:/home/git/freeside
Diffstat (limited to 'rt/docs/hacking.pod')
-rw-r--r--rt/docs/hacking.pod8
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