gitbutlerapp/gitbutler
1
1
Fork 0
mirror of https://github.com/gitbutlerapp/gitbutler.git synced 2024-12-24 18:12:48 +03:00
Code Issues Packages Projects Releases Wiki Activity
06edec70cb
gitbutler/crates/gitbutler-branch-actions/Cargo.toml

59 lines
1.6 KiB
TOML
Raw Normal View History

start moving virtual_branches to separate crate We want to move towards having each functional domain in a separate crate. The main benefit of that for our project is that this will enforce a unidirectional dependency graph (i.e. no cycles). Starting off with virutal_branches - a lot of the implementation is still in core (i.e. virtual.rs), that will be moved in a separate PR. Furthermore, the virtual branches controller (as well as virtual.rs) contain functions not directly related to branches (e.g. commit reordering etc). That will be furthe separate in a crate.
2024-07-07 14:32:35 +03:00
[package]
rename gitbutler-virtual to gitbutler-branch-actions This is to establish a patter of which crates represent a higher level logic
2024-07-10 15:49:48 +03:00
name = "gitbutler-branch-actions"
start moving virtual_branches to separate crate We want to move towards having each functional domain in a separate crate. The main benefit of that for our project is that this will enforce a unidirectional dependency graph (i.e. no cycles). Starting off with virutal_branches - a lot of the implementation is still in core (i.e. virtual.rs), that will be moved in a separate PR. Furthermore, the virtual branches controller (as well as virtual.rs) contain functions not directly related to branches (e.g. commit reordering etc). That will be furthe separate in a crate.
2024-07-07 14:32:35 +03:00
version = "0.0.0"
edition = "2021"
authors = ["GitButler <gitbutler@gitbutler.com>"]
publish = false
[dependencies]
add `--trace` to enable tracing This is useful to get simple performance metrics.
2024-08-11 15:55:00 +03:00
tracing.workspace = true
start moving virtual_branches to separate crate We want to move towards having each functional domain in a separate crate. The main benefit of that for our project is that this will enforce a unidirectional dependency graph (i.e. no cycles). Starting off with virutal_branches - a lot of the implementation is still in core (i.e. virtual.rs), that will be moved in a separate PR. Furthermore, the virtual branches controller (as well as virtual.rs) contain functions not directly related to branches (e.g. commit reordering etc). That will be furthe separate in a crate.
2024-07-07 14:32:35 +03:00
anyhow = "1.0.86"
git2.workspace = true
use `gix` powered merge-base for performance and reduced memory consumption
2024-08-26 17:08:06 +03:00
gix = { workspace = true, features = ["blob-diff", "revision"] }
start moving virtual_branches to separate crate We want to move towards having each functional domain in a separate crate. The main benefit of that for our project is that this will enforce a unidirectional dependency graph (i.e. no cycles). Starting off with virutal_branches - a lot of the implementation is still in core (i.e. virtual.rs), that will be moved in a separate PR. Furthermore, the virtual branches controller (as well as virtual.rs) contain functions not directly related to branches (e.g. commit reordering etc). That will be furthe separate in a crate.
2024-07-07 14:32:35 +03:00
tokio.workspace = true
move oplog to its own crate This protects us from cyclic dependencies. Unfortunatelly as part of this, i had to introduce the imp Project as trait implementations since now Project is foreign
2024-07-07 21:00:01 +03:00
gitbutler-oplog.workspace = true
move rebase module to a new repo crate
2024-07-08 01:27:17 +03:00
gitbutler-repo.workspace = true
extract user as its own crate out of core
2024-07-08 19:58:29 +03:00
gitbutler-user.workspace = true
move branch related modules to separate crate Unfortunatelly diff and branch types form a cyclical dependency via the "HunkLock" type. This will have to be refactored as a followup
2024-07-09 01:10:55 +03:00
gitbutler-branch.workspace = true
move reference module from core to its own crate
2024-07-09 02:14:28 +03:00
gitbutler-reference.workspace = true
move error module to it's own crate
2024-07-09 12:13:39 +03:00
gitbutler-error.workspace = true
move serde functions into their own crate
2024-07-09 12:49:12 +03:00
gitbutler-serde.workspace = true
move id module to its own crate
2024-07-09 13:39:18 +03:00
gitbutler-id.workspace = true
move time module to it's own crate
2024-07-09 14:08:12 +03:00
gitbutler-time.workspace = true
extract commit crate out of core
2024-07-09 14:19:49 +03:00
gitbutler-commit.workspace = true
move url module to a separate crate this code is awful - lets nuke it asap
2024-07-09 16:29:24 +03:00
gitbutler-url.workspace = true
assure `conflicts::mark()` writes its file atomically That way it can't be observed half-written, or remain in a half-written state in case of crash.
2024-07-15 09:08:38 +03:00
gitbutler-fs.workspace = true
move hunk and diff code to a separate crate, out of the branch one
2024-07-17 21:16:48 +03:00
gitbutler-diff.workspace = true
Introduce operating modes
2024-07-29 14:19:38 +03:00
gitbutler-operating-modes.workspace = true
Split branch creation and deletion into their own home
2024-07-09 17:43:58 +03:00
serde = { workspace = true, features = ["std"] }
Revert "Revert "Merge pull request #4652 from gitbutlerapp/git2-to-gix"" This reverts commit 88496e6219078035a974d8dbf563a8c0c1528b3b.
2024-08-09 11:30:52 +03:00
bstr.workspace = true
Bump the rust-updates group across 1 directory with 8 updates Bumps the rust-updates group with 8 updates in the / directory: | Package | From | To | | --- | --- | --- | | [serde](https://github.com/serde-rs/serde) | `1.0.203` | `1.0.204` | | [thiserror](https://github.com/dtolnay/thiserror) | `1.0.61` | `1.0.62` | | [console-subscriber](https://github.com/tokio-rs/console) | `0.2.0` | `0.3.0` | | [open](https://github.com/Byron/open-rs) | `5.2.0` | `5.3.0` | | [sysinfo](https://github.com/GuillaumeGomez/sysinfo) | `0.30.12` | `0.30.13` | | [rstest](https://github.com/la10736/rstest) | `0.20.0` | `0.21.0` | | [clap](https://github.com/clap-rs/clap) | `4.5.8` | `4.5.9` | | [diffy](https://github.com/bmwill/diffy) | `0.3.0` | `0.4.0` | Updates `serde` from 1.0.203 to 1.0.204 - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.203...v1.0.204) Updates `thiserror` from 1.0.61 to 1.0.62 - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.61...1.0.62) Updates `console-subscriber` from 0.2.0 to 0.3.0 - [Release notes](https://github.com/tokio-rs/console/releases) - [Changelog](https://github.com/tokio-rs/console/blob/main/release-plz.toml) - [Commits](https://github.com/tokio-rs/console/compare/console-subscriber-v0.2.0...console-subscriber-v0.3.0) Updates `open` from 5.2.0 to 5.3.0 - [Release notes](https://github.com/Byron/open-rs/releases) - [Changelog](https://github.com/Byron/open-rs/blob/main/changelog.md) - [Commits](https://github.com/Byron/open-rs/compare/v5.2.0...v5.3.0) Updates `sysinfo` from 0.30.12 to 0.30.13 - [Changelog](https://github.com/GuillaumeGomez/sysinfo/blob/master/CHANGELOG.md) - [Commits](https://github.com/GuillaumeGomez/sysinfo/commits/v0.30.13) Updates `rstest` from 0.20.0 to 0.21.0 - [Release notes](https://github.com/la10736/rstest/releases) - [Changelog](https://github.com/la10736/rstest/blob/master/CHANGELOG.md) - [Commits](https://github.com/la10736/rstest/compare/v0.20.0...v0.21.0) Updates `clap` from 4.5.8 to 4.5.9 - [Release notes](https://github.com/clap-rs/clap/releases) - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md) - [Commits](https://github.com/clap-rs/clap/compare/clap_complete-v4.5.8...v4.5.9) Updates `diffy` from 0.3.0 to 0.4.0 - [Changelog](https://github.com/bmwill/diffy/blob/master/CHANGELOG.md) - [Commits](https://github.com/bmwill/diffy/commits) --- updated-dependencies: - dependency-name: serde dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-updates - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-updates - dependency-name: console-subscriber dependency-type: direct:production update-type: version-update:semver-minor dependency-group: rust-updates - dependency-name: open dependency-type: direct:production update-type: version-update:semver-minor dependency-group: rust-updates - dependency-name: sysinfo dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-updates - dependency-name: rstest dependency-type: direct:production update-type: version-update:semver-minor dependency-group: rust-updates - dependency-name: clap dependency-type: direct:production update-type: version-update:semver-patch dependency-group: rust-updates - dependency-name: diffy dependency-type: direct:production update-type: version-update:semver-minor dependency-group: rust-updates ... Signed-off-by: dependabot[bot] <support@github.com>
2024-07-16 18:22:10 +03:00
diffy = "0.4.0"
move virtual outside of core
2024-07-07 16:51:07 +03:00
hex = "0.4.3"
regex = "1.10"
git2-hooks = "0.3"
url = { version = "2.5.2", features = ["serde"] }
md5 = "0.7.0"
move conflicts module to branches crate
2024-07-07 23:58:48 +03:00
itertools = "0.13"
move ProjectRepo into its own crate This type currently acts more or less like a command context that lives for the duration of the request. Regardless of if we wanna keep this pattern or not, separating it out helps us split up core
2024-07-08 14:23:03 +03:00
gitbutler-command-context.workspace = true
move project module in a separate gitbutler-project crate
2024-07-08 16:33:26 +03:00
gitbutler-project.workspace = true
combine the assets proxying implementaiton in one file Now it's only used in one place
2024-07-08 19:23:51 +03:00
urlencoding = "2.1.3"
reqwest = { version = "0.12.4", features = ["json"] }
start moving virtual_branches to separate crate We want to move towards having each functional domain in a separate crate. The main benefit of that for our project is that this will enforce a unidirectional dependency graph (i.e. no cycles). Starting off with virutal_branches - a lot of the implementation is still in core (i.e. virtual.rs), that will be moved in a separate PR. Furthermore, the virtual branches controller (as well as virtual.rs) contain functions not directly related to branches (e.g. commit reordering etc). That will be furthe separate in a crate.
2024-07-07 14:32:35 +03:00
[dev-dependencies]
once_cell = "1.19"
pretty_assertions = "1.4"
gitbutler-testsupport.workspace = true
enable max performance to be competitive in object database access. This is very relevant for tree-diffing performance, and more could be tuned here like pack-cache sizes and object cache sizes.
2024-08-13 15:10:17 +03:00
gix = { workspace = true, features = ["max-performance"] }
start moving virtual_branches to separate crate We want to move towards having each functional domain in a separate crate. The main benefit of that for our project is that this will enforce a unidirectional dependency graph (i.e. no cycles). Starting off with virutal_branches - a lot of the implementation is still in core (i.e. virtual.rs), that will be moved in a separate PR. Furthermore, the virtual branches controller (as well as virtual.rs) contain functions not directly related to branches (e.g. commit reordering etc). That will be furthe separate in a crate.
2024-07-07 14:32:35 +03:00
gitbutler-git = { workspace = true, features = ["test-askpass-path"] }
glob = "0.3.1"
serial_test = "3.1.1"
tempfile = "3.10"
add benchmark for branch-listing
2024-08-06 21:55:20 +03:00
criterion = "0.5.1"
[features]
## Only enabled when benchmark runs are performed.
benches = ["gitbutler-git/benches"]
[[bench]]
name = "branches"
harness = false
Reference in New Issue Copy Permalink