Skip to content

Actions: JuliaSurv/NetSurvival.jl

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
952 workflow runs
952 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

up
.github/workflows/Benchmark.yml #5: Commit aa70de3 pushed by lrnv
April 4, 2024 17:21 1m 39s main
April 4, 2024 17:21 1m 39s
pages build and deployment
pages-build-deployment #7: by lrnv
April 4, 2024 17:17 57s gh-pages
April 4, 2024 17:17 57s
pages build and deployment
pages-build-deployment #6: by github-pages bot
April 4, 2024 17:15 55s gh-pages
April 4, 2024 17:15 55s
up file name
CI #20: Commit 07ec05d pushed by lrnv
April 4, 2024 17:12 5m 57s main
April 4, 2024 17:12 5m 57s
up file name
.github/workflows/Benchmark.yml #4: Commit 07ec05d pushed by lrnv
April 4, 2024 17:12 3m 36s main
April 4, 2024 17:12 3m 36s
up action
CI #19: Commit bc550d1 pushed by lrnv
April 4, 2024 17:07 10s main
April 4, 2024 17:07 10s
up action
.github/workflows/Benchmark.yml #3: Commit bc550d1 pushed by lrnv
April 4, 2024 17:07 3m 35s main
April 4, 2024 17:07 3m 35s
add NetSurvival to benchmark project.toml
.github/workflows/Benchmark.yml #2: Commit dfb6b9d pushed by lrnv
April 4, 2024 17:04 32s main
April 4, 2024 17:04 32s
add NetSurvival to benchmark project.toml
CI #18: Commit dfb6b9d pushed by lrnv
April 4, 2024 17:04 4m 8s main
April 4, 2024 17:04 4m 8s
wrong branch name
.github/workflows/Benchmark.yml #1: Commit 0650f57 pushed by lrnv
April 4, 2024 17:02 54s main
April 4, 2024 17:02 54s
wrong branch name
CI #17: Commit 0650f57 pushed by lrnv
April 4, 2024 17:02 2m 31s main
April 4, 2024 17:02 2m 31s
Add a small benchmark
CI #16: Commit f7ed4e5 pushed by lrnv
April 4, 2024 17:00 2m 14s main
April 4, 2024 17:00 2m 14s
Flexibility of ratetables predictors
TagBot #7: Issue comment #2 (comment) created by lrnv
April 4, 2024 14:07 3s
April 4, 2024 14:07 3s
Flexibility of ratetables predictors
TagBot #6: Issue comment #2 (comment) created by lrnv
April 4, 2024 14:05 2s
April 4, 2024 14:05 2s
Flexibility of ratetables predictors
TagBot #5: Issue comment #2 (comment) created by rimhajal
April 4, 2024 14:04 2s
April 4, 2024 14:04 2s
Flexibility of ratetables predictors
TagBot #4: Issue comment #2 (comment) created by rimhajal
April 4, 2024 14:04 3s
April 4, 2024 14:04 3s
Fix usage of ratetables.jl
TagBot #3: Issue comment #1 (comment) created by lrnv
April 4, 2024 13:08 3s
April 4, 2024 13:08 3s
Fix usage of ratetables.jl
TagBot #2: Issue comment #1 (comment) created by lrnv
April 4, 2024 12:23 2s
April 4, 2024 12:23 2s
Fix usage of ratetables.jl
CI #15: Pull request #1 synchronize by lrnv
April 4, 2024 12:23 46s move_ratetables
April 4, 2024 12:23 46s
Fix usage of ratetables.jl
CI #14: Pull request #1 synchronize by lrnv
April 4, 2024 12:22 46s move_ratetables
April 4, 2024 12:22 46s
Fix usage of ratetables.jl
CI #13: Pull request #1 synchronize by lrnv
April 4, 2024 12:21 13s move_ratetables
April 4, 2024 12:21 13s
Fix usage of ratetables.jl
CI #12: Pull request #1 synchronize by lrnv
April 4, 2024 12:21 47s move_ratetables
April 4, 2024 12:21 47s
Fix usage of ratetables.jl
TagBot #1: Issue comment #1 (comment) created by lrnv
April 4, 2024 12:19 3s
April 4, 2024 12:19 3s
Fix usage of ratetables.jl
CI #11: Pull request #1 synchronize by lrnv
April 4, 2024 12:18 1m 9s move_ratetables
April 4, 2024 12:18 1m 9s
Fix usage of ratetables.jl
CI #10: Pull request #1 synchronize by lrnv
April 4, 2024 12:13 1m 31s move_ratetables
April 4, 2024 12:13 1m 31s
ProTip! You can narrow down the results and go further in time using created:<2024-04-04 or the other filters available.