-
Notifications
You must be signed in to change notification settings - Fork 0
Support Channels
Multiple ways to get help, report issues, and stay updated with sr-search-replace.
Best for: Bug reports, feature requests, and technical discussions
Found a problem? Please create an issue on GitHub:
👉 GitHub Issues - sr-search-replace
When reporting a bug, please include:
- Steps to reproduce the issue
- Expected behavior
- Actual behavior
- Your operating system and shell (bash version)
- Command output (with
-dflag for debug info) - Any error messages or logs
Example issue title:
Error: Backup creation fails on macOS with special characters in path
Have an idea for improvement? Open a feature request issue:
👉 GitHub Issues - Feature Requests
Include:
- Clear description of the feature
- Use cases and benefits
- Suggested implementation (if you have one)
- Examples of expected behavior
For general questions and discussions:
Best for: Direct support, custom consulting, and business inquiries
For direct support, bug reports, or general inquiries:
Email support options:
- Bug reports and technical issues
- Custom implementation questions
- Integration assistance
- Security concerns (use GPG if available)
- Commercial licensing inquiries
Please include in your email:
- Your name and organization (if applicable)
- Clear description of your issue or question
- Environment details (OS, shell version, script version)
- Relevant command examples and output
- Steps already taken to resolve the issue
Typical response time: Within 24-48 hours during business days
Best for: General information, technical documentation, and project overview
Visit the official website for more information about sr-search-replace and related projects:
Website includes:
- Project overview and features
- Use case scenarios
- Installation instructions
- Additional tools and resources
- Contact information and social media
Comprehensive documentation is available on this Wiki:
📖 Available Guides:
- Quick Start Tutorial - Get started in 5 minutes
- Installation Guide - Installation for different systems
- Command Reference - All available commands and options
- Basic Examples - Common usage scenarios
- Architecture Overview - Technical architecture
- Tool Configuration - Configuration and customization
- Backup & Rollback - Backup and recovery procedures
- Performance Tuning - Optimization tips
| Type | Response Time | Notes |
|---|---|---|
| Critical Bugs | 24 hours | Security issues, data loss risks |
| Regular Bugs | 48-72 hours | Normal bugs, workarounds available |
| Feature Requests | 1-2 weeks | Will be reviewed and discussed |
| Email Inquiries | 24-48 hours | Business days only |
| Documentation | 1-2 weeks | Wiki updates and improvements |
- Timezone: UTC+3 (Moscow Time)
- Business Days: Monday - Friday
- Support Days: Monday - Friday
View the source code, contribute, or track development:
👨💻 paulmann/sr-search-replace
Repository includes:
- Source code (sr.sh)
- Test suite
- Installation scripts
- Contributing guidelines
- License information
You're currently viewing the comprehensive wiki with guides and documentation:
Please do NOT create a public GitHub issue for security problems. Instead, email:
📧 [email protected] with subject: [SECURITY]
Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if you have one)
We will:
- Acknowledge receipt within 24 hours
- Investigate immediately
- Provide a fix or workaround
- Credit you in the release notes (if desired)
Before reaching out, please:
- Check the Quick Start Tutorial
- Review the Command Reference
- Check the FAQ section (if available)
- Search existing GitHub Issues
- Try running with
-d(debug flag) to see detailed output - Check the error messages in the Troubleshooting section
Do this:
# Include full command and output
sr -d "pattern" "replacement" --dry-run ./path/to/files
# Copy error messages verbatim
# Describe what you expected
# Describe what actually happened
# Include your OS and shell versionAvoid:
# Don't provide vague descriptions
# "It doesn't work" - not helpful!
# "Can you fix this?" - fix what?
# Don't assume we know your setup
# Include all relevant context| Channel | Best For | Link |
|---|---|---|
| GitHub Issues | Bugs, Features | github.com/paulmann/sr-search-replace/issues |
| GitHub Discussions | Questions, Ideas | github.com/paulmann/sr-search-replace/discussions |
| Direct Support | [email protected] | |
| Website | Information | deynekin.com |
| Wiki | Documentation | github.com/paulmann/sr-search-replace/wiki |
| Security Issues | Vulnerabilities | [email protected] (with [SECURITY] tag) |
Q: How long does it take to get a response? A: Typically 24-48 hours for emails, 48-72 hours for GitHub issues. Critical security issues get priority.
Q: Should I email or create a GitHub issue? A: Use GitHub Issues for public bugs/features. Use email for private matters, security issues, or commercial inquiries.
Q: What if my issue isn't resolved? A: We'll keep working on it. Complex issues may take longer. Feel free to follow up.
Q: Can I contribute to the project? A: Yes! See the Contributing Guidelines on GitHub.
Q: Is there a commercial support option? A: Yes, contact [email protected] for commercial support inquiries.