Skip to content

Planning, design, documentation, and discussion for Robograph Project

active 2025-03-072025-05-04 (UTC)

Complete coverage26,639 / 26,639 hourly files (100%) · 2 absent upstream2023-08-152026-08-28 (UTC)
Events
26
Pushes
1
Pull requests
0
Issues
18
Stars
1
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 59 days from 2025-03-07 to 2025-05-04. Pushes: 1 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 18 total, peak 8 in a day. Comments: 3 total, peak 1 in a day. Stars: 1 total, peak 1 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
emersonknapp22103

Recent activity

Latest issues, pull requests and releases

  • Issue#20emersonknapp2025-05-04 19:03
    Render launchfile to systemD services - down to the node/command level as a tree
  • Issue#19emersonknapp2025-04-29 07:04
    Xacro render launch substitution
  • Issue comment#19emersonknapp2025-04-29 07:04
    Xacro render launch substitution
  • Issue#19emersonknapp2025-04-29 07:04
    Xacro render launch substitution
  • Issue#19emersonknapp2025-04-29 05:14
    Xacro render launch substitution
  • Issue#18emersonknapp2025-04-29 05:06
    Python: Paths
  • Issue#17emersonknapp2025-04-29 05:05
    Key/value dicts as alternative to `name:, value:` list entities
  • Issue#16emersonknapp2025-04-29 05:05
    `group` should also accept a key `actions:` like the Python API, `children:` is opaque as a kind of "implementationy" detail about how the parsing is done
  • Issue#15emersonknapp2025-04-29 05:02
    `include:` should take a single text element as the file, if no other attributes are needed
  • Issue#14emersonknapp2025-04-29 04:56
    Launch XML/YAML ergonomics pass
  • Issue#13emersonknapp2025-04-28 21:01
    Launch error output specify source line from provided launchfile
  • Issue#12emersonknapp2025-04-28 21:00
    Launch accept pathlib.Path for IncludeLaunchDescription (and other pathlike)
  • Issue#11emersonknapp2025-04-28 20:01
    Autogenerate launch + launch_ros schema from sources
  • Issue#10emersonknapp2025-04-28 19:58
    Move trivial launch tutorial examples to XML and/or YAML
  • Issue#9emersonknapp2025-04-28 19:57
    Remove use of `PythonLaunchDescriptionSource` as a user-facing API
  • Issue comment#7emersonknapp2025-04-15 16:09
    Pull all launch file examples out into standalone files
  • Issue#7emersonknapp2025-04-15 16:09
    Pull all launch file examples out into standalone files
  • Issue#8emersonknapp2025-03-25 21:35
    Document `value = declare_parameter` Parameter pattern for basic parameter usage
  • Issue comment#5emersonknapp2025-03-25 21:17
    Update ROS2 Documentation for Launch to encourage declarative practices
  • Issue#7emersonknapp2025-03-25 21:16
    Pull all launch file examples out into standalone files
  • Issue#5emersonknapp2025-03-20 17:07
    Update ROS2 Documentation for Launch to encourage declarative practices

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