@@ -10,7 +10,6 @@ the developers managing and developing this open source project. In return,
10
10
they should reciprocate that respect in addressing your issue or assessing
11
11
patches and features.
12
12
13
-
14
13
## Using the issue tracker
15
14
16
15
The [ issue tracker] ( https://github.com/nicolargo/glances/issues ) is
@@ -24,7 +23,6 @@ restrictions:
24
23
* Please ** do not** derail or troll issues. Keep the discussion on topic and
25
24
respect the opinions of others.
26
25
27
-
28
26
## Bug reports
29
27
30
28
A bug is a _ demonstrable problem_ that is caused by the code in the repository.
@@ -65,19 +63,17 @@ Example:
65
63
> causing the bug, and potential solutions (and your opinions on their
66
64
> merits).
67
65
>
68
- > You can also run Glances in debug mode (-d) and paste/bin the glances.conf file (https://glances.readthedocs.io/en/latest/config.html ).
66
+ > You can also run Glances in debug mode (-d) and paste/bin the glances.conf file (< https://glances.readthedocs.io/en/latest/config.html > ).
69
67
>
70
68
> Glances 3.2.0 or higher have also a --issue option to run a simple test. Please use it and copy/paste the output.
71
69
72
-
73
70
## Feature requests
74
71
75
72
Feature requests are welcome. But take a moment to find out whether your idea
76
- fits with the scope and aims of the project. It's up to * you * to make a strong
73
+ fits with the scope and aims of the project. It's up to _ you * to make a strong
77
74
case to convince the project's developers of the merits of this feature. Please
78
75
provide as much detail and context as possible.
79
76
80
-
81
77
## Pull requests
82
78
83
79
Good pull requests—patches, improvements, new features—are a fantastic
@@ -133,6 +129,7 @@ included in the project:
133
129
134
130
5 . Test you code using the Makefile:
135
131
132
+ * make format ==> Format your code thanks to the Ruff linter
136
133
* make run ==> Run Glances
137
134
* make run-webserver ==> Run a Glances Web Server
138
135
* make test ==> Run unit tests
0 commit comments