At Github, we want to start new projects faster using best practices with a predefined structure and focusing on core ideas implementation rather than wasting time on environment configuration and copying boilerplate code.
I defined a spec template that I could use to quickly start building a full-fledged project.
In each directory, there is a README.md and an OWNERS, which explains what the directory does and who owns it.
Labels denger: Read about the automation tag design
Note: You can get started quickly with automation.
- Generate a new repository from the template.
- Clone the repository locally.
- Update files, read the README files in each directory.
- Write your code and tests.
Work with Makefile
❯ make help # show help
❯ make build # build binaryWork with actions
Actions provide handling of PR and issue.
We used the bot 🚀@kubbot, It can detect issues in Chinese and translate them to English, and you can interact with it using the command /comment.
Comment in an issue:
❯ /intiveWork with Tools
❯ make toolsWork with Docker
❯ make deploygraph LR
subgraph External Services
feishuAPI --> sheetParser
end
subgraph Sheet Parser & Manager
sheetParser[Sheet Parser] --> versionControl
versionControl[Version Control] --> sheetDisplay
end
subgraph Display
sheetDisplay[Sheet Display] --> UI
end
subgraph Backend
versionControl --> API
end
subgraph Frontend
UI[User Interface]
end
API --> UI
UI --> feishuAPI
MVC Architecture Design:
graph LR
A[View] -->|1. User interaction| B(Controller)
B -->|2. Requests data| C(Model)
C -->|3. Returns data| B
B -->|4. Updates view| A
Catalog standardization design structure:
.automation
├── CONTRIBUTING.md # Contribution guidelines
├── LICENSE # License information
├── Makefile # Makefile for building and running the project
├── README.md # Project overview in English
├── README_zh-CN.md # Project overview in Chinese
├── api # API-related files
│ ├── OWNERS # API owners
│ └── README.md # API documentation
├── assets # Static assets, such as images and stylesheets
│ └── README.md # Assets documentation
├── build # Build-related files
│ ├── OWNERS # Build owners
│ └── README.md # Build documentation
├── cmd # Command-line tools and entry points
│ ├── OWNERS # Command owners
│ └── README.md # Command documentation
├── configs # Configuration files
│ ├── OWNERS # Configuration owners
│ ├── README.md # Configuration documentation
│ └── config.yaml # Main configuration file
├── deploy # Deployment-related files
│ ├── OWNERS # Deployment owners
│ └── README.md # Deployment documentation
├── docs # Project documentation
│ ├── OWNERS # Documentation owners
│ └── README.md # Documentation index
├── examples # Example code and usage
│ ├── OWNERS # Example owners
│ └── README.md # Example documentation
├── init # Initialization files
│ ├── OWNERS # Initialization owners
│ └── README.md # Initialization documentation
├── internal # Internal application code
│ ├── OWNERS # Internal code owners
│ ├── README.md # Internal code documentation
│ ├── app # Application logic
│ ├── pkg # Internal packages
│ └── utils # Utility functions and helpers
├── pkg # Public packages and libraries
│ ├── OWNERS # Package owners
│ ├── README.md # Package documentation
│ ├── common # Common utilities and helpers
│ ├── log # Log utilities
│ ├── tools # Tooling and scripts
│ ├── utils # General utility functions
│ └── version # Version information
├── scripts # Scripts for development and automation
│ ├── LICENSE_TEMPLATES # License templates
│ ├── OWNERS # Script owners
│ ├── README.md # Script documentation
│ ├── githooks # Git hooks for development
│ └── make-rules # Makefile rules and scripts
├── test # Test files and test-related utilities
│ ├── OWNERS # Test owners
│ └── README.md # Test documentation
├── third_party # Third-party dependencies and libraries
│ └── README.md # Third-party documentation
├── tools # Tooling and utilities for development
│ └── README.md # Tool documentation
└── web # Web-related files, such as HTML and CSS
├── OWNERS # Web owners
└── README.md # Web documentationWe welcome everyone to join us and contribute to automation, whether you are new to open source or professional. We are committed to promoting an open source culture, so we offer community members neighborhood prizes and reward money in recognition of their contributions. We believe that by working together, we can build a strong community and make valuable open source tools and resources available to more people. So if you are interested in automation, please join our community and start contributing your ideas and skills!
We take notes of each biweekly meeting in GitHub discussions, and our minutes are written in Google Docs.
automation maintains a public roadmap. It gives a a high-level view of the main priorities for the project, the maturity of different features and projects, and how to influence the project direction.
kubecub Our goal is to build a top-level open source community. We have a set of standards, in the Community repository.
If you'd like to contribute to this automation repository, please read our contributor documentation.
Before you start, please make sure your changes are in demand. The best for that is to create a new discussion OR Slack Communication, or if you find an issue, report it first.
Automation is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.
