Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
steampipe-plugin-github
Use SQL to instantly query repositories, users, gists and more from GitHub. Open source CLI. No DB required.
-
steampipe-mod-community-tracker
A collection of benchmarks, controls, and dashboards used to track organization settings, repository settings, open issues and pull requests, and more.
If the projects were my own, I'd consider a monorepo. We use this approach for Steampipe samples - https://github.com/turbot/steampipe-samples
If it's a collection of changes, small improvements, etc to existing projects and repos then personally I'd go for separate forked repos. Then you can track your changes relative to the original project source code and (hopefully) contribute back PRs etc more easily.
As always - there are pros & cons to both - just a matter of choosing the approach that feels best 51% of the time :-). Of course, it's minor in general compared to the value of just keeping on moving on your projects and work!
We use our open source project Steampipe [1] to query data using the GitHub plugin [2] and mods [3]. We have also opened up the custom mod we built for the specific charts & reports [4].
I hope they help - let us know if you give them a try!
1 - https://github.com/turbot/steampipe
4 - https://github.com/turbot/steampipe-mod-community-tracker
Related posts
- Steampipe Hacktoberfest 2023
- Use SQL to query Okta applications, groups, password policies, users, and more (new open source project)
- Need to audit an Azure environment, any tip?
- Enrich Splunk events with Steampipe
- Use SQL to query Microsoft 365 drive files, mail messages, team members and more (new open source project)