Forks-sync

Latest version: v4.2.2

Safety actively analyzes 688087 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 3

2.2.0

- Removed the `branch` flag and functionality as it was causing issues and inconsistencies when cloning/rebasing and branches didn't match up. This became especially prevelant when repos started changing from master to main. Now, we will retrieve the default branch from the parent repo (upstream) and rebase against that. This ensures consistency and safety
- Changed clone depth from 10 to 1

2.1.0

- Renamed project from `Forks` to `Forks Sync`, usage and command names however were already that and did not change. This brings the documentation and GitHub references inline with the published package
- Fixed a bug that would attempt to rebase all your org repos unintentionally, now there are checks to ensure the repo belongs to the same person whose GitHub token is used
- Removed references of `master` branch and replaced with `main`
- Added a flag where you can specify the name of your branches (closes 3)
- Switched from Travis CI to GitHub Actions

2.0.0

- Added unit tests and test coverage
- Added a Makefile
- Added a CHANGELOG
- Automated releasing via Travis to PyPi
- Updated documentation
- Changed command line invocation from `forks` to `forks-sync`
- Refactored the entire codebase to use smaller units
- Bug fixes
- Added logging, log file rollovers

1.0.0

- Initial release

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.