GitLab CI execution is frozen and Gitea Actions remains disabled. Pipeline conversion is deferred to the owner.
This project used GitLab CI / Auto DevOps without a current CI YAML file. Use its preserved historical configuration and expanded definitions when deciding how to convert it to Gitea Actions.
Before enabling Actions, review the preserved runner requirements, schedules/triggers, permissions, variables/secrets, image publishing and deployment dependencies. Protected exports and original GitLab secrets/backups remain available to the server administrator; secret values must stay out of this issue.
Acceptance: the owner explicitly enables the converted workflow, validates build/deployment permissions, and replaces any legacy GitLab references.
Historical CI job execution, reports and downloadable artifacts are omitted from Gitea by owner decision. The immutable GitLab rollback backups retain the original data. CI definitions, settings and secrets stay in protected administrator exports; do not paste secret values here.
<!-- gitlab-to-gitea-ci-conversion:project-30 -->
GitLab CI execution is frozen and Gitea Actions remains disabled. Pipeline conversion is deferred to the owner.
This project used GitLab CI / Auto DevOps without a current CI YAML file. Use its preserved historical configuration and expanded definitions when deciding how to convert it to Gitea Actions.
Before enabling Actions, review the preserved runner requirements, schedules/triggers, permissions, variables/secrets, image publishing and deployment dependencies. Protected exports and original GitLab secrets/backups remain available to the server administrator; secret values must stay out of this issue.
Acceptance: the owner explicitly enables the converted workflow, validates build/deployment permissions, and replaces any legacy GitLab references.
Historical CI job execution, reports and downloadable artifacts are omitted from Gitea by owner decision. The immutable GitLab rollback backups retain the original data. CI definitions, settings and secrets stay in protected administrator exports; do not paste secret values here.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
GitLab CI execution is frozen and Gitea Actions remains disabled. Pipeline conversion is deferred to the owner.
This project used GitLab CI / Auto DevOps without a current CI YAML file. Use its preserved historical configuration and expanded definitions when deciding how to convert it to Gitea Actions.
Before enabling Actions, review the preserved runner requirements, schedules/triggers, permissions, variables/secrets, image publishing and deployment dependencies. Protected exports and original GitLab secrets/backups remain available to the server administrator; secret values must stay out of this issue.
Acceptance: the owner explicitly enables the converted workflow, validates build/deployment permissions, and replaces any legacy GitLab references.
Historical CI job execution, reports and downloadable artifacts are omitted from Gitea by owner decision. The immutable GitLab rollback backups retain the original data. CI definitions, settings and secrets stay in protected administrator exports; do not paste secret values here.