handle branch names in the release actions

Author: paulbkoch

.github/workflows/release_interpret.yml

@@ -14,8 +14,11 @@ jobs:
   publish_packages:
     runs-on: ubuntu-latest
     permissions:
+      contents: read
       id-token: write
     steps:
+      - name: Check out repo
+        uses: actions/checkout@v4
       - name: Set up Python
         uses: actions/setup-python@v5
         with:
@@ -36,6 +39,10 @@ jobs:
             echo "Error: commit_id is empty."
             exit 1
           fi
+          if git show-ref --verify --quiet refs/heads/${commit_id}; then
+            # If it's a valid branch, resolve it to a commit ID
+            commit_id=$(git rev-parse ${commit_id})
+          fi
           echo "Commit ID: ${commit_id}"
           workflow_runs=$(gh api -X GET "/repos/${{ github.repository }}/actions/runs?status=success" -q '.workflow_runs | map(select(.head_commit.id == "'"${commit_id}"'" and .name == "interpret-CI")) | sort_by(.created_at) | reverse | .[0]')
           run_id=$(echo "$workflow_runs" | jq -r '.id')

.github/workflows/release_powerlift.yml

@@ -11,8 +11,11 @@ jobs:
   publish_powerlift:
     runs-on: ubuntu-latest
     permissions:
+      contents: read
       id-token: write
     steps:
+      - name: Check out repo
+        uses: actions/checkout@v4
       - name: Set up Python
         uses: actions/setup-python@v5
         with:
@@ -25,6 +28,10 @@ jobs:
             echo "Error: commit_id is empty."
             exit 1
           fi
+          if git show-ref --verify --quiet refs/heads/${commit_id}; then
+            # If it's a valid branch, resolve it to a commit ID
+            commit_id=$(git rev-parse ${commit_id})
+          fi
           echo "Commit ID: ${commit_id}"
           workflow_runs=$(gh api -X GET "/repos/${{ github.repository }}/actions/runs?status=success" -q '.workflow_runs | map(select(.head_commit.id == "'"${commit_id}"'" and .name == "interpret-CI")) | sort_by(.created_at) | reverse | .[0]')
           run_id=$(echo "$workflow_runs" | jq -r '.id')

docs/benchmarks/ebm-benchmark.ipynb

@@ -122,7 +122,7 @@
    "outputs": [],
    "source": [
     "def trial_runner(trial):\n",
-    "    seed=42\n",
+    "    seed=99\n",
     "    max_interaction_features=1000\n",
     "    ebm_base_params = {}\n",
     "    xgb_base_params = {}\n",

docs/interpret/hyperparameters.md

@@ -118,6 +118,7 @@ guidance: We typically do not advise changing early_stopping_rounds. The default
 
 ## early_stopping_tolerance
 default: 1e-5
+
 hyperparameters: [1e-5, 1e-7, 0.0]
 
 guidance: early_stopping_tolerance is set to 1e-5 because it decreases the fitting time by 25%, however setting early_stopping_tolerance to 0.0, or even a negative value sometimes yields slightly higher accuracy. EBMs are a bagged ensemble model, so overfitting each individual bag a little can be beneficial because after the models are averaged together in the ensemble averaging decreases the variance due to overfitting. Using a negative value for early_stopping_tolerance allows the individual models to be overfit.