<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Source Control on Wingate365</title><link>https://blog.wingate365.com/tags/source-control/</link><description>Recent content in Source Control on Wingate365</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Sun, 19 Apr 2026 14:35:10 +0000</lastBuildDate><atom:link href="https://blog.wingate365.com/tags/source-control/index.xml" rel="self" type="application/rss+xml"/><item><title>Trying out GitHub Copilot Agent for a Functional Task?</title><link>https://blog.wingate365.com/2026/04/trying-out-github-copilot-agent-for.html</link><pubDate>Sun, 19 Apr 2026 14:35:00 +0000</pubDate><guid>https://blog.wingate365.com/2026/04/trying-out-github-copilot-agent-for.html</guid><description>&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;br /&gt;I've been using GitHub for a while https://github.com/andywingate but had never touched its agentic features. Working on the &lt;a href="https://nubimancy.com/"&gt;Nubimancy project&lt;/a&gt; gave me a good excuse. This is a practical breakdown of what I used, what it saved me, and where human judgement still mattered.&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Full context is in the&amp;nbsp;&lt;a href="https://nubimancy.com/2026/03/15/from-blueprint-to-build-validating-the-data-foundation/"&gt;Nubimancy project log&lt;/a&gt; - this post is about the tools and the approach.&lt;/p&gt;
&lt;h2&gt;The Task&lt;/h2&gt;
&lt;p&gt;Validate ~75 CSV schema files against Business Central master data import requirements. Check field names, required fields, data types, and format compatibility. Important, methodical, time-consuming if done manually. There are a number of extensions in the mix also on top of the standard BC tables. I gave it to a GitHub Copilot agent. Here's exactly what I did.&lt;/p&gt;</description></item><item><title>SVN / Subversion / Source Control</title><link>https://blog.wingate365.com/2013/07/snv-subversion-source-control.html</link><pubDate>Fri, 19 Jul 2013 19:38:00 +0000</pubDate><guid>https://blog.wingate365.com/2013/07/snv-subversion-source-control.html</guid><description>&lt;p&gt;Quick &amp;lsquo;what I did&amp;rsquo; to setup Subversion this week to deal with SSRS projects and reports.&lt;br /&gt;
&lt;br /&gt;
Installed the standard edition of VisualSVN Server&lt;br /&gt;
&lt;a href="http://www.visualsvn.com/server/download/?"&gt;&lt;a href="http://www.visualsvn.com/server/download/"&gt;http://www.visualsvn.com/server/download/&lt;/a&gt;&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Installed TortoiseSVN on users machines&lt;br /&gt;
&lt;a href="http://tortoisesvn.net/downloads.html"&gt;&lt;a href="http://tortoisesvn.net/downloads.html"&gt;http://tortoisesvn.net/downloads.html&lt;/a&gt;&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
The setup on the server was very easy, added users via the management interface, set the port and made sure the firewall was going to allow the connections. Created a couple of repos for the various project files.&lt;br /&gt;
&lt;br /&gt;
On local PC checked-out the repo folder to a local drive folder and added the project files, simply right click to commit the files to the repo - marking all the files to be added.&lt;br /&gt;
&lt;br /&gt;
Logging all the commits makes it very easy to roll back and check on what activity is going on. Clearly it makes sense to split out as best you can the different projects into . I did notice it&amp;rsquo;s worth it to un-version the user file that each project creates by default.&lt;br /&gt;
&lt;br /&gt;
Next thing to try is the VisualSVN plugin for visual studio which requires TortoiseSVN to work. And read the rest of the manual as TortoiseSVN politely recommends&amp;hellip;&lt;br /&gt;
&lt;br /&gt;
Edit: Now also added the Visual Studio plugin from VisualSVN, which is fantastic and very straight forward. Do all your commits, check the logs etc from within Visual Studio.&lt;/p&gt;</description></item></channel></rss>