proophessor
proophessor copied to clipboard
Create skeleton for new repositories
All repositories should have the same structure and settings. Let's discuss here what's needed and how. So new repositories can be easily created and have all needed information.
We should also use this for new major versions of current components
- markdown files (CHANGELOG.md, CONTRIBUTING.md, LICENSE.md, README-GIT.md, README.md)
- Be a badge poser? It's useful to see all meta stuff in one row like license, supported PHP versions ...
- Folder structure (doc, src, build, test, benchmark) all singular
- CI Tools (PHPUnit, PHP-CS), don't use Symfony's CS because we only use PSR-2
- composer.json with scripts and meta infos
- Create default bookdown doc structure
- CI files (.coveralls.yml, .scrutinizer.yml, .travis.yml, phpbench.json.dist, phpcs.xml.dist, phpunit.xml.dist, .gitattributes)
- Registering on CI Services
- Enable Gitter Bot for CI Services? Useful for VersionEye and outdated dependencies like uuid lib issue.
- Create
masteranddevelopbranch - Release Workflow?
Placeholder for files
- REPO_NAME
- REPO_NAME_URL
- NAMESPACE