Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support the Sapling identity in aliases #876

Open
bolinfest opened this issue Apr 16, 2024 · 0 comments
Open

Support the Sapling identity in aliases #876

bolinfest opened this issue Apr 16, 2024 · 0 comments

Comments

@bolinfest
Copy link
Contributor

Using the Mercurial docs, I was able to define a sync alias as follows:

[alias]
sync=!$HG pull && $HG rebase -r "draft()" -d master

Based on this:

env["HG"] = util.hgexecutable()

I believe only $HG is supported, though ideally something that reflects the identity would be used instead:

user: &UserIdentity {
cli_name: "sl",
product_name: "Sapling",
long_product_name: "Sapling SCM",
env_prefix: "SL_",
config_user_directory: Some("sapling"),
config_user_files: &["sapling.conf"],
#[cfg(windows)]
config_system_path: r"Sapling\system.conf",
#[cfg(not(windows))]
config_system_path: "/etc/sapling/system.conf",
scripting_env_var: "SL_AUTOMATION",
scripting_config_env_var: "SL_CONFIG_PATH",
scripting_except_env_var: "SL_AUTOMATION_EXCEPT",
},

It would also be good to document this on the Sapling website so users don't have to make guesses based on the old Mercurial docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant