Is there a way to show the list of file changes in Github Desktop as a tree instead of a flat file list?
It seems that that feature was present in v1 of Git for Desktop and it was removed in v2 of the app. There are posts asking for this in 2018 and we still don't have that functionality in 2020.
Source: https://github.com/desktop/desktop/issues/5468
Related
I'm currently developing wiki pages in TFS 2018 via Markdown. But as far as I know, there appears to be no way to create a link on a wiki page that opens within a new tab. All links created open in the existing tab. I read through the wiki documentation. I also reported it to be an official feature. But does anyone have any tricks or hacks I could implement in order to get that going for now?
Update
: I have tried basic html such as:
Google Link
But when I click save and view that link in Chrome Developer Tools, TFS 2018 is stripping out the target="_blank". Any possible reasons why TFS would do this?
Many thanks!
I tried now in Azure DevOps and it opens a new tab:
[Google](https://www.google.com)
Update:
It works only in Azure DevOps and not in TFS 2018.
We're using TFS 2015 Update 1 and have just noticed the 'welcome pages' feature. I've seen a few screenshots of this feature being used where a Team Project can have multiple .md files in it's root and they all appear in the left hand navigation off the welcome page. However, I don't seem to be able to get multiple menu items to appear, no matter how many .md files I add into the root of the Team Project.
Does anyone know if it's possible to do this?
thanks!
Unfortunately ，it doesn't currently work, the feature has been removed.
We have made some recent design changes, which reserved the left pane
for repository navigation for Git projects. We will be rolling out a
change soon to introduce a Table of Contents on the welcome page,
which will pick up other markdown files in your root directory.
In the meantime, a workaround is to provide a relative link to your
other file from README.md or use the Code Hub to view a tree of the
files.
Thanks, Yi-Wei Ang, Program Manager - Visual Studio Online
Source:Other .md files not appearing on welcome page
I’m beginning to consider moving an on-prem TFS 2012 installation to Visual Studio Online. So, one of the first things I started investigating was how we might export our content back out of VSO in the future if we ever decided we needed to. The more I’m looking, the less I’m finding. It seems there was a temporary time period when VSO first went GA that Microsoft offered that capability if you asked to have it done (http://www.visualstudio.com/en-us/news/2014-apr-3-vso.aspx). By implication, that would seem to mean that this isn’t something that is a planned feature of VSO.
Making a commitment to house all of my source and ALM data in a repository I’d effectively be barred from leaving doesn’t sound particularly appealing. Am I missing something, or does Microsoft really not have export capabilities on their VSO product roadmap? It would seem that this would be a show-stopper for many organizations from coming onto VSO, which is a perfect application to put into the cloud IMHO.
For code you can use Git. Even if you start with TFVC, you can use Git-TF. Clone with the --deep parameter to get the full history in a new Git repo, then push back to a new project (Git or TFVC).
For work items the TEAM tab in Microsoft Excel is a very capable export facility for work items, though you don't get links (other than parent child), or attachments.
In the original project, create a query that lists all your work items.
Open Excel, go to the TEAM tab and click 'New List', you should get the option to select your project and the query you just created.
In the Work Items tab select the 'Choose Columns' button and select all the columns you want to migrate.
If migrating to another TFS / VSO project, create that project, open another list in Excel connected to the new project.
Cut and paste all the work items from the original project list to the new project list (excluding the Id column).
Publish.
voilà.
You're right there's no good solution for this yet. However, if you're using Git as the source-control back-end (instead of TFVC), you can easily pull down the entire repo then push it up into any other source control server (non-VSO) with full history.
For TFVC source-control, or work items (or builds, test results, etc), things aren't so easy.
The answer is not black and white: with the TFS Client API you can connect to both platform and read/write as you please. It is not a trivial task, so someone has created tooling, like Brian says. Another option is using the open source TFS Integration Platform: it is complex but with some help you can do it.
What you really must consider and plan is the data model: moving from an ALM Platform to another is never trivial and the complexity lies in the difference of the underlying model and any customization you made.
As long as you do not customize you on-prem TFS, it is very doable, with a reasonable effort to move to VSO and back. In this context customize means: custom workitems fields, types or workflows, server-side plugins; shortly anything that requires code or schema change. Note that you can still customize builds as this is properly managed.
I expect to see more solutions arriving thanks to the new REST API, but it will take time before we see solid products.
So your original question has a positive answer (TFS on-prem -> VSO) using OpsHub, but know what you are doing and, as I write, it is practically a one way journey.
I am new in GitHub for Windows. I learn how to commit a single change.
But i don't understand how can i commit only a part of file.
On GitHub for Mac you can just select the line.
How can i do it on GitHub for Windows?
Update: January 2015, 14th: Partial commits in GitHub for Windows:
The newest release of GitHub for Windows supports selecting lines or blocks of changes when creating a commit. Simply click the desired lines in the gutter, create the commit, and leave the other changes for you to continue working on.
The GitHub post adds what I mentioned in my original answer below:
For people familiar with the command line, this change is similar to interactive staging using git add -i or git add -p.
(Original answer: Aug. 2013)
From GitHub for Windows, you can open the console, and type:
git add -p -- path/to/your/File
You will then be able to stage exactly what you want from that file.
git add --patch:
Interactively choose hunks of patch between the index and the work tree and add them to the index.
This gives the user a chance to review the difference before adding modified contents to the index.
I know I am a bit late on this thread. But I was facing an issue where the selected code block was not getting added when I click on the line I wanted to include in the commit. Just make sure you've disabled the Hide whitespace changes checkbox in the settings menu.
View History on an file in a branch show only changes since the branch. I need to go back further -- like how created the file in the first place. I've also tried Sidekicks, and it doesn't seem to show history from before the branch either.
Short of hunting down the file in the trunk manually, is there a way to view a file's history from the time it was added to now following the path in the branch?
You can upgrade to TFS 2010 for this support natively. The 2010 upgrade is well worth the time for many reasons, this being one of them.
I've used an addon TFS follow branch history the UI is a bit clunky but will get you what you're looking for. It only shows the branched history for a file but won't recurse to all files in a directory.