farce 0.0.1.alpha2-x86_64-linux-gnu

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 1dc3abfaad0b0f2caed64a35ce71d3b4341cef1464d9e8310c90eca7251e956a
+  data.tar.gz: 3da28fe3bd4144418e30025c880dfe8f1ed8664b529369723105014e8aae0c60
+SHA512:
+  metadata.gz: 686a93530cb33d5810bb86cd043a21c8074a8c668eb97e95d0c2f528c540c32838a35339e49f47b6f0a361791a248a543b0e686b77afa2c092e0244121ab5bc6
+  data.tar.gz: adba7be18980bf70175455a86c0c7fb525961128ce4d6fee51b515ea2bc59a76d5e7dfc16a6f546fed51aa13d9a261f8dba5c56d58f1d13b4cb849c68bac9e28

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,26 @@
+<!--
+# @title Contributor Code of Conduct
+-->
+
+# Contributor Code of Conduct
+
+As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
+
+We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery
+* Personal attacks
+* Trolling or insulting/derogatory comments
+* Public or private harassment
+* Publishing other's private information, such as physical or electronic addresses, without explicit permission
+* Other unethical or unprofessional conduct
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team.
+
+This code of conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers.
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.2.0, available at https://www.contributor-covenant.org/version/1/2/0/code-of-conduct.html

data/CONTRIBUTING.md

@@ -0,0 +1,71 @@
+<!--
+# @title Contributing to Farce
+-->
+
+# Contributing to Farce
+
+Contributions to Farce are welcome and appreciated! 💜💜💜
+
+To ensure a smooth contribution process, please follow these guidelines:
+
+1. Do not open issues or pull requests regarding open **security vulnerabilities**. If you discover a security vulnerability, please report it privately to the maintainers by emailing [security@rkh.im](mailto:security@rkh.im) with the subject line "Farce Security Vulnerability Report".
+2. **Bug reports** and **pull requests** should be submitted to the [main repository](https://github.com/rkh/farce) on GitHub.
+3. Please follow the **[code of conduct](CODE_OF_CONDUCT.md)** in all your interactions with the project and its community.
+4. If you use an **AI tool** to assist with your contribution, please follow the guidelines outlined in the [AI contribution policy](#ai-contribution-policy) below.
+5. Any code contributions added to Farce directly should be licensed under the **[MIT License](MIT-LICENSE)**. By submitting a pull request, you are agreeing to license your contribution under the MIT License. This does not apply to third-party plugins, repositories, redistributions, or other works that you may link to or reference in your contribution, which may be subject to their own licenses.
+6. **Run [the tests](#local-development)** and make sure it's happy before submitting a pull request. If your contribution includes new features, please also add tests and documentation as needed.
+
+Feel free to reach out with any questions and feedback.
+
+Thank you for being part of the Ruby Open Source community and for contributing to Farce! 🙌
+
+## Local Development
+
+You can use [mise](https://mise.jdx.dev) to run tasks against all supported Ruby versions.
+
+ | Task                 | With mise       | Without mise               |
+ | -------------------- | --------------- | -------------------------- |
+ | install dependencies | `mise install`  | `bundle install`           |
+ | compile extensions   | `mise compile`  | `bundle exec rake compile` |
+ | run tests            | `mise run test` | `bundle exec rake test`    |
+ | builds gems          | `mise build`    | `bundle exec rake gem:all` |
+ | update dependencies  | `mise update`   | see mise/tasks/update      |
+
+ To install dependencies, compile extensions, run the tests and build the gems, you can run `mise run` (without any arguments) and to do so on file changes, you can use `mise watch`.
+
+ Test runs have an external 300-second watchdog so a deadlocked Ruby VM cannot leave local development or CI stuck indefinitely. Set `TEST_TIMEOUT` to change the deadline. A timed-out run reports its Minitest seed and, on macOS, attempts to write a native stack sample to `tmp/test-watchdog`. The unsupervised `bundle exec rake test:run` task is available for debugging.
+
+ ### Test coverage reports
+
+ If you use mise, this will be handled automatically.
+
+ Otherwise you will need to set the `COVERAGE` environment variable to `true` when running tests. For a full report, you also need to run the tests with different Ruby versions within SimpleCov's merge timeout (defaults to 10 minutes), as they cover different parts of the codebase.
+
+ For instance, using [rvm](https://rvm.io/) could look like this:
+
+ ```bash
+ COVERAGE=true rvm 3.4,4.0,jruby do bundle exec rake test
+ bundle exec rake coverage:report
+ ```
+
+### Ruby subprocess tests
+
+Use `ruby_subprocess(source, env: {})` in tests that need a fresh Ruby process. It returns stdout, stderr, and `Process::Status`, adds the repository's `lib` and `test` directories to the load path, and reports captured output if the child times out.
+
+The subprocess timeout defaults to 15 seconds. Set `TEST_SUBPROCESS_TIMEOUT` for slower runtime startup, such as TruffleRuby on the JVM. An explicit `timeout:` argument overrides this setting. The whole-suite `TEST_TIMEOUT` watchdog remains independent.
+
+When `COVERAGE=true`, the helper starts SimpleCov before the child script loads Farce. Each child records a separate result for the merged report without adding coverage output to stdout or stderr. Use `coverage: false` for timing-sensitive probes. Use `ruby_command(source, coverage: false)` when a test needs to manage the process itself.
+
+## AI contribution policy
+
+If you wish to use an AI tool for assistance, please adhere to the following guidelines:
+
+* As a contributor, you are always the author and fully accountable for your contributions.
+* You must carefully read and review all LLM-generated code or text before asking maintainers to review it. This includes pull request descriptions, where we want to hear your personal voice rather than an unfiltered AI summary.
+* You should be transparent and make note if your contribution contains substantial amounts of tool-generated content.
+* You should be confident that your contribution is high enough quality to merit a maintainer’s time for review. You should be able to answer questions about your work during review.
+* You are responsible for ensuring you have the legal right to make your contribution under our license, and that your contribution does not violate the intellectual property rights of any third party.
+
+Any agents used for contributions may not take action without human review and approval. This includes, but is not limited to, making commits, opening pull requests, or posting in issue trackers.
+
+This policy is based on the [Hanami AI contribution policy](https://discourse.hanamirb.org/t/ai-contribution-policy).

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) Konstantin Haase
+
+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 the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS 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.