Support
Getting help and contributing to Copilot
Support
Learn how to get help with Copilot and contribute to its development.
Documentation
- Review the documentation
- Check the configuration guide and Features & Capabilities
Issue Reporting
When reporting issues, follow these steps:
Search first
Check existing issues to avoid duplicates.
Include in your report
- Detailed description
- Steps to reproduce
- Expected vs actual behavior
- Relevant logs and configurations
- Environment details
Community Support
- Use GitHub Discussions for questions
- Check Stack Overflow with tag
copilot - Join our community channels
Code Contributions
- Fork the repository
- Create a feature branch
- Make your changes
- Add tests if applicable
- Submit a pull request
Development Setup
# Clone the repository
git clone https://github.com/vypdev/copilot.git
# Install dependencies
npm install
# Run tests
npm test
# Build the project
npm run build
Pull Request Guidelines
- Follow the existing code style
- Include tests for new features
- Update documentation as needed
- Keep changes focused and atomic
- Add meaningful commit messages
Feature Requests
When requesting new features:
- Check existing issues and requests
- Provide clear use cases
- Explain the expected behavior
- Describe the benefit to users
- Consider implementation details
Security Reports
For security issues:
- DO NOT open public issues
- Email security concerns directly
- Include detailed information
- Await response before disclosure
Stay Updated
- Watch the GitHub repository
- Follow release announcements
- Join our mailing list
- Check our blog for updates
Contact
- GitHub Issues: Report a bug
- Email: efraespada@vyp.dev
We aim to respond to all inquiries within 48 hours during business days.