You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
git is case sensitive, check If there is a mismatch in the case, such as "Src" vs. "src", this can cause issues on case-insensitive file systems. Try cloning the repository fresh in a different location and check if the "Src" folder appears. You might have a git configuration issue where certain files are ignored. Check if there are any path-specific settings in your .git/config or global ~/.gitconfig files. If the folder does not appear locally, you can still remove it from the repo with the following Git command: git rm -r --cached Src– ArkoCommented Jan 10 at 8:34
-
I cloned the fresh repo and can see the "Src" folder only instead of the "src" folder but not both "Src" and "src" locally. but can see both "Src" and "src" on the azure repo. on the Azure repo, I want to keep the "src" folder and delete 'Src". Is it possible that earlier the folder was renamed? and then not remove and commit either folder to the Azure repo so that the old one "Src" remained there and then renamed the "src" folder is also there.– krunalCommented Jan 10 at 10:11
-
Since you can see both 'Src' and 'src' in Azure but only 'Src' locally, it suggests a case sensitivity issue. So you can see Src on azure repo right? If you don't need Src then remove it from portal itself. After removing 'Src' from Azure Repos, clone the repository anew on your local machine. This will ensure you have the latest version of the repository with only the 'src' folder. Check it once and let me know– ArkoCommented Jan 10 at 10:14
-
Post your local folder structure and what stack/language it is? So, we may also try doing the same activity to observe– Jashua CrissCommented Jan 10 at 15:30
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. python-3.x), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you