├── .gitignore ├── assets └── img │ ├── cslant-favicon.png │ └── cslant-logo.webp ├── .github └── ISSUE_TEMPLATE │ ├── custom.md │ ├── feature_request.md │ └── bug_report.md ├── profile └── README.md └── CONTRIBUTING.md /.gitignore: -------------------------------------------------------------------------------- 1 | .idea 2 | .vscode 3 | -------------------------------------------------------------------------------- /assets/img/cslant-favicon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cslant/.github/main/assets/img/cslant-favicon.png -------------------------------------------------------------------------------- /assets/img/cslant-logo.webp: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/cslant/.github/main/assets/img/cslant-logo.webp -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/custom.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Custom issue template 3 | about: Describe this issue template's purpose here. 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: "[FEAT] " 5 | labels: enhancement, feature request 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Is your feature request related to a problem? Please describe.** 11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 12 | 13 | **Describe the solution you'd like** 14 | A clear and concise description of what you want to happen. 15 | 16 | **Describe alternatives you've considered** 17 | A clear and concise description of any alternative solutions or features you've considered. 18 | 19 | **Additional context** 20 | Add any other context or screenshots about the feature request here. 21 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: "[BUG] " 5 | labels: bug 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | Steps to reproduce the behavior: 15 | 1. Go to '...' 16 | 2. Click on '....' 17 | 3. Scroll down to '....' 18 | 4. See error 19 | 20 | **Expected behavior** 21 | A clear and concise description of what you expected to happen. 22 | 23 | **Screenshots** 24 | If applicable, add screenshots to help explain your problem. 25 | 26 | **Desktop (please complete the following information):** 27 | - OS: [e.g. Windows, Linux-Ubuntu] 28 | - Browser [e.g. chrome, firefox] 29 | - Version [e.g. 22] 30 | 31 | **Additional context** 32 | Add any other context about the problem here. 33 | -------------------------------------------------------------------------------- /profile/README.md: -------------------------------------------------------------------------------- 1 |

2 | 3 | CSlant logo 4 | 5 |

6 | 7 | # Welcome to CSlant! 👋 8 | 9 | We are a community of developers, designers, and makers who love to share knowledge and help each other grow. 10 | 11 | > Additionally: 12 | > - We use another organization specifically for super admins. https://github.com/cslant-admin 13 | > - We use this organization for public activities when necessary. https://github.com/cslant-community 14 | > - We also have our own source code control system at https://git.cslant.com 15 | 16 | ## 📥 Projects 17 | 18 | - [Telegram Git Notifier](https://github.com/cslant/laravel-telegram-git-notifier) - A Laravel package to send Telegram notifications on GitHub and GitLab push events. 19 | - [Laravel Like](https://github.com/cslant/laravel-like) - A Laravel package to add interaction functionality to your Eloquent models. 20 | - [Github Project PHP](https://github.com/cslant/github-project-php) - Provides a simple and easy-to-use webhooks system to get the GitHub project's actions and implement comments on all activities in the project 21 | 22 | ## 📖 Official Documentation 23 | 24 | You can find the official documentation for CSlant on [docs.cslant.com](https://docs.cslant.com). 25 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | Our organization is committed to creating a welcoming and inclusive environment for everyone. We are **welcoming** to all people, regardless of age, disability, or health status. 4 | 5 | Please read and understand the contribution guide and code of conduct before contributing (creating issues, pull requests, etc.) to our projects. 6 | 7 | ## Reporting Issues 8 | 9 | If you find a bug in our projects, please open a new issue on GitHub and provide a detailed description of the issue. Please make sure to **check if the issue has been reported previously** before creating a new issue. 10 | 11 | ## Proposing New Features 12 | 13 | If you'd like to propose a new feature or enhancement for our projects, please open a new issue and describe your idea. We'll review and discuss the feasibility of the proposed idea. 14 | 15 | ## Viability 16 | 17 | Before contributing to our projects, please ensure the proposed changes are viable and align with the project's goals and objectives. 18 | 19 | Who may have entirely different needs and goals. Please consider your changes' impact on the project and its users. 20 | 21 | ## Contributing Code 22 | 23 | We welcome code contributions from the community. To get started, follow these steps: 24 | 25 | 1. Fork the project and create a new branch from `main`. 26 | 2. Make your changes in the new branch. 27 | 3. Create a Pull Request and describe in detail the changes you've made and the reason behind them. 28 | 4. Wait for feedback from the development team. 29 | 30 | We'll review Pull Requests and strive to provide feedback as soon as possible. 31 | 32 | ## Code Styling 33 | 34 | When contributing code, please adhere to the following styling guidelines: 35 | 36 | - Use the existing coding standards and styles in the project. 37 | - Always follow the conventions of the programming language being used. 38 | - Include comprehensive and understandable comments to explain your code. 39 | 40 | **Happy coding!** Thank you for contributing to our projects! 41 | --------------------------------------------------------------------------------