Add Forgejo Actions ports of the GitLab CI templates #1

Merged
robin.marquardt merged 1 commit from forgejo-workflows into main 2026-09-12 16:24:53 +02:00
  • shopware-plugin/-app: build+validate+release as one job; composer
    package uploaded as zip to the Forgejo registry instead of committing
    assets/composer.json onto the tag; existing package versions are
    replaced automatically (GitLab overwrite behavior)
  • npm-package: test + tag-gated publish to the owner-scoped npm registry
  • docker-container: kaniko matrix build (amd64/arm64) pushing to the
    Forgejo container registry
  • shopware-mirror: scheduled sync + tag publish via git archive upload
  • shopware-source-mirror is replaced by a native Forgejo pull mirror
  • MIGRATION.md documents setup, behavior changes and variable mapping
- shopware-plugin/-app: build+validate+release as one job; composer package uploaded as zip to the Forgejo registry instead of committing assets/composer.json onto the tag; existing package versions are replaced automatically (GitLab overwrite behavior) - npm-package: test + tag-gated publish to the owner-scoped npm registry - docker-container: kaniko matrix build (amd64/arm64) pushing to the Forgejo container registry - shopware-mirror: scheduled sync + tag publish via git archive upload - shopware-source-mirror is replaced by a native Forgejo pull mirror - MIGRATION.md documents setup, behavior changes and variable mapping
Add Forgejo Actions ports of the GitLab CI templates
Some checks failed
docker-container.yml / Add Forgejo Actions ports of the GitLab CI templates (push) Failing after 0s
npm-package.yml / Add Forgejo Actions ports of the GitLab CI templates (push) Failing after 0s
shopware-app.yml / Add Forgejo Actions ports of the GitLab CI templates (push) Failing after 0s
shopware-mirror.yml / Add Forgejo Actions ports of the GitLab CI templates (push) Failing after 0s
shopware-plugin.yml / Add Forgejo Actions ports of the GitLab CI templates (push) Failing after 0s
docker-container.yml / Add Forgejo Actions ports of the GitLab CI templates (pull_request) Failing after 0s
npm-package.yml / Add Forgejo Actions ports of the GitLab CI templates (pull_request) Failing after 0s
shopware-app.yml / Add Forgejo Actions ports of the GitLab CI templates (pull_request) Failing after 0s
shopware-mirror.yml / Add Forgejo Actions ports of the GitLab CI templates (pull_request) Failing after 0s
shopware-plugin.yml / Add Forgejo Actions ports of the GitLab CI templates (pull_request) Failing after 0s
docker-container.yml / Merge pull request 'Add Forgejo Actions ports of the GitLab CI templates' (#1) from forgejo-workflows into main (pull_request) Failing after 0s
npm-package.yml / Merge pull request 'Add Forgejo Actions ports of the GitLab CI templates' (#1) from forgejo-workflows into main (pull_request) Failing after 0s
shopware-app.yml / Merge pull request 'Add Forgejo Actions ports of the GitLab CI templates' (#1) from forgejo-workflows into main (pull_request) Failing after 0s
shopware-mirror.yml / Merge pull request 'Add Forgejo Actions ports of the GitLab CI templates' (#1) from forgejo-workflows into main (pull_request) Failing after 0s
shopware-plugin.yml / Merge pull request 'Add Forgejo Actions ports of the GitLab CI templates' (#1) from forgejo-workflows into main (pull_request) Failing after 0s
27a083ae60
- shopware-plugin/-app: build+validate+release as one job; composer
  package uploaded as zip to the Forgejo registry instead of committing
  assets/composer.json onto the tag; existing package versions are
  replaced automatically (GitLab overwrite behavior)
- npm-package: test + tag-gated publish to the owner-scoped npm registry
- docker-container: kaniko matrix build (amd64/arm64) pushing to the
  Forgejo container registry
- shopware-mirror: scheduled sync + tag publish via git archive upload
- shopware-source-mirror is replaced by a native Forgejo pull mirror
- MIGRATION.md documents setup, behavior changes and variable mapping
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
templates/workflows!1
No description provided.