A Scalable, User-Friendly Source Control System.
GPL-2.0 License
Bot releases are visible (Hide)
Published by github-actions[bot] 9 months ago
Published by github-actions[bot] 11 months ago
Below are the major changes of this release:
sl
now runs as a single binary on all platformschg
was disabled on macOSThe full list of ISL changelog is here:
sl isl
on the command line to open a dedicated OS window instead of just a browser tabFull Changelog: https://github.com/facebook/sapling/compare/0.2.20230523-092610+f12b7eee...0.2.20231113-145254+995db0d6
Published by github-actions[bot] 11 months ago
Published by github-actions[bot] 11 months ago
Published by github-actions[bot] 12 months ago
Below are the major changes of this release:
sl
now runs as a single binary on all platformschg
was disabled on macOSThe full list of ISL changelog is here:
sl isl
on the command line to open a dedicated OS window instead of just a browser tabFull Changelog: https://github.com/facebook/sapling/compare/0.2.20230523-092610+f12b7eee...0.2.20231109-183451+14d92511
Published by github-actions[bot] 12 months ago
Published by github-actions[bot] over 1 year ago
--no-root-relative
) handling for the status command (https://github.com/facebook/sapling/commit/bb37a6e0c51c22ae4487bd2dbdc1c561158ceb2c)sl {hide, unhide, show}
(https://github.com/facebook/sapling/commit/9f2cfe4af0e092d97249e2aed259d39fc9897377)See Sapling VS Code extension changelog for changes to the sl web UI
Full Changelog: https://github.com/facebook/sapling/compare/0.2.20230426-145232+7ea1f245...0.2.20230523-092610+f12b7eee
Published by github-actions[bot] over 1 year ago
Note that our version numbers changed to be compatible with PEP 440 in #606
See Sapling VS Code extension changelog for changes to the sl web UI
Full Changelog: https://github.com/facebook/sapling/compare/0.2.20230330-193452-h69692651...0.2.20230426-145232+7ea1f245
Published by github-actions[bot] over 1 year ago
This release includes fixes in various areas:
githelp
to properly include --dirs
for clean
command (#575).Published by github-actions[bot] over 1 year ago
This release mainly brings better file move detection as well as various improvements to the sl pr submit
command
sl pr submit
(https://github.com/facebook/sapling/pull/427). The ReviewStack message is auto disabled for single-commit stack.sl
not in PATH (71d6e67afd)sl pr submit
to not try to update closed PRs (5a354f7cd6)sl pr submit
to use "overlapping" PR strategy by default (a05035903a)sl pr submit
crash using non-placeholder issue approach (18a1987638)sl init --git
on a non-empty directory.sl web
just after building with make oss
.Published by github-actions[bot] over 1 year ago
This release focuses on bug fixes and improvements around the pr and ghstack commands.
sl pr list
did not work correctly in combination with chg
(https://github.com/facebook/sapling/commit/a1187e8766f4c55bdbf64d369be2ed766641636d).sl pr pull
to throw an appropriate error if no args were specified (https://github.com/facebook/sapling/pull/357).sl clone
silently failed for some repositories (https://github.com/facebook/sapling/issues/375) with (https://github.com/facebook/sapling/pull/386).sl goto pr123
, sl log -r PR456
should work, even without having to manually download some pull request. Using sl pr pull is still necessary, however, if one wants to get the most recent version of some PR.sl ghstack land
to properly rebase, avoiding spurious “non-fast forward” push errors (https://github.com/facebook/sapling/commit/ebbe7d8d7d71bc144d570f515b5c01da477b4d62), resolving https://github.com/facebook/sapling/issues/333 .Published by github-actions[bot] over 1 year ago
Published by github-actions[bot] almost 2 years ago
This release focuses on correctness issues around handling submodules as well as various usability/workflow improvements.
sl pr
command:
sl pr submit
explicitly: submit
is no longer the default subcommand for sl pr
, but s
can be used as an alias for submit
: https://github.com/facebook/sapling/commit/56b5e3e18070207881caeec9b7e0fc96efef4cae
sl pr submit
command now supports a --draft
flag: https://github.com/facebook/sapling/commit/6e9c3d7a6671839601c8064f0ae5fc2f3e2d361c
sl pr pull
subcommand: if you use sl pr submit
to create a stack of pull requests, now you can use sl pr pull
to import the stack back into your working copy: https://github.com/facebook/sapling/commit/d09d5985c2731df54269169bf8500bd31573baac
sl pr list
subcommand that mirrors the functionality of gh pr list
: https://github.com/facebook/sapling/commit/8f0a657a00bb24827cb26bc69e345894861a9a38
sl --config github.pr_workflow=single pr submit
. See https://github.com/facebook/sapling/issues/302 and https://github.com/facebook/sapling/commit/166e2640d353e67317302f5f998f20c791464402 for details.sl pr submit
now appends the stack information to the end of the pull request body instead of prepending it to the top: https://github.com/facebook/sapling/commit/8910d18fe82b791127d62ddfdf631fd474a6f6f3
sl pr submit
is now guaranteed to match the PR number: https://github.com/facebook/sapling/commit/e77e67bba710bc6665a4cc9119bc01303ff4509b
[email protected]:git/git-reference
) are now supported for remote names: https://github.com/facebook/sapling/commit/67fa8488e150513d21eedc66b37724d00f2034a9
sl clone --git <URL> --updaterev <branch/commit>
can now be used to clone a specific branch or commit: https://github.com/facebook/sapling/commit/9804c66bb8190a5ab4566c576db391ebe34c2d6b
sl rebase -b
was reworked for better selecting branching points by avoiding public commits (reverse rebase now works): https://github.com/facebook/sapling/commit/96b767efde6a59dbff31d2808736102b3929067a
sl bookmark --remote
can be used to list remote branches. Further, sl bookmark --remote-path myfork --remote tags
will list tags from remote myfork
:git.committer
config option when running a command. For example, sl --config git.committer="User <[email protected]>" amend
would update the committer for the current commit to User <[email protected]>
. Though note that if git.committer
is not set, the value defaults to the ui.username
config. This means that sl metaedit --user IDENTITY
will not update the committer to IDENTITY
if the git.committer
config is not set, but sl metaedit --config ui.username=IDENTITY --user IDENTITY
would. See https://github.com/facebook/sapling/commit/7f88efd7434720f54f36815b53ba3fe7a47cfb5a for details.gdbm
in the Python code, that was causing crashes for some users: https://github.com/facebook/sapling/commit/cfbb6a256b94c6e755db02658ef1a4312303bee6
Published by github-actions[bot] almost 2 years ago
Published by github-actions[bot] almost 2 years ago
Published by github-actions[bot] almost 2 years ago
Published by github-actions[bot] almost 2 years ago
Published by github-actions[bot] almost 2 years ago
Published by github-actions[bot] almost 2 years ago