sshtepa/toolkit
1
0
Fork 0
forked from sig_core/toolkit
Code Pull requests Activity
Various scripts and tools for SIG/Core
168 commits 1 branch 0 tags 2 MiB
Python 72.5%
Shell 23%
Go 3.2%
Ruby 0.9%
Dockerfile 0.4%
Find a file
nazunalika b376c168bb
start using templates for reposync
2022-06-11 10:49:37 -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 forcearch to drive the point home 2022-06-08 20:09:07 -07:00
iso start using templates for reposync 2022-06-11 10:49:37 -07:00
live begin ISO magic 2022-05-19 00:48:07 -07:00
mangle get rid of shellcheck errors 2021-07-06 17:46:34 -04:00
sync finish wrapper, start repoclosure 2022-05-25 21:39:32 -07:00
.gitlab-ci.yml fix: we need this guy in here 2021-07-06 17:46:30 -04:00
README.md add forcearch to drive the point home 2022-06-08 20:09:07 -07:00

README.md

sig-core-toolkit

Release Engineering toolkit for repeatable operations or functionality testing.

Currently mirrored at our github, Rocky Linux Git Service, and the RESF Git Service. Changes either occur at the Rocky Linux Git Service or 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 -> ISO related utilities
  • live -> Live image related utilities
  • mangle -> Manglers and other misc stuff
  • sync -> Sync tools, primarily for Rocky Linux 8

How can I help?

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

  • Have pre-commit installed
  • Have shellcheck installed
  • Shell Scripts: These must pass a shellcheck test!
  • Python scripts: Try your best to follow PEP8 guidelines

Your PR should be against the devel branch at all times. PR's against the main branch will be closed.

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.