facebook/sapling
1
1
Fork 0
mirror of https://github.com/facebook/sapling.git synced 2024-10-09 00:14:35 +03:00
Code Issues Projects Releases Wiki Activity
d4a19306ed
sapling/eden/scm/tests/test-remotenames-pushto-pathandname.t

58 lines
1.5 KiB
Perl
Raw Normal View History

tests: enable chg for 572 tests Summary: Add `#chg-compatible` to 572 tests that seem to pass with chg enabled. This should make them run faster. Reviewed By: xavierd Differential Revision: D18870507 fbshipit-source-id: fe895e733efffc9286cd3d17c7a156c803124395
2019-12-10 02:24:31 +03:00
#chg-compatible
treemanifest: enable treemanifest by default in tests Summary: Now that all our repos are treemanifest, let's enable the extension by default in tests. Once we're certain no one needs it in production we'll also make it the default in core Mercurial. This diff includes a minor fix in treemanifest to be aware of always-enabled extensions. It won't matter until we actually add treemanifest to the list of default enabled extensions, but I caught this while testing things. Reviewed By: ikostia Differential Revision: D15030253 fbshipit-source-id: d8361f915928b6ad90665e6ed330c1df5c8d8d86
2019-05-28 13:12:27 +03:00
$ setconfig extensions.treemanifest=!
push: add possibility to prohibit pushing to certain bookmarks One of the goals is to prevent situations when users push to default/something where default is one of the paths (or a rename of one). Had we not prohibited this, hg push would ask user to run it with --create and later create a new remote bookmark with name "default/something". `hg book --remote` would show it as "default/default/something". This is usually a mistake and we want to be able to add some basic gating to prevent it.
2016-01-19 20:58:30 +03:00
> echo "[extensions]" >> $HGRCPATH
remotenames: fix tests
2018-01-03 17:15:47 +03:00
> echo "remotenames=" >> $HGRCPATH
push: add possibility to prohibit pushing to certain bookmarks One of the goals is to prevent situations when users push to default/something where default is one of the paths (or a rename of one). Had we not prohibited this, hg push would ask user to run it with --create and later create a new remote bookmark with name "default/something". `hg book --remote` would show it as "default/default/something". This is usually a mistake and we want to be able to add some basic gating to prevent it.
2016-01-19 20:58:30 +03:00
> echo "[remotenames]" >> $HGRCPATH
> echo "rename.default = remote" >> $HGRCPATH
> echo "disallowedto = ^remote/" >> $HGRCPATH
Init the original "remote" repo
$ hg init orig
$ cd orig
$ echo something > something
$ hg ci -Am something
adding something
$ hg bookmark ababagalamaga
$ cd ..
Clone original repo
$ hg clone orig cloned
updating to branch default
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ cd cloned
$ echo somethingelse > something
$ hg ci -m somethingelse
Try to do the wrong push
$ hg push --to remote/ababagalamaga
pushing rev 71b4c8f22183 to destination $TESTTMP/orig bookmark remote/ababagalamaga
abort: this remote bookmark name is not allowed
(use another bookmark name)
[255]
Try to do the right push
$ hg push --to ababagalamaga
pushing rev 71b4c8f22183 to destination $TESTTMP/orig bookmark ababagalamaga
searching for changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 1 files
updating bookmark ababagalamaga
remotenames: do not crash if no bookmarks are passed to push discovery Summary: Today, there are cases where this function will be called but bookmarks will not have been populated. We will eliminate one of these paths next, but for safety, let's make sure we abort gracefully rather than with a stacktrace by referencing something that does not exist. Differential Revision: D7023172 fbshipit-source-id: 8e3b2afe9fe3b9d74d42aa5b947229418ec8c3ad
2018-02-20 14:09:32 +03:00
Set up an svn default push path and test behavior
$ hg paths --add default-push svn+ssh://nowhere/in/particular
$ hg push --to foo ../orig
remotenames: do not over-check for svn/git push targets Summary: Previously, if the user had an svn or git push target set up, we would bail from the normal push --to process even if the users were pushing to a different location. This is silly. Instead, let's only bail if the user is actually pushing to an svn or git destination repository. This bug was discovered while testing the updated svn-to-hg sync scripts. Differential Revision: D7023173 fbshipit-source-id: bec5e069bc043c2f73fb334bdaeb18a6fad93eef
2018-02-20 14:09:34 +03:00
pushing rev 71b4c8f22183 to destination ../orig bookmark foo
remotenames: do not crash if no bookmarks are passed to push discovery Summary: Today, there are cases where this function will be called but bookmarks will not have been populated. We will eliminate one of these paths next, but for safety, let's make sure we abort gracefully rather than with a stacktrace by referencing something that does not exist. Differential Revision: D7023172 fbshipit-source-id: 8e3b2afe9fe3b9d74d42aa5b947229418ec8c3ad
2018-02-20 14:09:32 +03:00
searching for changes
remotenames: do not over-check for svn/git push targets Summary: Previously, if the user had an svn or git push target set up, we would bail from the normal push --to process even if the users were pushing to a different location. This is silly. Instead, let's only bail if the user is actually pushing to an svn or git destination repository. This bug was discovered while testing the updated svn-to-hg sync scripts. Differential Revision: D7023173 fbshipit-source-id: bec5e069bc043c2f73fb334bdaeb18a6fad93eef
2018-02-20 14:09:34 +03:00
abort: not creating new remote bookmark
(use --create to create a new bookmark)
remotenames: do not crash if no bookmarks are passed to push discovery Summary: Today, there are cases where this function will be called but bookmarks will not have been populated. We will eliminate one of these paths next, but for safety, let's make sure we abort gracefully rather than with a stacktrace by referencing something that does not exist. Differential Revision: D7023172 fbshipit-source-id: 8e3b2afe9fe3b9d74d42aa5b947229418ec8c3ad
2018-02-20 14:09:32 +03:00
[255]
Reference in New Issue Copy Permalink