Thanks for taking the time to contribute.
These are the default contribution guidelines for Karaaslan Labs repositories that do not provide repository-specific instructions. If a repository has its own CONTRIBUTING.md, issue template, pull-request template, or maintainer guidance, follow that repository-specific guidance first.
- Check existing issues and pull requests for overlap.
- Keep the proposed change focused on one problem.
- For non-trivial work, prefer opening or commenting on an issue before implementation when the repository accepts external contributions.
- Do not include secrets, private user data, credentials, internal-only material, or proprietary third-party content.
A good pull request should:
- explain the problem being solved;
- keep unrelated changes out of scope;
- include tests or reproducible evidence when behavior changes;
- document important limitations or validation gaps;
- follow the repository's formatting, lint, test, and build requirements;
- disclose AI-assisted or AI-authored work when the repository requests or expects that disclosure.
Please do not claim tests, runtime reproduction, compatibility, performance, or security properties that were not actually verified.
Maintainers may ask for changes, additional evidence, a smaller scope, or a different implementation approach. A review comment is part of the engineering process, not an acceptance guarantee.
Submissions may be closed if they are duplicate, out of scope, unsafe, unverifiable, or incompatible with the repository's current direction.
Some Karaaslan Labs repositories may be public for transparency or deployment purposes without accepting general feature contributions. Check the repository README and issue tracker before investing significant work.