From bbe9b5e76e70e49ffe1a9301862ecdcc64c7df0a Mon Sep 17 00:00:00 2001 From: aBARICHELLO Date: Tue, 9 Oct 2018 13:48:26 -0300 Subject: [PATCH] Add Hacktoberfest label to contribution guide --- community/contributing/ways_to_contribute.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/community/contributing/ways_to_contribute.rst b/community/contributing/ways_to_contribute.rst index 48a89f8a3..5a5b9b384 100644 --- a/community/contributing/ways_to_contribute.rst +++ b/community/contributing/ways_to_contribute.rst @@ -84,7 +84,7 @@ To ensure good collaboration and overall quality, the Godot developers enforce some rules for code contributions, for example regarding the style to use in the C++ code (indentation, brackets, etc.) or the git and PR workflow. -A nice place to start may be the issue tagged as `junior jobs `_ on GitHub. +A good place to start is by searching for issues tagged as `junior jobs `_ (or `Hacktoberfest `_ during October) on GitHub. .. seealso:: Technical details about the PR workflow are outlined in a specific section, :ref:`doc_pr_workflow`. @@ -149,7 +149,7 @@ always provide: - **Hardware.** Sometimes bugs are hardware-specific, i.e. they happen only on certain processors, graphic cards, etc. If you are able to, it can be helpful to include information on your hardware. - + - **Godot version.** This is a must have. Some issues might be relevant in the current stable release, but fixed in the development branch, or the other way around. You might also be using an obsolete version of Godot and