Cleanup of contribute

Author: Pierre-Sassoulas

doc/developer_guide/contribute.rst

@@ -6,29 +6,9 @@ Contribute
 Pylint is developed using git_. We recommend using Python 3.8 or higher
 as it gives you access to the latest ``ast`` parser.
 
-You can clone Pylint using ::
+* `Create your own fork`_ of pylint before cloning it.
 
-  git clone https://github.com/PyCQA/pylint
-
-.. _git: https://git-scm.com/
-
-- Document your change, if it is a non-trivial one.
-
-- Send a pull request from GitHub (see `About pull requests`_ for more insight
-  about this topic)
-
-.. _`About pull requests`: https://support.github.com/features/pull-requests
-.. _astroid: https://github.com/pycqa/astroid
-
-
-Getting Started
----------------
-
-* Read the :ref:`technical-reference`. It gives a short walk through of the pylint
-  codebase and will help you identify where you will need to make changes
-  for what you are trying to implement.
-
-* :func:`astroid.extract_node` is your friend. Most checkers are AST based,
+* Read about :func:`astroid.extract_node`. Most checkers are AST based,
   so you will likely need to interact with :mod:`astroid`.
   A short example of how to use :func:`astroid.extract_node` is given
   :ref:`here <astroid_extract_node>`.
@@ -37,18 +17,26 @@ Getting Started
   message to find where the warning is raised,
   and therefore where the logic for that code exists.
 
+* Test your code :ref:`using the documentation <testing>`.
+
 * When adding a new checker class you can use the :file:`get_unused_message_id_category.py`
   script in :file:`./script` to get a message id that is not used by
   any of the other checkers.
 
-Building the documentation
-----------------------------
-
-You can use the makefile in the doc directory with ``make html`` to build the
-documentation. To test smaller changes you can consider ``build-html``, which skips some checks but will be faster::
+* You can use the makefile in the doc directory with ``make html`` to build the documentation.
+  To test smaller changes you can consider ``build-html``, which skips some checks but will
+  be faster::
 
   $ cd doc
   $ make install-dependencies
   $ make build-html
 
 We're reusing generated files for speed, use ``make clean`` when you want to start from scratch.
+
+* Send a pull request from GitHub (see `About pull requests`_ for more insight about this topic)
+
+.. _git: https://git-scm.com/
+.. _`Create your own fork`: https://docs.github.com/en/get-started/quickstart/fork-a-repo
+.. _`About pull requests`: https://support.github.com/features/pull-requests
+.. _astroid: https://github.com/pycqa/astroid
+>>>>>>> Cleanup of contribute