7451 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
Martin von Zweigbergk	de6da1a088	transaction: propagate errors from commit()	2024-11-13 23:05:24 -08:00
Martin von Zweigbergk	73186c1da4	op_heads_store: allow methods to return errors ... This was crashing our server at Google (when attempting to read from a repo that didn't exist).	2024-11-13 23:05:24 -08:00
Martin von Zweigbergk	5b844f630c	cargo: upgrade to sapling-renderdag ... There is now an updated version of `esl01-renderdag` published from the Sapling repo, so let's use that. That lets us remove the `bitflags` 1.x dependency and the `itertools` 0.10.x non-dev dependency.	2024-11-13 09:38:25 -08:00
Remo Senekowitsch	a650af3fcd	completion: improve docs for activation ... It was not clear if users should activate both sets of completions if they wanted the dynamic ones. The shell commands for activating the dynamic completions are aligned with the static version. Users can choose / are responsible themselves to add the activation to their shell config if they want them in every shell instance. For fish specifically, `script | source` is more idiomatic than `source (script | psub)`.	2024-11-13 18:13:54 +01:00
dependabot[bot]	8292d01c77	github: bump github/codeql-action in the github-dependencies group ... Bumps the github-dependencies group with 1 update: [github/codeql-action](https://github.com/github/codeql-action). Updates `github/codeql-action` from 3.27.2 to 3.27.3 - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](9278e42166...396bb3e453) --- updated-dependencies: - dependency-name: github/codeql-action dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>	2024-11-13 15:30:29 +00:00
dependabot[bot]	1e527dd293	cargo: bump serde in the cargo-dependencies group ... Bumps the cargo-dependencies group with 1 update: [serde](https://github.com/serde-rs/serde). Updates `serde` from 1.0.214 to 1.0.215 - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](https://github.com/serde-rs/serde/compare/v1.0.214...v1.0.215) --- updated-dependencies: - dependency-name: serde dependency-type: direct:production update-type: version-update:semver-patch dependency-group: cargo-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>	2024-11-12 23:30:52 +00:00
dependabot[bot]	7f0eae0be8	github: bump github/codeql-action in the github-dependencies group ... Bumps the github-dependencies group with 1 update: [github/codeql-action](https://github.com/github/codeql-action). Updates `github/codeql-action` from 3.27.1 to 3.27.2 - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](4f3212b617...9278e42166) --- updated-dependencies: - dependency-name: github/codeql-action dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>	2024-11-12 15:35:44 -06:00
Yuya Nishihara	7be4904982	tests: fix flakiness in shallow Git repo test ... This test reliably failed if I dropped tv_nsec part from statx(). Since we reload the repo now, several assertions get "fixed". I've added index().has_id() test to clarify that it's still broken.	2024-11-12 20:27:51 +09:00
Benjamin Tan	9ea91dc02a	cli: rebase -b: add support for --insert-after and --insert-before options	2024-11-12 16:38:17 +08:00
Benjamin Tan	1c1117f6fb	tests: modify rebase --after --before test case ... This commit modifies the commit graph used in the `rebase --after --before` test case to add an additional branch of commits for use in tests for `rebase -b` along with `--after --before`.	2024-11-12 16:38:17 +08:00
Benjamin Tan	d6a2034e01	cli: rebase: extract out common print_move_commits_stats function ... This commit extracts out the common code printing out the `MoveCommitsStats` information into a shared function. The printed output was also inconsistent between `-r` and `-s`/`-b` code paths, so I standardized it to say "Rebased ? commits onto destination" for both cases.	2024-11-12 16:04:53 +08:00
Yuya Nishihara	062a1bceb9	local_working_copy: on check out, skip entries conflicting with untracked dirs ... This seems more consistent because file->directory conflicts are skipped.	2024-11-12 16:12:12 +09:00
Yuya Nishihara	f3a75c5c46	local_working_copy: on check out, ignore diff of Git submodule ids ... This is different from skipped paths because the file state has to remain as FileType::GitSubmodule in order to ignore the submodule directory when snapshotting. Fixes #4825.	2024-11-12 16:12:12 +09:00
Yuya Nishihara	4983db563f	local_working_copy: migrate Git submodule test to MergedTreeBuilder ... I also removed tx.commit() because the test doesn't rely on the committed operation.	2024-11-12 16:12:12 +09:00
Benjamin Tan	1aad724798	repo: remove MutableRepo::rebase_descendants_return_map ... This function is merely a simple wrapper around `MutableRepo::rebase_descendants_with_options_return_map`.	2024-11-12 14:00:00 +08:00
Benjamin Tan	44ec7d0ee9	repo: remove MutableRepo::rebase_descendants_with_options ... This function had no callers within the codebase.	2024-11-12 14:00:00 +08:00
Benjamin Tan	cb1e0fbafc	rewrite: rebase_commits_with_options: avoid cloning of new parents	2024-11-12 14:00:00 +08:00
dependabot[bot]	793e9f100f	github: bump github/codeql-action in the github-dependencies group ... Bumps the github-dependencies group with 1 update: [github/codeql-action](https://github.com/github/codeql-action). Updates `github/codeql-action` from 3.27.0 to 3.27.1 - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](662472033e...4f3212b617) --- updated-dependencies: - dependency-name: github/codeql-action dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>	2024-11-11 21:23:15 -06:00
dependabot[bot]	d1261fc829	cargo: bump the cargo-dependencies group with 2 updates ... Bumps the cargo-dependencies group with 2 updates: [rustix](https://github.com/bytecodealliance/rustix) and [thiserror](https://github.com/dtolnay/thiserror). Updates `rustix` from 0.38.39 to 0.38.40 - [Release notes](https://github.com/bytecodealliance/rustix/releases) - [Changelog](https://github.com/bytecodealliance/rustix/blob/main/CHANGELOG.md) - [Commits](https://github.com/bytecodealliance/rustix/compare/v0.38.39...v0.38.40) Updates `thiserror` from 1.0.68 to 1.0.69 - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.68...1.0.69) --- updated-dependencies: - dependency-name: rustix dependency-type: direct:production update-type: version-update:semver-patch dependency-group: cargo-dependencies - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch dependency-group: cargo-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>	2024-11-11 21:23:02 -06:00
Emily	7d9e9a1434	docs: remove trailing whitespace in .md	2024-11-12 01:16:08 +01:00
Emily	f56f07bd54	editorconfig: only skip trimming whitespace for .rs files	2024-11-12 01:16:08 +01:00
Emily	235d57c053	docs: beginnings of an 'editor setup' section	2024-11-12 01:16:08 +01:00
Yuya Nishihara	ce3436b92b	cli: add "absorb" machinery and command ... The destination commits are selected based on annotation, which I think is basically the same as "hg absorb" (except for handling of consecutive hunks.) However, we don't compute a full interleaved delta right now, and the hunks are merged in the same way as "jj squash". This means absorbed hunks might produce conflicts if no context lines exist. Still I think this is more intuitive than selecting destination commits based on patch commutativity. I've left inline comments to the tests where behavior is different from "hg absorb", but these aren't exhaustively checked. Closes #170	2024-11-12 08:26:42 +09:00
Yuya Nishihara	3144a8cb9e	annotate: add line_ranges() and compact_line_ranges() iterator ... They allow callers to test range overlaps with e.g. diff hunks. "jj absorb" will leverage compact_line_ranges().	2024-11-12 08:26:42 +09:00
Yuya Nishihara	077bac8be1	annotate: add low-level function to specify starting file content ... In "jj absorb", we'll need to calculate annotation from the parent tree. It's usually identical to the tree of the parent commit, but this is not true for a merge commit. Since I'm not sure how we'll process conflict trees in general, this patch adds a minimal API to specify a single file content, not a MergedTree.	2024-11-12 08:26:42 +09:00
Yuya Nishihara	85e0a8b068	annotate: add option to not search all ancestors of starting commit ... The primary use case is to exclude immutable commits when calculating line ranges to absorb. For example, "jj absorb" will build annotation of @ revision with domain = mutable().	2024-11-12 08:26:42 +09:00
Remo Senekowitsch	325402dc94	completion: resolve aliases	2024-11-11 21:41:42 +01:00
Ilya Grigoriev	bfbd04b083	cli: document b as a "default alias" ... Unlike other documented aliases, it can be redefined by the user. However, I think it's important for people to be informed that `b` exists. I left `amend`, `unamend`, and `ci` undocumented, since I think we were considering removing or at least discouraging them.	2024-11-11 09:44:18 -08:00
Benjamin Tan	0e67ef9184	rewrite: avoid abandoned commit parent lookup in rebase_commit_with_options ... This is an optimization to avoid fetching the parent commit of an abandoned commit after rebasing, given that it might not even be used.	2024-11-12 01:33:12 +08:00
Benjamin Tan	9bd7e7707f	repo: add docs for MutableRepo::rebase_descendants_* functions	2024-11-12 01:33:12 +08:00
Benjamin Tan	d7f929fefb	repo: group MutableRepo::rebase_descendants_* functions together	2024-11-12 01:33:12 +08:00
Benjamin Tan	18faaf72a3	rewrite: remove DescendantRebaser ... Due to the gradual rewrite to use the `MutableRepo::transform_descendants` API, `DescendantRebaser` is no longer used in `MutableRepo::rebase_descendants`, and is only used (indirectly through `MutableRepo::rebase_descendants_return_map`) in `rewrite::squash_commits`. `DescendantRebaser` is removed since it contains a lot of logic similar to `MutableRepo::transform_descendants`. Instead, `MutableRepo::rebase_descendants_with_options_return_map` is rewritten to use `MutableRepo::transform_descendants` directly, and the other `MutableRepo::rebase_descendants_{return_map,with_options}` functions call `MutableRepo::rebase_descendants_with_options_return_map` directly. `MutableRepo::rebase_descendants_return_rebaser` is also removed.	2024-11-12 01:33:12 +08:00
Benjamin Tan	51675a2c14	cli: include commit summary when attempting to modify an immutable commit ... Previously, attempting to modify an immutable commit only showed the ID of the commit being modified, which wasn't very helpful when trying to figure out which immutable commit is being modified at a quick glance. This commit prints the commit summary as a hint to make it simpler for the user to see what the immutable commit is without having to run `jj show <commit-id>`.	2024-11-12 01:17:41 +08:00
Martin von Zweigbergk	6f38131193	cargo-deny: temporarily allow chrono-english crate ... https://rustsec.org/advisories/RUSTSEC-2024-0395 recommends migrating off od `chrono-english`, but that doesn't seem easy. I've spent a few hours on it already.	2024-11-11 07:04:21 -08:00
Martin von Zweigbergk	02486dc064	fallback: replace use of backoff crate of by own implementation ... https://rustsec.org/advisories/RUSTSEC-2024-0384 says to migrate off of the `instant` crate because it's unmaintained. We depend on it only via the `backoff` crate. That crate also seems unmaintained. So this patch replaces our use of `backoff` by a custom implementation. I initially intended to migrate to the `backon` crate, but that made `lock::tests::lock_concurrent` tests fail. The test case spawns 72 threads (on my machine) and lets them all lock a file, and then it waits 1 millisecond before releasing the file lock. I think the problem is that their version of jitter is implemented as a random addition of up to the initial backoff value. In our case, that means we would add at most a millisecond. The `backoff` crate, on the other hand does it by adding -50% to +50% of the current backoff value. I think that leads to a much better distribution of backoffs, while `backon`'s implementation means that only a few threads can lock the file for each backoff exponent.	2024-11-11 07:04:21 -08:00
Yuya Nishihara	6739dccc6d	templater: add != operator as user would probably expect that it exists	2024-11-10 21:41:24 +09:00
Yuya Nishihara	b556fc6093	templater: add abstraction to implement equality operation per type ... Maybe we can add comparison of ids, commits, etc., but I don't have a practical use case right now. If we add lt/gt, it might make sense to implement them on Timestamp type. I also changed lhs.and_then(..) to (lhs, rhs).map(..) since we don't need short-circuiting behavior here.	2024-11-10 21:41:24 +09:00
Remo Senekowitsch	c9e751ae6e	completion: teach rename about local bookmarks	2024-11-10 07:26:22 +01:00
dploch	5cbd348f2f	config-schema: add missing docs for auto-track	2024-11-09 12:58:01 -05:00
Remo Senekowitsch	db2b5890f8	util: add exec command for arbitrary aliases	2024-11-09 11:49:33 +01:00
Emily	d77ca1526a	cli: reference config settings for 'jj log -T' and 'jj git push -c'	2024-11-09 02:46:00 +01:00
Yuya Nishihara	7d34194502	cli: do not swallow error when checking working copy that became immutable ... .is_err() doesn't always mean the commit is immutable. Fixes #4798	2024-11-09 09:40:29 +09:00
Martin von Zweigbergk	fd271d39ad	cli: make jj desc and jj st aliases hidden ... Visible aliases interfere with shell completion, at least in Fish. For example, `jj des<tab>` stops as `jj desc` without adding a space afterwards, which make me stop for a second and wonder if I need to add more letters. They also show up in the auto-complete menu. I added "[aliases: <name>]" as part of the first line of the help text so the `jj help` output still looks the same.	2024-11-08 13:57:08 -08:00
Martin von Zweigbergk	cd88bafd05	cli: workspace update-stale: set description on recovery commit ... The recover commit we create in some cases (when an operation has been lost) doesn't currently have a description. That makes it easy to miss that it's special.	2024-11-08 12:32:24 -08:00
dploch	41631bc0e6	test_git: fix some clippy ref errors	2024-11-08 13:59:37 -05:00
Martin von Zweigbergk	1240487cb6	next/prev: delete obsolete help text about inferring --edit ... We don't infer `--edit` since 37421583b2.	2024-11-08 10:40:52 -08:00
dependabot[bot]	2aadae14a6	cargo: bump tempfile in the cargo-dependencies group ... Bumps the cargo-dependencies group with 1 update: [tempfile](https://github.com/Stebalien/tempfile). Updates `tempfile` from 3.13.0 to 3.14.0 - [Changelog](https://github.com/Stebalien/tempfile/blob/master/CHANGELOG.md) - [Commits](https://github.com/Stebalien/tempfile/compare/v3.13.0...v3.14.0) --- updated-dependencies: - dependency-name: tempfile dependency-type: direct:production update-type: version-update:semver-minor dependency-group: cargo-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>	2024-11-09 00:32:20 +08:00
Austin Seipp	643d772bab	github: cancel in-progress builds on stale PRs ... When a pull request is pushed multiple times in sequence (e.g. to fix small errors that are noticed post-submission), a backlog of builds ends up needing to be cleared out before your new update can be built. If you push N times, N builds are queued and need to clear out first. This can cause higher latency for *every* PR since the pool of public runners is shared, and in general seems uneconomical and inefficient since 99% of the time you want to build the new version ASAP. Luckily GHA has a universal solution to this: use the `concurrency` directive to group all builds for a PR under a name, and when a new build appears in that group, cancel all builds in the group that are in-progress. Taken from this useful blog post: "Simple trick to save environment and money when using GitHub Actions" https://turso.tech/blog/simple-trick-to-save-environment-and-money-when-using-github-actions Signed-off-by: Austin Seipp <aseipp@pobox.com>	2024-11-08 09:27:42 -06:00
Martin von Zweigbergk	86de9139b3	docs: fix a few typos noticed by automation at Google	2024-11-07 23:04:11 -08:00
Benjamin Tan	d7e06e6462	rebase: allow -r with --skip-emptied	2024-11-08 14:35:17 +08:00