Baltasar Dinis 64ea8bee47 git: reject remotes with forward slashes ... Although this behaviour is accepted by git, it's a degenerate case. Especially because we implicitely rely on being able to parse out the remote from the refname (i.e., `refs/remotes/<remote>/<branch>`). Branches can have forward slashes, but if remotes can also have them, parsing the refname becomes ambiguous, and a pain. Especially because it would be totally legal to have a branch "c" on remote "a/b" and a branch "b" on remote "a". Fixes #5731		2025-02-18 07:10:01 +00:00
..
examples	examples: use settings_for_new_workspace() when initializing workspace	2025-01-06 21:15:28 +09:00
src	git: reject remotes with forward slashes	2025-02-18 07:10:01 +00:00
testing	merge_tools: add "$marker_length" variable	2024-12-23 08:42:10 -06:00
tests	git: reject remotes with forward slashes	2025-02-18 07:10:01 +00:00
build.rs	build: fix cargo publish by symlinking cli/docs->docs	2024-11-05 17:37:14 -08:00
Cargo.toml	cli/tests: add gitoxide helpers	2025-02-11 13:46:25 +00:00
docs	build: fix cargo publish by symlinking cli/docs->docs	2024-11-05 17:37:14 -08:00
LICENSE