sshtepa/toolkit
1
0
Fork 0
forked from sig_core/toolkit
Code Pull Requests Activity
Various scripts and tools for SIG/Core
697 Commits 1 Branch 0 Tags 1.9 MiB
Python 72.5%
Shell 23%
Go 3.2%
Ruby 0.9%
Dockerfile 0.4%
e9f6b7a99f
Go to file
Louis Abel e9f6b7a99f
add kiwi config items
2024-04-24 00:24:12 -07:00
.github/workflows fix: don't use gha max cache 2023-11-19 07:14:57 -07:00
analyze Add really simple download stats script to parse fastly logs on disk 2022-05-12 18:33:23 -04:00
chat Add chat scripts and update propagation for amis 2022-05-26 00:24:52 -04:00
func add missing attr install 2024-03-19 10:53:55 -07:00
iso add kiwi config items 2024-04-24 00:24:12 -07:00
mangle rl10 configs are the true buildroot 2024-04-14 00:16:20 -07:00
sync fix: regex 2024-04-04 00:42:47 -04:00
.disable.gitlab-ci.yml fix up readme, disable gitlab tests for now 2022-06-28 12:41:12 -07:00
.gitignore remove leading space 2023-09-07 14:04:34 -04:00
README.md clarify readme 2023-01-09 10:32:45 -07:00

README.md

sig-core-toolkit

Release Engineering toolkit for repeatable operations or functionality testing.

Currently mirrored at our github, and the RESF Git Service. Changes will typically occur at the RESF Git Service.

What does this have?

  • analyze -> Analysis utilities (such as download stats)
  • chat -> mattermost related utilities
  • func -> (mostly defunct) testing scripts and tools to test base functionality
  • iso -> Contains empanadas, which provides ISO, Compose, and Sync related utilities.
  • mangle -> Manglers and other misc stuff
  • sync -> Sync tools, primarily for Rocky Linux 8 and will eventually be deprecated

How can I help?

Fork this repository and open a PR with your changes. Keep these things in mind when you make changes:

  • Your PR should be against the devel branch (not optional)

  • Have pre-commit installed if possible

  • Have shellcheck installed if possible

  • Shell Scripts: These must pass a shellcheck test!

  • Python scripts: Try your best to follow PEP8 guidelines (even the best linters get things wrong)

    • Note that not everything has to pass. Just try your best.

PR's against the main branch will be closed.

PR's are preferred at the RESF Git Service.

Will some of this be moved into separate repositories?

There may be some things that will be moved to its own repository in the near future. From a SIG/Core standpoint, we believe a good chunk of this should stay here as it makes it easier for us to maintain and manage.