Migrate from codeberg.org to forge.marvin8.zone #26
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/migrate-to-forge-marvin8-zone"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Migrate taibai from Codeberg.org (
MarvinsMastodonTools/taibai) to forge.marvin8.zone (marvin8/taibai).Changes
originupdated toforge-marvin8:/marvin8/taibai.git,forge-piremote added,clauderemote removedcodeberg.org/MarvinsMastodonTools/taibaitoforge.marvin8.zone/marvin8/taibaicodeberg.org/MarvinsMastodonTools/longweitoforge.marvin8.zone/marvin8/longwei(already migrated)forge.marvin8.zone/marvin8/wuming@main(already migrated)forge.marvin8.zone/marvin8/zaojun(already migrated)codeberg-small-lazy→suanniacross all workflowsmarvinsmastodontools.codeberg.page/taibai/latest/→taibai.marvin8.zone/latest/docs/javascripts/redirect.js(codeberg.page → taibai.marvin8.zone redirect)claudetoforge-piremoteWuMing
Found 2 issue(s). See inline comments below.
@ -0,0 +12,4 @@runs-on: zhuiriif: github.event_name == 'pull_request'steps:- uses: https://forge.marvin8.zone/marvin8/wuming@mainsecurity [HIGH]
External action referenced via branch '@main' instead of a pinned commit SHA. This allows arbitrary code changes to be executed without review, which could lead to credential exfiltration (forge.token and wuming_deepseek_key are passed to it). Pin to a specific commit hash or use a verified tag. (A08: Software and Data Integrity Failures)
@ -0,0 +88,4 @@run: |git config user.email "ci@forgejo"git config user.name "Forgejo Actions"git remote set-url origin https://x-token-auth:$FORGEJO_TOKEN@forge.marvin8.zone/${{ github.repository }}.gitsecurity [MEDIUM]
Access token passed directly in a shell command may be exposed in build logs if CI masking fails. Use a credential helper or environment variable with Git's credential store instead of embedding the token in the URL. (A09: Security Logging and Monitoring Failures)
This PR is too large to review automatically (2272 lines; limit is 2000). Please consider splitting it into smaller PRs.
This PR is too large to review automatically (2438 lines; limit is 2000). Please consider splitting it into smaller PRs.