facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-10-12 01:39:21 +03:00
Code Issues Projects Releases Wiki Activity
3293cc8526
sapling/tests/test-disable-bad-features.t

51 lines
1.2 KiB
Perl
Raw Normal View History

tweakdefaults: move allowmerge to core Summary: Let's start moving tweakdefaults things into core. Since we set the config in our rc files, I've renamed it. Reviewed By: ikostia Differential Revision: D10306236 fbshipit-source-id: 9a6b3bf7e22d8faf7b53446021660bb0923cf666
2018-10-15 17:24:54 +03:00
Test various flags to turn off bad hg features.
$ newrepo
$ drawdag <<'EOS'
> A
> EOS
$ hg up -Cq $A
tweakdefaults: port allowbranches to core Summary: Note that this is more aggressive than the tweakdefaults version; it doesn't allow named branches to be created or listed at all with the config set. As we want to delete named branches entirely, this seems reasonable. I ported the `--new` flag, but made it optional, to make it easier to support both the core and tweakdefaults callers. Saurabh Singh and I chatted with the releng team (Craig). **tldr:** we can remove named branches from the UI but should keep the innards for now Today the releng team doesn't make any branches (#continuous), but in the near-term future, they might either: - create remote bookmarks in hg (similar to fbsource) - create branches in SVN (which are then synced as hg branches by hgsubversion) - We'll leave all the hgsubversion code to do this alone, just remove user-facing entry points - They'll also need to be able to query for a commit's branch (`hg log -T '{branch}'` will still work) - Once www is on hg, this possibility goes away and we can kill named branches for good Reviewed By: ikostia Differential Revision: D10401485 fbshipit-source-id: 6f2f3ae28af249bae1fdf782eb14fe7bfc472bb7
2018-10-16 19:23:18 +03:00
Test disabling the `hg merge` command:
tweakdefaults: move allowmerge to core Summary: Let's start moving tweakdefaults things into core. Since we set the config in our rc files, I've renamed it. Reviewed By: ikostia Differential Revision: D10306236 fbshipit-source-id: 9a6b3bf7e22d8faf7b53446021660bb0923cf666
2018-10-15 17:24:54 +03:00
$ hg merge
abort: nothing to merge
[255]
$ setconfig ui.allowmerge=False
$ hg merge
abort: merging is not supported for this repository
(use rebase instead)
[255]
tweakdefaults: move allowtags to core (as ui.allowtags) Summary: NB: `hg tags` still prints out all tags, just with a warning first. Maybe we could disable that entirely too while we're here. Reviewed By: ikostia Differential Revision: D10314175 fbshipit-source-id: 603a4dc46e05337189934803a18eef1188a02272
2018-10-15 18:02:29 +03:00
Test disabling the `hg tag` command:
$ hg tag foo
$ hg tags
tip 1:9b0f5d3c138d
foo 0:426bada5c675
$ setconfig ui.allowtags=False
$ hg tag foo2
abort: new tags are disabled in this repository
[255]
$ hg tags
abort: tags are disabled in this repository
[255]
tweakdefaults: port allowbranches to core Summary: Note that this is more aggressive than the tweakdefaults version; it doesn't allow named branches to be created or listed at all with the config set. As we want to delete named branches entirely, this seems reasonable. I ported the `--new` flag, but made it optional, to make it easier to support both the core and tweakdefaults callers. Saurabh Singh and I chatted with the releng team (Craig). **tldr:** we can remove named branches from the UI but should keep the innards for now Today the releng team doesn't make any branches (#continuous), but in the near-term future, they might either: - create remote bookmarks in hg (similar to fbsource) - create branches in SVN (which are then synced as hg branches by hgsubversion) - We'll leave all the hgsubversion code to do this alone, just remove user-facing entry points - They'll also need to be able to query for a commit's branch (`hg log -T '{branch}'` will still work) - Once www is on hg, this possibility goes away and we can kill named branches for good Reviewed By: ikostia Differential Revision: D10401485 fbshipit-source-id: 6f2f3ae28af249bae1fdf782eb14fe7bfc472bb7
2018-10-16 19:23:18 +03:00
Test disabling the `hg branch` commands:
$ hg branch
default
$ setconfig ui.allowbranches=False
$ hg branch foo
abort: named branches are disabled in this repository
(use bookmarks instead)
[255]
$ setconfig ui.disallowedbrancheshint="use bookmarks instead! see docs"
$ hg branch -C
abort: named branches are disabled in this repository
(use bookmarks instead! see docs)
[255]
$ hg branches
abort: named branches are disabled in this repository
(use bookmarks instead! see docs)
[255]
branch: allow read-only operation Summary: Sadly `buck test` runs `hg branch` and it breaks. Reviewed By: DurhamG Differential Revision: D10458543 fbshipit-source-id: 15da7d9c45e4740fc8aa0c4f57d304bef320db6b
2018-10-19 05:51:53 +03:00
$ hg branch
default
Reference in New Issue Copy Permalink