No description
- TypeScript 93%
- CSS 4%
- Dockerfile 2.2%
- JavaScript 0.8%
|
|
||
|---|---|---|
| .forgejo/workflows | ||
| .vscode | ||
| app | ||
| components | ||
| hooks | ||
| lib | ||
| public | ||
| .dockerignore | ||
| .gitignore | ||
| auth.ts | ||
| CHANGELOG.md | ||
| components.json | ||
| docker-compose.yml | ||
| Dockerfile | ||
| eslint.config.mjs | ||
| LICENSE | ||
| next.config.ts | ||
| package-lock.json | ||
| package.json | ||
| pnpm-lock.yaml | ||
| postcss.config.mjs | ||
| README.md | ||
| schema.prisma | ||
| tsconfig.json | ||
omeka-cover
Deployment
# first time
git clone ssh://git@git.modernleft.org/AAC/omeka-cover.git
# update
git fetch
git checkout v1.6.1 # or latest
docker compose build
Development
Versioning
Commit messages control the CI semantic versioning. Examples:
0.0.0
<MAJOR>.<MINOR>.<PATCH>
fix: correct a bug # patch
feat: add a new feature # minor
refactor: a breaking change # major
Commit message types
Other types of commit messages do not affect versioning:
docs: documentation only changes
chore: other changes that don't modify src or test files
test: adding missing tests or correcting existing tests
ci: changes to our CI configuration files and scripts
refactor: a code change that neither fixes a bug nor adds a feature such as renaming a variable
Examples:
docs: update README
chore: update dependencies
test: add tests for new feature
ci: only build on main branch
refactor: remove unused imports
Making changes
# make your changes
pnpm run build