Skip to content
GitHub Explorer

Sydney-Informatics-Hub/Nextflow_DSL2_template_guide

View on GitHub ↗Related repositories →

Self-directed materials for using the Nextflow DSL2 template

active 2024-05-27 → 2024-09-12 (UTC)

Complete coverage26,628 / 26,628 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-28 (UTC)
Events
23
Pushes
8
Pull requests
4
Issues
7
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 109 days from 2024-05-27 to 2024-09-12. Pushes: 8 total, peak 3 in a day. Pull requests: 4 total, peak 2 in a day. Issues: 7 total, peak 7 in a day. Comments: 1 total, peak 1 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
georgiesamaha18641
github-actions[bot]2200

Recent activity

Latest issues, pull requests and releases

  • Pull request#9georgiesamaha2024-09-12 23:58
  • Pull request#9georgiesamaha2024-09-12 23:58
  • Issue comment#1georgiesamaha2024-08-27 02:59
    Guides: explainer for writing channels
  • Pull request#8georgiesamaha2024-08-25 05:54
  • Pull request#8georgiesamaha2024-08-25 05:54
  • Issue#7georgiesamaha2024-06-28 03:30
    Guides: plan what should go in here
  • Issue#6georgiesamaha2024-06-28 03:26
    Hands on tutorial: how to use the template to configure a simple workflow for HPC
  • Issue#5georgiesamaha2024-06-28 03:25
    Hands on tutorial: how to use the template to build a simple workflow
  • Issue#4georgiesamaha2024-06-28 03:23
    Software management page: containers, modules, conda(?)
  • Issue#3georgiesamaha2024-06-28 03:14
    Resource configuration page: monitoring resource usage with `trace`
  • Issue#2georgiesamaha2024-06-28 03:12
    Resource configuration page: how to configure compute resources
  • Issue#1georgiesamaha2024-06-28 03:05
    Guides: explainer for writing channels

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.