Merge pull request #24 from c-hydro/dev

Dev

.gitignore

@@ -0,0 +1,48 @@
+# The gitignore file lists files (and folders) that should be ignored by git.
+# Best practice is to ignore:
+## Generated Files (created in the build process, e.g. .pyc files)
+## Sensitive Information (passwords or API keys, e.g. .config, .env files)
+## User-Specific Files (including outputs of logs used for debugging)
+## Build Artifacts and Output (also results of running your code, e.g. /bin, /build folders)
+## Third-Party Libraries and Dependencies (including virtual environmen foldes such as /.venv or similar, DO commit a file that lists the dependencies, such as a requirements.txt)
+
+# TEMPLATES FOR .GITIGNORE FILES: https://github.com/github/gitignore
+
+# Example of a gitignore file for python projects
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# Environments
+.env*
+.venv*
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# IDEs and editors
+.vscode
+.idea

CHANGELOG.rst

@@ -1,6 +1,18 @@
 =========
 Changelog
 =========
+Version 4.0.0 [2024-07-31]
+**************************
+APP: **bulletin_hydro_fp-evr.py**
+    - Implemented a new approach for IBF with FloodPROOFS, based on pre-computed impacts at the MUL level
+
+Version 3.0.0 [2024-05-17]
+**************************
+APP: **bulletin_hydro_glofas.py**
+    - Update to GLOFAS 4.0
+
+APP: **bulletin_hydro_glofas_v3.py**
+    - Renamed for retrocompatibility
 
 Version 2.0.2 [2024-01-09]
 **************************

CODEOWNERS

@@ -0,0 +1,7 @@
+# Use the CODEOWNERS file to assign individual users as responsible for specific parts of the repository code.
+# example of CODEOWNERS file and more info can be found here:
+## https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#example-of-a-codeowners-file
+
+# You probably should assign yourself (i.e. the manager), as well as your co-manager(s) as owner(s) of the entire repository (uncomment below):
+# * @your-github-handle @other-ghithub-handle
+* @AndreaLibe