docs(contributing): update scopes

CONTRIBUTING.md

 # Contributing
 
-We would love for you to contribute to the backoffice of [Code du travail
-numérique][link-cdtn] and help make it even better than it is today! As a
-contributor, here are the guidelines we would like you to follow:
+We would love for you to contribute to the backoffice of [Code du travail numérique][link-cdtn] and
+help make it even better than it is today! As a contributor, here are the guidelines we would like
+you to follow:
 
 - [Contributing](#contributing)
   - [Code Naming Guidelines](#code-naming-guidelines)
@@ -18,14 +18,12 @@ contributor, here are the guidelines we would like you to follow:
 
 ### API-related Actions
 
-This includes react components methods as well as redux actions, action types
-and sagas:
+This includes react components methods as well as redux actions, action types and sagas:
 
 - Any `GET` call-related method should start with the verb **load**.
 - Any `POST` call-related method should start with the verb **create**.
 - Any `PATCH` call-related method should start with the verb **update**.
-- Any `DELETE` call-related method should start with the verb **delete** (or
-  **\_delete**).
+- Any `DELETE` call-related method should start with the verb **delete** (or **\_delete**).
 
 ### React Component Actions
 
@@ -41,8 +39,8 @@ Each commit message consists of a **type**, a **scope** and a **subject**:
 
 The **type** is mandatory and the **scope** of the header is optional.
 
-Any line of the commit message cannot be longer 100 characters! This allows the
-message to be easier to read on GitHub as well as in various git tools.
+Any line of the commit message cannot be longer 100 characters! This allows the message to be easier
+to read on GitHub as well as in various git tools.
 
 **Examples:**
 
@@ -50,22 +48,20 @@ message to be easier to read on GitHub as well as in various git tools.
 - `fix(release): need to depend on latest rxjs and zone.js`
 - `ci: configure dependabot`
 
-Do not hesitate check [existing commits][link-cdtb-commits] to get a better
-understanding.
+Do not hesitate check [existing commits][link-cdtb-commits] to get a better understanding.
 
 ### Revert
 
-If the commit reverts a previous commit, it should begin with `revert:`,
-followed by the header of the reverted commit. In the body it should say:
-`This reverts commit <hash>.`, where the hash is the SHA of the commit being
-reverted.
+If the commit reverts a previous commit, it should begin with `revert:`, followed by the header of
+the reverted commit. In the body it should say: `This reverts commit <hash>.`, where the hash is the
+SHA of the commit being reverted.
 
 ### Type
 
 Must be one of the following:
 
 - **build**: Changes that affect the build system or external dependencies.
-- **chore**: Changes to our CI configuration files and scripts.
+- **chore**: Updates and upgrades.
 - **ci**: Changes to our CI configuration files and scripts.
 - **docs**: Documentation only changes.
 - **feat**: A new feature.
@@ -77,25 +73,26 @@ Must be one of the following:
 
 ### Scope
 
-The scope should be the name of the npm package affected (as perceived by the
-person reading the changelog generated from commit messages.
+The scope should be the name of the npm package affected (as perceived by the person reading the
+changelog generated from commit messages.
 
 The following is the list of supported scopes:
 
 - **api**
+- **db**
 - **admin**
 - **contrib**
+- **data-filler**
 
 There are currently a few exceptions to the "use package name" rule:
 
-- **packaging**: Used for changes that change the npm package layout in all of
-  our packages, e.g. public path changes, package.json changes done to all
-  packages, d.ts file/format changes, changes to bundles, etc.
+- **packaging**: Used for changes that change the npm package layout in all of our packages, e.g.
+  public path changes, package.json changes done to all packages, d.ts file/format changes, changes
+  to bundles, etc.
 - **changelog**: Used for updating the release notes in CHANGELOG.md
-- none/empty string: useful for `style`, `test` and `refactor` changes that are
-  done across all packages (e.g. `style: add missing semicolons`) and for docs
-  changes that are not related to a specific package (e.g.
-  `docs: fix typo in tutorial`).
+- none/empty string: useful for `style`, `test` and `refactor` changes that are done across all
+  packages (e.g. `style: add missing semicolons`) and for docs changes that are not related to a
+  specific package (e.g. `docs: fix typo in tutorial`).
 
 ### Subject
 
@@ -107,6 +104,5 @@ The subject contains a succinct description of the change:
 
 ---
 
-[link-cdtb-commits]:
-  https://github.com/SocialGouv/code-du-travail-backoffice/commits/master
+[link-cdtb-commits]: https://github.com/SocialGouv/code-du-travail-backoffice/commits/master
 [link-cdtn]: https://codedutravail.num.social.gouv.fr