fgtclb / academic-programs
Add structured data for academic programs to pages
Installs: 42
Dependents: 0
Suggesters: 0
Security: 0
Stars: 1
Watchers: 6
Forks: 0
Open Issues: 2
Type:typo3-cms-extension
Requires
- php: ^7.4 || ^8.0 || ^8.1 || ^8.2 || ^8.3
- fgtclb/category-types: ^1.1.0 || 1.*.*@dev
- typo3/cms-backend: ^11.5 || ^12.4
- typo3/cms-core: ^11.5 || ^12.4
- typo3/cms-extbase: ^11.5 || ^12.4
- typo3/cms-fluid: ^11.5 || ^12.4
- typo3/cms-frontend: ^11.5 || ^12.4
Requires (Dev)
- fakerphp/faker: ^1.23
- friendsofphp/php-cs-fixer: ^3.14
- helhum/typo3-console: ^7.1.6 || ^8.0.2
- helmich/typo3-typoscript-lint: ^3.1.0
- phpstan/phpstan: ^1.10
- phpunit/phpunit: ^10.1
- saschaegerer/phpstan-typo3: ^1.8
- typo3/cms-extensionmanager: ^11.5 || ^12.4
- typo3/cms-fluid-styled-content: ^11.5 || ^12.4
- typo3/cms-frontend: ^11.5 || ^12.4
- typo3/cms-info: ^11.5 || ^12.4
- typo3/cms-install: ^11.5 || ^12.4
- typo3/cms-lowlevel: ^11.5 || ^12.4
- typo3/cms-tstemplate: ^11.5 || ^12.4
- typo3/coding-standards: ^0.7.1
- typo3/testing-framework: ^7.0
Suggests
- fgtclb/page-backend-layout: Add backend category preview
Conflicts
- fgtclb/page-backend-layout: <1.0.0 || >=2.0.0
This package is auto-updated.
Last update: 2025-03-10 10:39:14 UTC
README
Installation
Install with your flavour:
- TER
- Extension Manager
- composer
We prefer composer installation:
composer req fgtclb/academic-programs
URL | |
---|---|
Repository: | https://github.com/fgtclb/academic-programs |
Read online: | https://docs.typo3.org/p/fgtclb/academic-programs/main/en-us/ |
TER: | https://extensions.typo3.org/extension/academic_programs/ |
Create a release (maintainers only)
Prerequisites:
- git binary
- ssh key allowed to push new branches to the repository
- GitHub command line tool
gh
installed and configured with user having permission to create pull requests.
Prepare release locally
Set
RELEASE_BRANCH
to branch release should happen, for example: 'main'. SetRELEASE_VERSION
to release version working on, for example: '0.1.4'.
echo '>> Prepare release pull-request' ; \ RELEASE_BRANCH='main' ; \ RELEASE_VERSION='0.1.4' ; \ git checkout main && \ git fetch --all && \ git pull --rebase && \ git checkout ${RELEASE_BRANCH} && \ git pull --rebase && \ git checkout -b prepare-release-${RELEASE_VERSION} && \ composer require --dev "typo3/tailor" && \ ./.Build/bin/tailor set-version ${RELEASE_VERSION} && \ composer remove --dev "typo3/tailor" && \ git add . && \ git commit -m "[RELEASE] ${RELEASE_VERSION}" && \ git push --set-upstream origin prepare-release-${RELEASE_VERSION} && \ gh pr create --fill-verbose --base ${RELEASE_BRANCH} --title "[RELEASE] ${RELEASE_VERSION}" && \ git checkout main && \ git branch -D prepare-release-${RELEASE_VERSION}
Check pull-request and the pipeline run.
Merge approved pull-request and push version tag
Set
RELEASE_PR_NUMBER
with the pull-request number of the preparation pull-request. SetRELEASE_BRANCH
to branch release should happen, for example: 'main' (same as in previous step). SetRELEASE_VERSION
to release version working on, for example:0.1.4
(same as in previous step).
RELEASE_BRANCH='main' ; \ RELEASE_VERSION='0.1.4' ; \ RELEASE_PR_NUMBER='123' ; \ git checkout main && \ git fetch --all && \ git pull --rebase && \ gh pr checkout ${RELEASE_PR_NUMBER} && \ gh pr merge -rd ${RELEASE_PR_NUMBER} && \ git tag ${RELEASE_VERSION} && \ git push --tags
This triggers the on push tags
workflow (publish.yml
) which creates the upload package,
creates the GitHub release and also uploads the release to the TYPO3 Extension Repository.