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.

Sign up for GitHub

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

Jump to bottom

Repositories are not registered in SCM providers when they are in subdirectory of another repo #570

Closed
pmosko opened this issue May 10, 2019 · 1 comment
Closed

Repositories are not registered in SCM providers when they are in subdirectory of another repo #570

pmosko opened this issue May 10, 2019 · 1 comment
Labels
released

Comments

@pmosko
Copy link

pmosko commented May 10, 2019

  • VSCode Version: 1.33.1
  • OS Version: Ubuntu 14.04
  • Extension Version: 1.48.2
  • System Language: English
  • SVN Version: 1.8.1

Issue

My working directory is trunk of repository. Inside I have more different SVN repositories, so something like that:

SVN_repo
├───code1
├───code2
├───SVN_repo2
│ └───code3
└───SVN_repo3

Note that these are not externals, just plain repos ignored by main repo

In Source Control Prodivers I have only one repo: SVN_repo
File view also recognize changes only in SVN_repo

In SVN tab there is also only main repo, but File history is working fine

I enabled searching for multiple repositories, but it does not seem to work when parent is also repository
edgardmessias added a commit to edgardmessias/svn-scm that referenced this issue May 28, 2019
@edgardmessias
feat: Allow to scan repository on ignored folders (close JohnstonCode…
bb30563 
…#570)
JohnstonCode added a commit that referenced this issue May 29, 2019
@JohnstonCode
chore(release): 1.49.0 [skip ci]
8621d6d 
# [1.49.0](v1.48.6...v1.49.0) (2019-05-29)

### Features

* Allow to scan repository on ignored folders (close [#570](#570)) ([#586](#586)) ([be7069d](be7069d))
@JohnstonCode
Copy link
Owner

🎉 This issue has been resolved in version 1.49.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
released
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JohnstonCode @pmosko