aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorluigi1111 <luigi1111w@gmail.com>2022-05-10 16:53:48 -0500
committerluigi1111 <luigi1111w@gmail.com>2022-05-10 16:53:48 -0500
commit8480575cec2c6dd9de0660849dfa581657bb6d07 (patch)
tree5b6075aa536700c334c52d1e38c7353728d6948e /docs
parentMerge pull request #8293 (diff)
parentChange "Github" to "GitHub" (diff)
downloadmonero-8480575cec2c6dd9de0660849dfa581657bb6d07.tar.xz
Merge pull request #8300
070e41d Change Github to GitHub (Abdullah)
Diffstat (limited to 'docs')
-rw-r--r--docs/CONTRIBUTING.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
index 14b52a2af..a50114d1a 100644
--- a/docs/CONTRIBUTING.md
+++ b/docs/CONTRIBUTING.md
@@ -12,7 +12,7 @@ of software solid and usable.
* If modifying code for which Doxygen headers exist, that header must be modified to match.
* Tests would be nice to have if you're adding functionality.
-Patches are preferably to be sent via a Github pull request. If that
+Patches are preferably to be sent via a GitHub pull request. If that
can't be done, patches in "git format-patch" format can be sent
(eg, posted to fpaste.org with a long enough timeout and a link
posted to #monero-dev on irc.libera.chat).
@@ -43,7 +43,7 @@ Commit messages should be sensible. That means a subject line that
describes the patch, with an optional longer body that gives details,
documentation, etc.
-When submitting a pull request on Github, make sure your branch is
+When submitting a pull request on GitHub, make sure your branch is
rebased. No merge commits nor stray commits from other people in
your submitted branch, please. You may be asked to rebase if there
are conflicts (even trivially resolvable ones).