automl
diff --git a/‎.github/stale.yml
Lines changed: 1 addition & 1 deletion b/‎.github/stale.yml
Lines changed: 1 addition & 1 deletion
diff --git a/‎.github/workflows/pre-commit-update.yml
Lines changed: 30 additions & 0 deletions b/‎.github/workflows/pre-commit-update.yml
Lines changed: 30 additions & 0 deletions
diff --git a/‎.github/workflows/stale_reminder.yml
Lines changed: 61 additions & 0 deletions b/‎.github/workflows/stale_reminder.yml
Lines changed: 61 additions & 0 deletions
diff --git a/‎.pre-commit-config.yaml
Lines changed: 3 additions & 3 deletions b/‎.pre-commit-config.yaml
Lines changed: 3 additions & 3 deletions
diff --git a/‎CHANGELOG.md
Lines changed: 22 additions & 2 deletions b/‎CHANGELOG.md
Lines changed: 22 additions & 2 deletions
diff --git a/‎CONTRIBUTING.md
Lines changed: 18 additions & 0 deletions b/‎CONTRIBUTING.md
Lines changed: 18 additions & 0 deletions
diff --git a/‎Makefile
Lines changed: 7 additions & 3 deletions b/‎Makefile
Lines changed: 7 additions & 3 deletions
diff --git a/‎README.md
Lines changed: 12 additions & 3 deletions b/‎README.md
Lines changed: 12 additions & 3 deletions
@@ -2,7 +2,7 @@
 daysUntilStale: 60
 
 # Number of days of inactivity before a stale issue is closed
-daysUntilClose: 7
+daysUntilClose: 14
 
 # Issues with these labels will never be considered stale
 exemptLabels:
 
@@ -0,0 +1,30 @@
+name: Pre-commit auto-update
+
+on:
+  # every Monday at 1pm utc
+  schedule:
+    - cron: "0 13 * * 1"
+  # on demand
+  workflow_dispatch:
+
+jobs:
+  auto-update:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+
+      - uses: actions/setup-python@v2
+
+      - uses: browniebroke/pre-commit-autoupdate-action@main
+                 
+      - name: Run updated pre-commit
+        run: |
+            pre-commit run --all-files
+
+      - uses: peter-evans/create-pull-request@v3
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          branch: update/pre-commit-hooks
+          title: Update pre-commit hooks
+          commit-message: "chore: update pre-commit hooks"
+          body: Update versions of pre-commit hooks to latest version.
@@ -0,0 +1,61 @@
+name: Stale-Reminder
+
+on:
+  schedule:
+    - cron: '42 14 * * 3'
+  workflow_dispatch:
+
+jobs:
+  stale-reminder:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Get cutoff date for soon-to-be-stale issues
+      id: date
+      run: |
+        echo "CUTOFF_DATE=$(date -d '-46 days' '+%Y-%m-%d')" >> $GITHUB_ENV
+    - name: Collect issues that may become stale
+      id: stale
+      uses: lee-dohm/select-matching-issues@v1
+      with:
+          format: list
+          path: "potentially_stale_issues.md"
+          token: ${{ github.token }}
+          query: >-
+            is:open
+            -label:dependency,documentation,feature,enhancement,bug,test,example
+            updated:<${{ env.CUTOFF_DATE }}
+            sort:updated-asc
+    - name: Collect labelled issues that have not had interaction in a long time (but will not become stale)
+      id: old
+      uses: lee-dohm/select-matching-issues@v1
+      with:
+          format: list
+          path: "old_issues.md"
+          token: ${{ github.token }}
+          query: >-
+            is:open
+            label:dependency,documentation,feature,enhancement,bug,test,example
+            updated:<${{ env.CUTOFF_DATE }}
+            sort:updated-asc
+    - name: Combine issues into mail content
+      id: combine
+      run: |
+        echo $date
+        echo "## Issues that may become stale in <= 14 days <br />" >> mail.html
+        echo "$(<potentially_stale_issues.md) <br />" >> mail.html
+        echo "## Issues that have not had interaction in the last 46 days but will not go stale due to their labels<br />" >> mail.html
+        echo "$(<old_issues.md) <br />" >> mail.html
+    - name: Send mail
+      id: mail
+      uses: dawidd6/action-send-mail@v3
+      with:
+        server_address: ${{secrets.MAIL_SERVER_ADDRESS}}
+        server_port: ${{secrets.MAIL_SERVER_PORT}}
+        secure: true
+        username: ${{secrets.MAIL_USERNAME}}
+        password: ${{secrets.MAIL_PASSWORD}}
+        subject: '[Stale Issues]  Issues with last interaction before ${{ env.CUTOFF_DATE }}'
+        to: ${{secrets.MAIL_TARGET}}
+        from: SMAC3 Stale-Bot <${{secrets.MAIL_ADDRESS}}>
+        html_body: file://mail.html
+        convert_markdown: true
@@ -3,8 +3,8 @@
 # If things break on update, raise an issue
 
 repos:
-  - repo: https://github.com/pycqa/isort
-    rev: 5.10.1
+  - repo: https://github.com/PyCQA/isort
+    rev: 5.12.0
     hooks:
       - id: isort
         name: isort smac
@@ -37,7 +37,7 @@ repos:
         exclude: "scripts|tests"
 
   - repo: https://github.com/PyCQA/flake8
-    rev: 5.0.4
+    rev: 6.0.0
     hooks:
       - id: flake8
         name: flake8 smac
 
@@ -1,13 +1,33 @@
+# 2.0.0
+
+## Improvements
+- Clarify origin of configurations (#908).
+- Random forest with instances predicts the marginalized costs by using a C++ implementation in `pyrfr`, which is much faster (#903).
+- Add version to makefile to install correct test release version
+
+## Bugfixes
+- Continue run when setting incumbent selection to highest budget when using Successive Halving (#907).
+- If integer features are used, they are automatically converted to strings.
+
+## Workflows
+- Added workflow to update pre-commit versions (#874).
+
+## Misc
+- Added benchmarking procedure to compare to previous releases.
+
+
 # 2.0.0b1
 
-- Completely reimplemented the intensifiers (including Successive Halving and Hyperband): All intensifiers support 
-multi-fidelity, multi-objective and multi-threading by nature now.
+- Completely reimplemented the intensifiers (including Successive Halving and Hyperband): All intensifiers support multi-fidelity, multi-objective and multi-threading by nature now.
 - Expected behaviour for ask-and-tell interface ensured (also for Successive Halving).
 - Continuing a run is now fully supported.
 - Added more examples.
 - Updated documentation based on new implementation.
 - Added benchmark to compare different versions.
 
+## Bugfixes
+- Correct handling of integer hyperparameters in the initial design (#531)
+
 
 # 2.0.0a2
 
 
@@ -53,9 +53,27 @@ If you know how to fix a bug or implement your own feature, follow this small gu
 - Pull request must include tests.
 - We are using the Numpy Style Python Docstrings. Take a look at this [example](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_numpy.html#example-numpy). 
 - The code should follow the PEP8 coding convention.
+- Check that the copyright notice of all files that have been significantly changed includes the current year.
 
 We try to react as fast as possible to your pull request.
 
+## Git-Flow Workflow and Branch-Naming
+
+We aim to approximately follow the [Git-Flow Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow). 
+Thus, the following conventions apply:
+
+Branches are named as follows:
+- `main` The main branch, containing the latest stable release (tagged)
+- `development` The development branch, for merging features and bugfixes in-between releases
+- `release/<version>` Release branches for *preparing* a new release (no new features developed here), 
+   deleted after release
+- `feature/<feature-name>` Feature branches for implementing new functionality, updating existing functionality 
+   or fixing bugs on the development branch
+- `hotfix/<bug-name>` Hotfix branches for fixing bugs in the latest release
+- `support/<version>` Support branches for bugfixes in older releases (e.g., `support/v0.12.x`). New 'old' versions are
+   tagged here.
+- `gh-pages` The branch for the GitHub pages
+
 ## Reporting Security Issues
 
 If you find security related issues, vulnerabilities or bugs including sensitive information, please do *not* report this to the issue tracker, or elsewhere public. Instead, please let us know via [email protected]
@@ -1,8 +1,11 @@
 # These have been configured to only really run short tasks. Longer form tasks
 # are usually completed in github actions.
 
+SHELL := /bin/bash
+
 NAME := SMAC3
 PACKAGE_NAME := smac
+VERSION := 2.0.0
 
 DIR := "${CURDIR}"
 SOURCE_DIR := ${PACKAGE_NAME}
@@ -133,15 +136,16 @@ clean-data:
 # Will echo the commands to actually publish to be run to publish to actual PyPi
 # This is done to prevent accidental publishing but provide the same conveniences
 publish: clean build
-	read -p "Did you update the version number? Did you add the old version to docs/conf.py?"
+	read -p "Did you update the version number in Makefile, smac/__init__.py, benchmark/src/wrappers/v20.py? \
+	Did you add the old version to docs/conf.py? Did you add changes to CHANGELOG.md?"
 
 	$(PIP) install twine
 	$(PYTHON) -m twine upload --repository testpypi ${DIST}/*
 	@echo
 	@echo "Test with the following:"
-	@echo "* Create a new virtual environment to install the uplaoded distribution into"
+	@echo "* Create a new virtual environment to install the uploaded distribution into"
 	@echo "* Run the following:"
-	@echo "--- pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ ${NAME}"
+	@echo "--- pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ ${PACKAGE_NAME}==${VERSION}"
 	@echo
 	@echo "* Run this to make sure it can import correctly, plus whatever else you'd like to test:"
 	@echo "--- python -c 'import ${PACKAGE_NAME}'"
 
@@ -8,9 +8,9 @@ Status](https://codecov.io/gh/automl/SMAC3/branch/master/graph/badge.svg)](https
 
 <img src="docs/images/logo.png" style="width: 50%;" />
 
-SMAC is a tool for algorithm configuration to optimize the parameters of arbitrary algorithms, including hyperparameter 
-optimization of Machine Learning algorithms. The main core consists of Bayesian Optimization in combination with an 
-aggressive racing mechanism to efficiently decide which of two configurations performs better.
+SMAC offers a robust and flexible framework for Bayesian Optimization to support users in determining well-performing 
+hyperparameter configurations for their (Machine Learning) algorithms, datasets and applications at hand. The main core 
+consists of Bayesian Optimization in combination with an aggressive racing mechanism to efficiently decide which of two configurations performs better.
 
 SMAC3 is written in Python3 and continuously tested with Python 3.8, 3.9, and 3.10. Its Random
 Forest is written in C++. In further texts, SMAC is representatively mentioned for SMAC3.
@@ -96,6 +96,10 @@ incumbent = smac.optimize()
 
 More examples can be found in the [documentation](https://automl.github.io/SMAC3/main/examples/).
 
+## Visualization via DeepCAVE
+
+With DeepCAVE ([Repo](https://github.com/automl/DeepCAVE), [Paper](https://arxiv.org/abs/2206.03493)) you can visualize your SMAC runs. It is a visualization and analysis tool for AutoML (especially for the sub-problem
+hyperparameter optimization) runs.
 
 ## License
 
@@ -110,6 +114,11 @@ You should have received a copy of the 3-clause BSD license
 along with this program (see LICENSE file).
 If not, see [here](https://opensource.org/licenses/BSD-3-Clause).
 
+## Contacting us
+
+If you have trouble using SMAC, a concrete question or found a bug, please create an [issue](https://github.com/automl/SMAC3/issues). This is the easiest way to communicate about these things with us. 
+
+For all other inquiries, please write an email to smac[at]ai[dot]uni[dash]hannover[dot]de.
 
 ## Miscellaneous