npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ros2-cache

v0.0.4

Published

Cache ROS 2 files

Downloads

11

Readme

README

This script seeks to be useful in making the ROS 2 branch names more consistent. At the time of writing, the ROS 2 repositories have several default branch names, such as rolling, master, main, rolling-devel, and even crystal-devel or dashing-devel. The goal of this script is to clean things up so that all branches used by Rolling are called rolling. This will have a couple of major advantages:

  • Less confusing to new contributors (and the Open Robotics team)
  • Easier to automate operations across the ROS 2 repositories

Details

This script does the following. Note that all configuration is in src/index.ts. Also, this script doesn't have to change all of the default branches to rolling, you could use any other branch name in the configuration.

  • Find the list of repositories to apply the change to from a ros2.repos file
  • For each repository
    • Find the current default branch on the repository
    • Commits and pushes a GitHub action to automatically sync between ‘rolling’ and the old default branch
    • Creates a rolling branch and sets the Rolling branch as the default branch for the repository
    • Retarget all PRs for the old default branch to the new rolling branch
  • Updates ros2.repos and rolling/distribution.yaml files locally for all repos that had a new branch created

Note that this script handles the following special cases:

  • Specific repositories can be excluded
  • The rolling branch will not be created if it exists, nor will PRs be retargeted
  • The Github workflow will not be created if the workflow file already exists in the repository
  • Repos in the ros2.repos file but not in the rolling/distribution.yaml won't cause any problems
  • Reports the repositories that had errors creating a branch and pushing, often due to permission errors