File sync from hanakai-rb/repo-sync

Updated files:

- .github/ISSUE_TEMPLATE/bug-report.md
- CONTRIBUTING.md
- LICENSE
- spec/support/warnings.rb

Author: github-actions[bot]

.github/ISSUE_TEMPLATE/bug-report.md

@@ -21,6 +21,5 @@ A clear and concise description of what you expected to happen.
 
 ## My environment
 
-- Affects my production application: **YES/NO**
 - Ruby version: ...
 - OS: ...

CONTRIBUTING.md

@@ -1,29 +1,29 @@
-# Issue Guidelines
+# Issue guidelines
 
 ## Reporting bugs
 
-If you found a bug, report an issue and describe what's the expected behavior versus what actually happens. If the bug causes a crash, attach a full backtrace. If possible, a reproduction script showing the problem is highly appreciated.
+If you’ve found a bug, please report an issue and describe the expected behavior versus what actually happens. If the bug causes a crash, attach a full backtrace. If possible, a reproduction script showing the problem is highly appreciated.
 
 ## Reporting feature requests
 
-Report a feature request **only after discussing it first on [discourse.dry-rb.org](https://discourse.dry-rb.org)** where it was accepted. Please provide a concise description of the feature.
+Report a feature request **only after discussing it first on [our forum](https://discourse.hanamirb.org)** and having it accepted. Please provide a concise description of the feature.
 
 ## Reporting questions, support requests, ideas, concerns etc.
 
-**PLEASE DON'T** - use [discourse.dry-rb.org](https://discourse.dry-rb.org) instead.
+**Please don’t.** Use [our forum](https://discourse.hanamirb.org) instead.
 
-# Pull Request Guidelines
+# Pull request guidelines
 
-A Pull Request will only be accepted if it addresses a specific issue that was reported previously, or fixes typos, mistakes in documentation etc.
+A pull request will only be accepted if it addresses a specific issue that was reported previously, or fixes typos, mistakes in documentation etc.
 
 Other requirements:
 
-1) Do not open a pull request if you can't provide tests along with it. If you have problems writing tests, ask for help in the related issue.
-2) Follow the style conventions of the surrounding code. In most cases, this is standard ruby style.
-3) Add API documentation if it's a new feature
-4) Update API documentation if it changes an existing feature
-5) Bonus points for sending a PR which updates user documentation in the `docsite` directory
+1. Do not open a pull request if you can't provide tests along with it. If you have problems writing tests, ask for help in the related issue.
+2. Follow the style conventions of the surrounding code. In most cases, this is standard ruby style.
+3. Add API documentation if it's a new feature.
+4. Update API documentation if it changes an existing feature.
+5. Bonus points for sending a PR which updates user documentation in our [site repository](https://github.com/hanakai-rb/site).
 
 # Asking for help
 
-If these guidelines aren't helpful, and you're stuck, please post a message on [discourse.dry-rb.org](https://discourse.dry-rb.org).
+If these guidelines aren't helpful, and you're stuck, please post a message on [our forum](https://discourse.dry-rb.org) or [find us in chat](https://discord.gg/KFCxDmk3JQ).

LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2015-2025 Hanakai team
+Copyright (c) 2015-2026 Hanakai team
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of
 this software and associated documentation files (the "Software"), to deal in
@@ -18,4 +18,3 @@ FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
 COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
 IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
 CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
-

spec/support/warnings.rb

@@ -4,7 +4,10 @@
 
 require "warning"
 
-Warning.ignore(%r{rspec/core})
-Warning.ignore(%r{rspec/mocks})
-Warning.ignore(/codacy/)
+# Ignore warnings for experimental features
 Warning[:experimental] = false if Warning.respond_to?(:[])
+
+# Ignore all warnings coming from gem dependencies
+Gem.path.each do |path|
+  Warning.ignore(//, path)
+end