Skip to content

active 2024-11-132025-03-19 (UTC)

Complete coverage26,744 / 26,744 hourly files (100%) · 2 absent upstream2023-08-152026-09-02 (UTC)
Events
76
Pushes
0
Pull requests
0
Issues
24
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 130 days from 2024-11-13 to 2025-07-22. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 24 total, peak 8 in a day. Comments: 51 total, peak 8 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

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

ContributorContributionsPushesPRsComments
jsterne200016
kwatsen17007
RobertPeschi9009
derajara8006
QiufangMa6004
xorrkaz3002
shiyaashrf3002
robertjwills3003

Recent activity

Latest issues, pull requests and releases

  • Issue comment#24earies2025-07-22 09:31
    Metadata annotation to determine which template a node was applied from
  • Issue comment#24earies2025-07-21 14:14
    Metadata annotation to determine which template a node was applied from
  • Issue#30rampolisetty2025-07-21 05:04
    Can the template be applied to a leaf/leaf-list?
  • Issue#29rampolisetty2025-07-21 05:01
    Provide the ability to see the expanded view of configuration
  • Issue#25earies2025-07-20 13:10
    Misaligned module template name
  • Issue#23earies2025-07-20 12:54
    Clarify the ability to apply a template at the datastore root node '/'
  • Issue comment#8xorrkaz2025-03-19 07:16
    Support basic programmatic elements in templates
  • Issue comment#21jsterne2025-02-27 16:53
    The solution enables non-nmda servers to return the expanded data
  • Issue comment#18jsterne2025-02-27 16:17
    Support regex in template-config for template-consumer application
  • Issue#21derajara2025-02-27 16:11
    The solution must also cater to non-nmda deployments which returns the expanded data as state data
  • Issue comment#17jsterne2025-02-27 16:09
    The <operational> datastore returns unexpanded template config (depends on #15)
  • Issue#16kwatsen2025-02-27 16:02
    Common data nodes
  • Issue comment#15jsterne2025-02-27 15:54
    For NMDA, the <intended> datastore returns the unexpanded templates
  • Issue comment#15jsterne2025-02-27 15:39
    For NMDA, the <intended> datastore does not contain the templates themselves
  • Issue comment#14jsterne2025-02-27 15:34
    Off-box template-expansion of <running> containing templates must be possible (enabling off-box validation)
  • Issue comment#10jsterne2025-02-27 15:10
    For living templates, the configuration with both unexpanded and expanded templates is able to be returned
  • Issue comment#11jsterne2025-02-27 14:40
    Possibility to reorder some user-ordered list/leaf-list entries defined in a template
  • Issue#20jsterne2025-02-27 14:15
    When templates are applied at multiple ancestor nodes, the innermost (closest) template takes precedence.
  • Issue#19jsterne2025-02-27 14:11
    When multiple templates are applied to a node, the first one takes precedence
  • Issue comment#12jsterne2025-02-18 13:58
    The <running> datastore contains the unexpanded template
  • Issue comment#13RobertPeschi2025-02-18 08:39
    The <intended> datastore contains the expanded template
  • Issue comment#15jsterne2025-02-17 17:15
    The <intended> datastore does not contain the template themselves
  • Issue comment#13jsterne2025-02-17 17:12
    The <intended> datastore contains the expanded template
  • Issue#17jsterne2025-02-17 17:12
    The <operational> datastore does not include pre-expanded template config
  • Issue comment#12jsterne2025-02-17 17:04
    The <running> datastore contains the unexpanded template

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.