This repository contains organization-wide configurations and templates for JLU Software team. It provides default community health files, templates, and workflows that are shared across all repositories in the organization.
.github/
โโโ CODE_OF_CONDUCT.md # Code of Conduct
โโโ CODEOWNERS # Default code owners
โโโ CONTRIBUTING.md # Organization-wide contributing guidelines (English)
โโโ CONTRIBUTING_CN.md # Organization-wide contributing guidelines (Chinese)
โโโ FUNDING.yml # Sponsorship configuration
โโโ workflow-templates/ # Reusable workflow templates
โ โโโ python-project.yml
โ โโโ cpp-project.yml
โโโ workflows/ # Organization-level workflows
โ โโโ python-package.yml
โ โโโ dependency-review.yml
โโโ actions/ # Custom actions
โ โโโ python-lint/
โ โโโ build-docs/
โโโ profile/ # Organization profile
โโโ README.md # Public organization profile
Default files used across all repositories in the organization:
- Contributing Guidelines (English & Chinese)
- Code of Conduct
- Workflows
- Funding Configuration
- // Code Owners
Ready-to-use GitHub Actions workflows for:
- Python Projects
- C++ Projects
- Documentation Building
- Code Linting & Testing
Reusable actions for common tasks:
- Python Code Linting
- Documentation Building
-
When creating new workflows, check the workflow templates in Actions tab
-
Reference custom actions in your workflows using:
- uses: ./.github/actions/python-lint
-
Follow the contributing guidelines for consistency
-
Help us improve these configurations by opening issues or PRs
- Read through CONTRIBUTING.md before making contributions
- Use provided issue and PR templates
- Check workflow templates when setting up new projects
- These configurations serve as defaults and can be overridden by individual repositories
- Workflow templates are available in the "Actions" tab when creating new workflows
- Custom actions can be referenced from any repository in the organization
This repository is maintained by the JLU Software team. If you have suggestions for improvements:
- Open an issue to discuss the proposed changes
- Submit a PR with updates
- Ensure documentation is updated accordingly