Guidelines for Contributing to the OnlyAutomator Ecosystem
βοΈ License Information
IMPORTANT: OnlyAutomator is NOT an open-source project. It is proprietary software under the OnlyAutomator License.- All contributions become the property of OnlyAutomator
- Redistribution without explicit permission is prohibited
- The code cannot be forked for public or private projects outside the OnlyAutomator ecosystem
- All intellectual property rights belong to OnlyAutomator and New Web Order
π₯ Team Structure
Key Team Members
- Jocelin (Jopad Officiel) - CEO
- Syed Saif - Design & Development Manager
- Shahmeez Zaidi - Developer
- Kanza Tahreem - Developer
Core Team Roles
- Product Management: Jocelin (CEO)
- Design & Development Management: Syed Saif
- Development: Shahmeez Zaidi, Kanza Tahreem
π Repository Contribution Stats
Current Repository Stats (All Repositories)
Based on the latest Git data across all repositories:only-automator-webapp
only-automator-plugin-v2
only-automator-microservice
Total commits across all repositories
Repository Contributor Chart
The following chart dynamically represents the current state of contributions and will automatically update when the source data changes:π Dynamic Contribution Flow
The following diagram illustrates the flow of contributions across repositories and will automatically update to reflect changes in contribution patterns:π Internal Contribution Guidelines
The following guidelines are for authorized team members working on the OnlyAutomator ecosystem:Setting Up the Development Environment
- Access the Repository: Ensure you have the proper access rights to the OnlyAutomator repositories.
- Clone the Repository:
- Install Dependencies:
- Set Up Environment Variables:
- Copy the
.env.example
file to.env.local
- Fill in the required environment variables (request access keys from management)
- Copy the
Development Workflow
- Create a Branch:
- Make Changes: Implement your feature or fix
- Write Tests: Ensure your code is covered by tests
- Run Linting and Tests:
- Commit Your Changes:
- We follow Conventional Commits
Submitting Changes
- Push to Remote:
- Create a Pull Request: Go to the repository and create a PR from your branch
- Code Review: Wait for team leads to review your code
- Address Feedback: Make necessary changes based on feedback
- Merge: Once approved, your PR will be merged
π Coding Standards
- TypeScript: Write all code in TypeScript
- Component Structure: Follow the projectβs component hierarchy
- CSS Styling: Use Tailwind CSS for styling
- Testing: Write tests for your code using the projectβs testing framework
- Documentation: Update documentation for any new features or changes
π Code Review Process
All code changes must be reviewed by at least one team lead before merging. Reviews focus on:- Code quality and readability
- Performance considerations
- Security implications
- Test coverage
- Documentation completeness
π Contact & Support
If you have questions about the development process, contact our development team:- Email: contact@onlyautomator.com
- Personnal X (Twitter): Jocelin (Jopad Officiel)
Development Company
OnlyAutomator is developed by New Web Order, a remote software development company specializing in SaaS development, web applications, and AI solutions.- Website: https://www.newweborder.co/
- Email: contact@newweborder.co
- Phone: +44 736-085-6434
Β© 2024-2025 OnlyAutomator. All Rights Reserved.