Repository navigation
chore(deps): update requests requirement from >=2.31.0 to >=2.33.1 - #16
Closed
dependabot[bot] wants to merge 76 commits into
Closed
dependabot[bot] wants to merge 76 commits into
dependabot[bot] wants to merge 76 commits into
Conversation
added 30 commits
April 10, 2026 15:07
Approved design for v2: adapter pattern, multi-source support, dry run, filtering, parallel migrations, resume-on-failure, rich logging.
- Align create_mirror signature across BaseAdapter and all stubs (uid/auth params) - Fix user-mode listing to use auth-based endpoint, not destination org presence - Use _api_delay between paginated GitHub requests (was configured but ignored) - Guard repo_url=None in migrator when mode=repo - Add per-mode CLI validation with clear error messages - Remove gitlab/bitbucket from --source choices until adapters are implemented
- Add platform_name class attribute to BaseAdapter
- Remove uid/auth_username/auth_token from create_mirror abstract signature; use **kwargs
- Add non-abstract fetch_one_repo() defaulting to NotImplementedError
- Add non-abstract prepare_destination() returning {} by default
- Remove abstract delete_org from BaseAdapter (demoted to concrete Gitea method)
- Update GitLab and Bitbucket stubs: drop delete_org, fix create_mirror signature, add platform_name
Centralises env-var reading and validation for all platforms (github, gitea, gitlab, bitbucket, forgejo). Includes GITEA_TOKEN→ACCESS_TOKEN fallback for backward compat and 13 new tests covering all 5 scenarios.
Update GitHubAdapter constructor to accept config dict, add platform_name, and implement create_mirror via POST API + git clone --mirror + push --mirror.
…ination - Constructor now takes config: dict with url/token keys instead of positional args - Add platform_name = "gitea" class attribute - create_mirror reads uid/auth_username/auth_token from **kwargs - Implement prepare_destination: ensures org exists, returns uid in dict - Update main.py and test_gitea.py to use config dict constructor
Prints count of deleted and failed repos after org deletion so the user gets feedback instead of silent completion.
When migrating a single repo with -u <org>, dest_org was never set (only -o mapped to dest_org), causing repos to land under the authenticated user instead of the intended org.
Gitea creates a repo entry before validating ALLOWED_DOMAINS, leaving a dangling mirror with no clone URL on failure. Delete it when detected.
Credentials were only injected for private repos and required a non-empty auth_username — both conditions could silently drop the token. Now passes credentials whenever a token is available, defaulting username to 'oauth2'. Also surfaces the actual Gitea response body on 422 instead of a hardcoded message, making real errors visible.
docker-compose.yml only forwarded GITHUB_TOKEN, ACCESS_TOKEN, and GITEA_URL, silently dropping GITEA_TOKEN and all other platform credentials. Consolidate into a shared anchor covering all supported platforms.
prepare_destination returned auth_token: "" and auth_username: "", causing migrator.py's setdefault to skip injecting the real source token (setdefault won't overwrite an existing key, even empty). Removing these fields lets the source token flow through correctly.
Add .env*, *.pem, *.key, *.crt, and .claude/ to both .gitignore and .dockerignore to prevent accidental commit or inclusion of secrets and dev-tool configuration in Docker images.
SECURITY.md defines scope, GitHub private vuln reporting, and response timeline. CONTRIBUTING.md covers dev setup, test commands, adapter authoring checklist, and bug reporting path.
When git push --mirror fails, stderr may echo the push URL which contains the embedded token or password. Scrub the credential before raising RuntimeError so it never surfaces in logs or the summary table.
- Accurate platform support matrix (GitHub, GitLab, Bitbucket, Gitea, Forgejo) - Full environment variable reference for all platforms - Complete flag documentation including LFS, releases, cleanup-action, disable-workflows, ignore-repos - Examples for every major platform combination and feature - Updated project structure and troubleshooting section - Remove stale roadmap items (all shipped)
- Rename package directory github2gitea/ → gitporter/ - Update all imports across main.py and test suite - Update README, CONTRIBUTING, CLAUDE.md references - Update clone URL to github.com/KingPin/GitPorter - Update git remote to new repo location
The python:3.12-slim base image ships without git, which silently broke all subprocess-based mirror operations (GitHub, GitLab, Bitbucket dests). Also: - Add non-root 'gitporter' user (uid 1000) for container security - Add env_file (.env, optional) so credentials can be loaded from a .env file without manual exports - Tag built image as gitporter:latest - Gate test service behind --profile test so it doesn't start on docker compose up
Builds linux/amd64, linux/arm64, linux/arm/v7 on every push to master and on version tags. PRs build but do not push. Image published to ghcr.io/kingpin/gitporter with tags: - latest (master branch) - x.y.z (semver tag) - x.y (semver major.minor) - sha-<hash> (every build) Uses GitHub Actions cache for layer reuse across builds.
Show pre-built image as the primary path (docker pull + docker run), with build-from-source as the secondary option. Includes SHA pin example.
Two scan jobs: - image-scan: runs after Docker workflow completes and on weekly schedule. Scans ghcr.io/kingpin/gitporter:latest for OS and library CVEs. - fs-scan: runs on PRs, scans source/Dockerfile/requirements for vulnerabilities and misconfigs before merge. Both jobs upload SARIF results to the GitHub Security tab. Filters to CRITICAL and HIGH; ignores unfixed vulnerabilities.
Weekly PRs on Monday 06:00 UTC for: - Python packages (requirements.txt) - GitHub Actions (workflow action versions) - Docker base image (python:3.12-slim)
aquasecurity/trivy-action had a brief supply chain compromise; pinning to the full commit SHA (57a97c7e) prevents tag-based substitution attacks. Also updates from 0.28.0 to v0.35.0 (latest as of 2026-03-20).
- actions/checkout v4 → v6 - docker/setup-qemu-action v3 → v4 - docker/setup-buildx-action v3 → v4 - docker/login-action v3 → v4 - docker/metadata-action v5 → v6 - docker/build-push-action v6 → v7 - github/codeql-action v3 → v4 All Docker actions move to Node 24 runtime. Supersedes Dependabot PRs #3 #4 #5 #7 #8 #9 #10.
…#12) * fix(ci): guard SARIF upload when Trivy scan fails before writing file Add continue-on-error to Trivy steps and gate upload on hashFiles() so the workflow doesn't error when trivy-results.sarif is never created. * fix(ci): remove continue-on-error and unused step ids from trivy workflow Copilot review: continue-on-error masked real scanner failures (network, action errors) making the job green when scans never ran. The hashFiles() guard on the upload step is sufficient — Trivy step failures now propagate correctly while the SARIF upload is still skipped when no file was written. --------- Co-authored-by: kingpin <kingpin@localhost>
github.repository_owner preserves case (KingPin), but GHCR requires
lowercase. Use ${GITHUB_REPOSITORY_OWNER,,} bash expansion to set
OWNER_LC env var safely, then reference it in the image-ref.
Co-authored-by: kingpin <kingpin@localhost>
Updates the requirements on [requests](https://github.com/psf/requests) to permit the latest version. - [Release notes](https://github.com/psf/requests/releases) - [Changelog](https://github.com/psf/requests/blob/main/HISTORY.md) - [Commits](psf/requests@v2.31.0...v2.33.1) --- updated-dependencies: - dependency-name: requests dependency-version: 2.33.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the requirements on requests to permit the latest version.
Release notes
Sourced from requests's releases.
Changelog
Sourced from requests's changelog.
... (truncated)
Commits
111d2b7v2.33.1f0198e6Fix malformed value parsing for Content-Type (#7309)bc7dd0fFix cosmetic header validity parsing regex (#7308)4443b1aFix unintended test extra (#7306)389eea5Cleanup extracted file after extract_zipped_path test (#7305)7407309Packaging: DRY out extras definition (#7277)bc04dfdv2.33.066d21cbMerge commit from fork8b9bc8fMove badges to top of README (#7293)e331a28Remove unused extraction call (#7292)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)