Takashi Kokubun 81a2fdff1b Force blank issues on fork repos ... We don't use issues on ruby/ruby, but we do in some fork repositories. When filing issues, GitHub checks if you want to report a security issue when .github/SECURITY.md exists, but we don't do that on GitHub. So this commit attempts to always create a blank issue.		2025-06-30 08:52:12 -07:00
..
actions	CI: Run Launchable in the build directory	2025-06-20 17:40:59 +09:00
ISSUE_TEMPLATE	Force blank issues on fork repos	2025-06-30 08:52:12 -07:00
workflows	Use https://github.com/ruby/power_assert/pull/58	2025-06-27 11:14:50 +09:00
auto_request_review.yml	YJIT: ZJIT: Allow both JITs in the same build	2025-05-15 00:39:03 +09:00
dependabot.yml	Try to exclude rubygems Rust stuff from dependabot	2024-01-22 14:34:29 -08:00
labeler.yml	Ignore to add Documentation label when we pushed doc and src both	2025-01-23 11:48:29 +09:00
SECURITY.md	Move SECURITY.md into .github/ to reduce the files on the top directory	2019-12-10 18:05:51 +09:00