You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
## Hello! We are pleased to see you here 👋
2
2
3
3
Please read
4
-
common [CONTRIBUTING.md](https://github.com/green-code-initiative/ecoCode-common/blob/main/doc/CONTRIBUTING.md)
5
-
in `ecoCode-common` repository first.\
6
-
Also check the [starter pack](https://github.com/green-code-initiative/ecoCode-common/blob/main/doc/starter-pack.md) to
4
+
common [CONTRIBUTING.md](https://github.com/green-code-initiative/creedengo-common/blob/main/doc/CONTRIBUTING.md)
5
+
in `creedengo-common` repository first.\
6
+
Also check the [starter pack](https://github.com/green-code-initiative/creedengo-common/blob/main/doc/starter-pack.md) to
7
7
have the basic information before starting.
8
8
9
9
## Structure
@@ -49,9 +49,9 @@ But it can be useful to prepare a test project to check the correct execution of
49
49
50
50
### Before starting
51
51
52
-
Before even starting to implement the rule, it must have been discussed, mesured and documented in the ecoCode
52
+
Before even starting to implement the rule, it must have been discussed, mesured and documented in the Creedengo
53
53
referential. Please follow
54
-
the [dedicated documentation](https://github.com/green-code-initiative/ecoCode/blob/main/ecocode-rules-specifications/README.md)
54
+
the [dedicated documentation](https://github.com/green-code-initiative/creedengo-rules-specifications/blob/main/README.md#creedengo-rules-specification-repository)
55
55
to find out how to proceed.
56
56
57
57
### In the ESLint plugin
@@ -74,11 +74,11 @@ The project itself uses ESLint to helps linting rule algorithms.
74
74
75
75
### In the SonarQube plugin
76
76
77
-
Now that the rule has been implemented in the ecoCode referential and its implementation written in the ESLint plugin,
77
+
Now that the rule has been implemented in the Creedengo referential and its implementation written in the ESLint plugin,
78
78
all that remains is to reference it in the SonarQube plugin. Here are the simple steps:
79
79
80
-
1. Create a Java class in `src/main/java/io/ecocode/javascript/checks/` with the declaration of the SonarQube key and
81
-
the ESLint key (check other classes to have an example)
80
+
1. Create a Java class in `src/main/java/fr/greencodeinitiative/creedengo/javascript/checks/` with
81
+
the declaration of the SonarQube key and the ESLint key (check other classes to have an example)
82
82
2. Reference created in method `getAllChecks()` of Java class `CheckList` (please use alphabetical order)
83
83
3. Add the SonarQube key of the rule in the appropriate profile Json file.
Websites are becoming increasingly heavy and complex over the years. They represent an important part
4
-
of the digital environmental footprint. The objective of this project is to detect smells in a website source code
5
-
that can have a negative ecological impact: overconsumption of energy, "fatware", shortening of the life span of
6
-
devices, etc. This project is part of [ecoCode](https://github.com/green-code-initiative/ecoCode).
3
+
_creedengo_ is a collective project aiming to reduce environmental footprint of software at the code level. The goal of the project is to provide a list of static code analyzers to highlight code structures that may have a negative ecological impact: energy and resources over-consumption, "fatware", shortening terminals' lifespan, etc.
7
4
8
-
Rules in this repository are mainly based from book
9
-
[115 Web Ecodesign Best Practices](https://github.com/cnumr/best-practices).
10
-
This reference is maintained by [CNumR](https://collectif.greenit.fr/), a french collective that works
11
-
for a responsible design of digital services. You can find all applicable rules in the [RULES.md file](RULES.md).
5
+
Websites are becoming increasingly heavy and complex over the years. They represent an important part
6
+
of the digital environmental footprint. The JavaScript/TypeScript part of the project focuses on providing rules and guidelines to optimize web applications and server-side code written in JavaScript and TypeScript.
0 commit comments